[Bug 753323] mpegts: add support for JPEG 2000 to mpegtsmux and tsdemux

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=753323

--- Comment #131 from Aaron Boxer <boxerab at gmail.com> ---
(In reply to Sebastian Dröge (slomo) from comment #130)
> (In reply to Aaron Boxer from comment #129)
> > (In reply to Sebastian Dröge (slomo) from comment #127)
> > > (In reply to Aaron Boxer from comment #124)
> > > 
> > > > > (In reply to Aaron Boxer from comment #120)
> > > > > 
> > > > > > > Is a fixed framerate required, or can it be 0/1 or 0/0?
> > > > 
> > > > From what I can see, frame rate is fixed, so 0/0 is not allowed. Also,
> > > > frame rate of 0 is not allowed according to spec, so 0/1 also not allowed.
> > > 
> > > So you need to require a framerate in the caps, and it must be higher than
> > > 0/1. And this also makes it required that the input is actually fixed
> > > framerate.
> > > 
> > > Seems like a weird requirement for MPEG-TS... are you sure about that? Or
> > > maybe the framerate is only an indication, not necessarily to be correct?
> > 
> > No, not sure. Since timecode box is mandatory, doesn't this rule out
> > variable frame rate?
> 
> Question is if the timecode box could contain all-zeroes for example. But
> yes, if actual timecodes are required...
> 
> This seems very unlike MPEG-TS though, fixed-framerate that is.


>From the spec for time code:

------------------------------------------------------------------------------
Time code box (required)

This parameter is a 4-byte unsigned integer field which specifies the Hour (HH:
0-23),
Minutes (MM: 0-59), Seconds (SS: 0-59) and Frame Count (FF: 1-60). The HH, MM,
SS,
and FF fields are individual bytes packed contiguously
-----------------------------------------------------------------------------


So, it looks like this box cannot be all zeros.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.