[FFmpeg-devel] A53 Closed Captions in mpeg2video

Hi, What is the current status of closed captions for mpeg2 video outputs? I know caption pass through is supposed to work for libx264, but most ATSC broadcast is still in mpeg2. Do we have any timeline on when this part will be done yet? Zach ___ ffm

Re: [FFmpeg-devel] UDP constant bitrate feature (cbr)

ecause the transmission rate would change with each pcr. This would also reduce network storms induced by the heavy packet flow of bursty multicast streams. Zach On Thu, Nov 19, 2015 at 8:32 AM, Kieran Kunhya wrote: > On 19 November 2015 at 16:15, Zach Swena > wrote: > >> How have yo

Re: [FFmpeg-devel] UDP constant bitrate feature (cbr)

> How have you confirmed MPEG-TS compliance? While not completely definitive, I looked at it with a transport stream analyser and tested it at our TV station. At the TV station stream the file from our server through a remultiplexer that assembles the multi program transport stream with our vario

Re: [FFmpeg-devel] UDP constant bitrate feature (cbr)

> A proper ts remuxer is quite a different beast to what FFmpeg is > designed to do. As much as people try it can't be hacked into the > FFmpeg paradigm which is largely based around converting static files > of fixed codecs/resolutions in a nonrealtime environment from A to B. Why is there a udp

Re: [FFmpeg-devel] UDP constant bitrate feature (cbr)

, Nov 18, 2015 at 2:38 PM, Kieran Kunhya wrote: > On 18 November 2015 at 19:28, Zach Swena > wrote: > > Are you referring to this seperate applciation? > > > > https://github.com/mmalecki/multicat/blob/master/trunk/README > > > > While using that makes sense

Re: [FFmpeg-devel] UDP constant bitrate feature (cbr)

Just because an external applciation can fix the problem in some instances doesn't mean it isn't a problem in the first place. Zach On Wed, Nov 18, 2015 at 11:14 AM, Zach Swena wrote: > > Only for strict CBR streams which FFmpeg cannot know a priori. That's > > why the

Re: [FFmpeg-devel] UDP constant bitrate feature (cbr)

ion? Smooth output streams are needed in other applications then just relaying a stream. Why can't I find the term multicat in any of the code or documentation? Zach On Wed, Nov 18, 2015 at 10:37 AM, Zach Swena wrote: > Yea, how it is supposed to happen isn't complicated. To be

Re: [FFmpeg-devel] UDP constant bitrate feature (cbr)

n use FFmpeg. Zach On Wed, Nov 18, 2015 at 9:03 AM, Michael Niedermayer wrote: > On Tue, Nov 17, 2015 at 03:06:27PM -0800, Zach Swena wrote: > > Hi Pavel, > > > > I can confirm that there is a problem with the UDP packet engine in > > FFmpeg. FFmpeg has excessive jitter

Re: [FFmpeg-devel] UDP constant bitrate feature (cbr)

Hi Pavel, I can confirm that there is a problem with the UDP packet engine in FFmpeg. FFmpeg has excessive jitter in it's UDP streaming output to the point where hardware decoders can't handle it. My solution was to buffer to disk and have my own program read and send the datagrams via a very ti

[FFmpeg-devel] Overlay documentation does not mention pixel aspect ratio.

Hi, I would like to propose a change to the documentation for the overlay filter. The overlay filter does not detect pixel aspect ratio. This causes improper display resolution when overlaying smaller images on a larger image. A common example of this would be overlaying an SD source on an HD o

Re: [FFmpeg-devel] Default dynamic range compression on AC3

, 2015 7:51 AM, "Wiebe Cazemier" wrote: > > - Original Message - > > From: "Zach Swena" > > To: "FFmpeg development discussions and patches" < ffmpeg-devel@ffmpeg.org> > > Sent: Thursday, 26 March, 2015 3:34:22 PM > > Su

Re: [FFmpeg-devel] Default dynamic range compression on AC3

Something to keep in mind, AC3 is a broadcast format, so it makes sense to have range compression built in because many listeners are viewing on TV sets with limited range capabilities. I wasn't aware of this option, but will probably end up using it for a program I am making. I don't care about

Re: [FFmpeg-devel] Dshow Crossbar support

quot;Roger Pack" wrote: > On Wed, Nov 19, 2014 at 3:03 PM, Zach Swena > wrote: > > > Hi, > > > > Can anyone elaborate on why direct show devices that use crossbar are not > > supported by FFmpeg? Also, what is keeping someone from taking the > >

[FFmpeg-devel] Ticket #2547

Hi, What is the status of work on Ticket #2547 and the associated patch ? I am still running in to an issue with "dts < pcr, TS is invalid" under va

[FFmpeg-devel] Dshow Crossbar support

Hi, Can anyone elaborate on why direct show devices that use crossbar are not supported by FFmpeg? Also, what is keeping someone from taking the crossbar support found in VLC and porting it to FFmpeg, assuming the said port complied with the FFmpeg code conventions? The current work around seems

Re: [FFmpeg-devel] Patch mpegts_start_pid to allow ATSC PID ranges

iedermayer" wrote: > On Tue, Nov 18, 2014 at 01:56:21PM -0800, Zach Swena wrote: > > Sorry, I am new to using Git. I have a .patch file, but I am not sure > what > > the proper way to send it is. I am using GitHub for windows. Anyway, > the > > .patch file is att

Re: [FFmpeg-devel] Patch mpegts_start_pid to allow ATSC PID ranges

Sorry, I am new to using Git. I have a .patch file, but I am not sure what the proper way to send it is. I am using GitHub for windows. Anyway, the .patch file is attached. Zach On Tue, Nov 18, 2014 at 10:33 AM, Timothy Gu wrote: > Hi, > > On Tue, Nov 18, 2014 at 9:02 AM, Z

[FFmpeg-devel] Patch mpegts_start_pid to allow ATSC PID ranges

Hi, Here is a patch to allow FFmpeg to use PID ranges compatible with ATSC television. I based the new minimum value on the PID ranges here on wikipedia. This should be sufficient to allow the use of any standard PID used in ATSC television. Z