abacab

Any links? The only reference I see is to the Spring 2018 update.

Right. You can access the release notes for the 8 updates to CbB by clicking the "Whats new" link in the help menu, or here: https://docs.google.com/document/d/1aFOe_zJrd3x2EnaZ_Jc3iSbZPG2WANiCD4_RP83OjlA/edit The installed Platinum Reference Guide PDF copy that I have shows a date of 10/20/2017 as the last update. I believe that was the most current available for the last release of Platinum 2017.10. The associated .CHM file date was 10/23/2017. It should be sufficient for new users, or for those just catching up from Sonar 8.5 or X3, LOL! There was about a bazillion new features added during the Platinum years! I was a holdout on X3 until late 2016, and it really blew my mind what all was new in Platinum by that point. If you want to take a stroll back down memory lane to all of the goodies in Platinum since 2015, you can find them here: https://www.cakewalk.com/Products/SONAR/Whats-New#start The eZine PDF articles linked with the updates in 2015 and 2016 have many good how-to write-ups and tips regarding new features, and are worth reading. In 2017 Cakewalk switched from the eZine format to the "Learn more" links, then with 2017.05, they also resumed publishing the eZine articles in the "TECH + MUSIC" format. Good stuff!

Mac OS is actually a certified Unix OS as of 10.2. So Linux/Unix/BSD do have a lot in common under the hood. The different audio subsystems for each are probably the biggest consideration for any audio development. I have been a Linux user (for non-audio applications) for many years, and I get why some folks want to go there with their audio production. But that is an even smaller market than the Mac OS offers. I really don't think BandLab is going to re-write the Cakewalk code base for cross platform use any time soon. I think most current Cakewalk users would rather BandLab just make CbB the best possible DAW on Windows, and forget making crossovers. My earlier comment was really tongue in cheek, as I wouldn't be holding my breath for this one. There are DAWs that already run on Linux, but I cannot vouch for them as I have not tried them yet. https://www.slant.co/topics/6067/~daws-for-linux

Yes, wushowhide CAN hide the W10 version updates, just like any other update. Windows update will not download and run any hidden updates. This tool even works in Windows 10 Home. But the little trick is you must hide them before Windows update finds them. One thing to be wary of is that MS sometimes re-releases an update, which can make it available again even after you have hidden it, because it is now a new version of the update. Like a game of whack-a-mole.

If you have a recent copy of Sonar installed, you may find a slightly out of date 2348 page PDF version of the reference guide in "C:\Program Files\Cakewalk\SONAR Platinum".

That is why I always take a full Macrium Reflect image before any OS update/upgrade. I don't trust MS anymore. But with that image in hand I can roll back to where I was before in just 35 minutes(1). So if I don't like the update, or something has broken, no problemo! (1) using an external USB3 drive restoring to an internal SSD SATA drive; image file size 132GB.

I would recommend just starting out with all the good freebies available, before buying anything. That would give you a better idea of what your needs are, and where to put your budget. Then I would get all of the $1 - $29 dollar instrument deals that I could find. Then I would get SynthMaster (on sale). Then I would carefully pick and choose from among the current popularity contest winners (and u-he), and choose one or two keepers after trying the demos.

Yup, I generally hide the new releases for 6 months or more, until MS has published a few bug fix revisions. That way I am not just another unsuspecting beta tester.

I find the "wushowhide" utility very useful for allowing the monthly quality & security update to pass, but keeping the latest major feature update hidden until I am ready to upgrade. By hiding the feature upgrade, I can keep it hidden for as long as I want. MS will always quietly push out the next major feature updates when they consider them ready, so it is always good to run this utility before checking for any updates, so as not to get blindsided with a major update.

You can't pick and choose from the Windows update screen anymore, but you can hide the ones you wish to avoid before checking. Once you check, you will open up the chute for anything that is not hidden from Windows to come rolling downhill, LOL! Use the little MS utility "wushowhide" to hide unwanted updates. I have saved a shortcut icon on my desktop for it. EZ Tutorial for use here: https://www.tenforums.com/tutorials/8280-hide-show-windows-updates-windows-10-a.html

The CI feature reminds me of the days of dial-up modems and fax machines. There was always a negotiation step during the dial-up connection process where the two devices decided what transmission rate was acceptable to both. You always had to accept default to the lowest common denominator, or the speed of the slowest device. This sounds like a great way to roll out new MIDI features, while keeping the old standards intact. If you use two new devices that both support a new MIDI feature, then great, they should work together with the new v2 feature enabled. But if you buy a new device and want to connect it to your old stuff, it should still work, but only the v1 features will be available.

Dude, with all respect, you are just 100% wrong about this. I have been using Windows 10 Pro for 2.5 years, and Windows never updates until I ask it to check for updates. There is a policy setting in "Group Policy Editor" that lets you completely 100% disable automatic updating, as well as the notifications. I have never in 2.5 years had a Windows update that ran without me first clicking on "check for updates". Of course, I always take a full Macrium Reflect image before I push that button. Group Policy Editor > Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > All Settings > Configure Automatic Updates The text highlighted in blue in the image above explains how the policy works if it is set to "disabled". I am quoting it here for clarity because it seems that embedded screen captures on this forum have a max width of 400 pixels. Too small to read.

That can work if you are extra vigilant. But I have one computer with Home and one with Pro, and I had a major feature update slip past me on Home once when I temporarily disabled the Metered network option in order to let my monthly security update run. You will have to disable that to get any downloads to run. If you do so, you will effectively open up the download chute to any updates that are lurking when you check for updates. It is too late to pick and choose 'em at that point. Boom! I prefer the confidence that Pro offers to not get blindsided like that!

OK. Have just upgraded TX16Wx to v3.0.16b, and it is silent after the first stereo output in CbB. When I choose "all synth audio outputs" I get all the output channel strips in CbB with the VST2, but only the first output channel strip shows up with the VST3. So then I tried it in Studio One 4, and only the VST2 works over there with audio on all outputs. I can see the outputs from the VST3, but they are silent. I think the dev has some work to do with his new version...

CWITEC TX16Wx Software Sampler 2.4.2d, VST2, 64-bit, installed in 2016. Guess I missed the update? I'll have to check that out...

I have this working in CbB. You first have to insert the TX16Wx synth with "MIDI source" + "all synth audio outputs: mono (or stereo)" in CbB. This will give you all of the channel strips in CbB. This works essentially the same as any other multi out instrument. Then you can assign the individual program slots in TX16Wx to your choice of outputs as S1+2, S3+4, etc., or M1, M2, etc. Mono outputs would probably work best for drums. If you have only inserted TX16Wx as a simple instrument track, by default only S1+2 (stereo) is available for audio output in CbB, and selecting the other outputs in the plugin will fail to pass audio to CbB because no route exists for them in the DAW.

Off-topic, but the Sonitus DX stuff (as well as other DXi like TTS-1) opens in Reaper. That's the only other host that I am aware of with that capability out of the box. Reaper isn't my cup of tea, but I have to credit the developers with writing some tight code. The Windows installer is only 11MB. And the app is cross platform.

That appears to be a rather grand proclamation, but bottom line you offer no evidence, nor willingness to share the solution with the group. Why even bother?

We're still waiting for that.

You can simply install or upgrade to Windows 10 Pro. Then you can either turn off or have complete control over updates via "Group Policy Editor".

While that method will work because Addictive Drums has already been activated on that computer, XLN Audio Addictive Drums is not locked to the Sonar installation. If you ever had a license for Addictive Drums, your XLN Audio account and the XLN Online Installer will let you install your XLN plugins on any two computers, regardless of Cakewalk or Sonar being present. Addictive Drums is often discounted online, and a few of the leading online sellers currently have deals available. The best deal available is usually for the "Addictive Drums 2: Custom" bundle that gives you the full AD2 engine, plus your choice of any 3 kits and any 3 MIDIpaks. For example, the Custom bundle is listed at Audio Deluxe for $99 USD, but in the cart with automatic discount it is currently $82.95 USD. https://www.audiodeluxe.com/products/xln-audio-addictive-drums-2-custom

