I have posted this question before, hopefully someone can give me an answer, or I think it's time to change DAWs.
Logics arp doesn't seem to work in real play time. When changing from one note to the other on midi controller, the arp pattern is always delayed/late of the change. Why? Does anyone have a solution to this? it's driving me nuts!
It might be the Snap To value in the Arp module. Set this to something like 1/4 notes if you want it to trigger on beats, or to 1/1 if you want it to trigger on the start of each measure. You get to this in the Environment by clicking on the Arpeggiator module - the parameters will then display in the box on the left.
Thanks very much for trying, I tried that stuff ages ago to no avail.
Surely someone has a solution to this problem? I've spoken to others using different editions of logic and they have the same issue. Is Apple aware of this fault? Moderators?...
Hi Miles,
When you say the pattern is always delayed/late of the change, what exactly do you mean? Is it just the first note that changes later than you want it to (which might be because it's waiting for the next snap value), or is the whole pattern running behind the beat, ie not properly in sync?
It's the first note, and it's delayed by exactly one note. For example in a 8th note pattern it will change one 8th note late, but then I guess that is actually affecting the whole pattern because every time a new note is pressed it's going to delay the whole pattern by a 8th note.
Just curious.. what are you driving with the Arpeggiator, the sound source?
pancenter-
If by soundsource you mean softsynth? If tried it with every logic bundled synth and and many 3rd party softsynth plugins. Have also tried it with caps lock function, so I know it's not my midi controller causing the problem, but rather a fault in Logic.
Miles Allen wrote:
If by soundsource you mean softsynth? If tried it with every logic bundled synth and and many 3rd party softsynth plugins. Have also tried it with caps lock function, so I know it's not my midi controller causing the problem, but rather a fault in Logic.
Yes, that's what I meant by Soundsource.. but I was thinking of the "other side" not an input controller type problem.
Next question... have you tried it with an external MIDI device using an external MIDI track. (if you even have one)
If you do, I think you will find the problem does not exist and that the fault lies with the way Logic buffers audio internally. Especially softsynths and the manner in which a softsynth track must be "Live" for input.
This is the way Logic is designed, it's very efficient but there are drawbacks.
What would help is an Arpeggiator upgrade, get it out of the environment and into a MIDI plugin.
pancenter-
I'm not sure what an external midi track is? I have been using the arpeggiator function on my midi controller as a work around for the moment.
An external MIDI track drives an externam MIDI sound module or synthesizer...as opposed to a softsynth internal to Logic.
Anyway, Logic's Arpeggiator is probably 20 years old and due for an update. Maybe Logic X, who knows.
pancenter-
Logic Arpeggiator woes
