David Baay

What are the symptoms of not loading in Sonar Free Tier? This is abaoslutely not typical. Many here have projects and even WRK files going back decades that open without any issue. You should open a dedicated thread to troubleshoot your issues.

There have been issues reported with a recently released driver update from Focusrite. I dont know whether Focusrite have yet addressed this. Check their website/forum for info, and maybe try downloading the previous driver release.

Whatever is going on is not new to Sonar. On my non-touch screen laptop CbB has the same small-sized three-octave keyboard as Sonar. And on the touchscreen, they both have the larger 2-octave one which makes sense for touch-playability. I don't think I have ever seen more than three octaves in any version of SONAR/CbB/Sonar on any machine.

I'm not aware of any VSTs that send MIDI to a virtual OUT from the UI keyboard, but it's possible such a beast exists.

If you had a touch screen, it would be big in Platinum the same way it is in Sonar - probably even bigger because Platinum doesn't use vector graphics which are, in fact "wonderful", notwithstanding the handful of teething problems that some (not all) have encountered, depending on their display hardware, monitor setup, O/S configuration and project layouts which are infinitely variable.

That is definitely not right, and nothing like what I get. I have two laptops with different display resolutions but scaling adjusted to give very close to the same amount of realestate in Sonar. One is touch and one is not. The touchscreen shows two octaves and the non-touch shows three. The keyboard on the touch screen is much bigger, using approx. 60% of the screen width while the keyboard on the non-touch screen uses only about half that. But both are displaying the octave and hold controls amd full key lengths.

Working here, also. What exactly is not working? Not loading, not responding or some function not having the expected effect? Possibly the FX bin itself is disabled? This has caught me out a number of times.

A Move is inherently a Cut-Paste. That said, I thought Ripple All would always move everything regardless of Cut/Copy and Paste settings. If that's not the case, I think it should be. I'll try re-testing with one or both of my Copy/Paste Special dialogs set to exclude Meter/Key changes. EDIT: I retested this, and Ripple All seems to move everything, as expected, regardless of Cut/Paste Special settings. As this point, I think you might need to share a stripped-down copy of your project with exact steps to reproduce the issue.

What are you using for an audio interface, and are you trying to have MIDI in the project drive the sound engine in the Nautilus? If so, and you want to monitor the Nautilus' output through CbB (as opposed to direct from the Nautilus to headphones/speakers), you need to have an audio track in CbB with Input set to the audio input to which the Nautilus' audio output is connected, Output assigned to your audio interface (usually via a Master bus) and Input Echo enabled. If that's not the setup/intent, let us know what's in the project and how you're routing MIDI and audio.

Are you not able to record to an armed audio track, or is it just that you don't hear live output because neither the Mackie's direct monitoring mode or the Sonar track's Input Echo are engaged? You need to have one of the other - but not both - enabled in order to hear yourself in real time (since you're recording from a mic, I presume you're monitoring output from the Mackie via headphones...?). For monitoring your own performance while recording, you'll want to be using direct monitoring because 27ms of latency at 512-sample buffer is going to be to much for input monitoring The windows audio settings are only relevant to Windows sounds and generic multimedia players and browsers that use it; Sonar is going to be using the interface driver directly via its ASIO driver so the Windows audio setup doesn't matter, but you might do better to assign your onboard audio (e.g. Realtek) as the default I/O device for Windows, leaving the Mackie dedicated to Sonar so there's no chance of a conflict.

The question was about how many octaves are displayed at once.

My conclusion is that only Sonar has a sophisticated enough start-up process to expose a phony ASIO driver. 😁

Appears to be working in general here. Can you give a specific example of where the meter changes occur, what you're moving from where to where and how the result differs from your expectation?

I think you must be remembering some 3rd-party keyboard app.

Yes, that Generic Low Latency ASIO Driver is a Steinberg thing - usually installed with Cubase, but I think some other audio softwares leverage it as well. As Mark said it's that 'aggregate driver' tying up your dedicated Tascam interface driver when it's enumerated on startup that causes the problem. The Steinberg driver is a known cause of issues in Sonar for this reason and needs to be uninstalled. I've never had it, but I assume that can be done through Windows Applications and Features. If not you can just remove its key from HKEY_LOCAL_MACHINE\SOFTWARE\ASIO