Please ensure Javascript is enabled for purposes of website accessibility Jump to content

bpaluzzi

Members
  • Posts

    5
  • Joined

  • Last visited

Profile Information

  • Registered Products
    3

bpaluzzi's Achievements

Rookie

Rookie (2/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare
  • Conversation Starter Rare

Recent Badges

0

Reputation

  1. Hi - Apologies if this has been answered before -- I tried searching, but didn't find any hits. I'm trying to set up MIDI CC messages (sent to the HX Effects) that will exactly duplicate the 6 footswitch looper. The CC values in the manual require you to send one of two MIDI CC values (e.g., 1/2 speed is CC 66, any value 64-127; full speed is still CC 66, but a different value [0-63]). This is different than the front panel buttons -- I hit the same switch to toggle between 1/2 and full, but with CC control, it's required to keep the "toggle" state stored externally. Is there any way to exactly mirror the footswitch behavior? In the example above, I'd want any value sent to CC 66 to toggle the current 1/2 / Full speed status. E.g. -- first CC 66, value 0 message switches to half-speed, the second CC 66, value 0 message switches to full speed. This is the way that the footswitch CC messages (CC 49 to CC54 for switches 1-6, respectively) work -- if you send any value to CC49, it toggles the current status. Unfortunately, even when the 6-switch looper is in focus, the footswitch CC don't trigger it. Context: I'm a drummer, and trying to duplicate the footswitches with a drum multipad, so that I can easily control the looper with sticks in my hand. I'm using the DTX Multi 12, which is the most powerful MIDI controller available for this type of functionality, but it unfortunately only allows you to send a single CC # and value per pad. Any thoughts? Any secret way of sending a "toggle" value on dedicated looper CC? Or any way to get the footswitch CC to be "active" when the looper is foregrounded? Thanks in advance!
  2. So after doing more testing with this, I've come to the somewhat unbelievable conclusion that it's not possible to duplicate the function of the two on-board looper pedals - you need 4 external pedals to get the same functionality. Yes, it's my fault for not examining the MIDI spec more carefully before purchasing, but my goodness, why would Line6 choose such a bizarre midi implementation?
  3. 1 - issue midi command "record" to start loop playing 2 - issue midi command "overdub" to start overdub #1 3 - issue midi command "overdub" to stop overdub #1 4 - issue midi command "overdub" to start overdub #2 5 - issue midi command "overdub" to stop overdub #2 6 - issue midi command "overdub" to start overdub #3 7 - issue midi command "overdub" to stop overdub #3 8 - issue midi command "stop" to stop loop In this instance, there are two problems if you use an external toggle First of all, steps 3, 5, and 7 would be issuing "record" instead of overdub, which won't work Secondly, step 8 would issue "play" instead of stop. There is knowledge "in the system" about whether overdub/record or start/stop is the applicable function. Since only one of these commands *can* be used at a time (i.e., calling "overdub" when the system expects "record" means nothing happens), it's absolutely mind-boggling that line6 chose to separate these into separate control changes.
  4. Toggle externally won't work, though. The function for footswitch one won't go "record", "overdub", "record", "overdub" etc. It'll be "record", "overdub", "overdub", "overdub", "overdub" I can't imagine for the life of me why Line6 designed it this way, especially as the "alternative" functions for each controller are absolutely dead when it's not their "turn" to be called (e.g., if you hit "overdub" when no loop is playing, the system does nothing) In short, on the board, you use two pedals. Externally, you need four pedals, but only two can ever be used. What the?? ;-)
  5. Hi - Wanted to see if it was possible to control the looper via MIDI so that the external pedals act like the on-board pedals. What I mean by that: on the device, you have two pedals - one for record/overdub, and one for play/stop. If you hit the first pedal while no loop is playing, the m13 knows to issue the "record" command If you hit the first pedal while a loop is playing, the m13 knows to issue the "overdub" command Similarly for the stop / play pedal. However, in the MIDI implementation, record, overdub, play, and stop require 4 different CC messages to be sent. Is there a way to issue the "toggling" command via MIDI (i.e., one CC message for record/overdub, which is correctly interpreted based on the current status of the device) Thanks so much for your help!
×
×
  • Create New...