[NUT-devel] NUT samples / NUT muxer?

[Måns Rullgård]

Oded Shimon said:
> On Mon, Mar 27, 2006 at 08:58:22AM +0100, M??ns Rullg??rd wrote:
>>
>> Oded Shimon said:
>> > On Mon, Mar 27, 2006 at 08:06:46AM +0100, M?ns Rullg?rd wrote:
>> >> Rich Felker <dalias at aerifal.cx> writes:
>> >>
>> >> > On Sun, Mar 26, 2006 at 11:57:48PM +0100, M?ns Rullg?rd wrote:
>> >> >> Hi all,
>> >> >>
>> >> >> I thought it would be a good test of the NUT spec to see if I, not
>> >> >> having followed the design discussions at all, could implement a
>> >> >> demuxer (and later a muxer) only reading the spec.  To test whether I
>> >> >> got it right, I'd need some samples or a way of creating some.  The
>> >> >> muxer in the libnut repo tells me it creates broken files, and the
>> >> >> lavf implementation is badly outdated.  Is there anything that does
>> >> >> create proper NUT files?
>> >> >
>> >> > The muxer in the libnut repo is correct, to the best of our knowledge.
>> >
>> > Speaking of which, that's why it would be good if ffnut was synced, so we
>> > can check that libnut is nicely compliant...
>>
>> As I said, I started implementing a (de)muxer from scratch.
>
> Ah, yes, it's even still quoted in this mail. :) BTW, you should read:
> http://wiki.multimedia.cx/index.php?title=NUT
>
> It has a detailed explanation for keyframe exact seeking in NUT...

One step at a time ;-)

> Your de/muxer from scratch is gonna be in lavf?..

If it works...

>> >> OK, so what's with this:
>> >>
>> >> $ ./nutmerge
>> >> ==============================================================
>> >> PLEASE NOTE THAT NUTMERGE FOR NOW CREATES _INVALID_ NUT FILES.
>> >> DO NOT USE THESE FILES FOR ANYTHING BUT TESTING LIBNUT.
>> >> ==============================================================
>> >> bleh, more params you fool...
>> >
>> > read README
>>
>> I did:
>> DO NOT USE NUTMERGE FOR _ANYTHING_ EXCEPT TESTING!!
>> IT CREATES COMPLETELY INVALID BROKEN FILES, WHICH JUST "HAPPEN" TO WORK!
>>
>> So you're saying the files are OK after all, at least for some inputs?
>
> Well, in a very hackish way, nutmerge actually DOES generate valid files in
> the case of MPEG-4 ASP with vbr MP3 in AVI, and Vorbis in Ogg. But it's
> bad hack and could easily fail in some cases. (like, doesn't handle zero
> byte frames from mencoder)

So if I take a regular Ogg/Vorbis file as produced by libogg or an AVI with
with no tricks from lavf it should work?

-- 
Måns Rullgård
mru at inprovide.com