[NUT-devel] NUT samples / NUT muxer?

[Måns Rullgård]

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.

>> 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?

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