2017.1 Crash and Burn

Welcome to the world of beta testing.

John,
I tried that when 2016.12 was "problematic" on my x86 rig.
I don't "troubleshoot" much if I have an image that I know works.
I did do some trouble shooting with 12, because that image was a little "out of date".
What I know is, the post 2016.10 installs are "breaking" something in my rig.
Take my thoughts "with a grain of salt", but the fact that installing 11, 12, or 1 causes
SONAR to do the whole "Audio/Midi Setup" dance, I'm assuming something "big" is happening.
Is that "big" (registry changes maybe?) reversed when you rollback to 2016.10 or earlier?
Based on my experience, (YMMV) I would think not.
Of course, this could just be my imagination running "wild".
All I know is installing 2016.12 on my x86 rig caused "issues" that rolling back to 2016.10 didn't fix.
When 2017.1 did the same thing, I wasted no time reloading my (totally up to date) image.
I will be taking a hard look at having TTS1 "split" between two folders.
The 2017.1 "problems" I was having seemed to be centered on those two folders.
I'm headed to AZ for the rest of the winter so its a moot point for now.
 
T
 

That would make sense as far as the "Audio/Midi Setup".
Of course this is a desktop computer.
But still, if "major" changes are necessary to make the WASAPI work...
Hadn't thought about that.
 
T

Well I went thru the whole process again, installed 2017.1.
Used a new project to test.
Inserted TTS and EZD2 from the browser.
Started assigning drum maps, archive, etc.
4 new CWBRN cases in 34 minutes.
Rolling back to 2016.10 from the CCC didn't help.
"Must be project- or system-specific; I can't repro a problem with any of that"
Latest RME driver, 1.098; that doesn't mean that's NOT the problem.
Even starting a "new" project, its a "blank" template; 1 audio track and MASTER buss,
It's not a Cakewalk CWT file, its a cwp I created.
Reloaded my pre 2017 Win Image; I'm "out" for awhile.
Will re-visit in March when I get home.
T

"Where I ran into problems was archiving folders; TTS1 and EZD2 specifically.
Interestingly enough, I do have a TTS track (2 actually) in the EZD folder,
I use the TTS kick as a sub; wondering?
That might bear examining...
Also, I tried to turn off "input echo" at the folder level (EZD2 folder and there are 2 aux tracks
in that folder as well; Kick and Snare), that was the last straw.
I reloaded the Win Image I burned before the 2017.1 install."

Things are now back to "normal"; NOT! That pre 2017.1 Image was buggy as well.
 
I had to go back to my November Image, which incidentally is RME Driver 1.097 and SONAR 2016.10.
I did try "rolling back" the RME driver before going back to my Nov Image.
The very same "project templates" (my templates, cwp files) that were "problematic" (as described above)
in 2017.1 and 2016.10/RME 1.098 (CWBRN 68203) are now working fine.
System, drivers, Rockus and Rollus, the gods of rock music, just playin' with me?
Take your pick!
Evidently (obviously?) its not SONAR, although it looks like not everyone is running smoothly.
I have had some "issues" with 2016.11 (RME 1.091) on the StudioCat, that freebie from AAS; I had a bunch of
dump files trying to work with that back on January 6th.
So that about covers it.
I don't think its something that will be "easily" reproduced, pretty system specific I'm guessing.
It would be interesting to hear from other RME users what their experience has been with the 1.098 driver.
T

Keith,
I can't, I'm on the road as of 9am this morning.
Tom