![]() ![]() One thing to check, are the program change messages coming from Lemur being sent on midi channel 1? So it sounds like the problem is within Cubase, a setting or routing or something. Based on the picture Andreas posted, articulation 8 sends a note-on message for F#-2, so it seems he is using a keyswitching patch.Īndreas, if I understand correctly, you mentioned that you are able to switch articulations while auditioning sounds and while recording, but upon playing back a recorded passage the articulations don't switch? That seems to mean that the expression maps are set up properly but for some reason Cubase isn't recording the articulation changes along with the midi data. So in theory (I haven't actually tried it) if you were using UACC you could send a controller message for CC32 corresponding to the UACC value in Spitfire from the Output Mapping. The Output Mapping section is actually what determines how to switch articulations. So if it is set to program change messages, then Cubase is listening for program change messages and converting those into articulation changes. The Remote Settings in Cubase only determine how the user will be triggering articulation changes. I think you might be confusing program change with UACC (which by default uses CC32, it has nothing to do with program change messages). It had to be a key switch or program change message. I was fixated on sending CC32 info to the expression map, but it wouldn't respond to that info. *Edited to reflect information from my post below. Though I assume if your VEPro is setup correctly (as a rack or track), it should be fine. Update: I didn't try this with VEPro, I had it run through a track instrument (Kontakt) in Cubase. I use MIDI Kinetics Composer Tools Pro for my Lemur, but you can create or download what is easiest for your preferred recording setup. You use Lemur to trigger the key switch (any interface that sends a note on or program change message). Set the articulation, type (attribute/direction), and description in the bottom right expression map menu.Also, confirm you're sending it to the correct channel in your sample player. If it is a key switch library, set the note on value and correct note to trigger the articulation. The Data 2 value must match the UACC value listed in the library (you may also need to set the channel depending on your set up). ![]() Set Status to "controller" and Data 1 to 32. Also give it a name and assign an articulation symbol. Add a sound slot and set the "Remote" to whatever key you're going to trigger from Lemur.Set your Expression map "Remote Settings" to "Key Switches" or "Program Changes" depending on how you're sending Lemur info.If it is a key switch library, then note the appropriate key switches. Set Spitfire to Locked UACC mode and note the relevant CC values.Set the Cubase instrument track to receive from all MIDI inputs.I did get Cubase to record expression maps from Lemur. Click to expand.Thanks for following up Sean. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |