similar to: The one thread to solve problems in the Vorbis documentation

Hi, I need another clarification regarding the standard. In floor0 header decode (setup), the point no.7 says that if any of [floor0_order], [floor0_rate], [floor0_bark_map_size], floor0_amplitude_bits], [floor0_amplitude_offset] or [floor0_number_of_books] are less than zero, the stream is not decodable But as we see, all those values are read as unsigned integers. Now I'm not able to

Hi ! <p>I previously posted a mail in the vorbis-dev mailing list because I'm trying to implement a vorbis decoder in java from scratch in my sparetime and have some questions about the bitstream spec. As I did not get any replies, I got kinda dissapointed and demotivated - But now.... I'm trying to take my chances here. :-) I'm NOT a newbie to source coding (I successfully

Hello, It seems there is an error in the algorithm for floor0 decode in section 6.2.2 of the Vorbis specification. Here's the relevant part: 3 3) [coefficients] is an empty, zero length vector 4 4) [booknumber] = read an unsigned integer of ilog( [floor0_number_of_books] ) bits 5 5) if ( [booknumber] is greater than the highest number decode codebook ) then

Hello I'm working on a fix-point decoder for AOS/Bluebottle - the proprietary OS of ETH Zurich. I've some problems with Floor0-curve-computation: I don't know what the little omega [cos(w)] stands for, line 3 of the official Vorbis documentation. Does anybody knows what this value means? I've tried to get the answer from the jOrbis and Tremor, but both seem to do - among

Hi there ! I'm kinda "yet another guy who tries to implement a vorbis decoder from scratch only by using the vorbis spec". (pure Java, OO-style) (I downloaded the long-awaited-all-in-one-PDF) The data structures are quite ready, I can successfully load the codec setup packet and all its components it's containing. <p><p>So far so good.... Here's my first note

Here is my situation: I have large Speex encoded stream which I would like to playback on wave out device. I could decode whole stream to pcm and play it back as pcm audio, but this is not what I want. Instead I want to decode minimum decodable bits (bytes?) to pcm and play it ... then decode another minimum data chunk and play it, etc. This way I can achieve closest to real-time playback or

hi here some questions about the md5 checksum: - what happens when the md5 checksum of the decoded audio is different of the internally stored checksum due to file corruption ? Will playing/decoding still be possible (with some error frames) or will playing /decoding be not possible at all (so all audio data is lost)? - what happens when the metadata blocks get corrupt? will the audio part

Hi All, Can any one link me or send me a complete detailed spec of Vorbis encoder? I found the Vorbis_I_spec.pdf but it does not provide much information about encoding procedure. Ravi -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/vorbis/attachments/20050829/cf209e5a/attachment.html

Is there an obvious safe way to add some extra data to a flac file that spec decoders will happily ignore? I'd like to explore creating a tool which will add N extra redundancy frames at the end which will allow perfect decoding with up to ~N frames lost in the files. This would allow users to sacrifice a tiny amount of compression for a substantial increase in file robustness. This would

Hi I have downloaded a FLAC file somewhere and when trying to decode it to WAV it gives the error message: ERROR, MD5 signature mismatch So my question is now: are FLAC files that give the error message above still decodable to WAV (and how can you do this, because flac.exe doesn't want to decode the file), even if there is a MD5 signature mismatch, or is this not possible at all? thx

Hi, I'm the current developer of Xapian-Haystack, and I'm glad to announce that we've been finally able to install and pass all the tests of Xapian-Haystack with Xapian 1.3.3 in both Python 2 and 3, which means that Xapian-Haystack now supports Python 3. This naturally would not be possible without your efforts to push Xapian bindings to Python 3, and I thank you for that. Here I

--- Harry Sack <tranzedude@gmail.com> wrote: > 2007/7/25, Harry Sack <tranzedude@gmail.com>: > > > > Hi > > > > I have downloaded a FLAC file somewhere and when trying to decode > it to > > WAV it gives the error message: ERROR, MD5 signature mismatch > > So my question is now: are FLAC files that give the error message > above > >

Hi all, something which came up recently in relation to the design of Kate's granulepos was whether or not the granulepos of successive Ogg pages is allowed to be the same, ie. whether or not granulepos must be strictly increasing. As this question is more generally about Ogg granulepos, how about we answer it first and then get back to the discussion of Kate's granulepos ... Here is

> speex and flac have an "extra headers" field in the bos page, and > skeleton also has a field for recording the total number of headers > (as it's kinda important for editing files). If you know how many > headers there are going to be at the start of encoding, then adding a > field like that might be enough. I do know at start, and I have such a field too. However,

Using Trader's Little Helper 2.4.1.160 when testing some 16/96 FLAC files I run into the following error: "file is decodable without error, but flac fingerprint cannot be checked since it was unset in the streaminfo block." Is there an automatic checksum verification when testing/decoding? Is there any way to fix this, i.e. get rid of the error? Martin

Hi, I'm the main author of Speex (http://speex.sourceforge.net), an open-source speech codec that uses Ogg for file storage. I'd like to have feedback on the way we store Speex data in Ogg files to make sure we do the right thing. The Speex documentation can be found at http://speex.sourceforge.net/manual/ but here's the part about Ogg: <p><p>Speex bit-streams can be

Jean-Marc, What exactly does the speex code do to calculate the granulepos? With vorbis it's the 'count of decodable samples including this packet'. So if you had a packet that allowed you to decode 1024 samples since the beginning of playback, the granulepos is 1024, not for example 1023 which would be the *index* of the last sample assuming C-style array indicies starting at

2007/10/19, Josh Coalson <xflac@yahoo.com>: > > --- Harry Sack <tranzedude@gmail.com> wrote: > > hi > > > > here some questions about the md5 checksum: > > > > - what happens when the md5 checksum of the decoded audio is > > different > > of the internally stored checksum due to file corruption ? Will > > playing/decoding still be

I'm hoping this is a new proposal, and not a rehash of something that's already been discussed and shot down. Without logs of the recent IRC discussion there's no way for me to know without asking. When I suggested it in #theora earlier derf_ or AndrewBachmann said that it had already been discussed, so I'm under the belief that this is a new idea. <p>Ok so we've

We are working on OggVorbis encoder. In the porting effort we are trying to convert it to fixed point code (both 32 and 24 bit fixed point). Now the issue is how we do the testing. What should be the criteria for our testing. Does anybody has any idea how compliance testing (i.e. some objective tests) is done at encoder side? What is the criteria of testing at the encoder side? If anybody