Help - Search - Members - Calendar
Full Version: Program to analyze ogg files?
Hydrogenaudio Forums > Lossy Audio Compression > Ogg Vorbis > Ogg Vorbis - General
McGee
The title pretty much says it all. Is there a program I can use to analyze ogg files to see how they were encoded and to make sure they're ok? I didn't see anything here, at vorbis.com, or at RareWares.
Garf
Since there really is only 1 encoder, that isn't really necessary. By looking at the vendor tag of an ogg file in any player, you can see the used Vorbis version, e.g. Xiph.Org libVorbis I 20020717 which is Vorbis 1.0

All GT versions also identify themselves in that way.
spoon
dBpowerAMP Music Converter will tell you which bitrate (vbr cbr) and the version of the library used.
fenterbug
What are you needing that ogginfo.exe doesn't offer? It's part of the vorbis-tools pack downloadable from www.vorbis.com. Here's my output from it:
CODE
Processing file "[01]_Papercut.ogg"...

New logical stream (#1, serial: 00001796): type vorbis
Vorbis headers parsed for stream 1, information follows...
Version: 0
Vendor: Xiph.Org libVorbis I 20020717 (1.0)
Channels: 2
Rate: 44100

Nominal bitrate: 192.003000 kb/s
Upper bitrate: 0.000000 kb/s
Lower bitrate: 0.000000 kb/s
User comments section follows...
TITLE=Papercut
ARTIST=Linkin Park
GENRE=Rock
DATE=2000-10-24
ALBUM=Hybrid Theory
TRACKNUMBER=1
REPLAYGAIN_TRACK_GAIN=-9.9100 dB
REPLAYGAIN_TRACK_PEAK=1.1121
REPLAYGAIN_ALBUM_GAIN=-10.2800 dB
REPLAYGAIN_ALBUM_PEAK=1.1452
Vorbis stream 1:
Total data length: 4318354 bytes
Playback length: 3m:04s
Average bitrate: 187.036194 kbps
Logical stream 1 ended
Xenion
i think you don't have to analyse them because the information is already stored in the files. so you just have to read it out which every player can

eg winamp
Length : 4:38
Average bitrate : 184 kbps
File size : 6,432,185 bytes
Nominal bitrate : 192 kbps
Channels : 2
Sampling rate: 44100 Hz
Serial number: 29355
Version : 0
Vendor :
Xiph.Org libVorbis I 20020717

what else do you need ?
smok3
QUOTE(Garf @ Jan 28 2003 - 08:39 AM)
All GT versions also identify themselves in that way.

why not using your own ident? (like libvorbisGT3 or something)
Garf
QUOTE(smok3 @ Jan 28 2003 - 05:18 PM)
QUOTE(Garf @ Jan 28 2003 - 08:39 AM)
All GT versions also identify themselves in that way.

why not using your own ident? (like libvorbisGT3 or something)

Maybe I didn't explain very well. This is how GT3 identifies itself.

Xiph.Org/Sjeng.Org libVorbis I 20020717 (GTune 3, beta 1)

Since it's based on the reference libVorbis I library of 2002-7-17, it makes sense to have that in the version string.
minix
QUOTE(McGee @ Jan 28 2003 - 06:18 AM)
Is there a program I can use to analyze ogg files to make sure they're ok?

I have the same question.
What happens if the data stream is corrupted, for example, when downloading from internet?
A lot of MP3 files that I download from internet are corrupted (defective frames), and I'd like to know if there's a way to check that with ogg files.
Peter Harris
QUOTE(minix @ Jan 28 2003 - 03:54 PM)
What happens if the data stream is corrupted, for example, when downloading from internet?

"ogginfo" scans the whole file and will tell you if it is damaged.
minix
Thanks.
I've downloaded a dozen of ogg files, and half of them seem corrupted.

An example:
CODE
Warning: sequence number gap in stream 1. Got page 270 when expecting page 269. Indicates missing data.
Vorbis stream 1:
Total data length: 1137157 bytes
Playback length: 0m:48s
Average bitrate: 189,315816 kbps
Logical stream 1 ended
Warning: Hole in data found at approximate offset 1143000 bytes. Corrupted ogg.


All corrupted files have a hole in an offset position bigger than the data length. Is this possible? (I guess that file is also bigger than data length because of header, but I don't know...)

The worst example I found:
CODE
Warning: Hole in data found at approximate offset 4176000 bytes. Corrupted ogg.
Warning: sequence number gap in stream 1. Got page 980 when expecting page 979. Indicates missing data.
Warning: Hole in data found at approximate offset 12552387 bytes. Corrupted ogg.
Warning: EOS not set on stream 1
Vorbis stream 1:
Total data length: 12542809 bytes
Playback length: 9m:21s
Average bitrate: 178,559214 kbps


Is it normal then those errors at the end of file always?
Is there an easy way to know errors position in time format?
Any graphical front end for ogginfo?
Peter Harris
QUOTE(minix @ Jan 28 2003 - 05:16 PM)
Thanks.
I've downloaded a dozen of ogg files, and half of them seem corrupted.

An example:
*snip*


Lots of people corrupt ogg files by appending ID3 tags. Strip the tags, and the stream should be okay.

QUOTE(minix @ Jan 28 2003 - 05:16 PM)
The worst example I found:
*snip*


That looks more like a seriously damaged file.

QUOTE(minix @ Jan 28 2003 - 05:16 PM)
Is it normal then those errors at the end of file always?


No. Only when people append garbage to the end of the file (ID3 tags are common).

QUOTE(minix @ Jan 28 2003 - 05:16 PM)
Is there an easy way to know errors position in time format?
Any graphical front end for ogginfo?


None that I know of.
Kemayo
So... how would one go about removing the tags from an ogg file? (I just recently tried using the Lyrics3 plugin for winamp, and was slightly disturbed by the way it broke playback of any ogg file it retrieved the lyrics for...)
bluesky
Can someone post a link to a win32 binary of ogginfo? I can't find one that isn't broken.

Thanks!
bluesky
danke man!
darky
QUOTE(bluesky @ Jan 2 2005, 06:14 PM)
danke man!
*

=thanks man!
bluesky
He knows, he's from Germany!
Sebastian Mares
QUOTE(bluesky @ Jan 2 2005, 09:58 PM)
He knows, he's from Germany!
*

laugh.gif
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.