msmcleod

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

Ahh... I didn't go back as far as Sonar 8.5. I suspect you're right, it may have been broken with the introduction of the Skylight interface. I've logged it as an issue.

I don't think this has ever worked in TTS-1. I've tried it in as far back as SONAR X2, and it didn't work there either.

I guess you could, but the Mackie protocol is far newer and has much better support. For example: HUI has no master fader HUI scribble strips are limited to 4 chars per track (vs 6 chars in Mackie mode) There's currently no plugin automation support for HUI HUI is basically a deprecated protocol, which Mackie replaced with MCU a long time ago. The only reason that it's still around is to support Pro Tools. I'd strongly recommend using Mackie mode in the XTouch - the scribble strips should work fine with that.

Spectrasonics plugins are particularly CPU intensive, due to the complexity of their synthesis engine. I've certainly found Omnisphere to be one of the most CPU demanding plugins out of all of the ones I use. The other plugins you mention are largely sample based, so this is probably why they're not having any issues. It may just be that you have your ASIO buffer size set too low. A higher ASIO buffer size should reduce the load on the CPU, although this will increase latency. You could also consider freezing your Spectrasonics tracks - this will drastically reduce the CPU load for those tracks, and you can always unfreeze them if you need to edit them again.

Its definitely the most successful open standard I've ever come across - I guess VST 2 comes a close second. But the vast majority of open standards are widely (mis)interpreted by different corporations... all wanting to do things slightly differently.

It depends on your Firewire adapter. I was using an older one with Windows 7, and found I had to use the legacy drivers with Windows 10. The modded Yamaha 01X/i88x drivers I was using however, didn't play well with it in Windows 10, so I managed to get one that didn't require the legacy drivers (for less than $10): https://www.amazon.co.uk/Swiftswan-FireWire-IEEE1394A-Expansion-Incidental/dp/B07FZ4DKZT/ref=sr_1_fkmr0_1?keywords=Swiftswan+PCI+Express+PCI-E+FireWire+IEEE1394A+VIA+Chip&qid=1569977528&s=gateway&sr=8-1-fkmr0 Chipsets are a big thing as well - some audio devices prefer TI chipsets, others prefer VIA, so best to check what they recommend.

Yes, you're right - got the nanoKONTROL Studio in front of me at the moment, which has the scene button - the nanoKONTROL 2 is in my studio vocal booth - I forgot it didn't have the scene button. You can use the Korg Kontrol Editor to download scenes to the device, but I'm not sure if it'll play well with Cakewalk running at the same time as it seems to want to do everything via MIDI (which Cakewalk will have open). You might be able to use a software loopback device (e.g. loopMIDI: https://www.tobias-erichsen.de/software/loopmidi.html ) to get around this. You'll probably also need a MIDI patchbay/router to connect the nanoKONTROL 2 MIDI ports to the loopMIDI ports. There's a few you could look at: http://en.soundigy.com/midipatchbay.php https://www.yofiel.com/downloads/audio-apps/midi-patchbay-for-windows-10 Alternatively, AZController might have better options for switching control mappings. Best to ask @azslow3 But to be honest, the nanoKONTROL 2 isn't, in my opinion, the best device for controlling VSTi parameters. I'd personally recommend sticking to transport control with the nanoKONTROL 2, and maybe look at controlling VSTi parameters with something like the Korg NanoKEY Studio (if you use key switches for articulation) or the Akai MIDImix (it's got 24 knobs, 24 buttons & 9 sliders - so a good selection for parameter controls).

To be honest, I've not gone in to it in too much detail (I always use my nanoKONTROL 2 in Mackie Mode), but I believe you can configure several "scenes" which you can switch through on the nanoKONTROL. So say scene 1 is your transport control CC's, scene 2 could be a completely different set of CC's set to control other things.