Canopus

In the land of XLN Audio (and Toontrack as well) they have a saying that goes: Svepningen har inga fickor.

Just got myself the last missing paks & pieces of Addictive Drums 2. H*ll yeah. XO is next in line but will probably have to wait until next year.

Any chance of having this issue fixed as well in the main release? The problem still exists in 2020.11 Build 090. A video is attached to the initial post.

Unfortunately, no. I have been asking for such a feature for many years but it doesn’t seem to happen. Twice in the old forum: http://forum.cakewalk.com/FindPost/3493927 (2016) http://forum.cakewalk.com/FindPost/3758173 (2018) And once in this new forum: https://discuss.cakewalk.com/index.php?/topic/1925-how-to-easily-fit-midi-content/&do=findComment&comment=15437 (2019) I guess I've given up.

Let me first say that it’s great to have such an extensive library of Cakewalk articulation maps available. That was quite an accomplishment to make the conversion in such a short time. I must admit that I personally already have made Cakewalk articulation maps for almost all the libraries I own and normally use. Also, almost €70 for the whole shebang might be a bit too much for most amateurs like me. But if I may so suggest, why not consider creating smaller and cheaper sub-packages targeting a particular developer and/or library. Let’s say that I could get all Kontakt libraries for 8DIO for less than €10? Now that would definitely be an option. On a side note: one thing that I wasn’t particularly keen on though was the global use of the articulation name Long for Sustain regardless the tag used in the library itself. And perhaps there are more such anomalies? A better approach I think would have been to use the actual articulation names used by each manufacturer. However, I guess that could be quite easily changed by a global search and replace in a text editor if one would be so inclined.

Chord tracks were introduced in Cubase 7 (2012), six years before Studio One 4.0 was released with a similar function (2018). So Cubase was clearly leading the way. However, I have no idea how Cubase now stack up against Studio One in that respect.

Addendum: for those who have got a Groove3 subscription and haven’t yet noticed, Eli Krantzberg has expanded his tutorial UVI Falcon 2 Explained so that recent additions in Falcon 2.1 have also been included. The videos added to this tutorial are: Magnetic Bass Shaper (02:15) - Hear how this new bass-focused FX module adds the saturation characteristics from two different models of Fasel Red and Fasel Yellow inductors. Feedback Machine (03:52) - The Feedback Machine is a variant of the standard Effect Rack with a featured feedback loop, providing control over feedback amount, feedback injection delay, and overall mix amount. Explore it in action on an aggressive organ lead. Step Arp (05:45) - A beautifully designed hybrid step sequencer and arpeggiator, Step Arp gives unprecedented per step control over every aspect of pitch, time, and more. Gate Mod (04:05) - Learn about this probability based tool that allows us to add note skipping with optional beat protection, delay, and adaptive ratcheting. Gate Mod Poly (04:15) - See how this polyphonic version of the gate mod script is used to add probability based skipping, delays, and ratcheting on a per note basis, using a melodic sequence. Gate Mod Bernoulli (03:38) - Explore this 2 channel probability based note router on a simple melodic pattern. Chord Strum (01:36) - Watch how this new performance script is used to spread out the notes of a chord by pressing a trigger note outside the chord’s range. Arpeggiator Record (03:16) - Discover this fantastic new arpeggiator feature, which allows you to create patterns by step recording the notes presses on your keyboard instead of using the mouse.

When I try to move multiple articulations, it doesn’t seem to work in the same way you would move multiple MIDI notes in the PRV. After the selection has been made, Shift+Drag only moves the articulation located directly under the mouse and not the whole selection. That's not what I would expect, but perhaps I'm wrong? Here’s a short video.

I bought Cubase Pro 9.5 when Sonar was abandoned and later upgraded to 10.5. But the way Cakewalk is constantly being bug-fixed, tweaked and developed (now with articulation maps!) I can’t really see myself spending more money to upgrade something I hardly ever use.

I bought the original Synth Anthology in 2015. One of the UVI upgrades I never made and later regretted was from Synth Anthology to Synth Anthology 2. Now I’m offered an upgrade to Synth Anthology 3 for only $49. I’ve never previously seen UVI offer upgrades for those that doesn’t have the next to last version, so that was a positive surprise. And hopefully an indication for the future.

Yes, when CbB informs you that an Early Access version is available you simply choose not to install it. This is how the 2020.10 EA prompt recently looked like:

I see that you are using a German version of CbB. As far as I know the early access builds never support any other language than English because localizations are not a priority at that stage.

Depending on how you’ve set your Base Octave for Pitches in Preferences, you might have to adjust for that in the MIDI Events > Key/CC#. Most likely you should increase each Key/CC # with two octaves if you are starting from a Cubase Expression Map.

Until this function hopefully will be further developed, here's a temporary work-around to have Articulation Map stored in multiple-level nested structures. I have placed an empty text file called empty.artmap on each folder level where valid artmaps are not naturally stored, like on a Developer folder level if you’d like to have a further breakdown. Of course, these files could be called anything as long as they have an artmap file extension. Also, and equally important, by giving these empty files a Hidden attribute the folder structure will be visible in the Articulation Map Editor without showing the dummy artmap file(s), which might otherwise be distracting. However, there is one important drawback: the current Search function doesn't appear to scan in sub-folders located under a folder where no hits are found. However, with nested folder structures the Search function might be of less importance. I guess it’s a matter of personal preferences. And I actually have a workaround for that as well, but I'll spare you the ugly details.

Yes, I think that's exactly what I said.