msmcleod

@onlyinitforthemoney - I'd strongly recommend going through some video tutorials to see how things work nowadays. I learned most of my workflow on Cakewalk Pro Audio 9, and didn't really change my workflow right the way through to SONAR Platinum. It wasn't until I joined the beta team (before I was staff), that I made the effort to learn all the new stuff by watching some tutorials. It was a HUGE eye-opener. So many things I thought had gone had just been replaced with a different way of doing it, and there are loads of hidden workflow shortcuts I was completely unaware of. There are a bunch of links in the Tutorials section of this forum, but the ones that most helped me were: 1. SWA's Complete Sonar X2 : https://www.youtube.com/watch?v=TR1DLE2UIfM&list=PLKRYWdEpbc5PgUgvrNuSvVyfv5qkll0qj and the Sonar X3 follow-up: https://www.youtube.com/watch?v=EX09_s9wsDI&list=PLKRYWdEpbc5MtPslyvpY_tkunB34cvU75 2. Groove3's Sonar Explained and Sonar Platinum Advanced tutorials (needs a Groove3 subscription or can be purchased) P.S... don't skip the stuff you think you already know... there's some real gems (keyboard shortcuts/modifiers etc) in there that aren't apparent.

This is exactly what it's intended use is.

I've only used TouchDAW briefly myself, but abandoned it due to the whole Bonjour / MIDI network setup thing which I found I constantly had to reconfigure. I suspect this is your issue - i.e. when the android is turned off, it's wasting resources trying to look for it. When it's on, delays in the network due to the high CPU usage could be causing the issue. Microsoft are currently working on a native MIDI over network solution that will be built into Windows, so hopefully that will be far more reliable. Another thing it could be... I'm not sure about your machine specs, but many people (mainly laptop users) have major audio issues when the network is busy, and end up disabling it (albeit temporarily) when using their DAW. The issue there is that the network and USB ports used for the audio device are tied to the same resources on the motherboard. Personally, I'd recommend looking at a different control surface solution. If you don't mind not having motorized faders, the Korg nanoKONTROL Studio is fantastic. The nanoKONTROL 2 is pretty good too... I've got one stuck to the wall next to my vocal mic!

Got it in one @Wookiee.

The font it uses is "TtsNote Standard Regular" - it should be in C:\Windows\Fonts. It's not available separately for download.

The notes in the staff view are actually a custom font, so what you describe sounds like the font hasn't installed properly. Check you've not got any restrictions on your Windows user account preventing custom font installation, and try re-installing Sonar.

If you've got a Mackie Control Master fader assigned to the hardware out, the master fader on the Mackie will just control one side - the solution here is either: 1. Click the "lock" on the hardware output fader, so they always move together. 2. Re-assign the Mackie's Master fader to your Master bus in Sonar's Mackie Control dialog (under the utilities menu). Personally, I prefer option 2 as having the hardware output fader at unity gain is pretty much essential in order to get your audio exports at the same volume as your mix.

OK - ripple edit is off. There are four things I can think of that would do this: 1. You created an arranger section and moved it. 2. You made a selection and nudged it using keypad 5. 3. Somehow you invoked Project->Insert Time. 4. Assuming the clips were separate before, and they were set to absolute time, the tempo changed. [EDIT] - ahh... just re-read... you say there's a gap where there used to be audio... that would imply you made a selection and pressed delete or Del, or CTRL + X

Have you got ripple edit on? If you'd shown more of your screen we'd be able to tell!

This has been fixed for the next update. In the meantime, opening the track lanes will allow you to lasso the nodes.

I think the only ones that are missing are Workspaces and the new Backup/Restore Settings (i.e. multiple config profiles) in Preferences.

The only way I can get this to happen is if: 1. I accidentally move the mouse into the clip region; or 2. I select the nodes such that all of the nodes are selected within a particular time period. This is the same for me using the smart tool or the select tool. Does making the lasso region narrower (i.e. closer to the node boundaries) help? [EDIT] - ok, I can repro this if there's a clip there and take lanes are collapsed. If take lanes are expanded, then it behaves as expected. We'll investigate further.

If input quantize is on then the MIDI is being quantized as you record it - i.e. it'll already be quantized. So quantizing afterwards is going to do nothing. Input quantize can be useful if set to a fairly coarse value (such as 1/4 notes), but if set to 1/16th notes, unless your playing is very accurate you may find notes in the "wrong" 1/16th slot. Quantizing afterwards isn't going to help as it's already quantized. It doesn't know which notes are in the wrong positions - all it knows is the ones that are there are quantized to 1/16th notes already. I'd recommend switching input quantize off, as the quantize dialog gives far more options for threshold/strength etc.

The issue is now fixed - it'll be available in the next update.

As far as I know, nothing has changed within Quantize between CbB and Sonar - is this quantize via the Quantize Dialog, or Input Quantize?

Thanks - this has been fixed for the next update.

Press P for Preferences, then go to Customization->Display. English is always the top language in the dropdown.

I replied to the original post. The issue is caused by using the "Entire Mix" category when having more than one hardware output in the project. Better to use "Hardware Outputs" in this scenario.

I can now repro. The key to the repro is to have more than one audio source when doing an Entire Mix export, e.g.: 1. Load any project 2. Add an empty audio track routed to a different hardware output 3. Export using a filename of test.wav Result: file is exported as test_.wav We'll investigate this further. If you've only got one hardware output in the list, you won't get this underscore. The Entire Mix category is really special case of category "Hardware Outputs" for simple cases (i.e. one audio output). If you've got more than one hardware output, it might be better to use "Hardware Outputs" and uncheck the one you don't want to export.

The latest version of Sonar (2025.07 build 97) should fix this issue.

Ace of Wands - Steve Hackett

That's just how articulations work in Sonar. They apply to everything underneath them. Articulations are implemented in so many different ways within VSTi's, it would be impractical (probably impossible) to implement what you're asking for and have it work in all scenarios. In your example above, the easiest way would be to cut the duration of the articulation short of the last note.

No-one is forcing you into subscription. There are very few differences between the premium and free tiers of Sonar at the moment. All you need to do is sign in to activate (assuming you're running the latest Sonar) and you'll be able to save.

There's really no reason to uninstall unless you're desperate for HDD space. Most of the installation is common to both Sonar/CbB, so you'd not be freeing up much. Also, when CbB does fail to activate, it WILL still play back if you have a problem project - only save/export is disabled.

The minimum specs are determined from what a sensible PC set-up would be for the average user (based on what is on the market now), assuming zero tuning of their BIOS or Windows installation. One of the most common things we hear from noobs is that they're getting clicks & pops, when they've loaded up their project with 100+ tracks containing an overkill of plugins that they saw on their favourite you-tube channels and a bunch of CPU intensive VSTi's. Having a more generous minimum spec helps to mitigate issues from these users. Of course Sonar will run on far slower hardware, and as @Starship Krupa says, my main DAW is an old i7 3770. My workflow is pretty old school though. I only started using VST's around 10 years ago - prior to that, all my instruments and effects were hardware. My 2 x DS2416 cards may have given me hardware EQ & Compression on 48 tracks, but it only gave me 4 effects processors. As such, I learned to use them sparingly, which has continued with how I use VST's nowadays.