[Matroska-devel] Opus in Matroksa Cont.

Frank Galligan frankgalligan at gmail.com
Fri May 24 23:06:31 CEST 2013

I think making a big backwards-incompatible change is fine, at some point.
I just don't think trying to accurately represent how the
encoders/muxers currently handle codec delay and padding, warrants that
kind of change.

On Fri, May 24, 2013 at 1:53 PM, Moritz Bunkus <moritz at bunkus.org> wrote:

> Hey,
> > Maybe muxers should only allow a non 1.0f TrackTimecodeScale when a
> newer Matroska version (4) is forced ?
> > And for the EBMLReadVersion to 4 as well.
> one more thing. Introducing changes that require bumping EBML
> ReadVersion up to 4 (or even higher) are pretty much guaranteed to
> make any and all files unreadable by all of today's players (unless
> they completely ignore that field which, in turn, would also be a
> pretty bad violation and a source for serious playback issues).
> So are we back to backwards-incompatible changes? Then let's do it
> right and throw out the timecode-based "raw timecodes" and be done
> with it...
> Kind regards,
> mosu
> _______________________________________________
> Matroska-devel mailing list
> Matroska-devel at lists.matroska.org
> http://lists.matroska.org/cgi-bin/mailman/listinfo/matroska-devel
> Read Matroska-Devel on GMane:
> http://dir.gmane.org/gmane.comp.multimedia.matroska.devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.matroska.org/pipermail/matroska-devel/attachments/20130524/03fd701d/attachment.html>

More information about the Matroska-devel mailing list