msmcleod

Compare ALL of the export options between CbB and Sonar. If this doesn't help, most plugin issues can be worked around by doing a real-time render. Also, make sure your bounce buffer size is set to "Playback Size"

This has been fixed for the next update.

This has now been fixed for the next update.

No need to put in feedback.. it's on my radar. I'll look at it next week.

I'm pretty sure I know what's caused this, and there's a couple of ways this could be fixed... one is easy, one not so... Are you using any modifiers when doing the drag copy to force them to copy as linked? If so, it's probably an easy fix. [EDIT] - fixed for next update.

Set the audio input of your track to a mono input, and it'll record as mono.

Thanks for bringing this to our attention. The translation has now been corrected for the next update. Please let us know if any other translations are incorrect.

Can you send a copy of your project to @Jonathan Sasor? We'll take a look.

@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.