similar to: More on parallelism

Greetings. In looking through the mail archives, I don't see any mention of parallelism of the vorbis code (particularly the encoder). I was wondering if anyone was looking into this at all? Either with threads, and/or on some kind of parallel machine (e.g., a Beowulf cluster)? I see very little mention of threads in the source code, which leads me to believe that they are only there for

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 R help, I am having problems running calculations in both the standard R GUI (ver 2.11.0) and the Java GUI for R (1.7-2) in Windows XP Service Pack 3 (2.2 GHz processor with 2 GB of RAM). When I try to import my data and run calculations on it, the GUI closes within a minute, sometimes almost instantaneously after I try to import data to then run the rest of my script. Has anyone had this

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

Greetings. I'm a newbie Samba user; I spent the entire weekend reading the HOWTO's and various other tutorials and docs from around the web. So if this is a naieve question, please don't hesitate the tell me to go back and RTFM some more. :-) I downloaded and compiled 3.0.0rc4 from source on a Mandrake 9.1 system (with all MDK updates installed) with the following configure line:

A variation on questions that I've asked before... In working on the parallel version of oggenc (both threaded and MPI), a profiling run shows that the function vorbis_analysis() takes up the majority of the run time. This seems to be an obvious choice for parallelization -- send each vorbis_block to a different processor, and let them call vorbis_analsis() in parallel with each other.

Something might have slipped by me, but I got into the following situation installing Rcmdr: < install.packages("Rcmdr",depend=TRUE) > Oodles of Output, until: * Installing *source* package 'multcomp' ... ** R ** data ** inst ** preparing package for lazy loading Error in dyn.load(x, as.logical(local), as.logical(now)) : unable to load shared library

>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

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

Speaking of ogg123 fixes and Solaris... <getopt.h> doesn't appear to exist in Solaris. Hence, ogg123 won't compile on Solaris at all (even with gcc). I originally mentioned this back in November (http://www.xiph.org/archives/vorbis-dev/200011/0291.html). Can this be fixed? {+} Jeff Squyres {+} squyres@cse.nd.edu {+} Perpetual Obsessive Notre Dame Student Craving Utter Madness

I host and HPC podcast with Jeff Squyres of Open-MPI fame at http://www.rce-cast.com We have had a request to have Puppet featured on the show soon and we would like this also. Feel free to have a developer or two contact me off list and we can setup a mutual time, it takes about 1 hour and is done over the phone or skype. I hope to hear from you soon! Brock Palen

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

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

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

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

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 don't think that the getopt_long() situation is handled correctly in the vorbis-tools module. Here's my take (comments welcome!). ----- This applies to oggenc, ogg123, and vorbiscomment. See http://www.xiph.org/archives/vorbis-dev/200012/0359.html for background and prior discussion on this issue. There are 2 issues: 1. Summary: getopt() is a POSIX function. It will already be on