


an audio channel that has it's input set as the output (post mixer) of the midi channel. This is where the bar long midi note is triggered.Ģ. a midi channel with an external instrument plugin, these generally have 7-8ms of latency set. I've tried power cycling with the USB cable plugged in, still can't get it working.Ībleton set up: Delay compensation and reduced latency while monitoring are turned on. I understand there is a bug with USB midi in this version that we're waiting to be resolved. I've tried to get it working with USB midi to sanity check but I can't seem to get it working. Pro 3 has latest firmware installed: 1.1.0. For it to be "in time" it must show each note of the arpeggiator as being on the grid in the resultant audio recording.
Midi multiclock Patch#
This is weird.īy "in time" I mean that the audio signal that gets recorded in Ableton is on the grid when I use a basic patch with arpeggiator and trigger it with a bar long midi note from Ableton. The Pro 3 needs an offset of "+1ms" to be set on the ERM in order for it to be in time. There are other synths also clocked by the ERM and all have an offset between +30 to +49 as is to be expected. There is a Prophet 08 also being clocked by the same ERM multiclock at the same time, in order to be in time it's offset is set at +49ms. This means that we would expect any synth clocked by the ERM to need an offset set on the ERM of around +50ms or a little less in order to account for latency. The ERM is sent an audio signal from Ableton as it's master clock, on a track that has a -50ms delay. The Pro 3 is being clocked via midi din from an ERM multiclock. I've looked through the previous posts here and nothing seems to cover it, so I've created a detailed bug report. Firstly, I love this synth! However I am having some weird sync issues with the Pro 3.
