Now, there are ways around this by associating a widget with a CC parameter in a MIDI Out block but then you’ll also need to use the widget grouping feature so that you can have another widget that will control the desired plugin parameter. However, Gig Performer widgets do not send out MIDI messages directly so if you have a MIDI controller like the MIDI Fighter Twister (an expensive but really cool surface) with endless knobs and LEDs that can display current position, turning a Gig Performer widget will not be reflected in the Twister. For example, you can associate a widget with a knob on your MIDI controller for example. Gig Performer widgets can learn external MIDI events so as to respond to them. Right now, I’m experimenting with it to solve a problem that is due to a currently missing feature in Gig Performer. Or you can receive OSC messages from Gig Performer widgets and control a Wiimote! For example, you can configure it to receive MIDI notes and have it send keystrokes (yes, that’s right, as if you are typing) to an application. if it was raised to 8 it would help manage the other limitations a lot easier.If you’re on a Mac, there’s a great app out there called OSCulator that can be used to transform pretty much any input to any output. With that in mind if RME cant add global OSC support it would be good if they could increase the amount of mute/solo/fader groups. since doing that i realised you could probably use fader groups to access master channels from busInputs OSC page ? just add a single fader on from the bottom row to the group and then access it globally with /3/faderGroups/4/1 ? this should work but i havent tried it yet. i think they added support for mute/solo/fader groups recently also as im using a mute group in a handy way.
Its good RME added the lock to submix function that is a big help. there seems to be no official map of what mackie controllers do so i went ahead and worked it out in a basic capacity and its too cryptic to easily automate. I want to automate totalmix from a DAW a little and volume control is easy with CC's but the ability to use mutes is buried in mackie control. i dont know why they would restrict that ability ? for my situation no mutes via CC along with no global OSC control starts limiting things. The other thing that makes it hard to manage for my scenario is the lack of channel mutes via midi CC. its not great to have the inputs/playback/outputs restrictions, i wondered if the purpose of this was to support mackie controllers maybe ? seems like that is how they work. I recall hitting this problem a number of years ago but it was reminded to me again during this latest bit of work i was doing. I still hope that global OSC will be added some day, but I’m not holding my breath anymore. Usually this happens when starting up TMFX and connecting my controllers.Īlso I often have to disable and enable OSC control from TMFX settings to get things up and running, so not the most elegant solution, but it’s possible. This was a lot of work and while it works most of the time, I still get some panic states when the synced faders get their levels from a wrong submix or something else resets my submixes. I’ve been able to successfully program partial submix syncs with synced faders, synced solo buttons between only specific submixes etc.
Actually in this simple case you could use a single TMFX window, and enable midi control alongside OSC just for the Main out control. You could also translate OSC to midi with Osculator or any other OSC to midi translator. At least Lemur allows multiple OSC targets inside the same controller layout.
OSCULATOR WINDOWS WINDOWS
However this would require you to either send the command to switch to outputs / inputs first, or do as I and use multiple TMFX windows linked to different Osculator windows which are then connected to same controller / control layout.
OSCULATOR WINDOWS SOFTWARE
(This would have allowed any fader or button on any submix to be controlled at any time without switching submixes or rows.)ĭepending on the software you use, you could make a template on your own. RME promised to add global OSC control support to TMFX years ago, but unfortunately they were never able to deliver.
0 kommentar(er)
