msmcleod

Take a look at Synthmaster 2.9 (rather than synthmaster one, which is a different synth). IMO it's one of the most versatile synths out there.

When using the realtek, try using WASAPI or WDM as your driver mode. You might find you get better results. The ASIO drivers that come with these devices are rarely any good.

One thing I've noticed, is that if you've previously had "create one file per clip" switched off, and you turn it on when doing a "Save As" or "Save Copy As", it won't automatically split the clips up into separate files... not that I really expected it to. But if you want your clips as separate files, you'll need to "Bounce to clip(s)" on each individual clip after you've saved your new copy.

I guess it's easy to pick those locks if you've got ProTools.

It should be here, at the top of the clip view area on the right hand side: If it's not there, you're using an earlier version of CbB. In which case, click on the options drop-down (in red below) at the top of the Track view area, and make sure that both "Ripple Edit Selection" and "Ripple Edit All" are unchecked (in green below):

This may help: Cakewalk's own tutorial: @Gswitz's tutorial (the guts of the actual loop construction it are about 11 mins in):

A couple of things to check: 1. Check that Cakewalk Analytics is disabled. This points to nowhere at the moment, and could take a while for it to time out. 2. If you're using a custom template, and the browser on the right is set to the "Media" media tab, and your folder has a lot of files in it, it's really slow to populate. Make sure it's set to "Plugins", or make sure your Audio Library folder doesn't have too many files in the root folder.

If you want a free 64 bit auto-tune plugin, try the Melda Productions free bundle: https://www.meldaproduction.com/MFreeFXBundle which includes MAutoPitch: https://www.meldaproduction.com/MAutoPitch (amongst a bunch of other pretty awesome plugins)

Since you're a developer, have a look at the MIDI file spec: https://www.midi.org/specifications/item/the-midi-1-0-specification If you can come up with a better way of preserving envelopes that conforms to the specification, I'm sure the devs will be open to considering it. Just out of interest, do any other DAWs do anything different here?

Note also that plugin load balancing in CbB only affects VST effects, not VSTi's.

Really sorry to hear that Zargg. My thoughts are with you & your family.

The MeldaProduction free bundle has a good analyser, amongst a bunch of other great plugins: https://www.meldaproduction.com/MFreeFXBundle

yup - I can reproduce it.

I did a sample of my piano a few months back...

Your projects don't actually store the location of the VST's, just the ID of the VST being used. So moving the VST's, making sure you've got the new path in Cakewalk's VST preferences, and doing a plugin re-scan is all you should need to do. However, if you had to run an installer to install a VST, then those VST's might not work properly (or at the very least, the uninstall might not work). In this case, probably the easiest way is to create a symbolic link to point the directory on the existing drive to the location on the new drive. https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/mklink In saying that, if the drive is behaving erratically maybe its time to just replace the drive with a new one and give it the same drive letter?

The basic premise here is that Cakewalk is not a MIDI file editor. You can import MIDI files, at which point it becomes a CWP project... and you can export your CWP project as a MIDI file, at which point all the MIDI data that would have been sent by Cakewalk out the MIDI port is now stored in the MIDI file. When you re-load your MIDI file, what you're doing is importing a MIDI file back into a CWP project again. There is no automation lanes in the MIDI file, just MIDI CC data, which is why it's in the PRV and not in an automation lane. If you want things to be consistent, then just work in the PRV (or the Event List view) and avoid the automation lanes altogether. I suggest however that you compromise on not saving it as a CWP. If your end result is a MIDI file, then that's fine, but while you're still editing things you're much better off with working with a CWP project file until such a time your ready to export your final MIDI file.

My work laptop is still on 1709, and security updates are still being rolled out to that. I think what abacab means is, if you stayed on say 1709 for several years, there would eventually be a time where they'd stop doing security updates for that version. So you'd have to upgrade to a later version (e.g. 1809 or 1903) before you could start getting security updates again. FWIW I've upgraded to the latest pretty much as soon as its become available. Microsoft keep your old version on your hd for a month allowing you to rollback easily, but as I normally image my hard disk regularly (and especially before an upgrade), I've never had to use it.

It's certainly possible. Kontakt includes a scripting language so that sample library developers can provide specific behaviour for their libraries. There's absolutely no reason why there couldn't be (a) bugs in the developer's scripts and/or (b) bugs in the Kontakt scripting engine itself.

Although I doubt if I'll play live again any time soon, I still can't help thinking of the "how would I reproduce this live?" scenario. This helps me to limit the amount of tracks I use, by keeping it to a fairly standard band arrangement, which typically for me is vocals/guitar/keys/drums/bass + backing vocs. This makes what Craig says about which tracks are important even more applicable... so while I'll be perfectly happy to add extra guitars to embellish whats already there, I want to make sure that if there is only one guitar playing, it doesn't sound like something is missing and the song still works. Obviously this is hugely genre dependent.

TrueIron is more than worth getting, especially with the discount.

Totally missed this one! much better than my suggestion

I've bound CTRL + ALT + F to "Zoom out all tracks - vertically": While this doesn't zoom out all the way in one go, pressing it a few times gets you to where you want.

I find the best way to do this is to change the clip envelope - I know it sounds like using an envelope, but it doesn't actually involve drawing one. If you change the filter on the clip to Clip Gain, then hold the CTRL key down, you can move the volume up and down for the clip. As this just affects the clip, you're still free to use volume automation for the track independently: You can of course do this with the track volume as well, but this will be overridden by any fader changes or track volume automation.

As both SO4.5 & CbB are failing to scan it, it sounds like your install has somehow got corrupted, either that or its some weird permissions issue. If you right click->properties on Omnisphere.dll, do you see any security issues? A common one with Windows 10 is this: If it's not this, try running CbB as admin and rescanning failed plugins. FWIW, the size of Omnisphere.dll is exactly the same as yours, and it's working fine for me in Win 10. 64bit v1903.

Plugins that have their own protection scheme, like the Korg MS20 are far more likely to crash when bridged. Sometimes allowing JBridge to run with admin privileges can help, but other times not. Both the Korg MS20 and NI FM8 have 64 bit versions, so better to use them than bridging 32 bit ones. Basically, only used bridged plugins when you absolutely have to. Apart from SampleLord, when I use 32 bit plugins, I'll I also tend to render them by right clicking the clip / Process Effect on a copy of the track, and archive the original. That way I can remove the 32 bit plugin from my project.