search for: lookaheads

1. What to do with the last frame that is smaller then frame size? During encoding, the last frame is often smaller than the required frame size. In the sample code, proper number of zeros are padded at the end. So if I don't want those padded zero after decoding, I assume that it is up to me to keep track of the number of zeros. Is it right? 2. What does SPEEX_GET_LOOKAHEAD do? How to

I believe if you add the *decoder* lookahead time to the encoder lookahead time you are already referencing, you will get the numbers that you have calculated. --John On 4/11/2012 1:00 PM, speex-dev-request at xiph.org wrote: > Message: 1 > Date: 10 Apr 2012 22:07:20 +0200 > From: Thilo K?hler<koehlerthilo at gmx.de> > Subject: [Speex-dev] Speex Codec Delay Problem > To:

https://bugzilla.samba.org/show_bug.cgi?id=9812 Summary: Lookahead file-list loading and comparison Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: me at haravikk.com

Hi, I was hoping to get some clarification on the meaning of algorithmic latency in Speex. For wideband signals, algorithmic delay is specified to be 34 ms (20 ms is the frame size and 14 ms is the lookahead). Does this number (34 ms) account for the double-buffering on the input? Assuming that the computation time and sound wave propagation time are negligible, should I expect compressed

Hello R experts, I have two questions related to the nnls library (http://www.inside-r.org/packages/cran/nnls), and more broadly to linear regression with positive coefficients. Sample code is below the Qs. Q1: Regular regression (with lm) gives me the significance of each variable. How do I get variable significance with nnls? If there's no ready function, any easy way to manually derive

Hello All! SPEEX introduces an additional delay to the audio data, I found out by reverse enginiering (it is NOT the lookahead time): narrow band : delay = 200 - framesize + lookahead = 200 - 160 + 40 = 80 samples wide band : delay = 400 - framesize + lookahead = 400 - 320 + 143 = 223 samples uwide band : delay = 800 - framesize + lookahead = 800 - 640 + 349 = 509 samples To get the

Jean-Marc, What exactly does the speex code do to calculate the granulepos? With vorbis it's the 'count of decodable samples including this packet'. So if you had a packet that allowed you to decode 1024 samples since the beginning of playback, the granulepos is 1024, not for example 1023 which would be the *index* of the last sample assuming C-style array indicies starting at

Speex tells me that the decoder is always 5 ms, but it says that the encoder is 5 ms for NB, 8.9375 ms for WB, and 10.90625 ms for UWB. Is there an extra frame of delay in the encoder that isn't otherwise accounted for? John Ridges Jean-Marc Valin wrote: > Quoting John Ridges <jridges at masque.com>: > >> I also need to know the precise delays from Speex but I used

On 2015-12-18 02:29, Simon Urbanek wrote: > Michael, > > I got access to PDP AIX so I can try to replicate your problem. Can you, please, share exactly your setup - AIX version and well as how exactly you installed the compilers (=where from)? I can then try to replicate it. AFAICS there is no official binary for gfortran nor gcc 4.7 so it must be some 3rd party - which could also be a

Hello List, ? I have a dataset consisting of strings that I want to split while saving the delimiter. ? Some example data: ?leucocyten + gramnegatieve staven +++ grampositieve staven ++? ?leucocyten ? grampositieve coccen +? ? I want to split the strings such that I get the following result: c(?leucocyten +?, ??gramnegatieve staven +++?, ??grampositieve staven ++?) c(?leucocyten ??, ?grampositieve

On Sun, Jun 19, 2005 at 08:07:50PM -0400, Jean-Marc Valin wrote: > Hi Ralph, > > What speexenc does (Speex itself does not know about Ogg) is that it gives > packet N the granulepos "N*frame_size - lookahead". In the case of narrowband, > the first frame would have granulepos "1*160 - 80", so 80. I can't say about > your example because Speex cannot

Jia Pu a ?crit : > 1. What to do with the last frame that is smaller then frame size? > During encoding, the last frame is often smaller than the required frame > size. In the sample code, proper number of zeros are padded at the end. > So if I don't want those padded zero after decoding, I assume that it is > up to me to keep track of the number of zeros. Is it right? Right.

Hello! I am encoding small snippets of audio (e.g. 100ms) that contain important audio from the first sample till the last one. (means they dont start/end silent). Doing so raised a couple of questions I couldnt solve by reading the docu/faq/internet search. 1. Does the "complexity" parameter influence only the speed of the encoder or also the speed of the decoder? (I need fast

Am 04.02.2015 um 12:31 schrieb Timothy B. Terriberry: > M. Pabis wrote: >> 1. Each thread deals with frames from intra frame up to next intra frame >> - 1; > > This works if you know where the intra frames are. Could this information be gathered by having one thread encode a downsampled version of the input video sequence, or would this be a bad predictor? Who knows,

> >> 2. What does SPEEX_GET_LOOKAHEAD do? How to use it? >> In speexenc.c, there is following code: >> >> ... >> speex_encoder_ctl(st, SPEEX_GET_LOOKAHEAD, &lookahead); >> ... >> nb_encoded = -lookahead; >> >> Can someone explain what this means? > > The lookahead is the number of samples you need to discard at the > start.

I installed the Syncpeople textmate bundle ( http://syncpeople.com/downloads/syncpeople_on_rails_features ) and the commands all work from the menu, but the short-cuts never work for any of the snippets or commands ever work, because the scopes are not being selected properly. If I change the scope to just "source.ruby" it will work fine. But I cannot see why their scope selectors do not

JM, I also need to know the precise delays from Speex but I used the SPEEX_GET_LOOKAHEAD control requests to determine them (plus the "speex_resampler_get_output_latency" function from the resampler). The returned values from the Speex lookahead request don't seem to match with the values you gave Alexander. Am I doing this wrong? Thanks, John Ridges speex-dev-request at

hi there, I am new to mailing list so excuse me if I don't obey to the 'netiquette'. i am writing voice chat and speex is in the root of it. i write it in Java and use JNI to link with 'C'-based Speex 1.2beta. [I know of JSpeex but there are not implemented some features] recently i decided to use DTX feature of speex as well. the code follows. The problem is that no matter

Hi, I am using speex 1.2beta2 on a 24bit DSP that has a severe program and data space limitations. I am only interested in the speex decoder for 11kbps narrowband implementation. I am using the following parameters and structures 160, /*frameSize*/ 40, /*subframeSize*/ 10, /*lpcSize*/ 17, /*pitchStart*/ 144, /*pitchEnd*/ /* 11 kbps medium bit-rate

Hi Ralph, What speexenc does (Speex itself does not know about Ogg) is that it gives packet N the granulepos "N*frame_size - lookahead". In the case of narrowband, the first frame would have granulepos "1*160 - 80", so 80. I can't say about your example because Speex cannot encode a frame of one sample, which is a good thing becuse otherwise, the granulepos would be -79.