msmcleod

TouchDAW for Android, or TouchOSC (for iOS & Android) are good alternatives.

I think this is probably the likely cause. Whenever I've had similar issues (though, normally this is with MIDI devices rather than audio), it's been a power-on order thing. General advice: 1. Always use the same USB ports for your audio devices. Swapping them around causes Windows to see them as a different device. 2. Switch on your audio devices before you switch on your PC 3. Once you've switched on your PC, give it time for the L20 to initialize before you start Cakewalk. Opening the L20 ASIO panel before you start Cakewalk will show you if it's fully ready to go or not. 4. Make sure you've NOT got any aggregate ASIO drivers installed - i.e. ASIO4ALL, or the Steinberg, FL Studio or Magix equivalents. The way these drivers work is by wrapping your real device's WDM drivers up as ASIO drivers, which can cause the real ASIO driver to be blocked when Cakewalk tries to open it.

A couple of things that may be different from my setup: 1. I don't use the Korg USB drivers, as they keep breaking with Windows 10 updates. It works fine as a class compliant device. 2. Set your MIDI mode to MME rather UWP within Cakewalk.

SONAR Platinum was rent-to-own. If you paid 12 consecutive monthly payments, you'd own the version of the product at the point of your 12th payment. If you paid 12 months up front, you'd own the version of the product exactly a year after your payment. Once you owned the product, that version would continue to work regardless of whether you continued to pay or not. This is different from a subscription, which disables the product (either partially or fully) when you stop paying.

In my experience, the Korg nanoKONTROL 2 / nanoKONTROL Studio are by far the easiest to integrate with Cakewalk - as long as you're using it in Mackie/SONAR mode that is. It's pretty simple to set up... just follow the steps in the nanoKONTROL 2 manual: SONAR 1. While pressing and holding down the SET MARKER and REC buttons, connect the USB cable from your computer to the nanoKONTROL2. 2. Open the “MIDI device” window in SONAR, then select nanoKONTROL2 for “Input” and “Output.” 3. Open the “Controllers/Surfaces” window, then select “Mackie Control” for “Control Surface.” 4. Select nanoKONTROL2 for the MIDI In/Out ports used. If you're using it as a generic ACT controller, your mileage may differ however. Swapping between nanoKONTROL 2 "modes" can be a PITA ( i.e. using it in Mackie/SONAR mode, then changing it to CC mode) so I'd avoid doing it unless you want to go through the setup steps every time you swap. Better to get an additional (and different) controller so you have one for each mode. But to answer the original question of the post... "How many users does CbB have?"... go here: https://bandlabtechnologies.com/brands/cakewalk/

The issue is than you're using a network path - why this causes an issue, I'm not sure - we'll investigate further. For the meantime, I suggest mapping a drive to \\PLATINUM_STUDIO\! Wave\ So in Windows Explorer: 1. Navigate to \\PLATINUM_STUDIO 2. Right click on the "! Wave" directory, and choose "Map network drive" then choose a drive letter (e.g. P: ) 3. From then on, access your project as P:\Brian Sherwood\Step by Step.... etc. You may also wish to change your Project Files location within Preferences to P:\Brian Sherwood. FWIW - this isn't a regression in 2023.09... I get the same behaviour in 2022.11 if I use a UNC path (e.g. \\MYSHARE\ )

Ah yes, this makes sense - the selection has a time extent which in this case is dictated by the clip extent. So it will only select nodes that are under the clips that are selected.

I suspect this is down to how you are selecting things. Select All selects all tracks, which subtly different from selecting clips - and it's the clip selection that triggers selecting the associated track envelopes. For some operations, there is a notion of "implied" selection, where tracks are selected because all their clips are (and vice-versa), but not everything checks for this. Also synth automation, although shown on the track, isn't actually "owned" by the track the envelope is shown on - instead it's owned by a hidden automation track ( this is also why changing the shown automation track is such a simple operation - it only affects display, not who owns it). So this is why volume envelope is selected in this situation, but the synth envelopes aren't. I'm not 100% sure what is going on here, but it could be that the misbehaving envelopes are absolute time based perhaps?

There's a reason why, within Insert Soft Synth Options, "Display Automation On" defaults to "First MIDI Source Track" - it's so both your clips and envelopes can reside on this track and be selected together. This would be my first recommendation. The second would be to ensure you're using either Simple Instrument or Per-Output Instrument tracks. That way, you also get the audio track's volume automation showing. If you're using split instrument tracks, there are workarounds however: 1. If you want the audio track's volume automation to be selected along with the MIDI clip, the simplest way is to use CTRL + left click to also select the audio track. If you're using Copy + Paste (as opposed to CTRL + drag), remember to give the correct track focus when pasting. Alternatively, select the MIDI & Audio track and temporarily "Make Instrument Track". You can then do your operation, then split afterwards. 2. Within the Synth rack, the dropdown in the header allows you to change which track you want the automation for the selected synth to be shown on. This can actually be ANY track you want (even unrelated ones), and you can change it as many times as you want. So you can move your synth automation to the track who's clips your moving prior to doing your operation.

I'm totally confused by this post. The first page of this topic already says there are over 60 bugs fixed in this version. The point of the EA release is to allow a wider user base to verify we've not indavertently broken anything in fixing these bugs. Some such reports have already come in and have been fixed for the main release. There may be bugs that already existed in the 2022.11 release that have not been addressed in this release. This is unfortunate, but we have finite resources and have to draw a line somewhere and release something. It's been 10 months since the last release, and I think the community has waited long enough. This is the Early Access of Cakewalk by BandLab - it's is not going to be priced on the market. Once we're happy no further new regressions are present, we'll either release it as a release candidate prior to a final release, or go straight to final release. Once again, this is a release of Cakewalk by BandLab (i.e. the free product). Work is still ongoing on the new Sonar.

Also check that the following directory is not compressed: C:\Program Files\Cakewalk\Shared Utilities\Internal

@Jim Stamper - we've identified the issue and a fix will be available in the next CbB drop.

Modern cars certainly do have bugs, for example: - I drive through a spot that has a lot of tree cover, so my headlights switch on... it thinks it's dark, even though the dashboard clock clearly shows its the middle of the day. It takes up to 5 minutes to work out that it's not still dark and turn the headlights off. - The automatic wipers come on with a single drop of water, but then don't when it's raining lots of fine drops.

This is an old, old bug - we've tried several times to fix it, but haven't managed so far. There are a number of workarounds: 1. The easiest workaround is to "Bounce to Clip(s)" on each clip, prior to normalizing (this was something we tried to do programmatically as a fix, but had unexpected side effects when done "behind the scenes"). 2. Instead of using the built-in Normalize, use a 3rd party plugin and Process->Apply Effect. 3. Another thing that makes it less likely to happen is to have "Create one clip per file" checked in the Save As dialog. Note that this won't affect existing clips until you modify them.

For any of these services, check the fine print... there are so many gotchas there it's not funny. I've heard stories of people getting copyright strikes on YouTube from their own material, just because they've used a distribution service in the past. Whatever you do, don't base your decision on price alone.

Although the Add Track button does have some options that will override those in the dialog, for the most part the options from the Insert Synth Options dialog will always be respected (and remembered for next time).

The TTS-1 uses exactly the same samples as used in all of the Roland Sound Canvas modules - in fact it's actually a software emulation of the Sound Canvas. The D110 predates the Sound Canvas by quite a few years, and is a totally different beast being based on LA synthesis. AFAIK there are no piano samples in the D110 to speak of (except maybe the shortest piano attack you could imagine). I've got a D110, and the piano sounds are awful... but pianos aren't what you'd use this synth for. The U110 / U220, which were around at the same time have piano samples and aren't that bad for the time, but are to my ears inferior to the Sound Canvas (and therefore the TTS-1 too). I've got both the D110 and the U220 (as well as the MT-32 and CM-64)... they have their uses, but nowadays not so much! The D550 is the only one that still has charm for me.

@FaithD0ntFall - check your Templates folder within Preferences->File->Folder Locations. The default setting is: C:\Cakewalk Content\Cakewalk Core\Project Templates - this is where the installer puts the stock project templates. If you've got it set to a different folder, make sure there are actually project templates in there.

Take this example - you have two documents open in word or in a text editor. You select a range of text in both documents. You press delete - surely you'd only expect the text from the focused document to be deleted?

Commands will always target focus first, then selection. Windows apps have always worked this way - the focussed control receives always receives the command, then the command decides what to do. Right click doesn't always change focus - left click does (or alternatively you can use Tab to move focus around).

FWIW, the new Sonar will have Project Start /Project End markers.

Living in a Box - Living in a Box:

Compare the size of the files on both computers. Cakewalk can store multiple waveforms in a single file (the .wav file format supports this), but some file transfer programs try to get clever and try to re-interpret the file. This was a common issue with Cakewalk bundle files. If the file sizes are different, try zipping up the files into a single zip file and transfer that.

Why record it rather than generate it? MOscillator from MeldaProduction will generate a perfect 60Hz sine wave for you, and it's part of their free bundle: https://www.meldaproduction.com/MOscillator