bitflipper

PeterMc
Is there an easy and reproducible recipe for a crash, preferably starting from a blank project?

For me, it's easy and reproducible. All I have to do is 1) reboot the machine and 2) insert CA-2A into an FX bin (or open a project that already contains CA-2A in an FX bin).
 
Not everyone's experiencing the same symptoms, though. For example, I have no problem doing a scan.
 

I'm at my workstation and have just followed the above steps but no crash.
 
Versions / Builds
Windows Home 10x64: Build 14393.447
Sonar Platinum Version: 22.11.0 Build 111 (2016.11) x64
 
Sonar Platinum
All users / Run as an administrator
 
Windows 10 Settings
Background Apps: Disabled
 
Windows Tasks
Application Experience Task: Disabled
Feedback Task: Disabled
Customer Experience Improvement Program: Disabled
 
Anti-Virus Software
Windows Defender: Disabled
Bitdefender Basic
 
 

could the analytics be helpful here? identify differences between the crashes and crash-nots?

gokidsmusic
 
(FWIW) Plugin count significantly increased after update.  Discovered the "C:\Program Files (x86)\Cakewalk\Vstplugins" had been added to VST scan path after update.  Deleted path, rescanned, plug count as expected.
 

this came in with the newbie feature which "helps" defining first settings. on the machine where I did not click it away, it messed with my VST paths and brought back all excluded 32 bit plugs.
 
I don't like that at all - and it's certainly not going to do any good to improve newbie Sonar stability worldwide.

Zargg

John
Now I feel left out. 

Maybe we should go to the back of the room
I'm not having these issues either..

Come on back here guys. Everything's just fine at the back wall.

So I'm up at the studio and this rig crashed as soon as I tried to open a project. When I restart Sonar immediately after the crash, no reboot, it tells me I don't have audio devices. On second attempt (after a reboot) I checked that the audio devices were there before attempting to open a project - I picked a random project unrelated to the first and it crashed as well, then as before it would start but tell me I didn't have audio devices. This computer is on 2016.10 since its non-early release and has had the latest windows update since 11/9/2016. So strange this all happened at once and this computer is rarely online.
 Could it be an interface update? Roland doesn't really tell you when it updates apparently

So I rebooted and start sonar, check for audio devices, everything looks fine. start a new blank project and it does let me. First thing I masochistically do is open the pro channel and insert ca-2a and crash! I think I'm going to devote this week to practicing instruments and keep an eye on the forum... 

Try reinstalling it

I've had several problems since the update.
 
1. In one project, I was using Session Drummer for a click track (don't want to argue about the Metronome right now). After the update, Session Drummer started playing back one of its canned MIDI sequences along with the click when I started to track, at very high volume. (This was compounded by my not being able to find the Synth Rack, but that's my fault for not reading the e-zine.)
 
2. While opening a project containing Rapture Pro, I got a message reading "Failed to locate resource", then a MS crash message (0xc...05). I uninstalled and reinstalled Rapture Pro, which seemed to fix it.
 
3. Trying to open some projects from the Start Menu or from the File menu led to "SONAR.PLT has stopped working". They opened OK from Windows Explorer, and behaved normally after saving.
 
I'm sure all this is going to get worked out.

So, mine has been working for a couple days, and I am working on old projects that I have to insert Pro Channel and CA-2A, EQ etc on (all predate that) and I am having no issues. I didn't do anything either. .....like more than give up and go have dinner! LOL
 
Michael

I also am experiencing very odd behaviour. The odd thing is that I don't keep my music computer connected to the Internet. Yet when I turned it on Sonar was behaving with almost all the problems listed in previous threads.

Sonar claims that I must re authorize plug ins and that others don't exist. It is very weird. I hope they have a fix soon.

I just checked a project that has no plug ins and it loads and plays fine. So I presume, as has previously been said that it is caused by the plug in manager.