Ralph [RZ] wrote:Susan, JS does not store mute settings because they were designed as a temporary working tool. We can make this a permanent setting in a JS3 update.
Yes, please! I use mutes as a "temporary" tool, but often I have to leave the project and come back to it, so I'd like the states to persist with the save.
b_macinan wrote:thanks for the kind words guys. Ralph, I read that stability in Sonar is being looked at.... I have trouble with saving grooves and 7/4 time. Any chance those are on the list?
The 7/4 issue will be fixed in the next Beta. Did you have a separate save groove issue?
I did Ralph, but I can't seem to duplicate the error where it actually showed me the access error... now it just crashes bitbridge, and ultimately sonar... I'll get back to you if I can get the access error to show.
Good news and bad news. The good news is, I can save grooves now! Thank you for that.
Bad news is on the 7/4 time change front. It seems that going to the 7/4, it's starting one beat early..... what can I send you to assist? It's a pretty small sonar bundle.. there's only the one scratch acoustic track and the JS Instrument track.
I also get the pause when adjusting the Power knob with A16 and Reaper. Seems to specifically occur when the mouse up happens, if the mouse button is held down the Power will transition without the glitch.
I also get a bit of glitching at low latency settings when clicking on kit elements with the Mixer section open, trivial. So far it seems to be all good with the GUI closed.
I use mutes as a "temporary" tool, but often I have to leave the project and come back to it, so I'd like the states to persist with the save. 