mes wrote:
right but I'm talking about the drawn automation itself being delay compensated...not the output of the machines. would that still work? I understand Buzz and other music programs have machine delay compensation, but some don't also take into account the drawn automation when fixing the latency...so all the envelopes end up being off by however many samples/milliseconds the buffer is set to...and even more problems when you have a high latency plugin in the chain before the machine being automated. Ableton Live still has this problem and people have complained about it for years, but Renoise does this properly.
thank you for explaining... I was confused until now.
To delay a peer data signal, we can't use delays (since they are for audio signal) so forget what I wrote earlier...
but if you want to delay a peer signal, can't you just manually start the envelope a bit later?
the peer controllers I use they have triggers or manual lfo settings which you can control a cycle (start/offset, etc) completely.
So, you could use subticks in a peer pattern (for trigger), as a delay. x subticks into pattern, you trigger the envelope - thus the envelope starts x subticks later...
would that work with your desired machine of use?