similar to: Compile Problems

>From /., here's the URL with the announcement of mp3PRO http://www.twice.com/html/pagebeta.cfm?InputKey=2853 {+} Jeff Squyres {+} squyres@cse.nd.edu {+} Perpetual Obsessive Notre Dame Student Craving Utter Madness {+} "I came to ND for 4 years and ended up staying for a decade" --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage:

vorbis/lib/vorbisenc.c:138 and 157 have "//" comments. Patch included for the lazy (like me!). {+} Jeff Squyres {+} squyres@cse.nd.edu {+} Perpetual Obsessive Notre Dame Student Craving Utter Madness {+} "I came to ND for 4 years and ended up staying for a decade" Index: vorbis/lib/vorbisenc.c =================================================================== RCS file:

Per Monty's suggestions from a while ago, I have [finally] gotten around to playing with different schemes for parallel oggenc. Monty's main suggestion was to have a single thread loop over reading samples and calling vorbis_analysis_blockout(), and then queueing up the resulting blocks to be processed through vorbis_analysis() in other threads (in parallel). To verify that this works, I

It seems that the configure script in CVS does not check the CFLAGS environment variable at all. Indeed, on line 121 of configure.in, CFLAGS is explicitly set to be blank. Is this done for a reason? I see that several sets of CFLAGS are passed into the Makefiles by configure based upon specific architecture/compiler combinations -- perhaps this is the reason...? I ask because users may wish to

Happy new millenium! Summary: I'm having a problem queueing up the ogg_packet results of vorbis_analyze() for later writing to an .ogg stream. The docs don't seem to say if this is permissable or not. Hence, I don't know if I'm using the API incorrectly, or if this is an actual bug. ----- Attached is a short patch to vorbis-tools/oggenc/encode.c (from CVS head, 01/01/01... I

Hi. I created a patch for Bug #4 (ogg123 not honoring /etc/ogg123rc) and uploaded it to Bugzilla, but I have the feeling that the Bugzilla is somewhat neglected... so I just send the patch here. The changes are very simple, one typo (I guess) was fixed (from "/etc/ogg123.rc" to "/etc/og123rc" as it's documented), and I changed an if to a while-loop to make it read the

Since vorbiscomment is being resurrected in a new form, can someone please fix the vorbis-tools/vorbiscomment/Makefile.am? There's two things wrong: 1. Using _LDFLAGS doesn't allow the user to specify their own LDFLAGS. _LDADD or _LIBS should be used instead. 2. The order of libraries is wrong such that it won't link properly when compiled statically. Here's a trivial

I sent a message about 2 weeks ago about build problems at the head of the CVS tree with non-gcc compilers on POSIX systems, although I didn't correctly identify the link problems as being static-library only (see my previous mail about "static link broken"). Some problems have been fixed, but some still seem to be there. I have edited my original mail to list the problems that

I'm afraid this e-mail is me being lazy. I'm interested in adapting the encoder to farm out work to various machines on a network. I'm just trying to find out if this is going to be trivial. I don't know how the encoder works but from my very brief glance through the code it would appear that a state is maintained 'vorbis_dsp_state' that's going to make my distributed

Long awaited, but finally here - http://www.vorbis.com. Beta4 is out the door :) Below is a copy of the press release, which you can find here: http://www.vorbis.com/press/20010226.txt And a Binary Freedom article that went out today: http://www.binaryfreedom.com/content.php?content_id=26 jack. ----- Ogg Vorbis Creators Announce Formation of Xiph.org Foundation Coincides with Release of

Long awaited, but finally here - http://www.vorbis.com. Beta4 is out the door :) Below is a copy of the press release, which you can find here: http://www.vorbis.com/press/20010226.txt And a Binary Freedom article that went out today: http://www.binaryfreedom.com/content.php?content_id=26 jack. ----- Ogg Vorbis Creators Announce Formation of Xiph.org Foundation Coincides with Release of

Long awaited, but finally here - http://www.vorbis.com. Beta4 is out the door :) Below is a copy of the press release, which you can find here: http://www.vorbis.com/press/20010226.txt And a Binary Freedom article that went out today: http://www.binaryfreedom.com/content.php?content_id=26 jack. ----- Ogg Vorbis Creators Announce Formation of Xiph.org Foundation Coincides with Release of

Long awaited, but finally here - http://www.vorbis.com. Beta4 is out the door :) Below is a copy of the press release, which you can find here: http://www.vorbis.com/press/20010226.txt And a Binary Freedom article that went out today: http://www.binaryfreedom.com/content.php?content_id=26 jack. ----- Ogg Vorbis Creators Announce Formation of Xiph.org Foundation Coincides with Release of

<head> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <meta name="GENERATOR" content="Microsoft FrontPage 4.0"> <meta name="ProgId" content="FrontPage.Editor.Document"> <title>Do you want to capitalize on the Biotech Revolution</title> </head> <body> <p

I've fixed a heck of a lot of stuff in the time frame of just over ten minutes. And you all care... right. I actually ran Vorbize, and discovered some stupid bugs (e.g., segfault???). Fixed. Both Vorbize and Ogg123 should now speak fluently in Monty's comment-eese. I'll be working on getting both to implement all the comment tags; I'm seriously considering dropping all comment

------- Forwarded Message The following patches should fix vorbis-tools to build on NetBSD. I'm not including the diff to the configure scripts, so you'll need to rerun autoconf in the toplevel and libao directory after applying these patches to the configure.in files. It also appears that vorbis-tools/libao/ao_libs.inc is automatically generated by a configure script but checked into

I've been trying to tackle the vorbis source. I ran across what I think is a missing dependency in the vorbis-tools directory. Since ogg123 and vorbize are staticly linked to libvorbis and vorbisfile, when those file change, the executables should be rebuilt. Below I've attached a patch. (I hope it works. I am sort of new to patch and diff.) BTW, I've been trying to find a good

I first downloaded Vorbis about a month ago, around the time Rok Papez posted comparisons of Ogg and Lame [*]. Here's my much rougher test on a single file. CPU: AMD K6-233 MP3: LAME 3.70, mp3blaster 2.0b6 Ogg: Vorbize 0.6 (Xiphophorus libVorbis I 20000718), ogg123-0.1 Data set: Ministry, "The Fall" (51,955,724 byte WAV) * * * Ogg Vorbis command line: time vorbize -v -w

Hey. Last night I hacked grip so that it'd allow me to use vorbize and comments with grip. It's very ugly because grip'd need a bit of rearrangement in order to facilitate the way the vorbis comments work (that is, the comments are not added in after the encoded file has been written). Any one who wants to use it should patch grip-2.94 (http://www.nostatic.org/grip), and make sure you

I have sent some patches to some Makefile.am's as well as to some configure.in's, particularly for building without gcc and gmake. Can someone review those patches, and/or commit them? (we are working at the CVS head these days, no?) I cannot build in Solaris without gcc/gmake, for example -- running "autogen.sh" in the ao project with the native Solaris compilers causes