I am absolutely willing to start over to get it right! I have to be honest though much of what you described in your strategy is over my head. However I am so open to learning and prefer to implement the strategy you think is best if you are willing to help me through it a bit 🙂
I will answer your questions here… after doing so I will map out in very specific detail everything going on in my project with screenshots as there are a few other things at play to make the looper work. I want to be as clear as possible.
Lastly i can upload my ableton project file if it helps
to quote:
1) What incoming CC and value do you use to start each looper?
CC 1,3,5,7,9,11,13,15 ( each value comes from a different pedal and are sent to a different looper… 8 total… 8 pedals, 8ccs, 8 loopers) are sent from my pedal with a value of either 127, 0 or 1 and are tied to the play button on looper. (play triggers at any value)
There was an original strategy here tying the same ccs to mutes but that later was abandoned as the mutes on the loop chains got added.
all values trigger play and they are being sent from my pedal ( nektar pacer ) in a toggle state.. this keeps the LEDs on pacer in sync with the state of the loopers.
What is the outgoing CC and value?
The outgoing CCs where translated in bome so that If any of the incoming CCs came in Bome would send all other plays button CCs out. so that all loopers started on the first press of any loop.
It looks like you are using CC30 and CC40 to stop and start two different “Loop chains”
CC 30 sends 127 to 32-39 to start chain 1
CC 40 sends 127 to 42-49 to stop chain 2
Yes the reason for this is to fix a problem that arose with my original plan.
the original plan was
-send a CC from pacer in a toggle state
-translate it in bome to send all the other CCs that would play all loopers.
-Tie that same cc to the mute of the track that looper was in.
this would tie the mutes to the value of that CC so that they stayed in sync with the LED on the pedal.
However I later realized that my audio inputs would mute as well so I came up with the loop chains idea.
How it works now is
CC#32-39 are tied to loop chain 1 mute button in each track
CC#42-49 are tied to loop chain 2 mute button in each track
the values are reverse in my pedal so that when say CC32 value 0or1 is sent so is CC42 value 127.
they are tied to the mutes on the loop chains so that when one is muted the other is unmutes.
-looper is in loop chain 1
-no looper in loop chain 2
this allows for the looper to mute but allows for the audio input to always be coming through so when i mute looper the audio input is unaffected and maintains.
-the translators CC30 and CC40 in bome are CCs that are sent on preset load.
-there are 2 presets in my pacer ive made. all play and all stop.
-CC30 at 127 and CC40 at 0 will send on “all play” preset load will translate through bome to fire all loopers on. and on “all stop” preset load will do the opposite to shut all loopers off.
2) What incoming CC and value do you use to mute each looper?
3) What incoming CC and value do you use to unmute each looper?
CC 32-39 value 0or1 Mutes loop chain 1
CC32-39 value 127 unmutes loop chain 1
CC42-49 value 0or 1 Mutes loop chain 2
CC42-49 value 127 unmutes loop chain 2
What is the outgoing CC and value?
outgoing CCs are the same the only thing Bome does is send those values when receiving CC 30 or 40. values remain the same so if Bome receives CC30 value 0 it sends CC32-39 value 0 effectively muting all loop chain 1s
Right now it looks like CC 1 with a value of 127 mutes all loopers except the one pressed?
nope CC1 triggers all play. as does CC3-15 (odd numbers) at this point it would be ok for CC1 to be mapped to all the plays in the 8 loopers as my original strategy as mentioned earlier went out the window.
How does it know the one pressed needs to be unmuted? value Shouldn’t it send a value of 0.
It looks like looper mute output is CC 1,3,5,7,11,9,13,15 with a value of 127
my pedal allows for 6 different CCs to be sent at once per pedal. so for example what sends is …
pedal 1 sends
CC#1 value 127… this goes to bome and is translated to CC1,3,5,7,9,11,13,15 starting ALL PLAY
CC#32 value 127 which Unmutes LOOP CHAIN 1 ( chain with looper )
CC#42 value 0 which Mutes loop chain 2 (chain with no looper that allows for just input audio to run through)
CC#22 ( in a trigger state so both values ) which simply selects the track to put in in view.. however, I have one pedal that send CC#17 to bome. this changes the midi channel from channel 1 to channel 2 (CC17 value 127 ch2, CC17 value 0 ch 1) On channel 2 this CC is tied to the Big Multifunction Button in Bome essentially creating an over-dub mode.
pedal 2-8 do the same but move up in CCs so
pedal 2 sends CC#3, CC#33, 43, 23
pedal 3 send CC#5, 34,44,24
pedal 4 sends CC7, 35,45,25
pedal 5 sendsCC9, 36,46,26
pedal 6 sends CC11, 37,47,27
pedal 7 sends CC13, 38,48,28
pedal 8 sends CC15, 39,49,29
4) What incoming CC and value do you use to stop each looper?
CC#19 value 127 , stop buttons on all 8 loopers are tied to this CC
What is the outgoing CC and value?
this is passed straight into ableton. no change.
It looks like you are using CC30 and CC40 to stop and start two different “Loop chains”
CC 30 sends 0 to 32-39 to stop chain 1
CC 40 sends 0 to 42-49 to stop chain 2
answered this above
5) When you stop a given looper, do the other loopers also start?
no. any time one looper stops all loopers need to stop.
similarly any time one looper plays all loopers need to play.
the only thing that makes it sound like they are stopping and playing is the mutes and unmutes.
the rule I came up with in my head for making this behave like a hardware looper is..
if any looper is triggered to play, all loopers must play.
when the last looper is muted, all loopers must stop.
6) When you stop a given looper, do the other loopers also stop?
yes! always. the only time a looper is stopped is when the last looper is muted or an ALL STOP ( CC19 ) is pressed
there is never a point when some loopers are playing and some are stopped.
7) When you start a given looper is it in sync with the other loopers or do you have to start them all at once to keep them in sync?
they must all start at once
8) Does muting all loopers stop a loop?
right now no, but I need it to yes.
I assume not and you want to send CC19 to do this if they are all muted. What would be the incoming trigger? I assume looking to see if all loopers are muted.
YES YES exactly! so upon muting the last loop ( which could be any of the cc32-39 value 0 or 1 )
Ok im going to take a moment here to really map out every detail of my setup.
](https://www.bome.com/wp-content/uploads/cma_attachments/1550647656488_DAFC71F4-3359-4207-827E-1161785C1501.jpeg){kind=link}