msmcleod

You're probably thinking of Bars & Pipes Professional by Blue Ribbon Software on the Amiga... They were working on a Windows version (for win3.1 IIRC) when Microsoft bought them out; nothing ever came of the software except that the first (maybe first few) DirectX SDKs included some version of it for devs to implement things with (but I didn't find out about that till much later, after I was using Cakewalk 3 for windows, or I would've found a way to get that SDK just to use the B&P) I don't know CB's full history, but I thought they were concurrent with B&P's time, but CB was on the AtariST? The pre-cursor to Cubase was Steinberg Pro24, which definitely was on the Atari ST. IIRC Cubase 3 was the last version on the Atari.

Meter changes always need to be on a measure boundary - they don't make sense otherwise. So unless everything lines up with measure boundaries both before & after the paste, the meter map may not match what you expect. Also, be mindful of what you're copying pasting... by default, copying/pasting a clip will NOT copy the meter changes with it. For example:

We've identified the cause of this issue, and will issue a fix with the next update.

More colour customisation is coming:

Working fine here... Not sure what to suggest here. May be try a full VST scan in case your plugin catalog has somehow gotten corrupt?

The "generic low latency driver" is an aggregate driver - i.e. it's a wrapper around the WDM driver. It may behave like an ASIO driver, but it's talking to the WDM driver rather than the audio interface hardware directly. Sonar enumerates the drivers and their capabilities by opening each driver and determining the modes that are supported. This is done on start up of the application. When it opens the generic driver, the driver opens the device (and all other devices) using WDM. It then closes the driver in order to open the next ASIO device. The problem arises when, after closing the driver, and the driver doesn't let go of the WDM driver properly. You then get issues when opening the real ASIO device, as it may be using a different bit/sample rate than the one it's trying to use in ASIO, and although the drivers are separate, it's still just the one audio interface - e.g. it can't be at 16 bit/44.1K and 24 bit/48K at the same time. ASIO4ALL certainly is designed to be this way - i.e. when closed, it stays alive in the system tray with the WDM drivers open. The generic low latency driver (which I believe is a Steinberg device?) should behave more gracefully, however it's still at the mercy of how well the WDM drivers were written. The easiest thing is just not to use wrapper drivers, and stick to the manufacturer's genuine ASIO drivers.

There is no imposed device limit in Cakewalk or Sonar - they simply list the devices available from Windows. I've got 22 MIDI input/output devices listed on my office PC. I'm using MME as my MIDI driver mode.

From Google AI: The 16-device limit is a legacy problem often caused by "ghosted" or duplicate MIDI drivers in Windows' Device Manager, not a true Windows limit. To resolve it, you must show hidden devices in Device Manager (by typing set devmgr_show_nonpresent_devices=1 in Command Prompt) and then uninstall the greyed-out, unused MIDI devices. After deleting the duplicates, restart your computer to fix the limit and allow more devices to be connected. Steps to Fix the Limit Open Command Prompt as Administrator: Search for "CMD", right-click it, and select "Run as administrator". Enable Showing Hidden Devices: Type the command set devmgr_show_nonpresent_devices=1 and press Enter. Open Device Manager: Search for "Device Manager" and open it. Show All Devices: Click on the "View" menu and select "Show Hidden Devices". Locate and Uninstall Ghosted MIDI Devices: Expand the "Sound, video and game controllers" section. You will find greyed-out entries for unused MIDI or USB audio devices. Right-click on these greyed-out devices and select "Uninstall". In the dialog box that appears, make sure the option to delete the driver software is unchecked to keep the "real" port working. Delete Duplicate Entries: You may find multiple duplicate entries for a single device; delete the greyed-out ones. Restart Your Computer: After deleting the ghosted devices, restart your PC. Why This Happens Driver Duplication: When you uninstall a MIDI device, sometimes Windows doesn't fully remove its driver. Each time you reinstall the device, a new driver entry is created, leading to duplicates. Ghosted Devices: These duplicate entries count against a hidden device limit, even though the device is no longer in use. Legacy Limitation: This is often a remnant from older system designs and not a fundamental Windows limitation on the number of devices you can connect. FWIW - I've had a similar issue before, and the easiest way to stop it is to always use the same USB port for each device every time. A switched USB hub (i.e. with switches on each USB port) can help with this, as you can leave them plugged in and just use the switch to switch them on as needed. Just make sure it's just your MIDI devices on the hub, and not your audio interface!

If tracks are hidden, the track manager button will be lit. Clicking on it will unhide all hidden tracks; clicking again will hide the any tracks that were previously hidden. FYI - any hidden track presets you make in the track manager can be accessed quickly by right clicking this button:

The Sonitus plugins will remain in your plugin library as long as the operating system supports them. If your "Replace if possible on Project Load" setting with Preferences->File->VST Settings is unchecked, then your existing Sonitus plugins will remain unaffected. You'll be free to use either the old Sonitus plugins or the new ones. If your "Replace if possible on Project Load" setting with Preferences->File->VST Settings is checked, then loading any project with the old Sonitus plugins will result in them being replaced with the new Core plugins. Even if you had this checked, and migrated the Sonitus plugins to the new Core plugins in a particular project, there's nothing stopping you inserting the old Sonitus DX plugins... however these will be replaced with the Core plugins if that setting is checked when you next load the project.

Don't confuse the list of tempos in the Tempo Inspector with the tempo map - they're not the same. The list of tempos in the Tempo Inspector is a representation of the nodes / curves within the tempo track envelope. In most cases, the tempo map itself is then derived from that envelope, although there are exceptions: - When detecting tempo via Melodyne - When importing a MIDI file - When using "Set Beat at Now" - When using "Fit to Improvisation" - When loading an older pre-tempo track project ... in these five scenarios the tempo envelope is constructed from the tempo map. In saying that, there should be no issues inserting multiple tempos of the same value if you use the tempo track:

@Larry T. maybe I'm not fully understanding the issue, but what @Amberwolf says is correct: adjusting/automating the volume level alters volume by that amount, not to that amount. So the only time you'd see the db levels match between the volume fader and the meter readout is if the audio clip is at 0db. In saying that, it could be a completely different issue - have you checked you've not engaged offset mode at any point?

^^^ this Set your workspace to None

I think it's worth mentioning that unless you're adding MIDI parts or need a Sonar-generated click-track, it's not always necessary to have a tempo map. Even if you're adding MIDI parts, it doesn't really matter unless you need to edit them. You can have tempo set at 120bpm for the whole song, and the audio going between 85bpm and 90bpm, and it won't make a blind bit of difference. The only thing is that the time-ruler in M:B:T won't match the material. If I've got a live band recording with only audio tracks, for the most part I don't care about beats/measures. I'll just set the time ruler to H:M:S:F and mark out verses/choruses with arranger sections (with the arranger track in absolute time). That way I can easily navigate throughout the song and never need to worry about bars & beats. Where it does get useful is if you want to vary / correct timing. But there's nothing stopping you doing the tempo map later only if you actually need it. What I would recommend though, is if you are correcting timing by nudging the odd snare beat around, do all of your timing tweaks before you define the tempo map.