First project completed under Kingston update and my impressions

Finished this track, working on it completely as a new project to test out the kingston update.
 
https://soundcloud.com/slumbermachine/day-and-night
 
The negatives:
1. Having to click twice on a project name on the welcome screen is annoying, but a minor issue.
2. "+" and "-" icons for track zoom does not respond to more then one click. Work around is to zoom using the slider. not major issue, but did waste some time.
3. VSTI's got the wrong name index issue again (the wrong vsti opens). Had to reset and rescan and that seemed to fix it. Annoying and slowed me down. I shouldn't have to do this twice a week. Sometimes I wish Sonar was open source so I could modify the entire plug in manager.
4. Some rare crashes, nothing noteworthy, mostly after forgetting to disable virus scan and having left the system idle for awhile. Nothing huge, pretty stable.
 
The positives:
1. Fast. This thing flies. I made that above song, with mastering and plenty of **** around time in about 4 full days of work. That's the fastest I've ever done a complete song with so much complex parts. Plus learned some new software.
2. Stable. I went an entire studio session once without a single crash (6+ hours). This is a huge milestone as my sessions are hardcore vsti and sample intensive. I will load Omnisphere 2 along with 5 fx and have it doing 2 different automations and that is just one track. I get to ~24 tracks like that sometimes. This release is built like a brick **** house. Still has some rough edges with folders, routing, and that zoom issue, but overall one awesome update. Thanks!
 
 
 
 
 

Very cool track!  Nice buildup/release sequences
 
PLEASE take the time to submit a PR for each of the problems you identified.

Ok, so I got a chance to recheck the issues I mentioned. It seems the "start screen" is not getting focus upon start up, which is strange, but maybe it's not meant to be modal, which could be my misunderstanding of the screen.
 
For the "+" and "-" buttons, they are not working for multiple clicks.  So say I want to zoom in real close, but I want more precision then the slider. I may want to zoom in 5 steps. On my system, it will zoom 1 step and the rest of the clicks do nothing. Maybe my click speed on my mouse is off or something so it is thinking it's a click-hold?
Not even sure how I could test for this one.
 
The vsti crashes I get may just be the vstis having their own issues, so true, can't say that is a problem with Sonar.
 
Oh and thanks for the comments on the song! Appreciate it.
 
 
 
 

One thing that may have an impact on why my start screen only needs one click to open a project is I always setup my mouse to activate a window when it hover's over it. Window selection is automatic with this. It saves clicking on windows to bring them in to focus. Its a Windows setting. 

Here you go. This should work in all version of Windows.  Goto Control Panel. Find "Ease of Access Center" The list should show "Make the mouse easier to use" Click on that. Look at the section "make it easier to manage windows" check the first item "Activate a window by hovering over it with a mouse". That should do it.

Good music and thanks for posting your findings with Kingston.  
I've also noticed a real jump in speed with the latest release.  Have finished a couple of compositions over the holiday week/weekend and the update has contributed handily!
Although I did get one crash this past week, it seemed more like it was my own doing and not necessarily the fault of the update as I couldn't reproduce it all week.
Did I say that was good music? 

One thing that may have an impact on why my start screen only needs one click to open a project is I always setup my mouse to activate a window when it hover's over it. Window selection is automatic with this. It saves clicking on windows to bring them in to focus. Its a Windows setting.

I thought that this was a new feature in Windows 10. You can achieve this in older Windows versions??

I know where you're coming from Steve.  I'm taken my song/composition writing more serious now as well.
let me know if you figure out the problem with Omnesphere2.  May help a few others here as well.

No, Kingston still has the issue where the VST menus get desynced and choosing one from the menu ends up inserting something different. You don't need to rescan to fix it, just to restart Sonar. Hopefully it'll be fixed soon.

Kylotan
No, Kingston still has the issue where the VST menus get desynced and choosing one from the menu ends up inserting something different. You don't need to rescan to fix it, just to restart Sonar. Hopefully it'll be fixed soon.

I don't think you read what I quoted from slumbermachine.

So there are two vsti issues I'm running into:
 
1. The rename/bad index (wrong vsti) gets loaded. This happens ever so often on my system, maybe it's due to some vsti's not being available due to a missing iLok because sometimes my usb craps out causing my iLok to not connect my licenses. Not sure, but I have to reset and re-scan pretty often.
 
2. Certain VSTi's seem to crash often during freeze or get static or other strange issues randomly (usually on large projects). I narrowed this down to a few vsti that seem to give the most issues: Omnisphere 2, iris, and kontakt 5.
 

• The kontakt issue was fixed by changing the offline interpolation quality setting to "like realtime". 
• Izotope Iris was fixed by using the vst3 version and removing all instances of the vst2 version in my projects.
• Some other static issues were fixed by removing and readding the instruments.(usually involves, saving the patch and all the fx settings, copy and pasting the midi to a spare track, deleting the original track, then adding the vst back and all of the fx after a reset and rescan. Somewhat like rebooting an old mirage sampler... hehehe But the good news is that once this is done the track is fine from then on.
• Omnisphere 2 I was able to remove a lot of static by not ever automating any of the settings to 100%. There must be a bug in it where if it hits 100% in sonar automation it's going over the max for the setting in Omnisphere 2 (think of a filter cutoff going to 101% open, it's like nasty digital static).

Still getting Omnisphere crashes though on bounce and freeze. Something is buggy there and I can't figure it out.