similar to: linking, exported symbols

Hi all, I'd like to quantize a variable to map it into a limited set of integers for use with a colormap. "image" and filled.contour" do this mapping inside somewhere, but I'd like to choose the colors for plotting a set of polygons. Is there a pre-existing function that does something like this well? i.e., is capable of using 'breaks'?

Hi, I'm trying to convert some quicktime files into Ogg/Theora using the Xiph QuickTime Components version 1.8. The end goal is to stream these files using apache httpd and the cortado applet (and hopefully the embedded players that will be in Firefox soon). Using iMovie DV on OS X 10.4.11 (intel) I'm able to export as an ogg movie, however the resultant file has problems with audio on

Hello Srikant - A quantization distributes the results of your aggregation into ranges ordered by a power-of-two. Presumably what you''d do in your script is capture the inclusive elapsed time of each function call in your library, then use this quantization to see how tightly-banded the times are. Perhaps there''s some blocking I/O in some of your calls, for example, in which

Hi, I am kind of new to DTrace , I have written a script to time function calls in our application library , Wanted to know how to interpret the output from quantize of the elapsed time in each function call , here is a sample Here is the entry and return function for the library that is being traced pid$1:libswduar::entry { duarEntry[probefunc] = timestamp;

I have a probe: pid111::myfunc:entry { self->arg = arg0; } pid111::myfunc:return /self->arg/ { @[self->arg] = quantize(); } works great, but i''d like arg0 to be printed in hex. I''ve tried numerous approaches to do this but i''ve hit a wall every time. I''ve tried: 1) self->arg = sprintf(arg0); no, cuz dtrace has no sprintf 2) self->arg

Hello! I just noticed how the LPC prediction is quantized by browsing the source code of the java port jFlac: : int sum = 0; for (int j = 0; j < order; j++) sum += qlpCoeff[j] * data[startAt+i-j-1]; data[startAt + i] = residual[i] + (sum >> lpQuantization); : I checked the C version (libFLAC) and it matches. However, it was a surprise because this way of quantizing the

1) What are you doing "mathematically" in a procedure x86/x86enquant: oc_enc_quantize_sse2()? This - the assembler code, and I do not understand mathematically - that's going on there. --- A: 120 121 28 73 -20 -99 -98 -100 123 122 112 108 73 -32 -102 -98 123 123 117 121 100

Just switched to Ubuntu 2 days ago and trying to get the hang of Wine. I'm trying to run the IMVU client through it, but all that happens is that the login screen will come up and let me log in, but after that I get an IMVU icon in the upper right but no client to use. When running the command to execute IMVU through the terminal, I get the following: Code: env

---------- Forwarded message ---------- From: digital design <developer.fpga at gmail.com> Date: 21 March 2011 13:38 Subject: Re: [theora] alghorithm of working encoder in libtheora To: bens at alum.mit.edu Cc: Reply-All at xiph.org On 18 March 2011 23:15, Benjamin M. Schwartz <bmschwar at fas.harvard.edu>wrote: > On 03/18/2011 01:44 PM, digital design wrote: > > Now i

(Disclaimer: this is not an LPC vs. LSP question) After looking at the Vorbis code I was wondering why you were using LSP to quantize the spectral envelope instead of simply quantizing the cepstrum (DCT(log(envelope))) or modified cepstrum (DCT(envelope.^alpha)). To me it seems like when the information is already in the frequency domain, there's no need to go back to LPC. Also, I think a DCT

Has anyone seen the following error before? "error on enabled probe ID 2 (ID 473: sdt:unix:av_dispatch_autovect:interrupt-complete): invalid address (0x198) in action #3 at DIF offset 20" I''m trying to capture interrupt times as inlined in the below script. The script gives me some output after the errors, and I''m trying to understand if the errors are affecting

Hi, Jean-Marc Valin wrote: > Not sure I understand your question. Change the order of what within what? In cb_search, we iterate nb_subvect times over a codebook, finding nb_subvect codebook entries to quantize the excitation signal. After finding these nb_subvect codebook entries, they're written into the stream: /*save indices*/ for (i=0;i<nb_subvect;i++) {

Monty lost this one. :) ---------- Forwarded message ---------- Date: Fri, 21 Apr 2000 09:30:31 -0700 From: Monty <xiphmont@xiph.org> To: Gregory Maxwell <greg@linuxpower.cx> Subject: Re: Branch: residue codebook trainer. > > I was looking at the residue trainer in the branch, and I noticed: > > " /* seed the inputs to input points, but points on unit

Hi, I've been using the Vorbis codec for a while and recently I got the source code and had a look at the spec (great job on the doc BTW). I don't have any former experience with audio compression, but I do know what a DCT does and I totally grok Huffman coding (so I guess I'm not that much of a newbie, am I?). Anyway I just had some questions about how VQ works on the encoding side.

Author: bmc Repository: /hg/zfs-crypto/gate Revision: 213bfe03af413cdf71c523fb076aaa65a6306a7e Log message: 6256581 System got a hang or a panic with dtrace+kmdb 6264573 unanchored dtrace_getpcstack is rather imprecise toward function end 6289517 dtrace doesn''t like fd_intr anymore 6291378 dtrace helpers can interfere with the use of kmdb 6295554 dtrace doesn''t report

Hi. System is snv_56 sun4u sparc SUNW,Sun-Fire-V440, zil_disable=1 We see many operation on nfs clients to that server really slow (like 90 seconds for unlink()). It''s not a problem with network, there''s also plenty oc CPU available. Storage isn''t saturated either. First strange thing - normally on that server nfsd has about 1500-2500 number of threads. I did

Hello, I?m trying to install PIL (Python Image Library) in a CentOS-4.4, but I?m getting the follow error after unpack the tarball: ------------------------------- # python setup.py install running install running build running build_py creating build creating build/lib.linux-i686-2.3 copying PIL/ExifTags.py -> build/lib.linux-i686-2.3 copying PIL/ImageTransform.py ->

Hello folks, The codebook infrastructure for Vorbis is now well underway. This is it! The last piece needed for *real* bitstreams. To that end, I have a decent VQ codebook generator running. I was originally using some farily typical merge/split algorithms and then decided that the right way to do this was to model a VQ codebook as an m-dimensional set of bubbles (like a foam). I know there

OK, into the nitty-gritty, albeit a high-level version. If it sounds like I'm glossing important details, you're right. This discusses only the basic DSP; precise coding, framing, sync, etc, will be in another mail. Vorbis is a hybrid transform domain general purpose audio encoder, like MPEG in some respects (it is rooted in much of the same basic theory). For the most part, the

Hi Experts, _write value ------------- Distribution ------------- count 4096 | 0 8192 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 1161825 16384 | 2754 32768 |@