msmcleod

Is this happening on all projects or only this one? If it's only this project, you could try creating a new project and dragging the old project on to the track view from the media browser. I find this is a great way of "cleaning up" projects that are misbehaving.

The thing I think that will push most pro audio users towards Windows is Apple's decision to ditch Intel in favour of an ARM processor in their next line of Macs. Logic should be fine, as it's an Apple product, but for all the 3rd party DAW's and plugins it'll be a nightmare. They're likely to do some sort of emulator, like they did when they went from PowerPC to Intel, but I can't see them getting the performance needed for plugins from this.

I guess the most famous example is Madonna's "Live to Tell" which uses the D50 "Soundtrack" preset in the intro. The Sountrack patch is a simple fifth interval. There's been hundreds if not thousands of patches since that use that interval, as it's arguably the least dissonant.

If you've solved your issue with CbB crashing on startup, but it's only crashing when opening an older X3 project try this: Create a blank project in CbB Browser to your project using the Media Browser on the right hand side Drag the project on to the track area This should import the old project into your new one.

Things to try: Hold shift down whilst opening the project (or opening CbB) to open it in safe mode, to rule out any problem plugins. If it's more of a general problem, then try deleting AUD.INI from %APPDATA%\Cakewalk\Cakewalk Core. Also try re-installing your audio drivers. Check that no other processes are trying to access any of Cakewalk's files or your project files. Common culprits are virus checkers (including Windows Defender) and OneSync or any other cloud sync program. Make sure your the following directories are excluded from any of these programs: All the Cakewalk folders, e.g. Cakewalk global audio folder, picture folder and the folders listed in Cakewalk preferences Your VST folders %APPDATA%/Cakewalk Documents\Cakewalk It's probably worth sending your crash dump to Cakewalk support. The AppData folder is hidden, but you can get to it by pasting the following into Windows explorer: %APPDATA%\Cakewalk\Cakewalk Core\MiniDumps\

Have you tried freezing the tracks (with Track FX) before exporting them?

I'd recommend "Bounce to clip" after editing using audiosnap.

Things to try: Hold shift down whilst opening the project to open it in safe mode, to rule out any problem plugins. If it's more of a general problem, then try deleting AUD.INI from %APPDATA%\Cakewalk\Cakewalk Core. Also try re-installing your audio drivers. Check that no other processes are trying to access any of Cakewalk's files or your project files. Common culprits are virus checkers (including Windows Defender) and OneSync or any other cloud sync program. Make sure your the following directories are excluded from any of these programs: All the Cakewalk folders, e.g. Cakewalk global audio folder, picture folder and the folders listed in Cakewalk preferences Your VST folders %APPDATA%/Cakewalk Documents\Cakewalk

The DNS cache doesn't ever flush, unless you explicitly tell it to or you make a DNS/networking related configuration change. DNS records have a Time To Live (TTL) value associated with them which tells a DNS cache how long the particular record is good for. Records in the cache are kept for their TTL, then re-queried. So a reboot isn't enough. Normally this isn't needed, if a website's IP address is changed after the TTL value. But if the IP address is changed before the TTL expires, that's when you need to flush it. If you suspect it's out of date, you need to manually flush it.

Another thing to try is flushing your DNS cache. Run the following from a command line: ipconfig /flushdns

Have you got any custom firewall software running? It sounds like something is blocking internet access to the BandLab Assistant. Also, have you tried running the BandLab Assistant as administrator?

I definitely agree that some knob implementations are better than others. Maybe I came across too strong about the "real" look of VSTs - in fact, if it is an emulation of an existing bit of gear I prefer it to have the real-gear look, because you can use it as if it was the original... and in those cases, a knob makes total sense if it was a knob on the original. And I'm certainly not against good artwork on a plugin, as long as it doesn't affect its usability. There's the other end of the scale too, where the "functional" look is taken too far - take some of the Melda Production plugins for example... some of the GUI's leave me looking all over the place to find the parameters as everything looks the same. I do love the sound of the Melda stuff though. I guess what I'm looking for is a sensible balance between looks and ease of use. With the sonitus stuff, the look is a bit bland, but for me it doesn't affect functionality.

