Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Linford Bacon <linford.bacon@ngenius.ai>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] Consulting Engagement Request
Date: Thu, 17 Feb 2022 10:38:30 +0000
Message-ID: <LO2P123MB4748E5B116DE372DDAF3CB878A369@LO2P123MB4748.GBRP123.PROD.OUTLOOK.COM> (raw)

Hi All,

My name is Linford and I run a small startup based in the UK that is using machine vision to automate traffic surveys .

We are making extensive use of the ffmpeg library to consume and pre-process footage from network connected CCTV cameras.

I was wondering whether anyone would be interested in a consulting engagement to assist us with some development and/or debugging of the ffmpeg pipeline.

Initially, we are looking for some targeted support to optimise our use of the ffmpeg library but there could also be additional work to create custom components/filters and to improve the library integration into our pipeline.

Let me know if you would be interested in this and I can setup a call.

Best wishes,

Linford


Linford Bacon
CEO & Co-founder | ngenius.ai
Mob: (44) 7387 235 026
The Enterprise Centre, Norwich Research Park, UEA, Norwich, NR4 7TJ

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

                 reply	other threads:[~2022-02-17 10:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=LO2P123MB4748E5B116DE372DDAF3CB878A369@LO2P123MB4748.GBRP123.PROD.OUTLOOK.COM \
    --to=linford.bacon@ngenius.ai \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git