1 Dec
2003
1 Dec
'03
11:54 p.m.
Hi,
How can I get info from an ogg file that tells me things like sample
rate, bit-depth and other information? sndfile-info doesn't seem to know
about ogg files. (A surprise to me...)
Thanks in advance,
Mark
2 Dec
2 Dec
12:07 a.m.
What about:
file filename.ogg
from the shell?
GZS
Mark Knecht wrote:
Hi,
How can I get info from an ogg file that tells me things like sample
rate, bit-depth and other information? sndfile-info doesn't seem to know
about ogg files. (A surprise to me...)
Thanks in advance,
Mark
--
This Message is sent from my Red Hat 9.0 Linux server
Machine Registration number 205692 at http://counter.li.org/
.-. Gustavo Zamorano S.
.-. | Registered Linux user number 320898
.-. | | at http://counter.li.org/
| | | | ___
12:17 a.m.
On Mon, 2003-12-01 at 20:17, Gustavo Zamorano S. wrote:
What about:
file filename.ogg
from the shell?
GZS
Gustavo,
Hi. I didn't know about file. Thanks! I don't think it's telling me
too much, or I'm not sure how to read the results. It does tell me
sample rate, which is a step forward:
bash-2.05b$ file gmc2.ogg
gmc2.ogg: Ogg data, Vorbis audio, stereo, 44100 Hz, ~128031 bps, created
by: Xiphophorus libVorbis I 20011231 (RC3)
bash-2.05b$ file examplesustain.ogg
examplesustain.ogg: Ogg data, Vorbis audio, stereo, 44100 Hz, >256000
~224000 bps, created by: Xiph.Org libVorbis I 20020717 (1.0)
bash-2.05b$
I have an ongoing problem with the OSS part of Alsa. I noticed this
evening that the file examplesustain.ogg doesn't have the problem, while
pretty much every other ogg or wave file I play does. I was thinking
that one of these might be 16-bit, or 24-bit, etc., or something like
that, but I don't see that here.
I looked at the man page, but nothing jumped out at me.
Thanks very much though.
- Mark
12:27 a.m.
Yes.. As a Unix user I use the command file too much!...
But, as someone else posted, ogginfo does a better job in this case.
GZS
Mark Knecht wrote:
On Mon, 2003-12-01 at 20:17, Gustavo Zamorano S.
wrote:
--
This Message is sent from my Red Hat 9.0 Linux server
Machine Registration number 205692 at http://counter.li.org/
.-. Gustavo Zamorano S.
.-. | Registered Linux user number 320898
.-. | | at http://counter.li.org/
What about:
file filename.ogg
from the shell?
GZS
Gustavo,
Hi. I didn't know about file. Thanks! I don't think it's telling me
too much, or I'm not sure how to read the results. It does tell me
sample rate, which is a step forward:
bash-2.05b$ file gmc2.ogg
gmc2.ogg: Ogg data, Vorbis audio, stereo, 44100 Hz, ~128031 bps, created
by: Xiphophorus libVorbis I 20011231 (RC3)
bash-2.05b$ file examplesustain.ogg
examplesustain.ogg: Ogg data, Vorbis audio, stereo, 44100 Hz, >256000
~224000 bps, created by: Xiph.Org libVorbis I 20020717 (1.0)
bash-2.05b$
I have an ongoing problem with the OSS part of Alsa. I noticed this
evening that the file examplesustain.ogg doesn't have the problem, while
pretty much every other ogg or wave file I play does. I was thinking
that one of these might be 16-bit, or 24-bit, etc., or something like
that, but I don't see that here.
I looked at the man page, but nothing jumped out at me.
Thanks very much though.
- Mark
12:07 a.m.
On Mon, 01 Dec 2003, Mark Knecht <markknecht(a)comcast.net> wrote:
Hi,
How can I get info from an ogg file that tells me things like sample
rate, bit-depth and other information? sndfile-info doesn't seem to know
about ogg files. (A surprise to me...)
vorbis-tools come with their own utility
called ogginfo which does exactly
that.
Thanks in advance,
Mark
12:10 a.m.
On Mon, Dec 01, 2003 at 07:52:23PM -0800, Mark Knecht wrote:
Hi,
How can I get info from an ogg file that tells me things like sample
rate, bit-depth and other information? sndfile-info doesn't seem to know
about ogg files. (A surprise to me...)
Check out ogginfo(1) - it should've come with vorbis-tools and tells you
all that good stuff:
ross@turalyon:~$ ogginfo
/opt/music/ska/Deal\'s_Gone_Bad_-_Overboard/Deal\'s_Gone_Bad_-_Too_Early\,_To_Late.ogg
Processing file
"/opt/music/ska/Deal's_Gone_Bad_-_Overboard/Deal's_Gone_Bad_-_Too_Early,_To_Late.ogg"...
New logical stream (#1, serial: 76523cb2): 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: 112.001000 kb/s
Upper bitrate not set
Lower bitrate not set
User comments section follows...
title=Too Early, To Late
artist=Deal's Gone Bad
date=
album=Overboard
tracknumber=6
Vorbis stream 1:
Total data length: 3035797 bytes
Playback length: 3m:39s
Average bitrate: 110.815733 kbps
Logical stream 1 ended
--
Ross Vandegrift
ross(a)willow.seitz.com
A Pope has a Water Cannon. It is a Water Cannon.
He fires Holy-Water from it. It is a Holy-Water Cannon.
He Blesses it. It is a Holy Holy-Water Cannon.
He Blesses the Hell out of it. It is a Wholly Holy Holy-Water Cannon.
He has it pierced. It is a Holey Wholly Holy Holy-Water Cannon.
He makes it official. It is a Canon Holey Wholly Holy Holy-Water Cannon.
Batman and Robin arrive. He shoots them.
1 a.m.
On Mon, 2003-12-01 at 20:08, Ross Vandegrift wrote:
Check out ogginfo(1) - it should've come with
vorbis-tools and tells you
all that good stuff:
Thanks. That's definitely more interesting. I still don't see what
should cause one to create a huge popping noise when it starts and the
other doesn't.
My suspicion is that the first one, which pops, is generated from 240bit
audio, whereas I'm thinking that the second is generated from 16-bit
audio, but I don't know that for sure, and ogginfo doesn't seem to tell
me.
bash-2.05b$ ogginfo gmc2.ogg
Processing file "gmc2.ogg"...
New logical stream (#1, serial: 3691a8a7): type vorbis
Vorbis headers parsed for stream 1, information follows...
Version: 0
Vendor: Xiphophorus libVorbis I 20011231 (1.0 rc3)
Channels: 2
Rate: 44100
Nominal bitrate: 128.031000 kb/s
Upper bitrate not set
Lower bitrate not set
Vorbis stream 1:
Total data length: 4372644 bytes
Playback length: 5m:05s
Average bitrate: 114.389712 kbps
Logical stream 1 ended
bash-2.05b$
bash-2.05b$
bash-2.05b$ ogginfo examplesustain.ogg
Processing file "examplesustain.ogg"...
New logical stream (#1, serial: 6378c0ce): 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: 224.000000 kb/s
Upper bitrate: 256.000000 kb/s
Lower bitrate not set
Vorbis stream 1:
Total data length: 3122631 bytes
Playback length: 2m:08s
Average bitrate: 193.935677 kbps
Logical stream 1 ended
bash-2.05b$
1:10 a.m.
I don't know if what happens is that the header of a sound file has been
treated as sound and it is generating the noise.
You can cut it out with rezound, for example...
GZS
Mark Knecht wrote:
On Mon, 2003-12-01 at 20:08, Ross Vandegrift wrote:
--
This Message is sent from my Red Hat 9.0 Linux server
Machine Registration number 205692 at http://counter.li.org/
.-. Gustavo Zamorano S.
.-. | Registered Linux user number 320898
.-. | | at http://counter.li.org/
| | | | ___
| | | |/ _ \ ___ Unique Computer Operations, S. A.(UNICOPSA)
| /o\_'||.' o `.
| \=/ /|| `---' Celular: (507) 672-6487
\ ___// \
\____/ (`__') P.O. Box 872150, Zona 7
///////\\\\\\\ Panama, Republic of Panama
`--.____.--' mailto:gzsuniq@cableonda.net
Check out ogginfo(1) - it should've come with
vorbis-tools and tells you
all that good stuff:
Thanks. That's definitely more interesting. I still don't see what
should cause one to create a huge popping noise when it starts and the
other doesn't.
My suspicion is that the first one, which pops, is generated from 240bit
audio, whereas I'm thinking that the second is generated from 16-bit
audio, but I don't know that for sure, and ogginfo doesn't seem to tell
me.
bash-2.05b$ ogginfo gmc2.ogg
Processing file "gmc2.ogg"...
New logical stream (#1, serial: 3691a8a7): type vorbis
Vorbis headers parsed for stream 1, information follows...
Version: 0
Vendor: Xiphophorus libVorbis I 20011231 (1.0 rc3)
Channels: 2
Rate: 44100
Nominal bitrate: 128.031000 kb/s
Upper bitrate not set
Lower bitrate not set
Vorbis stream 1:
Total data length: 4372644 bytes
Playback length: 5m:05s
Average bitrate: 114.389712 kbps
Logical stream 1 ended
bash-2.05b$
bash-2.05b$
bash-2.05b$ ogginfo examplesustain.ogg
Processing file "examplesustain.ogg"...
New logical stream (#1, serial: 6378c0ce): 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: 224.000000 kb/s
Upper bitrate: 256.000000 kb/s
Lower bitrate not set
Vorbis stream 1:
Total data length: 3122631 bytes
Playback length: 2m:08s
Average bitrate: 193.935677 kbps
Logical stream 1 ended
bash-2.05b$
1:29 a.m.
On Mon, 2003-12-01 at 21:20, Gustavo Zamorano S. wrote:
I don't know if what happens is that the header of
a sound file has been
treated as sound and it is generating the noise.
You can cut it out with rezound, for example...
No, sorry. I wasn't clear enough. The files are fine. I can play them on
other systems, or with other sound cards, and I don't get any problem.
The only time the noise problem shows up is with my high end $500 sound
card, and only when using Alsa OSS emulation. It's perfectly fine on
Alsa audio.
For instance, I can play wave/jazz_seq1.wav using alsaplayer and I get
no noise, but xmms playing the same file through OSS has trouble.
The thing I was after tonight was that the examplesustain.ogg file is
the first one I've found that plays in multiple OSS apps and doesn't
make the noise. I wanted to try and understand why it doesn't make the
sound.
Sorry for not being more clear.
Thanks for your help.
- Mark
4:49 a.m.
On Mon, Dec 01, 2003 at 08:58:56 -0800, Mark Knecht wrote:
My suspicion is that the first one, which pops, is
generated from 240bit
audio, whereas I'm thinking that the second is generated from 16-bit
audio, but I don't know that for sure, and ogginfo doesn't seem to tell
me.
IIUC theres no "bitwidth" inside oggs, its just a representation of the
shape of the input signal, so the bitdepth of the source shouldn't have a
significant effect on the kind of data stored. I may be totaly wrong here
though.
Is there a DC offset which the cheap card is eating?
- Steve
9:47 a.m.
On Tue, 2003-12-02 at 00:48, Steve Harris wrote:
On Mon, Dec 01, 2003 at 08:58:56 -0800, Mark Knecht
wrote:
Cheap as in "this card was not the best $500 purchase I ever made?"
A DC offset is an interesting idea. How would I test for that?
Thanks,
Mark
My suspicion is that the first one, which pops,
is generated from 240bit
audio, whereas I'm thinking that the second is generated from 16-bit
audio, but I don't know that for sure, and ogginfo doesn't seem to tell
me.
IIUC theres no "bitwidth" inside oggs, its just a representation of the
shape of the input signal, so the bitdepth of the source shouldn't have a
significant effect on the kind of data stored. I may be totaly wrong here
though.
Is there a DC offset which the cheap card is eating?
- Steve
7715
days inactive
7716
days old
linux-audio-user@lists.linuxaudio.org
10 comments
5 participants
participants (5)
-
Gustavo Zamorano S. -
Mark Knecht -
Ross Vandegrift -
S. Massy -
Steve Harris