Login

Saving master page AHEAD time

Serious issues

Re: Saving master page AHEAD time

Postby Cupwise » Sun May 19, 2013 10:22 pm

just to underline how confusing this issue is-
there is a max look ahead length parameter for each program

there is a current look ahead setting parameter for each program

there is a max look ahead length parameter for nebula master

then there is force offset that also somehow has something to do with look-ahead apparently, even though i can leave it alone and still get different look-ahead lengths

do we really need FOUR separate controls just to dictate look ahead? and why can't devs just set this stuff in their program?

why is look-ahead limited to 1.5ms in default master neb config, which isn't enough to be really useful, and why is it limited to 10ms of timed length? both of those things could be set by the program. i just don't get it.
Cupwise
Expert
Expert
 
Posts: 773
Joined: Tue Nov 23, 2010 2:03 am

Re: Saving master page AHEAD time

Postby Cupwise » Sun May 19, 2013 10:43 pm

ok i've done this test, using my rayphlex comp with the same thresh/ratio settings each time, and fastest attack setting each time-

A.wav was done with these settings in the master xml:
<FORCEOFFSET> 1500 </FORCEOFFSET>
<AHEADLENGTH> 1500 </AHEADLENGTH>
then i went to 'edit' and 'glob', turned ahead to 'on' and set ahead to it's max length on that page, which was .687ms. you can see that the look-ahead did not catch all of the snare's initial transient.

B.wav used these settings in master xml:
<FORCEOFFSET> 1500 </FORCEOFFSET>
<AHEADLENGTH> 13000 </AHEADLENGTH>
in edit/glob set the ahead to max length again, which this time was 5.968ms. here you can see that the transients were caught. actually they get caught with a setting around 2ms but you can keep increasing from there all the way up to 5.968.

leaving forceoffset at 1500 didn't prevent me from seemingly getting a full 6ms of look-ahead. maybe forceoffset is related to look-ahead somehow, but i don't see how it can be setting the max look-ahead length.

PS- i hope i don't come off as TOO crazy with these last 3 posts. this issue just really has me confused.. :?
Cupwise
Expert
Expert
 
Posts: 773
Joined: Tue Nov 23, 2010 2:03 am

Re: Saving master page AHEAD time

Postby enriquesilveti » Mon May 20, 2013 9:40 am

I was wrong! From MAST page FAQ

Parameter name: Force offset
Description: When a program is loaded, every waveform is "peak-synchronized". Offset defines the distance between the start of the waveform and the peak position, it is expressed in milliseconds.
MAST page name: OFFSET
Master .XML name: FORCEOFFSET
Factory value (in Master .XML): 1500
Guru extra information: For small values the transient section of the kernel could potentially be windowed in a wrong way.

Parameter name: Look-ahead buffer
Description: This parameter controls the look-ahead buffer used by compressor and dynamic emulation programs in general. It is expressed in milliseconds.
MAST page name: AHEAD
Master .XML name: AHEADLENGTH
Factory value (in Master .XML): 1500
Guru extra information: Increasing this parameter will increase latency.
Enrique Silveti.
Acustica Audio customer and technical support.

MBP 11.5 (i7-4870 | 16 GB | 512 SDD)
SP4 (i5-6300 | 8 GB | 256 SDD)
RME UFX | PS Lyra2 | SD USBPre2
VM U15 | VM W10 | VM OSX 10.12
N4/NAT4 | SPX3 | RX5 | LN2C | Smaart8 | R5 | PT12 | PX10
User avatar
enriquesilveti
Global Moderator
Global Moderator
 
Posts: 2662
Joined: Sun Mar 28, 2010 9:00 pm
Location: Lodi | Madrid | Buenos Aires

Re: Saving master page AHEAD time

Postby Cupwise » Mon May 20, 2013 11:29 am

hmmmm
now i have to wonder if the forceoffset could be useful somehow..
Cupwise
Expert
Expert
 
Posts: 773
Joined: Tue Nov 23, 2010 2:03 am

Previous

Return to Bugs

Who is online

Users browsing this forum: No registered users and 4 guests