like at bar negative 950, and all at ONE moment in the time line. ALso, the new part does not contain any of the pitch bend cc info.īUT…if i look in the midi list editor, all the pitch bend cc info is recorded way before bar 0. To trouble shoot, i record the note, then (with midi merge enabled) i go back and record the pitch bend info.Įven though ‘merge’ is enabled, it creates a new part on top of the part containing the midi note. If i record the same procedure, it records the midi note but does not record the pitch bend cc info. With a midi track armed, i play a note, use the pitch bend on TouchOSC and it works as it should. Motu? "I think this is where you come in?".I have TouchOSC setup to control multiple different midi CC messages.
#TOUCHOSC AND OSCULATOR MOVIE#
Avid has that and also hardware work-surfaces running Eucon!Īs Jeremey Irons said in some movie I have forgotten the name of It's not elegant like Eucon, or a dedicated app like Logic and Steinberg and ProTools have. I still don't get why Motu killed DP Control?Īnd I find Mackie Control kind of half-a_d alternative. Unfortunately bars/beats are not, which is a pain. They can run the session from my iPad, and all the transport keys, click on/off, solo, etc. It's been great for not just key-switching, but also things like naming mixes and stems, and I even have a transport control section for when I'm working in studios with engineers that don't use DP regularly. It does receive it ( can see in the messages pane), but I'm not smart enough to get Osculator to send it to TouchOSC on the Ipad and make it work. I did try turning on send MTC Bars/Beats in DP and see if Osculator was receiving it. I'm sure there would be a way to send Mackie Control back and forth and also use regular key-switching features simultaneously. HOWEVER, if you have 2 iPads you can get around that by having 2 Osculator files open (they can be the same) and set one of them to port 8001 and use that one for all your MIDI stuff. At least that was my experience a while back. there may be a conflict as the Mackie protocol is pretty much MIDI so your keyswitching stuff may not work. If you are using your iPad for anything MIDI like keyswitching etc. One thing about using the Mackie Control. I started playing around with trying to get the counter to display a long time ago but I never followed through.īut I think one of those options (Mackie or Open Sound Control) should get you pointed in the right direction. Using the Mackie Control I can get two way communication with all faders, mute, solo, record, level meters etc. I use (have used) Mackie Control but there is also an Open Sound Control selection too. Click on the + button to add the controller type. Go to the "Control Surface Setup." command under the Setup Menu.įrom there the control surface setup box opens. Maybe someone smarter could.Īlso the warning that TouchOSC hasn't been updated in like years I think?
I'm not very technical, so if I can make it work, it's a low bar!Īlso I have not been able to get two-way communication to work. I use Osculator and also Keyboard Maestro together and you can basically do anything. Let Osculator do that, and it is bulletproof.
It is totally reliable as a button or fader, but not for a specific keystroke or MIDI note or message or whatever. TouchOSC is not reliable for assigning the actual whatever the final message is. The MAIN thing I learned is that TouchOSC works great and as faders and buttons, but DO NOT rely on it to actually send specific keystrokes or MIDI notes or whatever. I use its mainly for key-switching, another page for transport controls (this is great with engineers that don't know DP), another page for naming mixes and stems, another for Finale, etc.
I tried a bunch of others (Metagrid, DAW Control and Lemur) and ended up with Touch OSC. My experiences with TouchOSC have been largely positive.
0 kommentar(er)
