Canopus

No, that’s not correct. Their budget options UM2 and UM22 for very cost conscious users do indeed only offer ASIO4All drivers, but all their slightly more expensive options, such as the UMC204HD and UMC404HD, have native ASIO drivers. Just have a look at their download page under Product Group Audio Interfaces. https://www.behringer.com/downloads.html

I would look into the different pdf manuals supplied by NI. You will find them in your Shared Documents folder. At the end of each drum manual you will find all kit pieces and their articulations laid out with their respective default key and MIDI note number. They seem to be ordered not by key but by kit piece. Also, the default key in CbB will depend upon you setting of Base Octave for Pitches in Preferences. As an example, here’s the first part of the table for Abbey Road 50s Drummer Autumn Kit.

Drum Replacer works fine for me, but I noticed that @e2studio has an Italian version of CbB and may I assume that @Guillermo Torres Va has a Spanish version (mentioning GoogleTranslate)? Just a shot in the dark: perhaps there’s a localization issue with Drum Replacer?

No, the bom file only contains the list of files that should be installed but not their destination. The destination folders are fetched from the system registry. On my computer AAS installs no less than 3x VST2 and 1x VST3 of every instrument. So be it.

This is what I do after having downloaded a Custom “All” Installer from AAS: After having unzipped the aas-software-installer-win.zip file, I open up the file called “bom” in a text editor (that file hasn’t got any file extension). The bom file is a text file stored in the InstallerData folder containing references to everything that should be installed. In the text editor I then remove all lines that specifies my duplicates and my session instruments. As I’ve got the full version of everything AAS I don't want the session instruments installed, but they are always included. After saving these modifications I finally run the Setup program.

I just posted to say ...

There are many ways to skin a cat, and even more ways to extend a MIDI clip in CbB. If you get tired of the Groove Clip method mentioned by Colin, you might optionally try any of these methods: Ctrl+D to duplicate the clip any number of times. Use Paste Special and specify any number of repetitions. Use the Pattern tool found among the Draw tools in the Control Bar. But regardless method, just as Colin said you’d first want to stretch your MIDI clip to the next measure/beat boundary by dragging the right clip boundary. Otherwise the end result may be unpredictable.

Pretty much covered in this thread:

Oh, I agree! Having a Refresh button in Preferences > MIDI > Devices would be solid gold in cases when you’ve forgotten to turn on a USB MIDI device before CbB is started. Also it would be great if the Control Surfaces section at the same time would be refreshed with available in/out ports. The only currently working solution seems to be to restart CbB and reload your most likely large and very load-time-consuming project yet again ... @msmcleod Now that you're a part of the Cakewalk development team maybe you still feel that such a Refresh button would be really helpful...?

Thanks for the info! Luckily for me my MIDI keyboard has both a classic DIN MIDI output as well as a USB MIDI output. I’ve previously only had the DIN output connected to my interface and that was of course also the In Port chosen for ACT. But by specifying DIN as input for ACT and USB as input in Track View, I seem to get the best of both worlds: being able to use knobs and sliders of my MIDI keyboard as a control surface while not losing the animated keys in PRV. Now I only have to get myself a longer USB cable.

Just a wild guess: AAS do optionally supply NKI presets and previews for Komplete Kontrol. Is that something you have installed as part of your AAS plug-ins? If so, maybe such additions might add to both load times and memory usage. FWIW, I’ve also got the latest VST3 versions of these AAS plug-ins installed and have no problems running them in CbB on an eight-year old Core i7-3770 with 32GB of RAM and Windows 10 Pro 2004.

In order not to derail this thread any further, I will just say that the posts above indicate that the ACT layer somehow blocks the MIDI note data being sent from the controller to the code that renders the PRV keyboard. I don’t think it’s is any more complicated than that. And I sure hope it’s not by design. The important thing is that there now seems to be a reliable way to reproduce the issue.

Quite so! Great troubleshooting, @Mehrdad! In CbB I had created an ACT Controller/Surface for my MIDI keyboard and when I now removed it, the visual keys on the PRV keyboard started to work. And in SONAR Platinum by contrast I did not have any ACT Controller/Surface defined, which is why the visual keyboard worked there without any issue. Now that the cause seems to be determined there’s at least some hope to have it fixed. As long as the root cause wasn’t found I didn’t see any point in reporting it as not everyone was experience this issue. Maybe we should send a trouble report each to support in order to get some attention?

The same issue of not seeing the full Select module in Large size was present in the Early Access release as well. I assumed it was a cache issue so I opened and closed CbB a couple of times and I may also have switched between different themes once or twice. Finally CbB displayed the Large module as expected and I haven’t had this problem since then.

I can see that new owner is based in USA. What’s going to happen next, you might wonder.

This is not something that started to occur in 2021.01 EA. It has been like this for quite some time in CbB production releases, although I don't know exactly when it started. I know for sure that it was present in 2020.08 but I think it was a problem long before that. However, I also realise that not everyone is affected by this issue.

