similar to: vorbis_analysis() dependencies?

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

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

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

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.

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

Nothing on a branch yet; I'll be building a temp branch for my changes soon. First, I'm eliminating ordering dependancies in vorbis_block structures. They'll be totally sepreate and vorbis_analysis won't have a global state in vorbis_dsp_state that requires them being done in order. That way, a parallel-threaded encoder can run multiple vorbis_blocks through multiple

I apologize for bugging you all again, but I've been trying to wrap my head around the encoding process and I'm about to have an aneurysm :P I've gone through oggenc.c, encode.c, and audio.c and I think I have a basic idea of what happens. I got it down in pseudocode as follows: --- 1 get parameters 2 init vorbis_comment -- vorbis_comment_init() 3 init vorbis_info --

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

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 spent quite some hours in the archives of this mailinglist and read a few threads mainly by Jeff Squyres and Monty about making oggenc multithreaded. Those threads all are dated around January 2001, quite a time ago. For my work experience period I have to implement a parallel (threaded) ogg encoder (If this is possible, of course.) If it can be done, the code will be given back to 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 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

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

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