anyone on windows tablet?
-
@pipelineaudio hey so the guy that helped me program the midi brain has it sending CC on and off codes like...CC 60 127 then 60 0. does that mke a difference?
-
it can call two different rows that way. I have my first pedal send cc0 1 and cc0 3 so I can switch between two sounds that i use a lot. In reality, you can remap anything with piz's plugins, so I wouldn't worry. Having the two different values on 1 pedal can be really handy, and if you dont like what it does, you can tell things to ignore it...best of both worlds.
In other news, I got to try the Widi Bud today and it is AMAZING! It shows up as a MIDI port in REAPER and eliminates the need for MIDI berry or loop midi for the wireless pedalboard. Latency is indistinguishable to me from the wired!!!
https://www.instagram.com/p/BfZbSXoBqjE/?taken-by=pipelineaudio
-
nice awesome!
So what youre saying is that 60 127 and 60 0 are treated as the same code? or can be?
Right now it gets stuck after 12 commands. buggy. other than that its just tweaking hold times for bank loading.
-
@pipelineaudio are you able to assign specific cc numbers to Live COnfigs?
-
@brian-dress Not to the rows, it is infuriating. You can tell what cc# will control the entire config, but not what will call that row.
That's why i want to make the new one that loads and unloads actions, the first column will let you chose what action(s) and/or CC(s) will select that row
-
There are other ways to do all your switching though. SWS Restore saved mute states for all tracks can be stuck in a custom action with whatever else you want, even the track based crossfading script instead of MIDI Fade X, and you could assign whatever MIDI CC you want to each custom action.
-
ok so live configs uses 127 codes and for each code you pick a track and an activate action and deactivte action?
-
ok now im even more confused. I dont think im even sending the correct codes to use this properly.
Now youre saying live configs uses CC#0 so is 0:0 - 0:127?
-
For instance, I have live config 1 ( I think you can have 8 different live configs) set to cc0. cc0 value 0 picks the first row, cc0 value 1 picks the second row, etc. That's the sucky part, though its easy enough to piz your way around it. The way I'm picking tracks is through the load and unload actions on the rows.
SWS can automatically do all that for you, but at the expense of a long switching time, which I dont like
I really wish you could assign the rows a midi cc directly, but you can't so hopefully our other script or extension can be made
-
yeha because right now my thing send just bunch of CCs
-
Which is fine, piz can remap them no problem
-
i cant figure out how to get it to do anything in reaper at all actually
-
@pipelineaudio whats piz
-
https://www.thepiz.org/plugins/?p=pizmidi
Assuming theres no JSFX to handle it (though there probably is)
-
Ahh i figured it out now.
I just have to find the right actions for live configs. I think it will work with your project once i reprogram it to send the correct codes. I was missing out that its switching based on D2 value instead of D1 value.
And this is even better because you can have 8 active at once lol. So you can have 1016 prepared commands if you want hahahahaha.
-
For another way to do this, setua few tracks of your dream fx
Mute all but one of them
Go to actions and run Sws save mute and solo state for all tracks (I think it’s called) for slot 1
Repeat this for all your tracks to a new slot for each one[link text](link url)
Then go to actions, click on Sws restore mute and solo state for slot 1
Press add keystroke or whatever it’s called and then click your pedal
Repeat that for all of your saved mute states. Quick and dirty, but man is it quick!
-
I'm completely understanding how it works now.
If I wanted a wah I could just use your code with an expression pedal.... or even a pot on my guitar??? Hahaha
-
@pipelineaudio what is this "go to actions" ?
-
@pipelineaudio i was reading your thread on reaper forum about using Track muting vs receive muting in relation to audio dropout during switching. Which way did you eventually land on?
-
Go to actions I jus mean open the actions window.
Right now, I’m doing the MIDI Fade X method at the end of the fx chain rather than the start. I’m also having one with like soldanonx99 switching times, and that one seems to work better with MIDI Fade X at the beginning of the fx chain