That is a two-edged sword. The thing that gave Cakewalk an edge on Windows is because the developers worked very closely with Microsoft to leverage Windows audio technologies for the best performance possible. If Cakewalk had been developing for cross platform use from the start, things might be different now. Hindsight and all that ... Unfortunately that leaves the code stuck between a rock and a hard place as far as good, cheap, and fast (pick any two) porting to another platform. The Mac OS since OS X is a certified Unix system, and Apple has written a custom audio subsystem for it: https://developer.apple.com/library/archive/documentation/MusicAudio/Conceptual/CoreAudioOverview/CoreAudioEssentials/CoreAudioEssentials.html Windows audio architecture looks like this: https://docs.microsoft.com/en-us/windows-hardware/drivers/audio/windows-audio-architecture Very different animals.

This distinction has been muddied by Microsoft in their attempt to call Windows 10 the "last Windows", while at the same time trying to push a rapid development cycle of two feature updates a year. These feature updates (known as Anniversary Update, Creators Update, etc.) are actually full version updates, equivalent in some respects to the upgrades to Vista, Win7, Win8, Win10, etc. If you pay attention, you will see a full version installer run each time you update one of these semi-annual versions. They even change your computer ID, that some software activation relies upon, and that is what triggers the need to re-activate some items. The only real way to get control of this annoyance, is to use Windows 10 Pro. Using the Group Policy Editor in Pro, you can disable or defer the feature "upgrades" as long as you need to. I always attempt to stay one version behind the current one. You will need to upgrade eventually, because MS keeps dropping support for older versions of Windows 10. I think they maintain support for the most current 3 versions.

What you don't understand is the business side of this. Those DAWs + Logic Pro X create a significant barrier to entry for newcomers to the Mac market. Remember that they are already extremely popular DAWs that are already coded for the Mac and don't need additional millions $$$ invested for cross platform development (basically a re-write of the entire code base) to even begin marketing to Mac users. Cakewalk was barely rescued from the dustbin of history after being questionably successful in the Windows only market (rumor has it that it lost money for many recent years for its prior owners), and so it would be a huge marketing and development risk to go there commercially. Cakewalk on Windows is a mature technology that apparently requires minimum development to maintain in its current platform. Giving it away to Windows users has the potential to open up other marketing opportunities for its new owners. For the Mac market, Cakewalk would have to become more popular and appealing than the competition to succeed commercially in the long term. And if you would just plan to just give a Mac version away? How would you recoup the huge investment in development for a Mac version? Technical reality and business reality don't always coincide. So don't misunderstand me, I am not against doing this by any means. I have invested 20 years of my life into learning Cakewalk tools, and I would certainly love to see it flourish everywhere. But I am sure that the reality is not as simple as some may wish. At the end of the day if you are running a business, you still need to pay your employees and creditors, and hopefully turn a profit for your investors.

Ummm. With all due respect, I think the question was how to migrate everything from an OLD computer to a NEW computer. Your method would work for migrating to CbB on the SAME computer. So for starters, after you get Windows setup to your liking on the new computer, install your audio interface and MIDI devices with the latest factory drivers. Note: back up everything DAW related on the old computer before you attempt this. You will want to copy some stuff over, and you should have a backup of the rest anyway. 1. Install the Sonar version you are currently using and any add-ons that are bundled with Sonar on the new computer. 2. On the old computer, look in your Sonar preferences for the file folder locations used by your projects, templates, audio library, etc. You will want to back this all up and copy to your new installation of Sonar and adjust the locations in the new Sonar preferences to match. 3. On the old computer, look in your existing Sonar preferences for your VST folder paths and make note of them, then install/authorize as needed all of your plugins onto the new PC. Then adjust the VST paths in the new Sonar Preferences to match. The details of this will vary depending on what plugins you are currently using, and may take the most time. Some of your 3rd party plugins may need to be de-authorized on your old computer before you can activate them again. You may need to research each 3rd party vendor to determine how many activations you are allowed. The Cakewalk bundled plugins should be straightforward though., except for the XLN Addictive Drums 2 and Celemony Melodyne which use their own websites for your user accounts and activations. Those are the main points. As long as you have access to the old PC, you can compare configuration settings between the old and new until everything is running to your expectations. Good luck! If I forgot anything, I hope somebody else will chime in!