Volume automation latency issue (BUG)

[sintil8]

IMHO.
I dare say there are other situations where this could also impact. But for what I do and the amount of effort to silence a beat from playing is a lot of small repeating tasks from what I can see. I would just use the mute tool in the midi editor panel, but then I probably don't do the style of mixing in the Daw you are doing.

I can however see your need to have this work as expected tho' if that is your usual way of working.

Hope this gets sorted if it helps. kindest regards

 

[Navar]

But for what I do and the amount of effort to silence a beat from playing is a lot of small repeating tasks from what I can see. I would just use the mute tool in the midi editor panel, but then I probably don't do the style of mixing in the Daw you are doing.

It's not only about muting the beat itself it's also about muting the FXs in the chain. Sometimes you wanna have dead silence.

Funny addition: if I automate the output of "Impact" then sometimes it's silent and sometimes not.

 

[nofolobricity]

Funny addition: if I automate the output of "Impact" then sometimes it's silent and sometimes not.

I checked right now. Same thing . Maybe FSP is just so advanced that it randomly introduces 'analog gear imperfections' to keep things organic

 

[sintil8]

I have been trying to examine this from timing and midi ticks 1 tick =20.83 mil/secs @ 120 BPM according to googlies.

What I did discover and whilst maybe not ideal for everyone, in the track Inspector you can put a track delay of around 5 mil/sec upwards, and the muted (Fader control) note attack will disappear.
This might not be a good solution, but offers an indication what is misfiring.

Kindest regards