Re: Info/Xing tag: Should a decoder insist on zeroes after header?
robert <[email protected]>
| Newsgroups | gmane.comp.audio.mp3.lame |
|---|---|
| Organization | The LAME Open Source MP3 Encoder Project |
| Message-ID | <[email protected]> |
Hello Thomas! Am 10.03.2015, 08:10 Uhr, schrieb Thomas Orgis <[email protected]>: > Am Thu, 26 Feb 2015 09:37:21 +0100 > schrieb Thomas Orgis <[email protected]>: > >> Hints? Any reason there should be something else than zeroes between >> header/crc an "Xing" or "Info"? So far, this is the one and only file >> reported with that. Other decoders than mpg123 parse the frame without >> complaint, though. > > No takers? Is there someonHee specific I should talk to regarding the > design of the Xing/Info frame? To my own understanding Xing/Info tags are only valid in silent frames. If the user really was able to let LAME write it into a none-silent frame, I would be curious to know how he did it, cos that would be a bug in LAME. The problem with decoding the following frame was due to the back pointer pointing into the Xing/Info data? > > 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/