msmcleod

There is no need to double click - a single click is enough. What I suspect is happening, is you are moving the mouse slightly between the two clicks and depending on your snap settings, it's creating two nodes on a different snap point.

Also check your network activity... I've been caught out on at least 3 occasions in my studio, wasting an hour or so trying to troubleshoot drop-out issues only to find that Windows was downloading an update in the background.

Delete hole will only delete a hole in what is selected. Track 15 has nothing selected, so nothing from it gets deleted. You're better off turning on ripple edit all, then deleting the selection.

An easier way to switch between hardware profiles is in the works. It probably won't make the next release (which should be out later this month), but hopefully the following one.

I believe Sonar 2.2 was the first version to announce ASIO support: https://www.cakewalk.com/Press/Release/1004/01-16-03-SONAR22.

The laptop I used was a Dell Vostro 1500 (I also used a Vostro 1700, which is the 17" version) - however IIRC, the Vostro 1500 is basically a budget version of the Inspiron 1545. AFAIK the only difference is the Vostro is missing the docking port. I swapped the drives in both laptops with SSD's. The Vostro has a Ricoh firewire port, which works fine with mLAN for the 01X/i88x on Vista/Win 7 32bit, but crashes on shutdown with Win 10 64 bit. The wireless LAN had to be disabled in the BIOS to get any sort of performance.

What can cause issues is installing older software that forces an install of earlier versions of the Visual C++ runtime libraries. It amazes me that some software vendors are still releasing software and distributing VC++ runtimes as far back as 2013. Installing these earlier versions can upset more recent versions. The first thing I do whenever I get an mfc related error that I wasn't getting before is re-install the latest VC++ runtimes. 9/10 this fixes the issue.

From the screenshot, it looks very much like this issue. I've had the same issue myself with modulation wheels. Sometimes you can get away with just cleaning it or opening it up and re-seating the potentiometer (it can slip, so the wheel never reaches zero). As a last resort you could disconnect it completely.... or just get a new keyboard... but try cleaning or reseating it first.

Don't just turn on airplane mode - disable the driver in device manager. You can always enable it again afterwards. Make sure: 1. You're using ASIO mode using the official Focusrite drivers. 2. Uninstall ALL other ASIO drivers - especially ASIO4ALL, Steinberg or other ASIO wrapper type drivers. 3. Run LatencyMon to track down exactly what's causing the glitches: https://resplendence.com/latencymon 4. Ensure your Cakewalk Projects directory and Cakewalk's global audio directory are excluded from any anti-virus, or cloud-sync applications (e.g. OneDrive, DropBox etc).

FWIW I've successfully recorded: 24 simultaneous tracks on a 2008 2Ghz Core Duo laptop with 4GB RAM, through a Yamaha 01X / i88x / ADA8000. 16 simultaneous tracks on the same hardware using a Scarlett 18i20 / ADA8200. 16 simultaneous tracks on a MeLe 2Ghz silent pc (slightly bigger than a compact cassette case) with 8GB RAM through a Scarlett 18i8 / Fostex VC8. 32 simultaneous tracks on the MeLe through a RME DigiFace USB and 4 x Fostex VC8. In this scenario, I was also playing back 32 tracks of previously recorded audio as well. Bottom line is you need very basic hardware just to record audio. If you're using VST's as well though, that's another issue. I wouldn't even attempt to mix on either the core duo laptop or MeLe. What I would add though - make sure any unnecessary stuff (like Wifi) is switched off, and if possible use internal SSD drives rather than external drives.

Set the output of the track to an aux track or bus, then put your fx on that aux track or bus.

FWIW, I use Mega to backup my project files to the cloud... however the Mega sync app is never backing up directly from my project folders. Instead, I have a "mirror" directory which I copy the project files to/from, and Mega syncs from this directory instead. I've got two batch files: CopyToMega.bat and CopyFromMega.bat (for which I have shortcuts on my desktop ), which copy the project files to and from the sync directory. CopyToMega.bat looks like this: ROBOCOPY F:\SEQUENCE F:\Projects\SEQUENCE *.* /XO /E /COPYALL /DCOPY:DAT ROBOCOPY F:\PICTURE F:\Projects\PICTURE *.* /XO /E /COPYALL /DCOPY:DAT ROBOCOPY F:\WAVEDATA F:\Projects\WAVEDATA *.* /XO /E /COPYALL /DCOPY:DAT CopyFromMega.bat looks like this: ROBOCOPY F:\Projects\SEQUENCE F:\SEQUENCE *.* /XO /E /COPYALL /DCOPY:DAT ROBOCOPY F:\Projects\PICTURE F:\PICTURE *.* /XO /E /COPYALL /DCOPY:DAT ROBOCOPY F:\Projects\WAVEDATA F:\WAVEDATA *.* /XO /E /COPYALL /DCOPY:DAT Where: F:\Projects is my mirror directory F:\SEQUENCE is my Cakewalk projects folder F:\PICTURE is Cakewalk's picture cache folder F:\WAVEDATA is Cakewalk's global audio folder The /XO option in ROBOCOPY ensures only newer/different sized files are copied over... so it's very quick.

You could have a look at this utility: https://midi.org/forum/9914-wrk2mid-v1-0-0-cakewalk-wrk-to-standard-midi-files-open-source-translator-released It'll compile on Linux or Windows, but I'm not sure it'll compile on Mac without modification. Of course you could install VirtualBox and run a Linux distribution on that.

The refresh is sent out many times a second. The refresh includes a status - this is a bit mask, so there could be more than one flag set. One of these flags is the REFRESH_F_TOPOLOGY flag. If AZ Controller is looking for the REFRESH_F_TOPOLOGY flag on its own, that may be the issue.

That would make sense. Cakewalk only tells you things it's changed. If you know you've changed via the API, why do you need Cakewalk to tell you what you've changed?

You might be pleasantly surprised in the next release.... and it's much more than an indicator.

Just checked that now. In every project I've tried, the REFRESH_F_TOPOLOGY flag is definitely being set when a send destination is changed. This code hasn't changed since 2006. Are you actually changing the send destination, or just renaming it?

It's Microsoft's cryptic way of telling you the MIDI device is open by another application.

It sounds like you've got the capture mode set to "Match". Go to the options tab on the ACT Controller dialog, and change the capture mode to Jump.

It does make me wonder how permanent a lot of this actually is. Obviously subjecting yourself to really loud sounds/music could do physical damage, but there are environmental things that can temporarily "damage" your hearing. About 10 years ago, I was driving for 3 hours a day for around 2 years for my daily commute. The road noise in the car was sufficient for my brain to essentially do a fairly wide band cut around the road-noise frequency. Any mixes I did during those 2 years were awful, and I also found myself struggling to hear the dialog in TV shows. After I stopped the commuting, my ears did start to recover, but it did take maybe up to six months for my ears to readjust. If I'd have known at the time how much it affected my hearing, I'd have driven with ear plugs in!

Apart from Revalver, the only other ampsim company that I've seen doing Laney is Overloud TH-U - their British Classics rig has the Laney GH100L and Laney Ironheart... no Supergroup though.

Have you checked your master output level (they're the ones with the red faders) ? Click on your master bus, and check the levels in the inspector: Also, keeping these at unity gain will ensure the volume you hear in Cakewalk is the volume you'll hear when you export as audio.

This could be a real issue with larger sets with a lot of VSTi's. Personally, I don't use Cakewalk live, but what I have done is sampled all my hardware / software synth sounds so I can play them all on my SMPro V-Machine ( a ridiculously underpowered hardware VST host). Unless you need real time control of multiple synth parameters, using sampled versions of your sounds is far less resource dependent and you can get away with one VSTi (the sample player), and use program changes to swap sounds as and when needed. The downside is the time taken to sample all your synths. As a indication, it takes me on average a full 24 hours to sample 128 synth sounds using SampleRobot. There's about an hour or two's worth of prep to be done before-hand, but after that I can leave SampleRobot to do the rest automatically. Using something like GigPerformer or Cantable would be the other route. Cantable certainly supports MediaPlayer tracks for your backing, so I'm sure GigPerformer has something similar. As both of these are specifically tailored to live use, they may be better options.

Also check your low frequencies - there could be a bunch of low level information in some tracks that are inaudible, but pushing the signal to peak. I find putting a high pass filter on most of my tracks solves this... just move the frequency up until you just hear a difference, then back it off again slightly. Doing it at the track level means you get rid of far more of the frequencies you don't need.

+1 to this. Apart from the nightmare upgrading to 2020H1, Windows 10 has been a dream for me... and the refusal to upgrade to 2020H1 ended up being 3rd party drivers: one of them a Korg driver, the other a Native Instruments ISO reader driver that was no longer used/required. Funny you should mention a Core 2 system with 4GB RAM - I've got a dual boot Vostro 1700 Core Duo (2.2Ghz, 4GB RAM). One boot is Windows 10 64 bit, the other Windows 7 32 bit. I use the Windows 7 32 bit with my Yamaha 01X because it's rock solid, but I'm tied to using SONAR Platinum 32 bit. Windows 10 in general works marginally better, but the Yamaha MLAN drivers require Windows to be run in test mode and BSOD every time it shuts down... not a huge hassle for Windows 10, but the Windows 7 boot then insists on a full chkdsk on ALL drives on reboot. IMO the only reason to stay on Windows 7 is drivers and/or old applications. I've got a Windows 7 32 bit boot on my DAW PC simply to support my DS2416 cards and older 16 bit software (old patch editor software). My Windows 7 64 bit boot is pretty much never used now, apart from doing a quick smoke test on new CbB builds. Windows 7 is slowly becoming unusable. Many websites have updated security that older Chrome/The Edge/IE versions won't support. Firefox seems to be the only browser that continues to update on Windows 7, but who knows for how much longer. As far as CbB is concerned, Windows 7 does work still, but it may not in the future.