Post by André G. Mendes on Feb 13, 2019 6:10:01 GMT -5
Following the Manual - 4.2 Accessory Controls - Direct Pages Buttons I see that CC 65-72 are reserved for directly select pages. But when looking at the "alt_consts.py" it has different values: DIRECT_PAGE_BTN_NUMS = (9, 111, 112, 113, 114, 115, 116, 117)
I opened the Midi Fighter Configuration Application and I set the first 8 buttons to match the values I have in "alt_consts.py" at it worked. So a couple of questions:
In case I need to change these CCs... Should I change it in the Midi Fighter APP to match the ones on the "alt_consts.py" or is it the other way around?
Also for consistency with the manual shouldn't the DIRECT_PAGE_BTN_NUMS on the "alt_consts.py" = (65, 66, 67, 68, 69, 70, 71, 72, 73)? Can I change this?
No, the point of alt_consts.py is to allow you to define the note/CC numbers and channels you want to use. So, in most cases, there would be no reason for it to be consistent with what's in the manual. FWIW, I didn't create the controller files for the Twister that are on the repository. I would expect there is a good reason why alt_consts.py is set up the way that it is. So, unless you have good reason and a good understanding of the Twister, I would leave alt_consts.py as is.
Post by André G. Mendes on Feb 13, 2019 9:33:58 GMT -5
Ok thanks for the info.
Loving DDC btw Still have some work to do on the plugs I want to use it but so far I finally can do one thing I was looking to do for ages in arsenal but couldn’t quite do it with the flexibility that DDC allows.
I mean I love Arsenal but I really need a direct way for accessing different “banks” (in the case of DDC “pages”) of VSTs and this doesn’t just allows for a quick way of doing it but it also lets you make your layout on the midi controller which is awesome!
I think there are some ideas you could take from DDC to incorporate on Arsenal like the editor which is great to have for setting up mappings. Anyway I would really love to see Arsenal having a mode just like the DDC where we could add our own layout of mappings and direct access to pages. The advantages of a mode like this is that we could quickly change to another mode since Arsenal is a lot more flexible in changing between all the different modes. If there wasn’t the limit to 6 control surfaces it would be a lot easier...
Post by André G. Mendes on Feb 13, 2019 12:05:02 GMT -5
Ok I'm confused now... I don't know if maybe this is possible...
So I have an instrument Rack consisting of 5 VSTs each one on it's own chain. First question: Does DDC work for various VSTs that exist in an Instrument Rack or is this Track relative meaning we can only have one VST per track?
From what I've understand (correct me if i'm wrong) DDC follows the blue hand right?
I've already made my Midi Assignments for DIVA on the Midi Fighter using DDC1 and I was now going to do the same for Zebra2.
One thing I've noticed is that I've captured Zebra2 but I'm noticing that whenever I change the VST in focus in Live, the Midi fighter is always focused on DIVA despite it not being locked to DIVA in DDC. I though that when I moved the blue hand over Zebra2 (since it's not yet mapped) that the Midi Fighter wouldn't show any mapping.
Assuming I'll be using DDC1 for all VSTs, when opening the editor do I have to save a Mappings.py for each VST separately? So for example now that I've finished DIVA I should re-open the editor, delete everything regarding DIVA and start mappings on Zebra2? Is this how it works? Or does the DDC1 saves mappings of all devices?
If so does the name saved for every mapping needs to be "Mappings.py" or for the purpose of having this more organised could I have names like: "DIVA - Mappings.py", "ZEBRA2 - Mappings.py", and so on?
Sorry Stray... this is still new to me so I just want to be sure that I'm understanding all this perfectly
No, DDC has nothing to do with the blue hand as that would defeat its purpose (dedicated device control). It can control multiple devices on a track without any of those devices having to be selected.
And, yes, a single DDC script (such as DDC_1) can contain mappings for multiple devices. The mappings are edited via the DDC Editor. There is never a need to manually do anything with Mappings.py files.
Post by André G. Mendes on Feb 13, 2019 13:12:20 GMT -5
Ohh d**n... It's not going to work for me than (((
I saw the Lock button but I just now realised is to lock to the Track and Not to the device.
Been playing with this all day while I was finishing DIVA and this was the best ever way I found for working with VSTs that have a lot of parameters while having it all laid out organised in Midi Fighter in a similar way a modular synth works.
I had already made a very cool layout for controlling Diva across 4 pages that could be switchable on the first 4 buttons of the Midi Fighter and I set the last 4 buttons (13-16) for triggering Clyphx actions on the Clyphx Drumrack.. I thought that if I could apply the same methodology to all 4 u-He VSTs I would have some visual coherence when navigating across the Midi Fighter... so many possibilities.
I really thought I had something here for overcoming getting direct access to banks of parameters on VSTs while getting the Bonus of designing my own layout of how VST parameters get displayed in a Midi controller... I'm sad now :,(
Post by André G. Mendes on Feb 13, 2019 14:31:51 GMT -5
Ok before I quit and accept the fact that what I'm trying isn't possible I'll briefly explain how my setup works.
So my Synth Track has this structure:
From the Clyphx Drumrack I've set on a particular track, and using the buttons (actions) there created, I can navigate across my set and also trigger specific actions that apply to different aspects of any track or device.
On iPad I've built a navigation system that interacts with the Clyphx Drumrack:
Although I can control any Live parameter from the iPad plus having a lookalike visual feedback of whats going on, I can also control VSTs and maxforlive devices. The main difference here, in the case of VSTs, is that first: they don't have a visual look like with the case of Live devices and second for a more precise and fast control over plugins the physical knobs still win here.
So because of this I have a Launchcontrol loaded with Arsenal always set to device mode. This way when I select any device from the iPad the launchcontrol will follow and I use the knobs to control any selected device. All good.
Now on the iPad there are also 8 dedicated buttons that send Control Surface actions, to both Launchcontrol and Push, to move to specific banks of parameters. So with this i can move between different Preset Banks, moving launchcontrol in rows of 16 and Push in obviously 8.
Because I also have a Midi Fighter Twister (which was initially reserved for masterfx control) I thought maybe experimenting with it to control devices instead of using the Launchcontrol. The main reason being the fact that Midi Fighter has light feedback and when controlling VSTs this would be better than with the Launchcontrol.
But what happens is that the default mapping of device mode of the Midi fighter doesn't use all 16 knobs. Instead it only uses 8. If there was an Arsenal Script for it my problem was solved but because there isn't I was thinking for a way to have all 16 knobs always available for parameter control.
When I came across DDC I got excited because it had brought something into the table which was for a way to customise the layout of how parameters get displayed in Midi controllers. This was something I've already tried to achieve but never got far on it, so I basically abandoned the idea. But the thing is that after playing with it for a while I kind thought to myself how great would be to finally have this sort of customisation when mapping devices.
Can you think of a way to apply this idea, maybe using Arsenal I don't know?
Just to clarify about DDC, check out this video, which covers the purpose of the product. So, in your case, that would likely mean that you'd use one controller for Diva, another controller for Hive, etc. Just like you would if they were hardware synths.
Anyhow, as we discussed in another thread, for what you're looking to do, I'd suggest you use bindings as it allows for this sort of stuff and much more.
Post by André G. Mendes on Feb 14, 2019 13:08:43 GMT -5
No no sorry if I didn't explain myself the best way. I want to use the same controller for every plug in ableton device, in this case the Midi Fighter Twister because, as opposite to the Lauchcontrol, the knobs have light feedback which help a lot to get a more reliable info of whats going on before start messing with parameters.
I'm going to try to use bindings for the Midi Fighter and see if I can get all the 16 knobs to work in device mode.
Anyway what I love the most about DDC is the ability to design the layout of how the parameters would be displayed, in this case in the Midi Fighter (more than having multiple devices being controlled from the same Midi controller, although I understand how many people might enjoy this feature).
Having this ability in a controller like the Midi Fighter Twister, if Powered by Arsenal, would mean we could create custom layouts for plugs and Live devices and because Arsenal has Blue Hand capability that would also mean that when changing across devices we could get a more customised look of how the parameters are displayed in the controller.