@gravitas yes, so scenes in the Twister terminology are banks. Each bank holds the configuration for set of encoders . By default first bank encoders are CC0-CC15, second bank CC16-CC31, third CC32-47 and forth CC48-CC63
Here we go, I hope I did something useful. So I marked each knob to encoder like: CC [C:1] 63 0 means Ch1 CC63 value 0 (values ranging from 0 to 127 it turning encoder). I've also put respective CC number in to the value field.
Is it possible then to have controllers in Touch OSC that get updated once on project open? Kind of like what @skrat did with Mozaic but no scripting necessary with 'midi feedback' checked for the faders in Touch? @gravitas how do you set up this 'send CCs on open' behavior?
That's hard to say. @giku could of course just add feedback for the state of many UI elements but if you worked with only this feature for a while, you'll notice that it isn't enough to make a good groovebox-like experience without keeping your eyes on the screen too much.
So there's a lot of thinking and testing concepts regarding possible controller-only workflows, which includes a lot more than just 1:1 control mappings.
It might not grow as dedicated as the Ableton Move, but it will also offer you things that the Move can't do.
And you'll be able to use multiple MIDI controllers and save different controller mappings independent from your project, at least for the sequencer part.
’It might not grow as dedicated as the Ableton Move, but it will also offer you things that the Move can't do.’
Ha, currently Move is sitting on my desk and in my mind it feels like a toy compared to my Drambo rig, although I must admit it has some clever sequencer tricks.
It falls flat it terms of live use as well as sound design of course but that isn’t its intended purpose obviously.
I downloaded your template to make it for faderfox ec-4. Only I made not 4 scenes, but 16, to cover all presets. I specified everything as in your screenshots, but the feedback does not work. Where am I making a mistake?
How can I make it so that by default there are 2 active channels instead of a switch?
Comments
@gravitas for sure stick to the default as much as possible is good idea :)
Please let me know if you want me try out or test something.
Okay, cool.
Good to know.
I definitely will need you to test stuff as I don't have a Midi Twister Fighter to hand.
Are the 64 encoders created by using all four of the Scenes?
The push button info is also good to know because those could be used for step sequencers, more on that later.
@gravitas yes, so scenes in the Twister terminology are banks. Each bank holds the configuration for set of encoders . By default first bank encoders are CC0-CC15, second bank CC16-CC31, third CC32-47 and forth CC48-CC63
@idx so basically using all four Banks one makes up 64 encoders + 64 Buttons?
Do all of the Scenes transmit on Midi Ch 1 or is it Scene 1 = Midi Ch1, Scene 2 = Midi Ch 2, etc.
@idx
Could you put together 4 CC gen (multi)'s
with the values 0-15, 16-31, 32-47, 48-63 for both the header and
the value each knob represents in a dRambo file and post it up please.
Yes, all banks represents 64 encoders and switches.
No, all scenes send the same Ch1 for encoders. Range is: Ch1, CC0 - Ch1, CC127
What do you mean? Not sure I know what is 4cc gen multi and also what is dRambo file :)
Should I put midi monitor or something?
@idx
I've created a dRambo project here;
On the first channel is a Rack instrument.
In the Rack instrument are 4 CC gen (multi's).
Can you re-number the knob headers + the values that they output to the ones for the Midi Twister Fighter.
Currently MTF Scene's 1-4 (CC gen (multi) ) are numbered 1-16 and each CC number is at CC 0.
The headers for Scenes are clearly labelled.
Thank you.
Here we go, I hope I did something useful. So I marked each knob to encoder like: CC [C:1] 63 0 means Ch1 CC63 value 0 (values ranging from 0 to 127 it turning encoder). I've also put respective CC number in to the value field.
Hope it helps. Thanks!
@idx awesome.
I'm preparing to go live on YouTube tonight with a mic so bear with me.
Cool, I've sent you DM to get a link to the channel.
@idx cool.
Is it possible then to have controllers in Touch OSC that get updated once on project open? Kind of like what @skrat did with Mozaic but no scripting necessary with 'midi feedback' checked for the faders in Touch? @gravitas how do you set up this 'send CCs on open' behavior?
@idx
my apologies I'll catch up with you as soon as possible.
@wailem
I don't use Touch OSC, dRambo covers most of my midi controller to dRambo needs
and I mainly use the iPad screen and external midi controllers.
dRambo automatically sends out stored CC's as soon as it opens up a dRambo file, unless the CC's are on a randomizer.
What is your rig and what controllers are you using?
@idx
Here’s an update.
Screenshot;
Select the “MTF” on the left hand side.
Set the first Midi Output to Midi Feedback and the last one to the “MTF” on the right hand side.
By the way the Midi Channel switcher can be used with any hardware
midi controller especially those limited to only one midi channel.
@idx after this we shall be see about creating the visual feedback.
Hey @gravitas thanks for setting this up. I've recoded a vid for you, sent to DM.
No problem.
We still have a way to go yet.
Okay, I've had a look at the video.
First things first.
Is the MTF set to midi channel 1 on the MTF?
2nd thing if you map the volume on the Track it doesn't send out CC messages
that's why I asked you to create the CC gen multi because
we're going to use that to communicate with the MTF eventually.
Go into Settings and switch off TRACK and CONTROL on the MTF midi input.
To change the midi channel press the Buttons in dRambo on the left handside,
the numbers on the right hand side of the utility show you which midi channel you're currently on.
@idx
I'm streaming tonight at 12 am UK time.
If you're still awake pass through and I'll show you how I've used that utility for my setup.
Can I set up feedback for my Faderfox EC-4?
Yes, you will be able to.
I started putting something together for @idx however the midi feedback
landed so it's best to wait until it's actually on the AppStore version.
Oh new update coming with feedback it is huge.
Yes, it is huge.
Video short from the Dev.
Do you mean next update?
That's hard to say. @giku could of course just add feedback for the state of many UI elements but if you worked with only this feature for a while, you'll notice that it isn't enough to make a good groovebox-like experience without keeping your eyes on the screen too much.
So there's a lot of thinking and testing concepts regarding possible controller-only workflows, which includes a lot more than just 1:1 control mappings.
It might not grow as dedicated as the Ableton Move, but it will also offer you things that the Move can't do.
And you'll be able to use multiple MIDI controllers and save different controller mappings independent from your project, at least for the sequencer part.
@rs2000
’It might not grow as dedicated as the Ableton Move, but it will also offer you things that the Move can't do.’
Ha, currently Move is sitting on my desk and in my mind it feels like a toy compared to my Drambo rig, although I must admit it has some clever sequencer tricks.
It falls flat it terms of live use as well as sound design of course but that isn’t its intended purpose obviously.
I downloaded your template to make it for faderfox ec-4. Only I made not 4 scenes, but 16, to cover all presets. I specified everything as in your screenshots, but the feedback does not work. Where am I making a mistake?
How can I make it so that by default there are 2 active channels instead of a switch?
I thought that you had understood that it was better to wait for bidrectional midi feedback
to actually be implemented in the app store version of dRambo after we've beta tested it fully.
When you wrote, I thought that the update would come out very soon
Well, all I can say is that you either figure it out yourself or wait
until the update is released because I'm not going to do it twice.
Ok, I understand you. Thanks for your answer.