5/15/2023 0 Comments Osculator templates for logic![]() ![]() I've been reading the doc but meh, I'm someone who learns from examples. (set variable, read variable, address variables, etc.) So, eventually, my question is : do you have documentation and examples of codes like this ? I've set a variable in visible field of the switch my text field displaying track name, I've tried to script the visibility by changing the variable. Ok, so, use case : I want my script to analyse the track name and display the articulation if the set is relevant. However, if I click notes in LPX then an articulation, it is not changed, but I guess it's not possible to edit articulations in Logic without using that stupid dropdown in editor. I've set a switch grid to send articulations to LPX this works. It works well from LPX > O-S-C, not the opposite (clicking the button does nothing in LPX). I'm also having a button retrieve the mute status. I'm trying OSCulator and I manage to get track name from Logic to O-S-C. ![]() My main use case : select a track and see articulations and select them. I'm using LPX which, as I understand, is incredibly poor at remote controlling. Now I'm back on it with very little progress. Note that I haven't tried this.Ok, I had to leave my OSC project for a few months. Just have Osculator send the same messages and Logic will think that device is really there. Or something simpler like a Frontier Tranzport. So the point is that you may be able to have Osculator emulate an MC to some degree. Logic then sends an appropriate note message that toggles the transport lights on the MC. If you look at the play command in the assignments, and load up MIDI Monitor, you'll see that the MC sends and receives note messages to control Logic's transport. Below I have the template for the connection generated from the automation pane of the Azure Portal. The logic app requires a connection to Office 365. In the Control Surface Setup, install a Mackie Control and set its in and out ports to Osculator. I have a logic app that I am trying to automate through an ARM Template. Since I have several supported devices, I don't have much need for messing with controller assignments, but there is something you can try. Much of the controlling logic for supported control surfaces happens behind the scenes. It must be sending *something* for Mackie Control-type devices to work. I don't touch my computer keyboard anymore when recording, and it only took me a couple of hours to create just the interface I needed.Īlso, is there a way to monitor what messages Logic sends when using the Transport Bar (Play, Cycle, Stop etc). Some control apps do that (ProRemote.) but I don't know how. I must have been kidding myselfĪlso, I can't get the kind of shuttle control you get with Mackie Control hardware by using keyboard shortcuts (you only get "shuttle left" and "shuttle right", can't be done with a two-way fader with travel distance controlling shuttle speed). That's why I was curious if there was some "universal" way of sending out commands. ![]() But because OSCulator can't send any function key above F16 I had to change that. I didn't say TouchOSC could receive OSC commands, I'm just discovering the possibilities and was wondering if a two-way toggle switch was one of them.Īn example for changing key commands: for a long while I had Left/Right Locators "set" and "'go to" commands assigned to F16-F19, right above the numeric pad which I use for most transport commands. ![]()
0 Comments
Leave a Reply. |