similar to: Question re: vorbis_block_clear()

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.

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

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

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

Hello all Can anyone point me to some form of description for the fields in the following structures : 1/ vorbis_dsp_state 2/ vorbis_block Thank you. regards ~previr _____________________________________________________________ Previr Rangroo STMicroelectronics Associate Systems Lab Engineer Plot No. 2 & 3, Audio Competence Center Sector 16A,

Hello all Can anyone point me to some form of description for the fields in the following structures : 1/ vorbis_dsp_state 2/ vorbis_block Thank you. regards ~previr _____________________________________________________________ Previr Rangroo STMicroelectronics Associate Systems Lab Engineer Plot No. 2 & 3, Audio Competence Center Sector 16A,

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

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'm having trouble tracking down why it leaks, but below is an example program which shows--using valgrind--that vorbis_info_clear() leaks memory if called before vorbis_dsp_clear(), but not if called after vorbis_dsp_clear(). Just compile and run under valgrind, using the -l switch to the example program to trigger a leak. Tested under OS X 10.7 and Ubuntu 12.04. This may be by design, or

Hi, This mozilla bug report is a crash triggered by a Vorbis file with corrupt headers: https://bugzilla.mozilla.org/show_bug.cgi?id=481601 The patch to fix the crash adds a new vorbis_dsp_init() function to libvorbis, and calls that from fs_vorbis_init() in libfishsound: https://bug481601.bugzilla.mozilla.org/attachment.cgi?id=366150 The public function it adds is: void

Using libvorbis (1.3.5) I wish to extract the raw vorbis packets.  I've built some simple code on the excellent libvorbis API overview on the xiph.org site, but the example relies on the ogg_packet struct for final output and input to decoder, and shows now examples on how to do without it. Taking a look at the vorbis_bitstream_flush() function, which in the overview is the last step before

> > Which part? > > Well, my biggest problem is dealing with files. As you have mentioned > that fill_buffer() is obsolete, what has replaced it? ogg_sync_buffer() > didn't seem to be what I was looking for, as far as I can tell... am I > headed in completely the wrong direction? Ah, OK, I understand where you're headed now. The libvorbis API is different than

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

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

I am trying to create a Graphical User Interface for a Vorbis Player under MS Visual C++ 6.0 I was initially trting to use the code from decoder_example.c but I keep getting linker errors. I have set up my project as told to by James Boer on this mailing list. This is as follows: This document was prepared from an email received from James Boer on the Ogg Vorbis mailing list. It gives a

Okay, how do I drop a changeset/patchset/tag for you folks from SVN? At this point, I have written three examples of how to use the basics of the ogg streaming and decoding in Tremor. I heartily welcome any suggestions, improvements and corrections that you can point out in the code. The examples required me to make some small modifications to the main tremor library. However, the changes

Hello everybody, Since there is almost no documentation on the vorbis algorithm I have to post some questions on this list. To remind you: I am trying to implement a parallel (multithreaded) ogg encoder, using a manager-worker model. 1. About the vorbis algorithm. I plan to let the workers each process a buffer of vorbis_blocks. The point is that each worker has to start somewhere and can not

I added a new function to libvorbis that allows lossless changes of the volume to an vorbis_block. This can help to get reasonable loudness on hardware players that do not support the Replay Gain tags. int vorbis_gainadj(vorbis_block *vb, ogg_packet *op, float* dbgain); dbgain contains the relative adjustment for each channel. The trick is quite simple. I adjust the first 2 floor values for

libvorbis does not currently have any simd/vectorization. Following patches add generic framework for simd/vectorization and on top, add ARM-NEON simd vectorization using intrinsics. I was able to get over 34% performance improvement on my Beaglebone Black which is single Cortex-A8 based CPU. You can find more information on metrics and procedure I used to measure at

Hi All, I am trying to build an Ogg/Vorbis plugin for RealOne Player through the HelixCommunity source. During runtime, however, I saw an access violation. I did some debugging and narrowed it down to the following function in the Vorbis source.. int vorbis_synthesis(vorbis_block *vb,ogg_packet *op){ vorbis_dsp_state *vd=vb->vd; backend_lookup_state *b=vd->backend_state;