Tez

@mark skinner Cheers Mark, I'll take a look, but exactly where is the "copy to audio folder" option? Hopefully the O9 quirks viz CbB will get sorted out, and it's absolutely a must have for me too, audio engineering is not my forte, so the more help the better & Ozone helps! One other thing to note with O9 is if you want to export a 32 bit wave file the only option is float, not all web sites accept this format for uploads, that includes... Bandlab, that was the case the last time I uploaded, but O7 came to the rescue.

Hmmm, well I upgraded from 07 to O9 standard, the loyalty offer is in my account for $199 & the bundle shows the 4 icons for the O9 Advanced & Neutron 3 Advanced, plus the Tonal Balance & Nectar 3. The price at the bottom $349 is just the regular sale price. If the loyalty offer is in your account then the 4 items is what you'd get for $199... With the O9 Latest Update: 9.1, I have a couple of issues that make me hesitate to upgrade, 1. The vst in CbB for the standard takes 20+ secs to load. I've used multiple instances of O7 in projects which all load swiftly, the excessive load time for O9 makes it's use limited as each instance adds significantly to the project load time. 2. For the standalone O9 if you create a new Ozone project, import audio to a track and close the project taking the option not to save any changes, the imported audio doesn't get deleted, and should. In O7 this didn't happen. I'm on the latest w10 with no fancy configurations. O9.1 is the 3rd update to the original release, so it seems to me that there still maybe glitches. The advanced version is recently now 9.1a sort of a hot fix for some issue. The issues I mentioned I reported yet they still persist. Such a pity, just as well I still have O7 for my CbB projects & the O9 standalone I can cope with, manually deleting any unsaved imports. Last I've no idea if the Advanced O9 has the same issues as the standard, but I suspect so. Parting with cash for a bargain that ends up with a limited use is to say the least irritating...

Hi @Irena, It's not complicated, name it what you like e.g. "Mybat.bat" , the example targets the "D" drive If your SSD is named "X" then substitute X for D e.g. "X:\Cakewalk Projects", etc. Keep it simple save your .bat file on C and run it on C as stated in 2. and 3. but it can be run from any drive where it was saved. The reason to use a batch file is to avoid typo's and for simplicity. That means use the bandlab assistant which you downloaded and installed, and use it to install CbB as if it was going to the C drive, but having run the batch file first, and as previously mentioned: Or if not "D", whatever SSD drive you chose as the target for the data in your batch file... And that's all there is to it! Just don't forget to run the batch file as an administrator then go ahead and use bandlab assistant to install CbB as normal ? Last, this assumes you don't have CbB already installed ?... If you do, then instead, move the folders "C:\Cakewalk Projects" and "Cakewalk" in "C:\Program Files" to the target locations specified in the batch file, then run the batch file...

A simple example using Kontakt: Load an instance of Kontakt selecting “Enable Midi Output”. Then first go to Kontakt --> Options --> Engine. There find "Send MIDI to outside world" and select "Incoming CC's" and "Incoming notes". Assuming the Kontakt instance is “Kontakt 1”, load an instrument vst of your choice, and in the midi channel input select “Kontakt 1” and a midi channel of your choice, and turn “Input Echo” on. For each additional instrument vst, repeat the above. Any notes or cc’s played on Kontakt will be forwarded to each addition instrument. One in, effectively many out, not a cascade...

Great! That's what the forum's all about, and Cakewalk Content , VST and Audio folder locations can be set via preferences... Happy music making!

This is what I would try: 1. Create 2 folders on your D drive: D:\Cakewalk Projects D:\Cakewalk 2. In a new batch file (.bat) on your C drive place these 2 softlink lines: mklink /D "C:\Cakewalk Projects" "D:\Cakewalk Projects" mklink /D "C:\Program Files\Cakewalk" "D:\Cakewalk" 3. Run the batch file as an administrator on your C drive. After you’ve done that, then just install CbB as normal, since the folders for CbB exist as represented by the softlinks, they will be the target for the install but the data will be on your D drive.

C5 it is then... should of googled "The MIDI designation of middle c" & this explains why the sampled pitch .wav file names, for say a piano, differ by an octave.

On a 76-key keyboard, which I use, the 3rd C is “Middle C”, and according to my ear and the fundamental shown in Voxengo’s Span this is middle C. The Span identifies this as C4 which is standard. The PRV shows this note as C5. Is the PRV off by an octave?

Creating a softlink with mklink is fairly straight forward e.g for Cakewalk on C-drive, linking to the relocated Cakewalk, say D:\Cakewalk it would be: mklink /D "C:\Program Files\Cakewalk" " D:\Cakewalk" and if no longer required simply delete the link, for other actions, “copy”, “cut” & “paste” requires more understanding as to the effects. As Mr. @scook said & I quote: On a new machine you should have no issue... However the BandLab Assistant locates in AppData\Local\Programs so I'm guessing it's not optional... In my case I've got prior Sonars installed on 224 GB ssd C-drive so that's where CbB also must live, but on reaching a storage crunch which is hardly imminent using the softlink mechanism outlined above I'd save about 5 GB. On a fresh install , "Cakewalk Projects", "Cakewalk Content" & other folders can be located where you want without worrying that other installations might need the reference to a C-drive location...

