Steve Harder

Williard Sorry for the late reply, been on vacation off the grid. Here is the multi Here is an example of how I have artic maps set up for HW Strings (non Opus) using that multi. These are not identical to your example but do work. In the above the Legato would be on midi channel 1, Spiccato on midi channel 2, etc. In the above note what is happening in the Out line of each transform event, locking all output to a specific channel. And above is the midi channel 7. Does that help?

Layers is somewhat of a "niche" virtual instrument in that it is restricted to playing chords with various structures. This recent vid will point you to other free virtual instruments that broaden your tool kit for creating music.

All I can say is Opus and Orchestrator and Cakewalk and Scaler together are functioning under heavy performances for me. So I'm not concerned that Cakewalk hasn't been "blessed" by a written list somewhere. Right after Opus release I had interactions with both Wolfgang Kundras and Michael Plubell re CCX subscription white noise issue. Michael asked about how Opus was working in Cakewalk. EW support has been very responsive. Logic Pro users are dealing with a number of big Orchestrator issues so I'm glad I'm on Cakewalk.

Here's my Cakewalk setup for using Scaler to drive Opus Orchestrator. It took some trial and error to sort this out. I found that I needed to use Scaler VST2, VST3 caused some Audio Engine dropouts (9). Possibly just my setup but VST2 works. Basically it's Scaler to intermediate Midi track to Opus. I had a number of issues when trying to go Scaler to Opus directly. Possibly just my setup ... ----- Then when I want to capture the midi out from Opus. I set up 16 midi tracks. First set to Opus Ch1, etc. Conveniently Opus Orchestrator is consistent is assigning a slot to a midi channel, so you can provide a generic name for each track. And then you can replace with name of actual articulation or target instrument. ----- I'm currently exploring the Ostinato - 16th Notes Accents Orchestrator presets. The Scores presets get old pretty fast. But the Ostinatos provide a rich departure point for creating your own unique patterns. Many of the staccato instruments have long series of notes all on the same step. So going in and tweaking to Step+1, Step -2 starts to get the arpeggiator juices flowing. And some of the "accent" presets have nice variation in note velocity. The trick is to move those notes to new locations because setting velocity on new notes is not overly friendly. And CC1 is nice but hard to dial in on a note by note basis. The Orchestrator Arranger Modes provide an opportunity to "get lucky" without the total randomness that some other arpeggiators' "random" modes create. And driving Opus with Scaler brings another dimension to the party. My current instinct is to stick with a midi track driving Scaler into midi into Opus for the time being. I'm not at all ready to commit to capturing midi and then sending that on to other non Opus instruments. Lots of layers to peel apart as we learn how to utilize Opus. I wish the Orchestrator midi editor was friendlier but early days yet.

I have several forum buddies who are using Opus and Orchestrator with Cakewalk, really putting it thru the paces. Turns out that Cakewalk can easily capture midi output from Orchestrator. But folks with Logic Pro cannot, with no quick fix in sight there is a lot of groaning going on.

Opus and Orchestrator are functioning correctly for me on i5 with 32gb and ssd drives. 2 days ago new updates appeared in EW Installation Center so update if you haven't. And contact EW support, they have been using TeamViewer to help users with config issues.

The original creator and sharer of these is "ALittleNightMusic" on https://vi-control.net/community/members/alittlenightmusic.24110/ They did all the hard work. All I did was import the Cubase expression maps and then saved in Cakewalk. These are a good jump start on using Opus master keyswitch articulations. Be aware that master keyswitch instruments consume large amounts of ram (especially Diamond) in Opus, so that may be a reason to use individual articulation instruments rather than master keyswitch instruments. Or to be selective in which articulations you allow Opus to load in a keyswitch instrument. Opus is much more flexible with this than Play was. Using the "Don't Preload" option can really help keep ram usage low, only notes played will be loaded. Here's typical contents Note the disparity between the Note value in Cakewalk artic editor of note C1 and Opus Note of C0 (see 3rd screenshot below). This is caused by Cakewalk and Opus assigning different values to Bass Octave. I have mine set to -1 (at bottom on 1st screenshot below). (This is something to check out if an artic map you create doesn't function, try an octave up or down for the note value.) These use the Master keyswitch patch. ---- On first loading keyswitch patch may have some articulations turned off. --- You manually turn them on by clicking the little slider switch at upper left of each articulation you want to use. To save ram you might only want a few articulations turned on. --- Then you assign a keyswitch to the articulations you turned on manually. You right click in the articulation box. You click on the None dropdown and select Key Switch. And Opus assigns the next keyswitch in order to that articulation. --- Do this for any/all turned off articulations you want to use. To save ram you might only want a few articulations turned on. The changes you make will be saved with your project. If you want this setup to be your new standard for this articulation then you would save the changes to the instrument in Opus. EW Hollywood Opus.zip

