Jump to content

bpford

Member
  • Posts

    11
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

bpford's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Collaborator Rare
  • Week One Done
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. To answer my own question: No it has not.
  2. Has the multi-timbral track delay bug been fixed? I didn’t see it in the list of fixes…
  3. Hey Dewdman, Thanks for turning me onto Bidule. I got it stuck in my head after I discovered it's capabilities, that it would be better if I could do this process with just one midi plugin (bidule), instead of 2 (bidule, my script). So this is what I built in Bidule and it seems to work like it should. I haven't bought the full version of Bidule yet, so I'm not 100% positive it would work within Logic, but I can't see why it wouldn't.
  4. Just got back from a long day. Incredible! Thanks so much!
  5. Right, because a software instrument (that's hosting kontakt or an instance of VEPro), doesn't behave in the same way as an external instrument plugin? The output (triangle thingy) that you cable from in the environment on a software instrument track is actually BEFORE the midi script in the midi signal flow I suppose?
  6. Right so simply: Lemur sends CC119 to Logic and depending on what track is selected in Logic, Logic sends midi back to Lemur which tells it what patch to switch to. This would also be a lot easier, if, whenever you select an instrument track in Logic it automatically sends out a custom midi message containing the channel number and program change number.
  7. Here's the way it works using the transformer object in the environment. All of my software instrument tracks are cabled to their own individual transform objects. The condition for all these individual transform objects is that they need to see CC 119. And they all perform the same operation but with different user inputted values. So, when CC 119 is met, you fix a program change to a user specified channel and program change number. My violin 1 track is cabled to a transform object that will spit out Channel 1, Program Change 0 for instance, and my violin 2 is cabled to a transform object that will spit out Channel 1, Program Change 1. All of these transform objects are then a cabled to an instrument whose port is set to the virtual Lemur Daemon Output 0, which is the virtual input port on the iPad. So, now I scroll to my Violin 1 patch in Logic. I press the "recall" button on the iPad app, which sounds out a CC 119 message. The selected track in Logic sees that, performs the transform operation and then sends back out the channel number and program change unique to it to the iPad app. When the iPad sees that info, it switches to the corresponding patch with all of its unique articulation switches, sliders, etc. It makes it easier to keep track of hundreds of different instruments and their own unique keyswitches as well as any other custom controllers you'd like to build into the iPad patch.
  8. Damn. Well thanks for all your help. I'll submit the feature request, but I don't think the workaround will work for my case.
  9. So...I'm out of luck? There's no way to send the midi information generated by the script back out of the software instrument channel? Sorry I sound thick-headed. I appreciate your help!
  10. yes! That worked! Thanks! So I know that my script works, but how do I get it to work with a regular software instrument? Connecting a cable from a software instrument channel to a midi instrument with its output set to the correct port in the environment should perform the same function, no?
  11. Hi y'all, I'm trying to replace a transform object in the environment that's used to recall patches in Composer Tools Pro on my iPad for articulation switching. It's a simple transform object that listens for CC 119( coming from CTPro on the iPad), and converts it to a user specified program change number and channel number. The transformer than filters all other information out and sends the program change and channel out to a specified Lemur port via another midi instrument in the environment. The program change number and channel number is the unique ID that Composer Tools Pro uses to identify which patch to recall. If my explanation is confusing, here's a youtube example of the setup: So, I know next to nothing about java scripting, but I can't use environment objects because of my workflow. I've moved away from using one huge template pre setup with these environment objects, and instead populate each project with channel strip presets and track stack patches as I go. The problem is those saved channel strips and patches don't bring along their attached environment objects though. But if I had a script that did the same thing, it would always travel with the instrument preset...e.g. Spitfire Violin 1 or whatever. But I've failed to get anywhere cobbling together code from various examples. Here's what I've got so far. /*Script that transforms control change 119 into a program change with user definable channel number and program change number and filter all other midi events */ var PluginParameters = [ { name:"Channel", type:"valueStrings", defaultValue:1, minValue:1, maxValue:16, numberOfSteps:15 }, { name:"Program #", type:"valueStrings", defaultValue:0, minValue:0, maxValue:127, numberOfSteps:127 }, ]; function HandleMIDI(recall) { if(recall instanceof ControlChange && recall.number == 119) { var p = new ProgramChange; //generates program change message and saves as "p" var prog = GetParameter("Program #") //retrieves program number from user input and saves to "prog" var chan = GetParameter("Channel") //retrieves channel number from user input and saves to "chan" p.channel = chan //sets program change to "prog" p.number = prog //sets program change channel to "chan" recall.trace(); //filters out all other midi messages p.send(); //sends out only channel and program change # } } Did I mention I don't know what I'm doing? Anybody got helpful hints? So far, the script is just spitting out what I send it...CC 119. It would also be GREAT if I could specify what port to send out the program change to, but as far as I can tell, that's not a capability? That would also help me to avoid having to cable each instrument to the instrument object that's pointing to the Lemur output port.
×
×
  • Create New...