For me the GUI of the sonitus plugins is pretty low priority. IMHO there's too much emphasis on trying to make VST's look like "real" gear, often at the expense of usability. Turning knobs with a mouse isn't the most intuitive thing, whereas sliders and graphical envelopes are perfect for a mouse. If anything, making the GUI slightly bigger would be nice, but apart from that the interface works well for me and they sound great.

What I tend to do is switch the ProChannel off before freezing, this means that it's not included in the freeze. I can then switch it back on to mix the frozen audio.

I've done a similar thing with other VSTi's, and it took days, but it was worth it as it left me less overwhelmed by the number of presets to choose from. I guess I did the same thing when sampling my hardware synths too: I went through every patch on every hardware synth I had, decided if I liked it or not, and sampled each one. I also went through all my old unfinished projects (some dating back to Pro Audio 7), and updated them to use the sampled synths rather than the real ones. This took about 3 months, but it does mean all my old hardware synths are now all "in the box", and in particular on my laptop when I'm on the move.

I quite often choose to not include Track FX when freezing tracks that are using soft synths. This free's up the processing associated with the soft synth, but still allows me to use Track FX when mixing... so of course in this case, the FX rack will not be disabled. If however, the track FX are part of the "sound" (e.g. GuitarRig on a guitar part), I'll choose to freeze with Track FX.

Out of Amplitube 4, GuitarRig 5, Revalver 4 and TH3, overall TH3 stands out for me as the best. All four products are great and have their place though. I love the guitar modelling of Revalver, and the sheer number and range of presets in GuitarRig is very impressive and the sounds are good, if a tad over-processed for my liking. But as far as TH3 is concerned, the upgrade to TH3 Full from the Cakewalk Edition was well worth it. The upgrade from TH3 Full to TH-U is not as big an upgrade, but I welcome the new presets & models.

Looks like these loops disappeared at the time of Cakewalk Inc shutdown: http://forum.cakewalk.com/loopmasters-sample-magic-and-xmix-content-collections-won39t-install-m3692709.aspx Presumably their license became defunct when Cakewalk Inc became no more.

I got the email too, and I've upgraded. It worked out at £52.00 once VAT was added. Not a huge difference to TH3 Full, but the new models & presets are welcome. It installs separately alongside TH3 so my existing sounds are untouched.

There shouldn't be any headaches if you use the Cakewalk Plugin Manager. Just select the plugin, click on Plugin Properties and toggle the "Load with JBridge Wrapper" checkbox. Doing it this way (as opposed to using the JBridger app to create wrappers) means that Cakewalk sees it as the same plugin regardless of which wrapper its using.

BitBridge wrapped plugins have a blue/white title bar: JBridge wrapped plugins have a normal title bar, but have an extra bar at the bottom with a "Settings" button.

I tried a few kits out a good few years back, although I never actually got around to buying one (I'm still using a DIY kit based on a Remo practice kit & Alesis DM5). The Roland kits definitely stood out as the best, at least from a controller point of view - i.e. pad responsiveness (especially the mesh kits) and also the fact the hi-hat was completely variable between open and closed. Sound-wise I actually preferred the Alesis, but the hi-hat is an on/off type with nothing in between. In practice this didn't cause me too many issues, but it did limit my playing. Personally, I think the TD-17KVX is a good choice... and I think you're right about the machine gun effect being more to do with Roland's internal sounds.

I was thinking the same myself. Another thing that crossed my mind was exporting the stems and importing them into ProTools First (which is free, but limited to 16 tracks). At least that way you're actually sending a ProTools session to your colleague. But if quality is maintained in BandLab, then that might be a good choice... as long as the 6 minute limit isn't an issue.

JBridge is well worth the small investment. It offers far more options/tweaks to get around potential compatibility issues with various 32 bit plugins. Note that there's no need to use the JBridger program to create wrappers for each plugin. If you fire up Cakewalk Plugin Manager and select plugin properties on your 32 bit plugin, you can just check the "Load with JBridge wrapper" option and it takes care of it for you.

This is a known issue with Addictive Drums. Every time you do a major Windows update, you have to un-authorise and re-authorise your computer using the XLN installer.