similar to: By design or a bug?

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

Hi While implementing OSS Ogg/Vorbis encoding and streaming using RTP/RTCP for both unicast and multicast, I have come across a few issues I need to clear out regarding the numbering of ogg_packets and their granulepos value. Below are the result for two different scenarios. <p>In the first scenario, ogg_packets are generated using a) vorbis_analysis_headerout() b) while

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

So, I abandoned the hope of using the ogg python bindings to do pure ogg container encoding. I started looking at the libogg in the hopes of retooling the bindings to follow a better object model and it actually looks like the problem is down in libogg, not the bindings. Am I crazy or does libogg rely on libvorbis to return ogg_packets, and that there are no functions that will build an ogg_packet

Hi. I'm trying to implement Ogg/Vorbis support for the MPEG4IP project. The goal is to support Ogg/Vorbis audio for MPEG-4 streaming. So far I have managed to make the encoder save Ogg packets as an Audio object in an .mp4 file. As a side effect, it can also save Ogg pages in an .ogg file playable by xmms, but that's no big deal. So what I'm doing is this. First the init part. a)

1.) after initializing a ogg_stream_state may I just keep calling ogg_stream_packetin with valid ogg_packet's until no more ogg_packets needs to be added? Or do I need to call ogg_stream_pageout after every ogg_stream_packetin? Iaw may I delay calling ogg_stream_pageout until there are no more packets to be added? 2.) I assume I have call ogg_stream_pageout until no more pages can be

Monty -- I'm still running into problems with my threaded encoded, and I think I just figured out why. I have N threads running in parallel calling vorbis_analysis_blockout() and vorbis_analysis() to do the number crunching on the input samples. They all share a single vorbis_dsp_state -- my understanding was that this was ok; they only *read* from the vorbis_dsp_state, therefore not

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.

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

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

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

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

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

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

I read some lines in libvorbis/include/vorbis/codec.h: /* vorbis_block is a single block of data to be processed as part of the analysis/synthesis stream; it belongs to a specific logical bitstream, but is independant from other vorbis_blocks belonging to that logical bitstream. *************************************************/ My question. Does this imply that vorbis_analysis

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,