steven galutia

I've noticed a new unusual behavior recently, I probably have inadvertently changed a setting, but it's got me stumped. After recording a Virtual Instrument, say Spitfire violins, I'll go back and write the CC data from my midi controller for CC 11 and 1, and maybe repeat that until I get it right, and I'll use "write" mode for that track and keep it on Sound on Sound recording, as well, otherwise the notes would be erased, and until recently it would overwrite any previously CC data and substitute my new CC data, now I can only record on top of previously recorded CC data, and the resulting buildup is an up and down jerky mess. Ideas?

Amberwolf, your suggestion..."If you turn off the "save every X number of changes" and only use the timed autosave, does it correct the problem?" was spot on. Zeroed the save every x changes option, and the problem disappeared. Thanks!

Just noticed this on project today, (I am running the new .36 update since y'day). The "Time" area on the control bar flares with a quick save every 6-7 seconds, First I noticed that I couldn't open up any cascading menus because it times out and Save happens before I could get to my desired option from the dropdown. I have checked the autosave settings and there doesn't seem to be anything amiss there. Suggestions? Thanks-

I wholeheartedly agree! I've been starting to do a lot more Midi orchestration, and the PRV color scheme is pitiful, only the blownout whitish scheme shows a significant difference between selected notes and unselected notes. and measures and beat lines are barely discernible. I know I should get Cubase for this type of stuff, but I've been on Sonar since it began, and it's gotten too comfortable to change. If Sonar wants to be a contender in the Midi orchestration market, they need to glean some more usability features from the top competitors. Please...