Bug (audio glitch with automation) : U-he synths return audio a few samples prior to receiving MIDI notes !
-
- KVRist
- Topic Starter
- 37 posts since 18 Mar, 2012
The issue is not the automation accurate. The issue is : the synth sends audio before the MIDI note-on.
-
- u-he
- 30216 posts since 8 Aug, 2002 from Berlin
Yes it does. But to me, it's a solution, not a problem.Pere Founasse wrote: Tue Mar 19, 2019 9:10 am The issue is not the automation accurate. The issue is : the synth sends audio before the MIDI note-on.
-
- KVRist
- Topic Starter
- 37 posts since 18 Mar, 2012
It can be an issue.
For exemple, in this exemple, before each measure, we can listen a glitch (MIDI notes don't start before the measure). The synth is not automatised. Only the parent volume track is automatised.
For exemple, in this exemple, before each measure, we can listen a glitch (MIDI notes don't start before the measure). The synth is not automatised. Only the parent volume track is automatised.
-
- u-he
- 30216 posts since 8 Aug, 2002 from Berlin
-
- KVRist
- Topic Starter
- 37 posts since 18 Mar, 2012
When you use lots of automation, it can destroy the workflow : you have to check when the issue occurs, you have to add more automation points if you want to keep a clean structure with region and measure (I use automation items).
Too, I will have to make some tests to see what is the good automation delay and fight with the random glitch. When I will move region, one part of the delayed automation will not be moved.
Plus, it can appear disorder/not very logical to see the automation starting before the note played or not starting exactly on the grid.
Same thing for the note which doesn't start at the grid. If I open an old project i could think than one automation delayed is wrongly placed and moved it.
Psychologically, it can be perceived like handiwork/not accurate/dysfunctional .
Why not propose two options (+/- 8 samples and classic way) to solve this issue ?
Or maybe not apply this "dispatching" (-8 samples) at the start of a midi note (my preference) ?
Too, I will have to make some tests to see what is the good automation delay and fight with the random glitch. When I will move region, one part of the delayed automation will not be moved.
Plus, it can appear disorder/not very logical to see the automation starting before the note played or not starting exactly on the grid.
Same thing for the note which doesn't start at the grid. If I open an old project i could think than one automation delayed is wrongly placed and moved it.
Psychologically, it can be perceived like handiwork/not accurate/dysfunctional .
Why not propose two options (+/- 8 samples and classic way) to solve this issue ?
Or maybe not apply this "dispatching" (-8 samples) at the start of a midi note (my preference) ?