Hi All, For my new file (and thus mp3) server I've decided to switch completely to Ogg Vorbis. This means having to reencode ~30GB worth of 128Kb MP3's, but i figured that it would all be worth the effort. So I downloaded the sources for libogg, libvorbis and vorbis-tools and fired up my trusty old compiler. libogg and libvorbis built and installed like a charm. Not so for vorbis-tools... It seems that when building vorbis-tools libao is required. It also seems, however, that the only vorbis-tool linking with libao is ogg123 - the one tool I don't need on my server (which has no soundcard anyway). I must be able to encode to ogg (oggenc), change comments (vorbiscomment) and list the info for these files (ogginfo). All of these are not linked to libao : $ ldd `which oggenc` `which ogginfo` `which vorbiscomment` /usr/local/bin/oggenc: libvorbisenc.so.0 => /usr/lib/libvorbisenc.so.0 (0x4001d000) libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0x400e1000) libm.so.6 => /lib/libm.so.6 (0x400fd000) libogg.so.0 => /usr/lib/libogg.so.0 (0x4011f000) libc.so.6 => /lib/libc.so.6 (0x40123000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) /usr/local/bin/ogginfo: libvorbisfile.so.0 => /usr/lib/libvorbisfile.so.0 (0x4001d000) libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0x40023000) libm.so.6 => /lib/libm.so.6 (0x4003f000) libogg.so.0 => /usr/lib/libogg.so.0 (0x40061000) libc.so.6 => /lib/libc.so.6 (0x40065000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) /usr/local/bin/vorbiscomment: libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0x4001d000) libm.so.6 => /lib/libm.so.6 (0x40039000) libogg.so.0 => /usr/lib/libogg.so.0 (0x4005b000) libc.so.6 => /lib/libc.so.6 (0x4005f000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) Of course, I have no idea how to work around the configure and makefile problems to build all but ogg123. Of course, I could install libao or copy the tools I need from another box but there's little challenge in such a solution ;) Can anyone give me some pointers on how I should change the source distribution to build without libao and ogg123 ? Thanks ! Paul 'WEiRD' de Weerd --- >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-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
> > >For my new file (and thus mp3) server I've decided to switch >completely to Ogg Vorbis. This means having to reencode >~30GB worth of 128Kb MP3's, but i figured that it would all >be worth the effort. >Sorry, but it won't be worth the effort. For a number of reasons, transcoding from MP3 to Ogg Vorbis is NOT a good thing. The main reason being that your audio will end up sounding _worse_. See other messages on this list for more info. ** To the vorbis.com site admins: Perhaps someone should post a short article saying that this is bad, and all the reasons why it's bad. Seems the average user doesn't get it, and therefore, to save ourselves some breath, we could just reference to the website. As for you compiling questions, i'm sorry, i can't help you with that. Though your motives are scewed, i think this is a valid question, and actually something i wondered when having fun compiling vorbis-tools for myself. Some wise coder please tell us. Jonathan --- >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-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
On Mon, 3 Sep 2001, Paul de Weerd wrote:> It seems that when building vorbis-tools libao is required. > It also seems, however, that the only vorbis-tool linking > with libao is ogg123 - the one tool I don't need on my > server (which has no soundcard anyway). I must be able to > encode to ogg (oggenc), change comments (vorbiscomment) and > list the info for these files (ogginfo). All of these are > not linked to libao :Yes. Libao is used to playback audio to sound devices. The easiest thing to do right now (as you point out) is to install libao, and then delete it and ogg123. However, if you really want to compile without libao, you'll have to do the following hack (which requires that you have the autoconf/automake tools installed): Edit configure.in and remove the line: AM_PATH_AO(,AC_MSG_ERROR(libao needed!)) ./autogen.sh You will then have to cd into the dir for each tool you want to build and do "make" and "make install". I don't know if there is a strong need in general to compile some of the tools, but not others. If so, we can look into enabling the configure script to selectively compile certain tools. --- Stan Seibert --- >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-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Reasonably Related Threads
- [paul@mail.me.maar.nu: Building vorbis-tools without libao]
- vorbis-tools-1.1.1 build mechanism stubbornly refuses to build with FLAC, ogg123, speex
- libao NAS compilation and playback issues
- patches to beta 4 spec files
- Xiph.Org releases libao 1.0.0, libVorbis 1.3.1, and vorbis-tools 1.4.0