Yes, same for me as well. This problem has been mentioned before, but I’ve never seen any response or comment from support. https://discuss.cakewalk.com/index.php?/topic/18788-prv-animation-on-midi-input https://discuss.cakewalk.com/index.php?/topic/18923-issue-with-piano-roll As I wrote in one of those threads, when I run SONAR Platinum 2017.10 (i.e. last SONAR) it still works with live input, but not so in CbB. Something seems to have been changed in the code that renders the PRV keyboard, but not for the better. Here’s an animated GIF showing the problem in CbB side by side with SONAR:

And you can get just Pinnacle Studio 24 Ultimate for only €1. That software has a regular price of $129.95. I've already got Pinnacle Studio 23 Ultimate but for €1 I have no problem buying a new full license. Heck, the money is burning in my pocket so I’ll probably buy two.

The theme Lead has now been updated to support GUI modifications in CbB 2021.01, or more specifically the addition of four buttons to the Large size Select module. Personally I will however switch to the Medium size Select module so that everything will look as before to save some screen estate. There are some additional changes as well: The Arm All Tracks button in the Control Bar’s Mix Module has previously been blue (as it is in Mercury). However, as the Arm button on each individual track is red, Arm All Tracks has now been made red as well for better consistency. The meters in the Performance module have been changed from orange to blue to better match the theme’s overall appearance. Unselected synths in the Synth Rack now have a dark background colour, as the previous blue highlight background for both selected and unselected synths may have been confusing. The button in the Export module had a slightly incorrect back­ground in both large and small size. This has now been fixed. The Freeze and Archive buttons didn’t exactly match the appearance of the other buttons in the Track module. This has now been fixed. Download the theme from the link supplied in the first post.

Both Gran Vista and Carbon have now been updated to support GUI modifications in CbB 2021.01, or more specifically the addition of four buttons to the Large size Select module. There are some additional modifications as well: The Control Bar buttons used to set areas for Select, Loop, and Punch have been slightly modified, in that the marker triangles on those buttons have been gi­ven the same colour as the corresponding function in the Track View; yellow for Loop, green for Selection, and red for Punch. This is a feature that I’ve borrowed from my Lead theme where it was introduced. Here’s how these changes look in Gran Vista, but Carbon has similar modifications. The Arm All Tracks button in the Control Bar’s Mix Module has previously been blue (as it is in Mercury). However, as the Arm button on each individual track is red, Arm All Tracks has now been made red as well for better consistency. The meters in the Performance module have been changed from orange to blue to better match the theme’s overall appearance. That colour wasn’t pos­sible to change at the time these themes were created, but has apparently been quietly exposed to the Theme Editor since then. Unselected synths in the Synth Rack now have a dark background colour, as the previous blue highlight background for both selected and unselected synths may have been confusing. Download the themes from links supplied in the first post. There you will also find a link to the release history.

Well, I think there is. In Preferences > Customization > Keyboard Shortcuts > Key Bindings, set Area to Track View and in the Search field write Ripple. This will result in two functions being displayed: Options | Ripple Edit Selection and Options | Ripple Edit All, ready to be bound to whatever keys you'd like.

Have you looked at this page? http://www.moessieurs.com/ins-montage.html At the bottom of the page you can download a Cakewalk .ins file, which, if I understand it correctly as it's in French, is said to cover Montage with OS V3.50. I don’t have a Montage myself though so I haven’t tested it.

Yeah, I got a measly €20 voucher this time which equals around 12 % of my purchases directly from UVI last year. And it’s only valid until the last of January, a month when they normally don’t have any deals anyway. Oh, well. They can keep it. My loyalty has its limits.

My plan was to watch for a couple of minutes but I ended up seeing the whole hour-long video. Great performance, great tribute.

There are mainly two types of piano plug-ins; those that are sampled and those that are modelled. Sampled instruments are based on actual recordings of physical instruments, while modelled instruments are based on computer algorithms emulating the sound of physical pianos. There are also some hybrids of which the True Pianos previously bundled with some versions of SONAR is one. Of the pianos mentioned above, XLN Audio's Addictive Keys is a sample based instrument while Pianoteq makes modelled ones. Each kind of technique has its loyal followers. May I suggest that you try to decide for yourself what pianos you prefer before you pick out your Big Credit Card. Free pianos do exist but are few and far between. Also, the quality may vary. In addition some of them require the full Kontakt plug-in from Native Instruments, which in itself is quite expensive. There are plenty of demos. Some of them are quite usable but often come with a limited number of octaves and/or fewer microphone perspectives. The 49 key demo from XLN Audio that John mentions above I think is very good. It's free and there is no time limit so you can use it as long as you wish. Should you look for a full 88 key version and are on a tight budget, there is a grand piano called Mini Grand from AIR Music Technology which often can be found for $10 or thereabout. It’s actually currently available for €10.27 at Plugin Boutique. It’s not on level with more expensive grand pianos, but as always you get what you pay for. However, it does require iLok for copy protection.