Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Development opportunity: LTC noise on files created from videotape source: filter idea
Date: Mon, 18 Jul 2022 19:36:43 +0200
Message-ID: <CAPYw7P6cqEDi0ui2xTn+YmKVeGNfUZRGi2BmM645jCpD=noWiQ@mail.gmail.com> (raw)
In-Reply-To: <20220718171412.GS2088045@pb2>

On Mon, Jul 18, 2022 at 7:14 PM Michael Niedermayer <michael@niedermayer.cc>
wrote:

> On Mon, Jul 18, 2022 at 09:53:14AM +0000, Stephen McConnachie wrote:
> > Hi FFMPEG developers,
> >
> > I have a proposal for a paid development opportunity to add a filter to
> FFMPEG.
> >
> > I followed the advice on the FFMPEG Consulting page at
> https://ffmpeg.org/consulting.html and am emailing this list to try to
> identify if any of the FFMPEG developers may be able to take on a
> development commission.
> >
> > Background: we are digitising high volumes of videotape carriers, and
> have identified a common case in some videotape formats where Linear Time
> Code from the tape carrier is present on audio stream 1 in the encoded file
> - manifesting as a continuous noise.
> >
> > Idea: could a filter be developed in FFMPEG, based on example files we
> can provide, to identify the presence of an LTC-derived audio stream, and
> additionally identify which of the streams is the LTC stream.
> >
> > If this filter idea sounds achievable, I would aim to identify which of
> the FFMPEG developers may be able to take on this work, and estimated costs
> and timeline.
>
> It should be possible to implement a LTC decoder that turns a audio track
> into
> LTC binary data. If that succeeded and the data is valid then teh track
> would
> very likely have contained LTC.
>
> Do i understand correctly that the tracks are LTC or normal audio not
> mixed?
> or are there tracks that mix audio and LTC and require seperation ?
>
> I think there are several developers who could develop such filter.
> I could do it, Iam sure paul could do as well.
>

Perhaps it there are clear specifications I could.


>
> thx
>
> [...]
>
> --
> Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> "I am not trying to be anyone's saviour, I'm trying to think about the
>  future and not be sad" - Elon Musk
>
> _______________________________________________
> 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".
>
_______________________________________________
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-07-18 17:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18  9:53 Stephen McConnachie
2022-07-18 17:14 ` Michael Niedermayer
2022-07-18 17:36   ` Paul B Mahol [this message]
2022-07-19  7:06   ` Stephen McConnachie

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='CAPYw7P6cqEDi0ui2xTn+YmKVeGNfUZRGi2BmM645jCpD=noWiQ@mail.gmail.com' \
    --to=onemda@gmail.com \
    --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