robertmderosa Posted August 15, 2017 Share Posted August 15, 2017 Hi all, This issue is driving me crazy! I just picked up a Helix Rack and installed firmware v. 2.21 and do not have an expression pedal. I'm mainly using this to record. Whenever I boot up Logic X, expression pedal 2 which is assigned to the volume pedal block on all default patches, immediately drops to 0%. If I manually pull it back up in the editor on the computer or on the rack unit itself, within a couple seconds it will go back to 0%. It seems the only solution is to either turn off the volume pedal block or change the associated expression pedal. This is not an issue when Logic X is not open. Does anyone know if this is a Logic X issue and if there is a way to stop it? If not, is there a way to globally assign anything using expression pedal 2 to another pedal? Will buying an expression pedal fix this issue? I would like to avoid going through each patch and either reassigning or deleting the volume block. Thanks! Quote Link to comment Share on other sites More sharing options...
Digital_Igloo Posted August 15, 2017 Share Posted August 15, 2017 EXP 2 globally responds to MIDI CC#2; maybe Logic is spitting that out? Also try turning Global Settings > MIDI/Tempo > Knob 2 (MIDI Thru) to "Off," just in case there's a MIDI loop somewhere. 1 Quote Link to comment Share on other sites More sharing options...
jbuhajla Posted August 15, 2017 Share Posted August 15, 2017 Hi all, This issue is driving me crazy! I just picked up a Helix Rack and installed firmware v. 2.21 and do not have an expression pedal. I'm mainly using this to record. Whenever I boot up Logic X, expression pedal 2 which is assigned to the volume pedal block on all default patches, immediately drops to 0%. If I manually pull it back up in the editor on the computer or on the rack unit itself, within a couple seconds it will go back to 0%. It seems the only solution is to either turn off the volume pedal block or change the associated expression pedal. This is not an issue when Logic X is not open. Does anyone know if this is a Logic X issue and if there is a way to stop it? If not, is there a way to globally assign anything using expression pedal 2 to another pedal? Will buying an expression pedal fix this issue? I would like to avoid going through each patch and either reassigning or deleting the volume block. Thanks! I am not familiar with Logic X. Do you have any midi CCs programmed in that software? Midi CC#1-3 control the expression pedal inputs on Helix. If you are sending CC #2 with a value of zero, you are commanding EXP2 to zero. 1 Quote Link to comment Share on other sites More sharing options...
robertmderosa Posted August 16, 2017 Author Share Posted August 16, 2017 THANK YOU BOTH! It definitely is a midi cc Logic X is sending out. When I go into Helix global settings and turn off Midi Over USB, the issue stops. Now I just need to trace where it's coming from... :D 1 Quote Link to comment Share on other sites More sharing options...
tedulrich Posted August 16, 2017 Share Posted August 16, 2017 THANK YOU BOTH! It definitely is a midi cc Logic X is sending out. When I go into Helix global settings and turn off Midi Over USB, the issue stops. Now I just need to trace where it's coming from... :D There's an app simply called "MIDI Monitor" for Mac that has helped me troubleshoot stray MIDI signals causing issues between Logic and Helix. It's free, and simple, and I've solved more than one issue with it. It's worth having on your machine. 1 Quote Link to comment Share on other sites More sharing options...
robertmderosa Posted August 29, 2017 Author Share Posted August 29, 2017 Thank you! Meant to log on sooner but haven't had time. Was able to trace it in logic using MIDI Monitor and turn it off. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.