And there is another Opus version coming to fix white noise issue for CCX.

As far as I can tell, after just a couple of hours with Orchestrator, there is not a drag/drop export midi capability currently. But Opus does export midi. To capture midi. Play or draw midi on the Opus instrument track. Then you Insert a Midi track, select Opus Midi Omni as input, select Record on the inserted midi track, and record the output of the Opus track. Orchestrator may use up to 16 channels. So you select all the notes in the newly recorded midi track. Then you use Split Channel to Tracks.cal to create a track for each channel. Another approach would be inserting multiple midi tracks and set input of each to Opus Midi Ch 1,2,3. But that's really more work than use midi omni and Split Ch to Tr.cal and then deleting tracks that are empty. Early days yet and others may find easier approaches. But at least capture of midi created by Orchestrator is possible. I don't have an opinion on the long term usability of Orchestrator but is has some interesting capabilities. It appears to be a unique take on combining a very capable arpeggiator with management of samples. It may be easiest to just treat Orchestrator as a black box instrument that you play simple chords into. But capturing the midi of interesting results may be worth the effort for educational purposes. Fwiw

If problem persists try in articulation editor change Chase Mode to Note or Full. set velocity to non zero value In artic lane draw articulation across entire area that you want that artic to affect.

What sample library are you using?

Thanks for that link. I will never become a guru. My first step will be finding existing Cal that accomplishes tasks similar to my goal, then modify if possible. Lots of voodoo and workarounds in Cal.

Thanks, the first 2 links on that page are new for me, so some reading to do.

Rogério I just put 2 and 2 together and discovered you are the author of HumanizePlus cal. Can you point me towards resources that will help me understand the basics of Cal? I am fluent in several programming languages, I've wanted to jump into Cal and I now have a couple of specific tasks that I'd like to accomplish with Cal. I'd like emulate a couple of the functions in Cubase Logical Editor that I can't find existing Cal files for.

And as you work with artic maps for other sample libraries you will find that the "most essential thing" can be different. Your find of extending "everywhere it belongs" is needed by your current sample library. But I use little blips of artic maps in other libraries like VSL Synchron and they work fine. So you do end up creating slightly different work habits for each sample library. But at the end of the day artic maps are great for navigating complicated libraries and for documenting what you have done. Here's a project using VSL BBO Eridonus which has lots of riffs and effects. I would go nuts returning to this project after a couple of months if I didn't have all the artic maps to document what was going on.

Try setting the velocity of the articulation notes in your Chase Mode Notes to something other than 0. In the latest version of Cakewalk, that I'm using, the velocity of notes you add defaults to 100. Might be worthwhile to update Cakewalk if you are not on latest version. Some sample library instruments will interpret a note with velocity 0 as "Note Off".

Fwiw In US many public libraries use Libby to provide magazines to members. My library offers Computer Music along with 2k other magazines. May be worth checking yours and getting card.

Try switching Chase Mode to Note. And if that doesn't work try Chase Mode to Full. Reply if still not working and we'll talk more. Each library may behave differently but articulation maps are really helpful once set up. Once you get a couple of artics working it's easy to copy and create larger maps. And look thru threads in the artic maps contents section. https://discuss.cakewalk.com/index.php?/forum/37-articulation-maps-new/

That is frustrating. Over the long haul Nektar does an excellent job of integration with Daws but issues crop up. One thing to keep in mind is Lx61 uses 2 midi streams to talk with Cakewalk. One is the usual music stuff and the other is transport and mixing control. Worst case, reset Lx61 to factory preset and reinstall the Nektar Cakewalk package. Good luck.

Here's a short vid demonstrating one task that chord track could help with.

Please give us more info. I had read about Studioware and had decided I didn't have the tools needed to create panels.

And also excellent 2nd video on editing CC data.

Mike at @Creative Sauce has a great video.

Read up on the stretch tool. I use it when I step record ostinato as 1/4 notes and then reduce them to fit whatever slot I want.