Skip to main content

Latency compensation does not work

Posted

Hi there,

just trying to use the latency compensation to tighten some lazy spiccato-samples, but whatever value i type in there....nothing changes.

Neither the per Instrument nor the per channel latency compensation does have any affect at all.

Is it a bug or do i miss something here?

Thx

Seb

 


Sat, 2018-10-20 - 13:20 Permalink

Neither the per Instrument nor the per channel latency compensation does have any affect at all.

There is no latency compensation in Synfire. So this isn't a bug and I don't know what you're referring to with this statement. 

 

When using latency introducing plugins your best bet is to combine SF with a Rewire capable application or Vienna Ensemble Pro.

Syncing with Midi Clock is more tricky when high latency comes into play but has it's upsides as well...

 

 

 

Sat, 2018-10-20 - 15:02 Permalink

There is a manually adjustable latency compensation. You can set it globally per rack instrument or individually for each midi channel within a rack instrument. I can post a screenshot later.

Sat, 2018-10-20 - 15:26 Permalink

There is also an option to ignore latency compensation, it's one of the parameters per instrument but cant rememebr where, so make sure this isnt ticked.

Sat, 2018-10-20 - 16:10 Permalink

There is a manually adjustable latency compensation. 

 

Ah, alright. I thought "PDC" like in other DAWs, which is usually full automatic.

Manual without at least "Latency Groups" doesn't make too much sense to me, as this is an always changing variable. 

 

(If it gets saved with the preset /rack though and you only need to set it once, I don't get why this can't be automatically calculated

and needs just a ​'Global Latency Compensation On/Off'  tick box?)

Sat, 2018-10-20 - 16:13 Permalink

just trying to use the latency compensation to tighten some lazy spiccato-samples

You can also try to shift stuff around in time with the "Shift" Parameter.  If you don't use it for anything else, it can double as "Latency Compensator".

 

Sat, 2018-10-20 - 16:51 Permalink

Latency is a setting of the device description telling Synfire how long it takes for the synth or plugin to respond to MIDI input. It is up to you to find out which value works best for a particular sound. If latency compensation is enabled, Synfire will render MIDI notes earlier (expressed in milliseconds) to compensate for the delay.

This is great for playback, but once you export to a file or drag & drop to your DAW, you may want to disable the compensation, so your MIDI data shows up correctly quantized on the DAW's piano roll or notation sheets.

Sat, 2018-10-20 - 17:06 Permalink

Thank you all for your comments and thoughts. So far i didnt find a switch to turn it on or off. Need to check the workaround via shift as well.
Andre,  could it be that the function is not working as desired? i found out if i put in a very high value (eg 2000ms) for only one instrument, the whole playback will be delayed by this value not just the one instrukment. So far all my instruments used are part of a global rack.

 

Sun, 2018-10-21 - 12:49 Permalink

There are two latency settings, one per device and one per sound (fixed-channel sounds only).

If you set one per device, it will affect all sounds on that device.

(image upload is broken currently, will try and and fix)

Sun, 2018-10-21 - 14:54 Permalink

Hi Andre,
i'm aware of the two different settings. It simply does not work here.
I set up two new rack modules, each module with a fixed channel sound.
If i put in a latency value in only one of the rack modules, it will affect the playback of both rack modules.
For example, if i try it with a very high numer (eg 2000) an press play, the playback is delayed  or 2 seconds and then all sounds of all racks will played simultaneously.
Does it work in another way in your setup?

Best,
Sebastian

 

 

Thu, 2018-11-08 - 12:38 Permalink

Sorry for my late reply. Latencies are considered to estimate the amount of pre-roll for playback, but individual notes don't seem to be shifted against each other. Either the original intention was to do something else, or it's a bug. Added this to the bugfix list.

Thu, 2018-11-08 - 14:26 Permalink

It would make sense to have the manually set latency affect all notes on that particular channel.
As mentioned before, i would use it to tighten up the timing of spiccato samples which have a slow attack.