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

 

[nofolobricity]

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.

Nice catch, sintil8! That pretty much proves the automation engine and MIDI/audio are out of sync by a few milliseconds.
While adjusting Track Delay for dozens of channels is way too tedious for real-world projects, this is a huge clue for the devs. This definitely needs to go into the ticket to show them where the math is breaking down. Thanks for digging into this!

 

[sintil8]

Nice catch, sintil8! That pretty much proves the automation engine and MIDI/audio are out of sync by a few milliseconds.
While adjusting Track Delay for dozens of channels is way too tedious for real-world projects, this is a huge clue for the devs. This definitely needs to go into the ticket to show them where the math is breaking down. Thanks for digging into this!

IMO,
To me this should be examined from the, automation, point placement rather than a clock being out of sync?
When the data points are created, they are made after or on a beat or quantize point. Those very same data points do not display any timing data for where they sit on the timeline, so split second timing is not shown or easily adjusted?
QED.
In other words...It is up to the user to place them wherever they choose.
The method of highlighting the area followed by adjusting the level might be worth looking into as a process, as it is not working as you want/need. Also, this offset might be due to the order of midi processing. It's important to look at what other factors could be in play.

I hope you might consider the above if you submit a ticket.

Hope this helps, kindest regards.

 

[nofolobricity]

I hope you might consider the above if you submit a ticket.

I get your point, sintil8, but the whole purpose of a grid in a modern DAW is that snapping to it should work accurately. We shouldn't have to manually guess micro-offsets just to make a basic volume cut work. The engine should handle the math, not the user. But I appreciate the input, and all these theories will definitely be useful context for the ticket!

 

[sintil8]

I look forward to FSP update logs to see if this is addressed in some way.
I have a mountain of things to get on with, so please excuse me from further comment.
I hope it gets resolved to meet your needs.

Kindest regards