Logic Pro 9 2 issues (CC4 reset and Virtual VTR)

Hi,
I am finding that Logic sends out a 0 value on stop when using CC4. Anybody know a way for this to either be turned off, or disabled somehow. As it stands the solution is to use another CC for the fader control it's assigned to, but that means a couple of hours of reprogramming a rather large Logic template.

Second, anybody use Virtual VTR and can give me some time to ask a few questions about it? If so, please PM me.
 
Hi George,
Did you try to disable the CC chase in the Logic midi settings? There were a few CC# chase ranges in that dialog as far as I remember (I'm away of Logic at the moment), so disable the lowest range where CC3 belongs to
or disable all CC# just for the test.
Regards,
A.G
 
Upvote 0
Yea, we tried that. It still went to 0 and made the faders we wanted to control essentially shut down... no audio. It almost seems that it's stuck in the "on" position as for as the chase function goes.
 
Upvote 0
Hi George,
Today I was away of my Logic and could not try that. All the time I was sure that CC4 was working properly in the former Logic versions. I just tested that scenario on my PC laptop using L5 and it works fine without sending zero reset during transport stop. After that I tested it on L8 & L9 and it matches your issues. As a whole CC4 is a foot control and I guess Apple decided to change its behavior to linear. I.e all messages behave as 0 ->Current message (something like the bypass step automation).
Your original idea of CC# transform is still valid and I do not think it's hard cause it requires just one transformer patched before the external instrument object. You can use CC12 for example and transform it to CC4 in the transformer and set up the transformer as a track header object.
Have a look at the image below.
Regards,
A.G
 

Attachments

  • cc12_cc4.png
    cc12_cc4.png
    15.4 KB · Views: 161
Upvote 0
Back
Top