Before C15, “Track Delay” could be + or -. Now, with the new Attack Compensation setting in the Expression Map setup, only + values are allowed (per articulation), where track delay previously required a - value to move the onset of sound earlier. Consistency problem? The global Track Delay is still present, so if both are set to 100, (-100 and 100 respectively) does that equal 200 ms delay? Can’t find help in the manual.
Also, the Attack Comp doesn’t seem to work properly on the Celli and Basses instruments of Iconica Sections & Players. If an attack comp is set for either on, say, Sustain or Legato articulations, going from staccato to sustain or legato seems to disable the held aspect of the note and truncates a whole note into an eighth. Doesn’t seem to affect violins or viola. Bug, or is there something unique about lowest strings?
We had a detailed discussion to work out the best naming and numerical convention, and we decided to call it ‘Attack Compensation’ and not ‘delay’ or ‘pre-delay’, and to ensure that it used only positive numbers to reduce potential confusion. A positive value for the attack compensation will cause the notes to start earlier, so it if you have a 50ms attack compensation and a track delay of -100 then this means notes will be started 150ms earlier.
For the issue you mention, could you attach a project that shows the issue?
Ok, understood, but still confusing. We’ve all been using neg vals, now inverted. Oh well.
Can’t upload the project, file too large (19.7 Mb). Note: the project was originally created in Nuendo 14. I installed Cubase 15 on the same machine and open the Nuendo project in Cubase. Seems to work, but who knows if there are conflicts. When I save the project when in Cubase, it does not create a .cpr file, it remains a .npr file & opens (successfully) on either platform. I use save, not save as. Still, the prob only affects the low strings. All other instruments work as expected.
Negative values can still be used for delay because a positive delay means increasing time. Part of the hope of using a positive value for latency compensation is to reduce confusion because it’s only possible to use a positive value.
I won’t need any audio, just the npr/cpr file. You might find it zips up quite small to send in a DM, otherwise are you able to upload to Google Drive, OneDrive, Dropbox etc?