msmcleod

There was a new hotfix released ( Build 25.09.0.70 ) ealier today which addresses this issue.

... now in fact !

This issue has now been fixed - there will be a hot fix for it out very soon.

iCon / X-touch can both use the MackieControl protocol. Also, FWIW all my enhancements (apart from the one I changed above) are in the official Cakewalk MackieControl.dll for the 2019.09 release. The only exception is that my version has 3 DLL's, which allows you to have up to three independent Mackie compatible controllers controlling Cakewalk (4 if you include Cakewalk's MackieControl DLL). I use a real MCU + XT + C4 in my studio, but also have a nanoKONTROL 2 by my vocal mic. Having the separate DLL's allows me to do this.

Hi Rick, Thanks for the report. Unfortunately, all I had to work with for this was the MCU in HUI Mode, and the TouchDAW Android app. It sounds like the HUI isn't getting a regular enough heartbeat from the MackieControl.dll, which is why it keeps going offline. The other issues may or may not be related to this, but if it keeps going offline its likely there's far more MIDI traffic going on re-establishing the link than is needed. I've updated it to ping the HUI much more often - can you give it a go and see if it works any better for you? http://msmcleod.co.uk/cakewalk/MMcLMackieControlSetup.zip Thanks, Mark.

Hybrid drives work by having a very small SSD inside which holds copies of the most used files. On my old laptop, I originally swapped to a hybrid drive before going full SSD. As an OS drive, I found the speed increase from HDD to hybrid far more obvious than from hybrid to SSD - in other words, it was almost as fast as an SSD for most things. The only drawback, was when I did a Windows update, sometimes it would take up to a day or two for it to catch up and replace its "most used files" cache - obviously depending on what was updated (i.e. sometimes it was fine). As the cost in most cases is pretty similar to a standard drive, it's really a no-brainer, but just be aware that on occasions it'll revert back to normal HDD speed every now and then as the cache changes.

The automation value / control widget area was enlarged to the same size as the track FX bin for 2019.09, so you should no longer see this issue:

I think 8GB will be fine, as long as you're not using lots of sample based synths. I've got plenty of projects that still work fine in 32-bit SPLAT which is limited to 3.5GB RAM.

I've got one of these velcro'd to the wall next to my vocal mic, configured as a Mackie Control with a long USB cable:

Specifically, what functionality that is missing are you referring to? It may be that its just moved or requires different modifier behaviour.

Try increasing your MIDI prepare buffer. The default is 250 - I normally use 750:

Its probably more to do with the limitations of VSTi's. Although plugin load balancing is available for VST effects, VSTi's will only use multiple cores if they've been specifically coded to do so. This means that if you've got a multi-timbral VSTi using only one hyperthread, it'll only show up as using 6% of the CPU on a i9-9900K - even though that particular hyperthread is running at 100%. There's only so much you can do with parallel processing / multi-processing, and even when you can do it you can quickly get in to diminished returns due to synchronisation of the processes actually taking up more CPU than doing the work itself.

A hotfix is just a mini-release to fix any major or serious issues. It'll be out very soon.

I remember the transition from SONAR 8.5 to SONAR X1 was a difficult one for me. So much had changed, it almost destroyed my workflow. The only saving grace was the fact that most of the keyboard shortcuts remained unchanged, so I could at least work with them. About 6 months ago I watched the Groove 3 course on SONAR Platinum, and it went through everything in detail. Even though I've been a Cakewalk user since CW Pro Audio 7, I was amazed at the amount of features I had no idea about, and in particular the smart tool. The VAST majority of things can be done with the smart tool, once you know the right area of the clip to hover on and the various SHIFT / CTRL / ALT combinations. It more or less covers everything the other tools need. It may feel awkward at first, but believe me, once you're used to it you wouldn't want to be without it! You can find out all about the clip zones / keyboard combinations here: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Tools.04.html Also, as you hover over the various areas, not only does the cursor will change, the topic in the help module will also automatically change - so you can see exactly what the tool will do. Seeing as you're coming from 8.5, you might want to consider disabling comping on the smart tool until you get used to its behaviour. I quite often do this anyhow if I'm not comping, just so it doesn't get in the way.

The left / right combination is certainly the same as most TRS jacks I've worked with. Best to check with a meter if you're not sure.

It looks like the red is connected to the tip, which is correct... but its hard to tell. But it also looks like the end of the blue is touching the red?

When doing this in the past, I've always worked with the mixed down stereo wav as this makes things so much easier. First of all, I'd add an additional SMPTE time rule so you're always seeing the actual time: Next, it's just a matter of using the cut tool to split up your track, and putting fades in where necessary. If the cuts are clean, then you're good to go - otherwise use the xfade tool to introduce a slight cross fade (make sure lanes are expanded, and do the edits on the clip within the lane): You could also try using the time-stretch tool for small adjustment using SHIFT+CTRL and dragging the end of the clip - note the "+time" at the end showing how much you're stretching the clip by: Note it's normal that the quality of the stretched audio may not sound great, depending on the algorithm used in preferences: In the settings above, the "Online Render" is set to Elastique Efficient, which is quick, but doesn't sound that great. If I right click on the clip, then "Bounce to clip(s)", it will render using Elastique Pro - so always make sure you do the Bounce to clip(s) after your edit to make sure you get the high quality version.

Up until 2019.09 Midi Bank select messages weren't being sent to VST's- this was fixed for 2019.09. I find the best way to do this is to insert them via the event list, after you've recorded your notes. That way you can make sure the time is the same, and they appear directly before the note: If this still doesn't work, take a look at your Patch browser settings for the track (make sure you're on MIDI tab if you're using an instrument track):

You might want to look at ProjectScope, which will do most of what you're looking for: http://forum.cakewalk.com/ProjectScope-for-Sonar-Project-Files-CWPs-updated-to-support-new-Sonar-project-features-m3584169.aspx You could always ask the developer to add features if its missing anything.

I normally print out a diagram to remind me, as my memory is awful nowadays:

You can insert MIDI FX, but if you're using simple instrument tracks, you need to insert them in the inspector when the MIDI tab is engaged:

Also, Lenses are global whereas Screensets are per project. The idea of Lenses is to streamline workflow, so you can focus on a particular task by removing the items you don't need for that task. Screensets on the other hand are different layouts within a project. For example, track view on set 1, console on set 2, PRV for track 1 on set 3, PRV for track 2 on set 4 etc. Lenses are down to personal taste. Personally, I don't use them as I find things changing in the control bar confusing - i.e. things aren't where I'm used to... but I guess everyone is different. Others prefer to remove the "noise" and hide what they're not going to use.

Press "X" - to toggle it on/off.

I made 12 TRS male to XLR female cables today (well, I've not got around to doing the XLR part yet, as they're all on a rack panel), but yes the hot, cold & ground must absolutely NOT touch each other. You also need to take care to ensure the right pins are connected. After doing one end, I always check with a multimeter that all connections are working and are isolated... then I do the same again once the other plug is soldered on. You also need to ensure that the cable is actually touching the terminals when soldering - don't rely on the solder being the conductor, else you'll get dry joints at a later date.

The easiest way is via the PRV (Piano Roll View), which you can get to by: Double Clicking on the Clip; or Using ALT + 3; or Using the context menu: right click->View->Piano Roll View; or Using the Views menu, and selecting Piano Roll View Alternatively, you could use the Event List: ALT + 8; or Right Click->View->Event List; or Views->Event List