Re: Info/Xing tag: Should a decoder insist on zeroes after header?

Am 11.03.2015, 10:20 Uhr, schrieb Thomas Orgis <[email protected]>:

> At least you confirm that it is not expected that LAME wrote the frame
> like that, right? So perhaps it's really just garbage. So, I'd think
> the decoder is right in being suspicious and refusing to use the frame.
> But the user says "Everything works when you use that info, why do you
> want to cripple the features (gapless decoding, fast seeking) of the
> decoder?"

I can't rule out that LAME isn't at fault there. Maybe there is/was a
bug in LAME, but it isn't normal behaviour.

> Well, I guess one has to look at that data to see if it might be some
> information added by a third-party tool. But I got only one report
> about a single file so far …

I have no experience with tools that fix missing LAME/Info headers.
Eventually there is some tool out there putting it just into the
first frames ancillary data section?

Well, if you got that file, put it aside and ignore it for now.

> Alrighty then,
>
> Thomas

Ciao Robert

-- 
There is an art, it says, or rather, a knack to flying. The knack lies in  
learning how to throw yourself at the ground and miss. Pick a nice day,  
[The Hitchhiker's Guide to the Galaxy] suggests, and try it.

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Lame-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lame-dev