Edited by Bob Bone - Original subject line (put here because I wanted to add CWBRN to subject and there wasn't enough room):
 
"Automating arpeggiator on/off still broken - also bounce arpeggiator to clip not accurate "
 
I noticed this back in X2 and gave up on the idea, but now I really need to use it and had hoped it was fixed in X2a, alas not. I have a vague recollection of filing a bug report back then but not 100% sure. 
 
Basically, automating the arpeggiator's on/off button only works if the MIDI track in question is selected. If it's not selected, then either the automation won't work at all or it will work but your on/off envelope will be offset by a few bars. This means you can only hear the automation if you have the track selected during playback. If you have more than one track on which you want to automate the arpeggiator, forget about it. 
 
Also, bouncing the arpeggiator's output to a MIDI clip doesn't work so well. It sort of does, but the MIDI clip that you get is usually slightly different to what you get from just having the arpeggiator turned on. I guess you can theoretically edit the MIDI clip to get it to sound the same, but that's sometimes a very laborious and complicated thing to do. 
 
All of this is really frustrating. I'd played a MIDI bass line on the keyboard and happened upon an arpeggiator preset that really transformed it into something magical. I don't want it to arpeggiate throughout so I tried automating the on/off button, which off course doesn't work properly. So I bounced it to a MIDI track and the result is just different enough to ruin the groove that the arpeggiator was rocking. Hope all this gets fixed in X2b or X3. Will file a bug report. 

Frustrating to say the least.
 
There is a simple workaround of course, just isolate the notes you want arpeggiated and move them to a new midi clip, set the input to the same synth & switch on the arpeggiator

Ha, that's an idea!

Great workaround!

Great work around...pity it's another work around needed, when things like this should be fixed by now.

Great workaround, but nobody spotted the deliberate mistake.
 
You set the OUTPUT of the 2nd Midi track to the synth, not the INPUT  

I knew that's what you meant. Just didn't want to call you out on it!

So this still seems to be broken in Sonar Platinum Gloucester, so it's been broken for years now.
 
In short if you create a midi track and put a single note on it and turn on the track Arpeggiator and then do a bounce to clip, the clip changes to the arpeggiated version.  But if your clip has say Arpeggiator Rate animated with a curve, when you do the bounce the Arp effect is turned off, but the resulting MIDI is the same as without the animated rate change.
 
Here's screen shots:

This is just a simple MIDI track with one note and the Arpeggiator turned on with the default settings.
If you bounce that to a clip (right click, bounce to clip) you get this:

So that's good, but then if you undo and add an animation to the Arp rate like this:

And bounce it to a clip you get this:

Which is wrong the note lengths should be changing (and do with playback before the bounce).
 
 
 

Please log here and post CWBRN.
https://www.cakewalk.com/...Contact/Problem-Report

Host please move to problem reports forum.

They have had many,many years to fix this, logging the problem won't help and will only waste my time.  Moving this  post will only hide it (and it's been here for years).  Reporting and moving this post are not solutions to this huge problem with how bouncing clips and automation work.  A Cakewalk employee can easily verify this and create their own bug and fix it.  That's what we need.  Not shuffling forum posts around and not (hidden to public) bug reports (of which there must already be dozens on this issue).