search for: jsquyr

I notice that the user is not able to set their own CFLAGS or LDFLAGS in the ao, ogg, vorbis, and voribs-tools projects. Is there a reason for this? I understand the fact that these modules want to set extremely high optimization flags, and that most users won't know what these are offhand, but there are times when it is useful for the user to specify their own CFLAGS/LDFLAGS. For example,

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

...l disks? (just to be sure, I checked the recycle bine that is available for the local disk on the Windows client and my deleted file is not listed there -- as one would expect :-). Is there something else that I need to enable, or do I have something silly in my smb.conf? -- {+} Jeff Squyres {+} jsquyres@osl.iu.edu {+} Research Associate, Open Systems Lab, Indiana University {+} http://www.osl.iu.edu/

...ls (imagine that :-), mainly because vorbis exactly fits a convenient generalized manager/worker model. So to anyone on this list who is interested, I'd appreciate any feedback, comments, suggestions, corrections, etc. Here's the URL where to get the paper: http://www.mpi.nd.edu/~jsquyres/vorbis/ Thanks. {+} 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: http://www.xiph...

Without "no-dependencies" in every single Makefile.am's AUTOMAKE_OPTIONS line, automake will put gnu-specific instructions that will barf a) if you don't use gmake, and b) don't use gcc. This is actually in the automake manual, section 7.11, page 26 -- it's not an unexpected thing: "Currently, this support [automatic dependency generation] requires

...oblem that it will drop up to (Q_SIZE-1) packets at the end; that's not the point here); you can clearly hear its wrongness by playing the resulting .ogg file. Try it for yourself; the sample input that I've been using for testing is a short ~10 second clip: http://www.mpi.nd.edu/~jsquyres/vorbis/uh_ungawaa.wav Is this by design, or a bug? Is it not permissable to queue up ogg_packets for later writing? I didn't see any state that is stored in the ogg_packet or ogg_stream_state that seemed to be related to successive calls to vorbis_analyze() -- indeed, that would seem to be...

So it looks like the Frauenhoffer boys are issuing an updated format -- MP3pro. They claim that it will give 128kbps/MP3 quality in 64kbps. I'm interested to see what others think of this. I'm also curious: I've seen others on the list say that Ogg/Vorbis' sound quality is "better" than MP3. Can this be quantified (or is this already on a web page somewhere)? I kinda

Hello, I've been trying to compile some things but have run into some problems. I've have the vorbis directory inside of /usr/src. I have compiled vorbis itself with no problems. I've also copied the results to their respective directories as per the README file. I've also compiled the XMMS plugin with no problem. However when it is installed in the

...does seem to work, and does give mostly linear speedup as you add more CPUs. So if this group is willing, I can help out (yes, with code :-) with the parallelism -- although I will need help understanding the algorithms, etc. I give the following URLs as reference: http://www.mpi.nd.edu/~jsquyres/bladeenc/ - The parallel version of the bladeenc encoder, with lots of explanations http://www.mpi.nd.edu/lam/ - The main LAM/MPI web site http://www.mpi-forum.org/ - The main MPI web site (contains the specs, etc.) Thanks for your time. (I'...

It seems that configuring/building with "--enable-static --disable-shared" causes some problems with building vorbis-tools -- the Makefile.am's in oggenc and ogg123 do not appear to be correct. That is, if you build ao, ogg, and vorbis statically and try to compile oggenc or ogg123, you'll get unresolved symbol linker errors. This happens on all POSIX architectures and

The configure script for vorbis-tools requires one to manually specify: --with-ogg-prefix=PATH --with-vorbis-prefix=PATH --with-ao-prefix=PATH This is quite a pain to type. It would seem that most people will be installing all of these packages into the same $prefix. So in the absense of specifying these flags, it would seem suitable to just check for the appropriate

The file vorbis/ltconfig appears to be checked into CVS. This is an automatically generated file -- it should not be under CVS control. {+} 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

getopt() seems to be on all the Unix flavors that I can check (Solaris, IRIX, AIX, HP-UX, Linux). getopt() may be a standardized POSIX function...? I'm not sure offhand. Regardless, I think it's safe to assume that it's in all flavors of Unix -- oggenc/ogg123 need not include a local version of it for POSIX builds. Indeed, the getopt.c that is in oggenc is not friendly to the Sun

I'm running into memory leak and read-from/write-to unallocated errors in the cleanup phase of parallel oggenc. I see in vorbis_block_clear() that it references some fields on the vorbis_dsp_state that it cached during vorbis_block_init(), and conditionally does some cleanup based on the values of those fields. Does this fact effectively mean that you can't have multiple vorbis_block

>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:

1. ogg123 still won't build systems that don't have <getopt.h>. Was anything ever decided on how to procede with that? oggenc supplies its own getopt implementation. The only function really in question is getopt_long(), because getopt() is standard POSIX. See http://www.xiph.org/archives/vorbis-dev/200012/0359.html for a discussion of this issue. 2. Also, NAME_MAX is used in

There's some compilation issues on Solaris with the native compilers with the current CVS head. OGGENC: ======= -- "oggenc.c", line 202: warning: improper pointer/integer combination: op "=" I believe the problem here is that rindex() is prototyped in <strings.h>, which is not included. This may be a sun-specific thing. OGG123: ======= -- "ogg123.c",

vorbis-tools/oggenc/utf8.c:164 has a //-style comment; it should be /* ... */ so that non-gcc compilers won't barf (e.g., solaris Forte 6.1 cc). Patch included, if you're really lazy. :-) {+} 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: oggenc/utf8.c

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:

This time in vcut: vorbis-tools/vcut/vcut.h:23 and 24. No, I'm not spending quality time with grep; I'm trying to compile vorbis with the native Sun Forte compilers. Much badness, of which these // issues are only part. :-( More details to follow... Patch/inc/lazy. {+} Jeff Squyres {+} squyres@cse.nd.edu {+} Perpetual Obsessive Notre Dame Student Craving Utter Madness {+} "I