similar to: subversion link incorrect

Displaying 20 results from an estimated 1000 matches similar to: "subversion link incorrect"

2006 Apr 27
2
summer of code
Congrats Jean Marc, Just heard you got a new google assistant for the Ghost project! Tom ______________________________________________ Tom Harper Lead Software Engineer SightSpeed - <http://www.sightspeed.com/>http://www.sightspeed.com/ 918 Parker St, Suite A14 Berkeley, CA 94710 Email: tharper@sightspeed.com Phone: 510-665-2920 Fax: 510-649-9569 My SightSpeed Video Link:
2006 Oct 24
2
vad changes
Jean-Marc, So I saw in the latest code that the vad in the preprocessor is gone/going to be re-written. Is there a plan as far as this goes? Just wondering as the current one seems to work pretty well. Thanks! Tom ______________________________________________ Tom Harper Lead Software Engineer SightSpeed - <http://www.sightspeed.com/>http://www.sightspeed.com/ 918 Parker St, Suite A14
2005 Oct 25
1
(small) bug in nb_decode?
re: At 03:22 PM 10/25/2005, Jean-Marc Valin wrote: >Are you really sure you didn't have some corruption elsewhere? Totally possible- this is the first time this has happened that I know of in many many hours of usage- On the other hand, this null check isn't in my code base and it was in nb_decode_lost, and nb_encode- so I figured it was just an oversight- Tom
2005 Oct 24
2
(small) bug in nb_decode?
Hi, So I got a crash on the following code: k1=SUBMODE(lpc_enh_k1); k2=SUBMODE(lpc_enh_k2); which in the newer codebase is: bw_lpc(SUBMODE(lpc_enh_k1), st->interp_qlpc, awk1, st->lpcSize); bw_lpc(SUBMODE(lpc_enh_k2), st->interp_qlpc, awk2, st->lpcSize); I am not sure if the newer code will have the same issue but the following check is
2004 Oct 06
4
Cpu bandwidth for Speex on Win32 platforms
At 12:35 PM 10/6/2004, Matthias Granberry wrote: >There is some SSE assembly >language, but it's in GCC/AT&T syntax rather than the windows-standard >Intel syntax, so you might have to do some of your own translation to >something your compiler understands. We submitted an intel patch a ways back- maybe it is in the archives somewhere... Tom -- Tom Harper -
2005 Feb 21
2
speex denoiser adaptation time
Hi Jean Marc & List, So I have been fiddling with the denoiser (again). While poking around I noticed that nb_preprocess is basically a counter that is mod-ded with 100 (the default), which causes Smin[] to be re- seeded with the value in Stmp[] (min of the previous adaptation period). Smin[] is then used to update the noise probability, which is (probably) less likely when adaptation
2007 Jun 09
3
Moving to Git
Hi everyone, I'm currently attempting to move Speex development over to Git. Because Git is distributed, I means that anyone would be able to do development and commits without having to get write access (and I can just pull from them). There are of course other advantages, like sane handling of branches and tags, local history, ... Now, one of the disadvantages is that Git currently
2005 Oct 26
4
small patch for preprocess
Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: preproc_patch_dth_10_26_05.patch Type: application/octet-stream Size: 8774 bytes Desc: not available Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20051026/c27a3ed6/preproc_patch_dth_10_26_05.obj
2005 Nov 11
0
mdf no sound issue
Jean Marc, I ran across the silence issue that results from the echo canceller producing "bad" floating point data. Unfortunately this hasn't been done in a way i can reproduce, but I found that calling reset didn't fix the silence, unless I also reset: st->PHI[i] st->Eh[i] st->Yh[i] So it may be good to add these to the reset function. I was using these in
2006 Jan 05
2
Re: sigsegv in _mm_load_ups (linux/gcc 3.x)
That's definitely strange and I've never encountered that. Normally, the only way for _mm_load_ups to generate a segfault is for the input to be invalid memory, in which case the C version should crash too. I suspect the compiler (or something else) may be hiding the real problem. Can you get a debugger and see exactly what assembly statement is causing the crash and what the operands are?
2006 Dec 06
0
c99 syntax in filterbank_psy_smooth
Jean Marc, So the C99 array syntax is breaking some lesser compilers- is there a known max size for bark[]? Fiddling with latest svn again... Thanks! Tom ______________________________________________ Tom Harper Lead Software Engineer SightSpeed - <http://www.sightspeed.com/>http://www.sightspeed.com/ 918 Parker St, Suite A14 Berkeley, CA 94710 Email: tharper@sightspeed.com Phone:
2007 Jun 09
0
Moving to Git
There is a port to mingw, which is what many folks use now: http://repo.or.cz/w/git/mingw.git I haven't had a chance to fiddle with it yet so ymmv. Tom At 06:00 AM 6/9/2007, Jean-Marc Valin wrote: >Hi everyone, > >I'm currently attempting to move Speex development over to Git. Because >Git is distributed, I means that anyone would be able to do development >and commits
2004 Aug 06
1
speex preprocess redux
I'm not sure if this is due to the same problem, but I get the same clipping behavior when trying to use VAD+denoiser on a particular mic+speaker setup that has significant background noise (enough to really foul up the codec should the denoiser be turned off.) Leaving VAD off and transmitting continuously seems to be the only way to avoid this clipping. Another person I regularly
2005 Nov 18
1
mdf no sound issue
Jean Marc, Ok so I tested with the new code, same result- frame size= 160, filter length=160 ms/1280 samples, 8000 Hz diverged after 9564 calls/packets or 191 seconds. My system stays relatively in synch but is not perfect- difficult to measure if there is any clock drift, but it probably is. In order to make it break faster I use an open air usb microphone that is part of a logitech notebook
2005 Nov 04
3
Compile failure current SVN
Current SVN compilation fails on Win32 (Intel C++ compiler 9.0): ..\..\libspeex\mdf.c(317): error: declaration may not appear after executable statement in block float adapt_rate; Just moved it up to the variable declaration block to solve it locally, but as it's not valid C, I thought I'd mention it ;) PS: With the same compiler, AGC fails horribly (Zlast goes to several
2005 Sep 08
1
ultra wide band packet questions
Hi Jean Marc and List, So I have started finally fiddling around with Ultra-wideband mode. It appears to be very similar in operation to Wide mode, except that when peering into the packet structure it looks like (and these are kind of questions as much as statements here): 1. update rate 0 is not used in UWB- only 1-4? 2. The total bits used for each UWB update rate seem to be as follows:
2005 Oct 25
1
audio preprocess questions
Jean Marc, I have been fiddling around with preprocess to try to get it sounding less metallic/underwater- so based on some things said recently, I have been first fiddling with mean_post and mean_prior to try to get them to do change the update rate, so that update_noise gets called at the right times. Haven't made it too deep into the code, but I have a few questions in speex_preprocess:
2005 Nov 16
2
mdf no sound issue
Jean Marc & list, Following up on this- there seems to be an issue with this calculation in mdf.c (Smooth echo energy estimate over time) Pey += Eh*Yh; Pyy += Yh*Yh; it goes too large for floating point, which seems to be caused by extremely large values in st->Rf[j], st->Yf[j] and smaller values in st->Eh[j], st->Yh[j]- things were relatively quiet
2004 Oct 06
0
speex algorithm
? is there any speex code in place that may help enable variable speed playback ? or perhaps another open source project has some code for this ? variable speed playback for voice messaging is an attractive feature, that would be well recieved for sure ! thx for any reply, Mark Tom Harper <tharper@sightspeed.com> wrote: At 12:35 PM 10/6/2004, Matthias Granberry wrote: >There is
2004 Aug 06
0
speex preprocess redux
Jean Marc, Thanks for the advice. The estimate update may come in handy. I have had some time to play with the adaptation time. I tried making the adaptation time 80, 160 and 320. It seemed like the smaller value was actually the best in my initial testing, but I need to test this against a more noisy setup than I have here. I am guessing that for vad a shorter adaptation time is probably