similar to: Comparison Between MP3 and Vorbis

Hello All, I realize that this is all highly unscientific and probably unprofessional as well. Still, I couldn't resist the urge. I ripped track 6 (prelude) from Yanni's "Tribute" album and encoded it with the latest versions of lame and oggenc. I present below the command line I used for both encodes: time oggenc -a 'Yanni' -t 'Prelude' -l 'Tribute' -c

Hello All, I realize that this is all highly unscientific and probably unprofessional as well. Still, I couldn't resist the urge. I ripped track 6 (prelude) from Yanni's "Tribute" album and encoded it with the latest versions of lame and oggenc. I present below the command line I used for both encodes: time oggenc -a 'Yanni' -t 'Prelude' -l 'Tribute' -c

Hello, I found out about Vorbis and Ogg recently and am very interested in it. I grabbed the latest sources from CVS and have been able to compile almost everything. The only thing (to my knowledge) that I can't compile is the 'cmdline' demo. Everything compiles correctly there error comes in the linking stage. The error message is reproduced below: make target

Hello, I found out about Vorbis and Ogg recently and am very interested in it. I grabbed the latest sources from CVS and have been able to compile almost everything. The only thing (to my knowledge) that I can't compile is the 'cmdline' demo. Everything compiles correctly there error comes in the linking stage. The error message is reproduced below: make target

Hello, I have been following Ogg Vorbis for about two months now. I like it. A lot. I can't wait to use it. I want to use it so bad it hurts. The only thing stopping me at this point is the inability to add artist, title, and album information to the file. I consider that a must before I start ripping files into the .ogg format. Does anyone have *any* kind of a timeframe on an encoder (for

bonjour, hello, buenas dias, ça ne fait pas longtemps que je suis sur cette mailing list, J'éspére que quelqu'un parle le français car techniquement je suis pas doué ni en anglais ni en d'autres langues... it isn't a long time i 'm on the mailing list, i hope someone is speaking french, because i don't write very well others languages about technical probléms... no

On 12 Feb 2003, Karl Heyes wrote: | |does the mount point end with .ogg? | |karl. | Karl, Yes, it does. Named scanner.ogg I just tried something though. Xmms has its libvorbis.so listed and enabled. But I just tried from the commandline on the server using ogg123, and it seems to be working just fine. Although using ogg123 from my client here at work gives me this: [bryank@net bryank]$ ogg123

My machine is running RedHat Linux 7.3, and I believe it came with vorbis 1.0rc3 by default. To my knowledge, I upgraded all libraries, documentation, and binaries with 1.0 versions. it placed everything in /usr/local whereas the old stuff was in /usr, so I manually deleted the old stuff from /usr. When I run 'oggenc', it does say: "OggEnc v1.0 (libvorbis 1.0)"

The latest CVS update of libvorbis fails to compile on SuSE Linux 6.4. The error is below. Also, what happened to the xmms plugin directory in cvs? It complains that it is missing when I do a 'cvs update'. gcc -DPACKAGE=\"libvorbis\" -DVERSION=\"1.0beta3\" -DHAVE_ALLOCA_H=1 -DHAVE_ ALLOCA=1 -I. -I. -I../include -O20 -ffast-math -mno-ieee-fp -D_REENTRANT -fs

Hi I'm getting frequent segmentation faults (on the order of one every hour) while listening to the stream at http://62.93.224.180:15000/radio404.ogg . This is on FreeBSD 5.3 with everything installed from the FreeBSD ports (this means libvorbis-1.0.1), but I had the same issue with an older FreeBSD 5.1 installation. The backtrace looks like : (gdb) bt #0 0x28741d88 in

One thing I must note before I begin is that, I probably just am not that well skilled at listening, but I can hear no difference between vorbis, mp3, and wav at the bitrates I encoded them at. lame 3.83 (beta) was used to encode the mp3s and mpg123 was used to decode. The current (Jun 8 00) encoder/decoder examples were used for vorbis. mp3s were encoded at 128 kbps, and vorbis is unknown

On Sun, Oct 22, 2006 at 07:15:56AM -0700, Ralph Giles wrote: > On Sun, Oct 22, 2006 at 02:49:07AM +0200, A.David David wrote: > > > Hi all, I am trying to append some image to my ogg file > > but it results to corruption of the file, as there is no real way of > > including images > > in the OGG, I just tried to append the image at the end. > > Yes, that will

Contained in tonight's last commit: Fixed a link-crossing bug in libvorbis (total time was reset to -1 at the link boundary until the next packet with a frame number arrived) Implemented instantaneous bitrate capability in libvorbis; added ov_bitrate_instant() to interface. I know I talked about a different interface to this with the Sonique folks a few months ago... I couldn't remember

I have done fresh builds of xmms-1.2.5, libogg-1.0rc2, and libvorbis-1.0rc2 on a sparc-solaris-2.8 platform, using gcc-2.95.3. I had to use the GNU binutils to get the libvorbis libraries to link correctly. Everything built clean and without protest. When I install it all and try an ogg-vorbis file, I get noise. I'm wondering if this is a big-endian problem somewhere. I'd appreciate

I'm forwarding this mail, since thomasvs on #vorbis can't seem to subscribe/send to the list. Please Cc: thomas@apestaart.org when you answer, or write directly to him. ----- Forwarded message ----- Hi, I've been asked by Vakor to help out on the packaging of the 1.0 release (for Red Hat). (For some reason xiph.org is refusing any mail from our server, urgent.rug.ac.be, so I

Since the decoding went so much faster, I actually listened to the song I encoded all the way to the end, at which point the thing segv'd. Through a little easter egging, I managed to trace the problem down to a call to vorbis_dsp_clear(). I've just commented it out in the current source. As to why it's segving I am uncertain, but, save possible memory leaks, everything seems to be

> > >you probably have an old release, maybe we should put some checks in to >make sure. > It appears that I have version 1.0 rc2-1 I found the following RPM's with ogg or vorbis in the name: libogg-devel-1.0rc2-1 libogg-1.0rc2-1 libvorbis-devel-1.0rc2-2 libvorbis-1.0rc2-2 vorbis-1.0rc2-1 I figured I better try to remove these before installing a new version from source. I

Ian Malone wrote: > On 23/10/06, Conrad Parker <conrad@metadecks.org> wrote: >> On Sun, Oct 22, 2006 at 07:15:56AM -0700, Ralph Giles wrote: >> > On Sun, Oct 22, 2006 at 02:49:07AM +0200, A.David David wrote: >> > >> > > Hi all, I am trying to append some image to my ogg file >> > > but it results to corruption of the file, as there is no

Hello I am new at this. I have compiled the libogg and libvorbis libraries and installed them on my MacOS X machine. The libao cannot be compiled yet since stuff is missing. But I only want to play round with encoding right now. So I also unpacked the vorbis tools distribution and am in oggenc. In oggenc I do a cc *.c -I. -L/usr/local/lib -logg -lvorbis -lvorbisenc I get unknown symbols

--- Sigmund Augdal <sigmunau@stud.ntnu.no> wrote: > On Sun, Mar 09, 2003 at 03:58:22PM +0100, Sander Roobol wrote: > > Hello Dan Johnson, hello list, > > > > It's really weird that there's no working command line player for > FLAC > > files. Dan Johnson created flac123 (licensed under the GPL) to fill > that > > gap, and started the flac-tools