similar to: Stream integrity ?

After accidentally ogginfo-ing a WAV file, I'm wondering if there's any reason I shouldn't commit my fix that breaks out of the current file test if header integrity fails. Is there any case where the header integrity will fail but there is still any useful information to get out of the stream? I don't think so... -- Kenneth Arnold <ken@arnoldnet.net> - "Know

>> Running ogginfo on the stream data gives: >> stream_integrity=fail >This line in the ogginfo output concerns me. It means that there are actually >damaged Ogg packets in the stream. How are you saving this stream to disk? This particular one was obtained with wget on OpenBSD. I've observed the same problem with files saved from Winamp. >I think there is a problem

I hope that this is the appropriate venue for this question. If it's not, let me know and I'll take it elsewhere (perhaps vorbis-dev). Saved streams are great - it lets this norteamericano get his fill of BBC Radio 1's Essential Mix. Unfortunately, saved streams aren't seekable. Running ogginfo on the stream data gives: erial=1626603590 header_integrity=pass vendor=Xiphophorus

I hope that this is the appropriate venue for this question. If it's not, let me know and I'll take it elsewhere (perhaps vorbis-dev). Saved streams are great - it lets this norteamericano get his fill of BBC Radio 1's Essential Mix. Unfortunately, saved streams aren't seekable. Running ogginfo on the stream data gives: erial=1626603590 header_integrity=pass vendor=Xiphophorus

>>I realize that I may have unintentionally been misleading you by leaving some information out. That error report from ogginfo keeps going, repeating the same 3 errors (as above) over and over again. It ends after a stream_truncated=true, not giving a final header_integrity=fail. (Perhaps because there's not another packet?) Then it reports a total playtime of 0. > >Yes,

Hello everyone, ff123 compiled Monty's branch of the RC1 encoder, see his post on r3mix.net forum: http://66.96.216.160/cgi-bin/YaBB.pl?board=c&action=display&num=994299736&start=30 Anyway it only supports ~128kbps mode, so I did a quick listening test with some files that bugged vorbis beta4. grace.wav - the right channel is still a bit watery, and I think this can be seen

I noticed that clipping occurs in lossy audio compression even if there is no clipping in the original file (though the original file has peaks that are just below the maximum). I know that this happens due to all the filtering involved during compression, but I'm wondering just how audible this clipping is because I don't hear anything wrong. I mean, as things are now, is it safe to say

Check this clip (it's small, 373kb) http://www.geocities.com/jdxss/udialwav.zip It left oggenc, lame and MP+ encoders choking in dust. -- Vorbis Xtreme | http://solair.eunet.yu/~aldov/ Ogg Vorbis is the free, open source alternative to MP3 --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a

Comments? ---------------------------------------- "Mark Taylor" <mt@sulaco.org> wrote: [...] > This is related to one minor objection I have to vector quantization > based codecs like Vorbis and the MPEG4 VQ codec: they do not compute > the quantization noise during the encoding process. The choice of > codebooks (use a big codebook: low quantization noise, use a

Hi. Since I'm new to this mailing list, I don't know whether this was discussed in this mailing list, or if it is already fixed. Anyway, the problem is that all audio encoders out there add a small amount of silence to the start/end of the encoded file. This is usually a small amount, around 0.03 seconds. Most of the time it goes unnoticed, BUT when you have tracks that flow into one

Monkey's Audio lossless compressor (currently win32 only, free but not open-source except decoder) author is thinking to implement a kind of audiophile-quality lossy compression which would filter "noise bits" that are hard to encode lossless but which are (or should be) inaudible and thus improve lossless compression (avg. 300-450kbps). I think that implementing something like this

I have a CD ripped with RC2, ogginfo from 1.0 claims they are all "broken". ogg123 also goes a little wild with them. I'll experiment a little more, maybe play with xmms, etc. RC3's ogginfo do not see anything wrong with them... an example: ---------- ogginfo 1.0 New logical stream (#1, serial: 2aab0567): type vorbis Vorbis headers parsed for stream 1, information follows...

---- "Aleksandar Dovnikovic" <aldov@EUnet.yu> wrote: > I think that AAC wasn't developed to be used as 'another' > MP3, it's usage is focused towards companies that sell audio > over the internet, for portable players, satellite communications... A-ha! That explains a lot. There used to be a project called FAAC but I presume it's gone. After seeing

I was doing some testing with RC2 and I noticed that RC2 doesn't encode past 19kHz with this clip (-b256 and -b350). There are no problems with this clip like it was before, but this clip contains signal past 19kHz which is audible as a faint high-frequency hiss - and that hiss is gone in the encoded file since RC2 cuts off at 19kHz. I think that -b256 and -b350 should encode at least up to

I couldn't catch Monty on IRC, so I'll ask here... how's RC3 coming along? Can we expect RC3 anytime soon, and what are the main improvements over RC2? -- Vorbis Xtreme | http://solair.eunet.yu/~aldov/ Ogg Vorbis - free, open source audio __________________________________________________ Do You Yahoo!? Listen to your Yahoo! Mail messages from any phone. http://phone.yahoo.com ---

Check this out: http://7amnews.com/2001/features/032101.shtml Greetings, Aleksandar --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list

Hi. Winamp version 3.0 has been announced. There will be no public beta and final version is expected for Christmas. Winamp 3.0 will be completely re-written version, but current plug-ins and skins (for winamp 2.x) will NOT be compatible with Winamp 3 (though this will be addressed in later winamp 3 versions). More info: http://www.winamp.com/nsdn/winamp3x/ Anyway, the reason I'm sending

Hi, there. Although I'm not a hacker at all, I noticed an audible noise on Beta 4 encoded files. So, I'd like to report it here. I ripped and encoded 'A Day Without Rain' on the album with the same name By Enya into Vorbis using Oggenc and Oggdrop Beta 4 from the Vorbis site. (You know, she is quite an encoder-killer.) At all the bitrates, files encoded by Oggdrop had audible

In case you missed it, RC2 is on slashdot.org too: http://slashdot.org/article.pl?sid=01/08/13/1811241 BTW Gian-Carlo Pascutto wrote on /. that RC3 should appear very soon (in a week or so)? Also, it looks like Wall Street Journal article is not available on-line (at least to non-registered persons). If someone is registered or have a paper edition, please post this article somewhere so that we

During the interesting interview that binaryfreedom has made with Monty and Jack, Monty mentions cascading, a feature that will be added, quote: "Cascading is the ability to make multiple passes through the frequency spectrum, iteratively filling in more detail, like a progressive jpeg". What are the advantages of something like this - does this generally improves quality or is it used