Jump to content

Steve Harder

  • Content Count

  • Joined

  • Last visited

Community Reputation

135 Excellent

Recent Profile Visitors

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

  1. I don't often add new vst so I do a manual vst scan when needed. This also reminds me to visit the "uncategorized" section of the menu to select categories for the addition. Cakewalk by BandLab will scan your plugins automatically each time you open the program. You can change this in the Preferences menu under File > VST Settings > Scan Options.
  2. Here's an important tweak. My goal was to get Ch1 - bottom note, Ch2 - 2nd from bottom, ... Within midiPolyphony set NotePriority to Low.
  3. I really like the real-time capability. I can rough out a piano sketch with chords on a single track. Then I can send that track to Midipolyphony to split the chords and send to multiple brass or string instruments. I can audition different instruments or easily switch the stack number of the chord note going to that instrument. I also can tweak note timing. And this is all without committing any midi to the individual tracks. Eventually I do arm some or all of the instrument tracks and record the Midipolyphony output and then go on to really finetune timing, etc. But a lot of the heavy work gets done in an environment that encourages experimentation before I commit to lots of individual midi tracks. CAL doesn't give me that real-time capability.
  4. I searched several threads on discuss.cakewalk seeking a means of splitting sequences of chords into separate tracks, but I didn't find a solution that didn't involve a lot of copy/paste/highlight/delete. And I didn't find any mention of Midipolyphony vst, so started new thread. I wanted to take a chord progression I liked and split it up to be sent to individual instruments, and get it done efficiently, and in real time if I was just noodling around. I've now found a vst that will take a chord of up to 16 notes and split it to 16 midi channels. Midipolyphony.dll is a 64 bit vst created in 2011 and then eventually forgotten about. You insert it as an instrument. You route midi to it. Midi that contains non overlapping chords. You insert multiple instruments or midi tracks. You set the input of each to a specific Midipolyphony midi output channel. You turn on their input echo. Now select the Midipolyphony track and play chords into it. The lowest chord note played will end up on channel 1, 2nd lowest on ch2, etc ... Here's an important tweak. My goal was to get Ch1 - bottom note, Ch2 - 2nd from bottom, ... Within midiPolyphony set NotePriority to Low. Caveats: the notes in a chord must arrive simultaneously in Midipolyphony. So playing on keyboard may not provide correct notes. You would need to record and quantize before sending to Midipolyphony. For my noodling around purposes I set up chord progressions in Scaler, bind chords to keyboard, so then when I press a key all notes are sent simultaneously. Or I send quantized midi. The processing seems immediate, I used notes 8 ticks long as source chord and they were processed. Playing midi on Midipolyphony track and recording on a split out track, the MBT in the event list is identical, so no latency that I can detect. Midipolyphony has other capabilities hinted at in discussion forums, google "kvraudio insert piz". You will need to do some digging to suss out the features. The "Insert Piz" package has a number of different vsts, created when routing/tweaking midi was a much more hands on process. Last active dates were a decade ago. you can download it here, its in the "pizjuce_x64_20120113.zip" ... top of the page: https://code.google.com/archive/p/pizmidi/downloads And because midipolyphony.vst is public domain I've attached it here as an unzipped file. As Midipolyphony is poorly documented and unsupported YMMV. But I'm getting a lot of good out of it in the manner I use it. FWIW. midiPolyphony.dll
  5. My normal workflow is to use Synchron player interface to audition articulations and then assign appropriate artic from map. My strategy for artic map layout is to mimic the layout of the Synchron player menu as this makes finding correct artic easy while looking at Synchron player. This is a wonderful brass library. The solo brass have pretty extensive articulations. Here's the Solo Trumpet. VSL Synchron Brass by Harder.zip
  6. Rolling back to 2021.04 solved my issue, so I'll stay there until I get my new artic maps built. Would suggest bug fix on 2021.06.
  7. I have an issue with editing long articulation names in 2021.06. I have not reverted to prior versions to see when issue cropped up but I know when artic maps were initially introduced I had no problem double-clicking an artic name and then being able to see or scroll through a long string of characters while editing. I now can only see or scroll through the left most characters and have to guess at what I've typed. Above is a long artic name that I've entered while guessing. Above is the edit window that only shows me the left most part of the long artic name. This behavior occurs in any of my artic maps so do not think it is tied to a specific project. Above is an entry from an artic map that I created in Jan 2021 ( don't know for sure what version of Cakewalk then). I had no issues then but now cannot scroll in 2021.06.
  8. https://www.vsl.co.at/en/Synchron_Series/Synchron_Brass
  9. Artic maps are very powerful while using orchestral libraries but other instruments may not benefit from them as much. The quick replies to this thread indicate that some folks are using them, or at least paying attention.
  10. Re: Opus and Orchestrator Absolutely no issues running Opus and Orchestrator in Cakewalk.. I've had 10 instances of Orchestrator along with multiple instances of Opus along with Kontakt and Synchron being driven by Orchestrator, all happily coexisting. Opus "dont preload" is a huge ram saver. EW Michael Pluebell, head of tech support: "Hey Stephen, We tell people that we don't officially test on cakewalk so it's not officially supported - which is true. But in most cases, any daw accepting 64-bit vst, vst3, au, or aax plugins should work with Opus. "
  11. 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?
  12. 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.
  13. 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.
  14. 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.
  15. 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.
  • Create New...