This is only a suggestion if there is no better way, that knowledgeable individuals such as @Noel Borthwick or @scook could suggest! Assuming the following: 1. You install bandlab-assistant-windows-latest.exe this will install to the folder %userprofile%\AppData\Local\Programs\bandlab-assistant. 2. Use BandLab Assistant to install “Cakewalk by Bandlab” this will install to the folder C:\Program Files\Cakewalk. If you move the folders “bandlab-assistant” and “Cakewalk” from their locations to a location on your data drive as an Administrator you could create softlinks as an Administrator with “mklink” as follows: 1. A softlink to the relocated bandlab-assistant in “%userprofile%\AppData\Local\Programs”, and 2. A softlink to the relocated Cakewalk in C:\Program Files. The BandLab Assistant is about 210 MB, maybe you’d want to leave that where it is... In my "C:\Cakewalk Projects" I use softlinks for "Audio Data" & "Picture Cache" the later can be 0.5 GB or more. So the above should work, assuming you know how to use “mklink” in a .bat file run as an Administrator. Other CbB folder locations such as for "Cakewalk Content" can be set via "Preferences>Folder Locations"...

Thanks for the info @pwalpwal, Already saw the 1st link a while ago, iZotope thinks 9_02 solved all or most of the 9_01 issues, but it didn't, they've got my CbB dump, this time around, guess they're slow on the uptake... Unfortunately the 2nd link, is what you said "generic", viz. the snail pace load time not apropos... But if you spot anything else do give a shout...

@earhears Final thought, do you have CbB installed & have you tried Oz9 in CbB??

Took a look, that's quick... Is that a separate module, or whole mastering vst?

Well, if you get a chance, and only if you feel like it, try the standalone, create a project, import an audio file, close the project and don't save it, and see if deletes the imported audio. The support rep I reported this to, said she couldn't make that happen, but it does, so wondering if there's a remote chance it's just me ?.

Don't have anything that needs iLok, so never have used it, nor inclined to at this point. I did actually send a link for a CbB dump of test project with nothing but 2 Oz9 VSTs that took 30 secs to load and that was the last I heard. Another weirdness was with the standalone app, by the way I've got the Standard not the Advanced. If I launch the app, create a new project and import an audio file, but close the project and don't save the changes it should delete the imported audio, but it doesn't. Oz7s VST loads quick, and the app deletes unsaved project imports. Have you found any other glitches?

Must be iLok...

Your OS is the same as mine, there are multiple "Microsoft Visual C++ 2005 Redistributable (x64)" versions and each has a version number mine is 8.0.61000, you can find yours by looking in Control Panel>Programs>Programs and Features under Name "Microsoft Visual C++ 2005 Redistributable (x64)" the last column is the "Version". If yours differs from mine that may be significant, on the other hand authorization via iLok might improve load times... Who knows ??

Hmmm... I don't need a tool to uninstall my 2005 x64. Regardless there's no problem with multiple versions, but the question still remains... What's your version, as before you'll find it in "Control Panel\Programs\Programs and Features"?

Well it's a nice thought @earhears, but I'm not sure . I think if there's a significant difference for your 2005 x64 & my 2005 x64 then you might be onto something, otherwise... What is that screen print you show, coz it don't look quite like my Apps & Features in settings? Anyway my version is 8.0.61000 what's yours, you'll find it in "Control Panel\Programs\Programs and Features"?

Hmmm, probably a dropout, no explicit cancel was done, in fact no manual activity at all during the render, maybe Noel knows??

1. Prior to CbB 2019.11 on a bounce to tracks, Fast Bounce off, the Now Time line would move with render time, now it stays at the start of the selection time interval, is this a specific 2019.11 change? 2. Occasionally on a bounce as per 1. above, I'll get the "Render operation was cancelled" popup even though it wasn't cancelled, why and what causes this annoying unexpected cancellation? Any answers welcome...

Thanks @Noel Borthwick, I am and I have... The support rep wanted a dump. First is there any objection to sending a dump of CbB and second, this would be after the fact, the load would have occurred, would there be any significant value to the exercise in your opinion?

@noynekker Supported Hosts: Logic Pro X, Ableton Live 9–10, Pro Tools 12.8-2019, FL Studio 20, Cubase 9–10, Nuendo 10, Wavelab 9, Sound Forge Pro 13, Sound Forge Mac 3, Studio One 4, REAPER 5, Reason 10, Audition CC 2019, Premiere Pro CC 2019, MASCHINE 2, Komplete Kontrol, Bitwig Studio 3, Final Cut Pro X. Guess we're not in there... But, Cubase from some forum I saw, had the same issue with v9_01, maybe Noel knows something??

In both the last Splat and current CbB, the latest Ozone 9 VSTs (2 & 3) have excessive load times, this is on W10 1903 latest update. For example a test project that had only 2 output buses each with an instance of Ozone 9 took 30 seconds plus to load. Is anyone else experiencing this with CbB??

Thanks Noel will see what is possible. FYI though 1. It is sporadic & not predictable, the error code is always 1. 2. It occurs most often when performing some activity in the tracks pane e.g. "opening or closing a folder" or "maximizing, minimizing or resizing a track". 3. It may not be specifically Aux track related, but the Aux tracks in this current project have a lot of FXs and it might be, I'm guessing, related to "Always Stream Audio Through FX" being checked which if I understand correctly continuously streams silence. And, as if on cue, just 5 minutes ago I launched CbB and opened the project and the dropout toast error code 1 immediately popped up just as the gui rendered... Further in this particular instance pressing play stalled, with another dropout error code 1, recurrently. Had to restart CbB & reopen the project ?... Just out of curiosity, no biggie, did you get a chance to glance at that crash dump? Many thanks...