Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: Insane problems with this update
2016/12/03 10:45:18
(permalink)
Yes, but it went away all by itself. The only difference was that the computer went through a couple of restarts. Of course ideally, my computer is become ever-more intelligent, enhancing its AI, and fixing itself  Just a hunch, but with the new drivers, I wonder if deleting the AUD.INI file and letting it rebuild might solve some problems?
|
Noel Borthwick [Cakewalk]
Cakewalk Staff
- Total Posts : 6475
- Joined: 2003/11/03 17:22:50
- Location: Boston, MA, USA
- Status: offline
Re: Insane problems with this update
2016/12/03 11:33:50
(permalink)
Bristol_Jonesey
Yes John this update has caused more problems than anything I've seen since the dark days of X1a/b.
They all seem to be related to the Plugin Manager so I just hope the Bakers have enough information to work out what went wrong and issue a fix.
There are zero changes to the vst scanner or plugin manager in the 2016.11 update. Which version were you using prior to this update? Your problems are most likely coincidental and caused by something else.
|
bitflipper
01100010 01101001 01110100 01100110 01101100 01101
- Total Posts : 26036
- Joined: 2006/09/17 11:23:23
- Location: Everett, WA USA
- Status: offline
Re: Insane problems with this update
2016/12/03 11:54:00
(permalink)
Both pluginmanager.exe and vstscan.exe show version 22.11.0.111. Do you increment the version number with each release, regardless of whether there have been any changes? Nothing wrong with that if you do (easy for us to verify we're up-to-rev), but it makes it impossible for users to determine if changes have been made.
Should note that whenever a scan hangs or aborts, it is almost always a problem with a particular plugin, not with the plugin manager.
Back on topic: I have experienced crashes here as well, involving CA-2A and Rapture. Each time, the problem could not be reproduced until after a reboot. After rebooting, the problem reappears, but only once. The following exception (stack overrun) occurs if I drag CA-2A into any FX bin. After restarting SONAR, the problem is gone - until the next reboot.
Faulting application name: SONARPLT.EXE, version: 22.11.0.111, time stamp: 0x583d02e6
Faulting module name: CA-2ALevelingAmplifier_64.vst3, version: 2.0.1.97, time stamp: 0x5802558a
Exception code: 0xc0000409
Fault offset: 0x0000000000085e88
Faulting process id: 0x1e8c
Faulting application start time: 0x01d24d854f2cc61f
Faulting application path: C:\Program Files\Cakewalk\SONAR Platinum\SONARPLT.EXE
Faulting module path: c:\program files\common files\vst3\CA2ALevelingAmplifier\CA-2ALevelingAmplifier_64.vst3
 All else is in doubt, so this is the truth I cling to. My Stuff
|
John
Forum Host
- Total Posts : 30467
- Joined: 2003/11/06 11:53:17
- Status: offline
Re: Insane problems with this update
2016/12/03 12:16:02
(permalink)
Now I feel left out. 
|
papacucku
Max Output Level: -88 dBFS
- Total Posts : 135
- Joined: 2015/04/13 16:28:35
- Status: offline
Re: Insane problems with this update
2016/12/03 12:33:49
(permalink)
Had issues for the first time with this one as well. With windows "Cause" can be a grey area. My case was likely an order of operation issue with visual C++ runtime, windows updates and platinum/command center update.
To the user it appears cakewalk "caused" the issue. The technician might recognize that it only "triggered" the issue but that does not matter. Updating cakewalk hosed my platinum and I was unable to get it working in my studio at all until resolving the a regsvr dll issue.
To the eye it appeared the new command center update caused my issue. It was likely deeper.
Its cakewalks problem if they get caught in an update/runtime hot potato and they know it. I am sure they are aware of it.
Rig1: Platinum. 1513 Intel Core i7 5930K (3.50GHz) 32GB DDR3 SSD, GTX 970 Windows 10 64. Focusrite Saffire 6i6. Presonus Monitors. Rig 2:Platinum. Win 7, Quad CPU 8 DDR3. SSD. RME multiface II, Oktopre MKII, StudioLive AI 16, Presonus Sceptre Coaxial Monitors. Drums:TAMA ImperialStar, Roland TD30 Keys: Yamaha Mx-61, M-audio Keystation IRIG I/O Midi Controllers. Additional Plugs:Melodyne Editor, Izotope (all), Autotune, Trillian, East West(most),Addictive Drums2, Addictive Piano, AIR FX Collection.
|
mixmkr
Max Output Level: -43.5 dBFS
- Total Posts : 3169
- Joined: 2007/03/05 22:23:43
- Status: offline
Re: Insane problems with this update
2016/12/03 13:14:53
(permalink)
I had a minor issues when updating.
1. I was guided thru the "setup" again, like when initially installing Sonar. That has never happened.
2, Even after this new "setup", I had to assign my MIDI in/outs again. (2nd time)
3. My latest session had an instance of EZD2 that had no output. I was able to just delete the synth and install again in that session and it was fine. ALL other checked sessions with EZD2 seemed fine.
4. Sonar DID crash when deleting EZD and my "fault reported" showed up about 20 times in my task manager. I just closed ALL windows in my Windows task bar.
After the weirdness above, all seems fine. My CA-2A seems fine in both FX bin and ProChannel....either as an old instance already in a project or a new insert.
I guess we'll see. The Setup again kinda freaked me a little...as I didn't know if it was the tip of the iceberg or not.......but calmed down now ;-)
|
DarkMatter12
Max Output Level: -90 dBFS
- Total Posts : 23
- Joined: 2012/01/21 04:04:49
- Location: Germany
- Status: offline
Re: Insane problems with this update
2016/12/03 13:59:37
(permalink)
After the update from 2016-10 to 2016.11 Sonar Platinum crashes every time when I open my projects.
When I disable CA-2A (shift+open file) it works.
Then I tried to insert CA-2A into my project again, Sonar crashes immediately.
When I create a new project and try to insert CA-2A in Prochannel or FX bin, it crashes.
I did a new installation(Command Center) of CA-2A , without success.
What is going wrong with that plugin and the new update?
Sonar Platinum, Win10 64bit, Core i7, 8Gb RAM, SSD 500GB, Roland XV 3080, EMU Orbit 9090, Korg M1, Boss DR-660, Eridol M-16 DX, Midisport 2x2, Roland A-800 Pro, Behringer Denoiser, Yamaha FX 500, Rode NT1, Presonus TubePre, div Plugins, Yamaha HS80m
|
abacab
Max Output Level: -30.5 dBFS
- Total Posts : 4464
- Joined: 2014/12/31 19:34:07
- Status: offline
Re: Insane problems with this update
2016/12/03 14:20:24
(permalink)
Don't know if this is related or not, but I did experience a small issue with drag and drop from Windows explorer into the Sonar workspace, after upgrading from 2016.09 to 2016.10 a few days ago (just before 2016.11 was released). http://forum.cakewalk.com/Installed-the-latest-update-and-now-dragdrop-isnt-working-again-m3519421.aspx#3521517 Rolling back to 2016.09, followed by a reboot, cleared the issue. Then when 2016.11 was released, I jumped on that. Same issue, but it cleared after a reboot. No further issues ... Never any issues with crashes or plugin scanning ... Can insert CA-2A anywhere without a hitch.
DAW: CbB; Sonar Platinum, and others ...
|
Zargg
Max Output Level: 0 dBFS
- Total Posts : 10666
- Joined: 2014/09/28 04:20:14
- Location: Norway
- Status: offline
Re: Insane problems with this update
2016/12/03 14:48:36
(permalink)
John
Now I feel left out.
Maybe we should go to the back of the room  I'm not having these issues either..
Ken Nilsen ZarggBBZWin 10 Pro X64, Cakewalk by Bandlab, SPlat X64, AMD AM3+ fx-8320, 16Gb RAM, RME Ucx (+ ARC), Tascam FW 1884, M-Audio Keystation 61es, *AKAI MPK Pro 25, *Softube Console1, Alesis DM6 USB, Maschine MkII Laptop setup: Win 10 X64, i5 2.4ghz, 8gb RAM, 320gb 7200 RPM HD, Focusrite Solo, + *
|
ampfixer
Max Output Level: -20 dBFS
- Total Posts : 5508
- Joined: 2010/12/12 20:11:50
- Location: Ontario
- Status: offline
Re: Insane problems with this update
2016/12/03 15:23:37
(permalink)
When I installed the update the menu at the top of the screen was unreadable and greyed out. This lasted about 20 minutes and then cleared itself. It seems that most times that I have a glitch (very rare) it fixes its self and remains a mystery. I suspect Windows updates are involved because they randomly turn on all the audio stuff I've turned off. With the current rate of change in the OS, Sonar and hardware drivers, I find it almost impossible to establish cause/effect relationships when things get weird on the computer.
post edited by ampfixer - 2016/12/03 17:19:31
Regards, John I want to make it clear that I am an Eedjit. I have no direct, or indirect, knowledge of business, the music industry, forum threads or the meaning of life. I know about amps. WIN 10 Pro X64, I7-3770k 16 gigs, ASUS Z77 pro, AMD 7950 3 gig, Steinberg UR44, A-Pro 500, Sonar Platinum, KRK Rokit 6
|
PeterMc
Max Output Level: -80 dBFS
- Total Posts : 504
- Joined: 2003/11/12 23:46:34
- Location: Tasmania
- Status: offline
Re: Insane problems with this update
2016/12/03 18:11:52
(permalink)
This is a long shot but might be worth checking. Is your installation 64bit i.e. x64? With this latest update, and for the first time ever, CCC had verbose install enabled. I notice it had 32bit Platinum chosen by default. I always install 64 bit. If verbose install was disabled, I would not have known.
Could the 32bit version cause the problems people are having?
Cheers, Peter.
i5 6500, H170M, Intel HD 530, 16GB, Focusrite Scarlett 8i6, Win 10 Pro (1803) (64 bit), Cakewalk by Bandlab
|
Fabio Rubato
Max Output Level: -81 dBFS
- Total Posts : 500
- Joined: 2006/09/01 21:51:29
- Location: Australia
- Status: offline
Re: Insane problems with this update
2016/12/03 19:10:24
(permalink)
I'm having some issues as well. Every time I open a project I've been working on, I'll get the plt stops working crash. However, each time I restart the project, it's all good.
The other day, I too inserted CA-2A in Prochannel FX bin and got the dreaded spit/meltdown issue which had been okay. I also inserted a wave plug-in on the bus and the same thing occurred...big noise through my monitors, red-lined input, horrendous noise. I have to immediately turn down my monitors, save my project and restart...then it's all good...weird and really annoying as it puts a halt to my work and doesn't do my monitors any good I'm sure. I have a work-around now where I'll turn down my monitors each time before inserting a plug-in.
No magical system auto fixes here unfortunately.
Sonar: Platinum, (X3e) - x64 PC: Win10 Pro 64; Computer: Gigabyte Z68X-UD3R-B3; Intel i7, 2600k @ 4.2 (8 Cores); 16 GB Corsair Ram; Visual Card: Gigabyte GTX 580; Audio Interface: RME UFX; Monitors: Adam A77X, Sub8; Midi Controllers: Komplete Kontrol S88, Novation Bass Station 2; NI Maschine Mk 2; Other Hardware: Joe Meek Twin Q Dual Studio Channel; Mics: RODE NT2-A, ASTON Spirit Latest Song: Lay Down Before the War
|
soens
Max Output Level: -23.5 dBFS
- Total Posts : 5154
- Joined: 2005/09/16 03:19:55
- Location: Location: Location
- Status: offline
Re: Insane problems with this update
2016/12/03 19:20:54
(permalink)
Bristol_Jonesey
soens
Dumb question: Are the updates cumulative? If so, do you inherit the bugs from the last update with the next one?
Updates are indeed cumulative but that's not to say any given bug wasn't eliminated prior to releasing a new update, otherwise no bugs would ever be squashed!
I ask because if I choose to pass on this update but go with the next one because it has something I like/need/want, I could end up with a bug I tried to avoid that wasn't fixed.
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: Insane problems with this update
2016/12/03 19:57:24
(permalink)
Fabio Rubato
I'm having some issues as well. Every time I open a project I've been working on, I'll get the plt stops working crash. However, each time I restart the project, it's all good.
Same here, but here's what's REALLY interesting: I had this happen on my desktop computer (which always lags my laptop by a few weeks) with 2016.10, not 2016.11 - but only right after a Windows update. I also started having an issue where my monitor didn't open at the right resolution. There's a lady in Gibson's graphics department who had the same problem; I asked if she knew of a fix but said it happened with the last Windows update and she has to edit the resolution after opening (which is what I have to do as well). I think Ampfixer is spot-on about "too many variables." I'm seeing the same thing happen with the forced MacOS updates (if you know any Final Cut Pro users, ask them about what happened with the last update - some of them will say things that will truly expand your vocabulary of cuss words). Frankly, I think both Microsoft and Apple could learn a thing or two from Cakewalk, specifically rollbacks and quick hot fixes.
|
tenfoot
Max Output Level: -53.5 dBFS
- Total Posts : 2186
- Joined: 2015/01/22 18:12:07
- Location: Qld, Australia
- Status: offline
Re: Insane problems with this update
2016/12/03 20:52:38
(permalink)
☄ Helpfulby abacab 2016/12/03 22:10:07
This is all very true, however my studio PC is on an isolated network not connected to the Internet. I connect and run Windows updates at times of my choosing. I have not updated windows in the last 2 months and still had issues with the last Sonar update. Short of there being a crucial recent update (I am runnig WU as we speak) the windows update variable doesn't apply. Sometimes it's just Sonar. I couldn't count the number of times I have had issues over the years where all kinds of windows update solutions/causes were suggested that I spent many hours trying to no avail, but after a further Sonar update/fix release all was well:)
Computers are a fickle world of infinite variables, but I do find a little patience often trumps speculation:)
Bruce. Sonar Platinum 2017-09, Studio One 3.5.3, Win 10 x64, Quad core i7, RME Fireface, Behringer X32 Producer, Behringer X32 Rack, Presonus Faderport, Lemure Software Controller (Android), Enttec DMXIS VST lighting controller, Xtempo POK.
|
The Grim 
Max Output Level: -76 dBFS
- Total Posts : 724
- Joined: 2016/04/19 02:31:06
- Location: hades
- Status: offline
Re: Insane problems with this update
2016/12/03 21:02:35
(permalink)
☄ Helpfulby abacab 2016/12/03 22:09:55
the last time i let windows 10 update or check for updates was 31st of july, i'm still on v1511, i am not having any issues with stuff mentioned here or in other threads. had a slight hiccup on first installing the latest platinum update, but that was cured, or disappeared after a reboot.
|
RonCaird
Max Output Level: -88 dBFS
- Total Posts : 101
- Joined: 2012/10/04 21:16:41
- Location: Atlanta, GA
- Status: offline
Re: Insane problems with this update
2016/12/04 01:34:20
(permalink)
I did have a problem after this last upgrade with one project. When I tried to open it from the start screen, Platinum would stop working, give me the microsoft error message and shut down. This happened a couple of times in a row. I started Sonar again and opened a different project and everything was fine. I again tried to open the project that initially caused the problem and the same crash occurred. After restarting Sonar, I closed the Start window and tried to open the problem project from the file menu. This time it opened fine. I did some work on the project, saved it and closed the program and shut down the computer. The next time I started, attempting to open that project from the start screen again caused the crash. I restarted Sonar, opened the project from the file menu and saved it under a different file name. Thus far, I have been able to open the renamed project from the start screen without a problem.
RonCBB, Gateway DX, Core i7 2600, Windows 10 64 bit, 6 GB RAM, 1 TB C Drive, 2 TB D Drive, 1 TB Network Drive, Akai EIE Pro 4 channel Audio Interface. Music: RonCaird.com Blog: GuitarAccompanist.com
|
mixmkr
Max Output Level: -43.5 dBFS
- Total Posts : 3169
- Joined: 2007/03/05 22:23:43
- Status: offline
Re: Insane problems with this update
2016/12/04 01:38:26
(permalink)
RonCaird
I did have a problem after this last upgrade with one project. When I tried to open it from the start screen, Platinum would stop working, give me the microsoft error message and shut down. This happened a couple of times in a row. I started Sonar again and opened a different project and everything was fine. I again tried to open the project that initially caused the problem and the same crash occurred. After restarting Sonar, I closed the Start window and tried to open the problem project from the file menu. This time it opened fine. I did some work on the project, saved it and closed the program and shut down the computer. The next time I started, attempting to open that project from the start screen again caused the crash. I restarted Sonar, opened the project from the file menu and saved it under a different file name. Thus far, I have been able to open the renamed project from the start screen without a problem.
I've had that same thing happen as well...and before this last update.
|
Re: Insane problems with this update
2016/12/04 02:10:23
(permalink)
The "synth tab missing" is the only problem I've had so far as well Jonesey. Had to open it via Views > Synth Rack View as well or press "o" to display the synth rack.
|
lapasoa
Max Output Level: -87 dBFS
- Total Posts : 193
- Joined: 2010/07/16 11:29:58
- Location: Venice ITALY
- Status: offline
Re: Insane problems with this update
2016/12/04 03:06:56
(permalink)
It's not the first time i had troubles with some new updates. Expecially with 2016.10, I had to roll back to 2016.09.
With november update I had some "Sonarplt.exe has stopped" all related to plugins like Melodyne, AD2 and TH3. But I've found that with every start of Sonar things become better and better. Now everyting is all right.
I think that these issues originate from Windows, that at the first starts of Sonar's new updates is fighting to stabilize the daw.
|
ampfixer
Max Output Level: -20 dBFS
- Total Posts : 5508
- Joined: 2010/12/12 20:11:50
- Location: Ontario
- Status: offline
Re: Insane problems with this update
2016/12/04 03:46:34
(permalink)
What makes it even harder is the fact that the updates roll out in different global regions at different times. I always seem a week behind the Americans when it comes to updates. At least that;s what I notice with the bigger OS updates. Folks talk about the big update and I see it a week later. I imagine it's all based on infrastructure and legal issues.
Regards, John I want to make it clear that I am an Eedjit. I have no direct, or indirect, knowledge of business, the music industry, forum threads or the meaning of life. I know about amps. WIN 10 Pro X64, I7-3770k 16 gigs, ASUS Z77 pro, AMD 7950 3 gig, Steinberg UR44, A-Pro 500, Sonar Platinum, KRK Rokit 6
|
THambrecht
Max Output Level: -73 dBFS
- Total Posts : 867
- Joined: 2010/12/10 06:42:03
- Location: Germany
- Status: offline
Re: Insane problems with this update
2016/12/04 04:18:04
(permalink)
With the november update the "add track" dialog pops up by commands as "clear audio folder" and "insert fx chain preset" and randomly by other commands. Also it is not possible to bind any key for "insert marker". Also my Behringer X-Touch can't insert a marker since this update.
I also see no synthesizer tab.
But obviously I'm almost the only one - I see this phenomenon on all my computers. So it cannot be due to the hardware and windows updates.
Very mistery.
We digitize tapes, vinyl, dat, md ... in broadcast and studio quality for publishers, public institutions and individuals.4 x Intel Quad-CPU, 4GHz Sonar Platinum (Windows 10 - 64Bit) and 14 computers for recording tapes, vinyl ...
4 x RME Fireface 800, 2 x Roland Octa Capture and 4 x Roland Quad Capture, Focusrite .... Studer A80, RP99, EMT948 ...
(Germany) http://www.hambrecht.de
|
millzy
Max Output Level: -73 dBFS
- Total Posts : 890
- Joined: 2005/01/28 20:32:51
- Location: Melbourne, Australia
- Status: offline
Re: Insane problems with this update
2016/12/04 05:05:28
(permalink)
I've had the 'add track' dialogue pop up randomly when doing something else.
Millzy i7 3770K, 16gb ram, Samsung EVO SSD, 2 x WD drives, RME Babyface, Win 10 (x64), Cakewalk by Bandlab, heaps of other stuff.
|
klauselix
Max Output Level: -90 dBFS
- Total Posts : 9
- Joined: 2015/01/11 09:05:41
- Location: Germany
- Status: offline
Re: Insane problems with this update
2016/12/04 05:06:48
(permalink)
For me the problem started with Sonar crashing when loading projects. Loading projects in safe mode was possible when confirming each plug-in one by one. A workaround that works for me. After loading successfully Sonar was rock solid as always.
Rolled back to 2016.10 and still had the same issues, went back to 2016.11. Windows 10 updates are up to date.
Subsequent project loads mostly work without crashing SONARPLT.EXE. But the problem reoccurs after rebooting the PC.
Then I decided to do a plug-in reset and rescan. The rescan only gets to CA-2A.._64.dll and hangs. Closing the box and clicking Reset again this time successfully scans CA-2A but hangs at RaptureSession_64, same repeats with about 6 more plug-ins. Then the rescan is complete. Another workaround that's ok for me so far.
In between I had "Runtime Error! R6025: pure virtual function call", but not reproducable.
I'm sharing my experience here because it may help narrow in on the problem and the workarounds may work for others as well.
Sonar Platinum 2016.11, Z3TA+2, Rapture Pro, Komplete 9, EZ Drummer 2, Windows 10 x64, Intel i7-4770 @3.4GHz, 16GB, SSD 256GB, HD 1TB, Steinberg UR242 (ASIO) Music: soundcloud.com/klaus-elix
|
DarkMatter12
Max Output Level: -90 dBFS
- Total Posts : 23
- Joined: 2012/01/21 04:04:49
- Location: Germany
- Status: offline
Re: Insane problems with this update
2016/12/04 05:39:20
(permalink)
@klauselix: I have the same problems with CA-2A and I got the same Runtime Error R6025.
I deinstalled CA-2A and rescaned all plugins. Now I can load my older projects, but can't use CA-2A anymore.
I tried to roll back, but as you mentioned the issues are the same.
A second crash was caused by melodyne 4.1 dll, when I open older projects.
I never had so much problems with Sonar.
I'm not sure if it's a problem of 2016.11 Sonar-update or Win 10. The last update of Win10 was on 1.12.16
Sonar Platinum, Win10 64bit, Core i7, 8Gb RAM, SSD 500GB, Roland XV 3080, EMU Orbit 9090, Korg M1, Boss DR-660, Eridol M-16 DX, Midisport 2x2, Roland A-800 Pro, Behringer Denoiser, Yamaha FX 500, Rode NT1, Presonus TubePre, div Plugins, Yamaha HS80m
|
klauselix
Max Output Level: -90 dBFS
- Total Posts : 9
- Joined: 2015/01/11 09:05:41
- Location: Germany
- Status: offline
Re: Insane problems with this update
2016/12/04 05:43:50
(permalink)
Interesting. I'm still on Melodyne 4.0 which seems to be fine for now. Was planning to go to 4.1 this week. Will pushi this back now.
Sonar Platinum 2016.11, Z3TA+2, Rapture Pro, Komplete 9, EZ Drummer 2, Windows 10 x64, Intel i7-4770 @3.4GHz, 16GB, SSD 256GB, HD 1TB, Steinberg UR242 (ASIO) Music: soundcloud.com/klaus-elix
|
Songroom
Max Output Level: -87 dBFS
- Total Posts : 174
- Joined: 2013/09/19 02:18:32
- Location: UK
- Status: offline
Re: Insane problems with this update
2016/12/04 06:18:41
(permalink)
As a comparison, my Windows 10 (x64) is fully up to date and the latest Sonar Platinum update seems to be fine.
Since the CC update, I've installed and scanned two new Waves plugins (Super Tap / Electric 200 Piano) and worked a on an existing session which includes CA-2A. Melodyne Editor 4.1 is also operating as expected.
I've posted this in the hope that it helps to eliminate possible culprits.
Sonar Platinum - BandLab Cakewalk - Presonus 16.0.2 - Tannoys - Lava BandLamp ?
|
gustabo
Max Output Level: -49.5 dBFS
- Total Posts : 2591
- Joined: 2009/01/05 17:32:38
- Status: offline
Re: Insane problems with this update
2016/12/04 06:59:57
(permalink)
Songroom
As a comparison, my Windows 10 (x64) is fully up to date and the latest Sonar Platinum update seems to be fine.
Since the CC update, I've installed and scanned two new Waves plugins (Super Tap / Electric 200 Piano) and worked a on an existing session which includes CA-2A. Melodyne Editor 4.1 is also operating as expected.
I've posted this in the hope that it helps to eliminate possible culprits.
Same here except I've installed different plugins since the update.
Cakewalk by Bandlab - Win10 Pro x64 - StudioCat Platinum Studio DAW - 32 GB Ram - MOTU UltraLite-mk3
M-Audio Keystation 88ES - Akai MPD26 (hot-rodded) - Alesis DM10 - a few guitars, a few amps
Novation Launch Control - Korg nanoKONTROL2 - PreSonus FaderPort - DAW Remote HD on iPad
Adam A7X - Behritone C50A
PreSonus Monitor Station v2 (controlling the mons)
https://www.facebook.com/groups/sonarusergroup/
|
Deon_C
Max Output Level: -90 dBFS
- Total Posts : 20
- Joined: 2010/12/20 21:10:05
- Status: offline
Re: Insane problems with this update
2016/12/04 07:13:28
(permalink)
I have also had the crash on project open a number of times since installing the update. Similar to some of the other reports after a crash, re-opening the project does work, but it may crash once or twice more before it does.
I have not had a crash for a while prior to that. Dont know if it is related but when it does crash, the vst scanner is running during the crash and gets stuck on waves.
Also running win 10, i have delayed updates, but am connected to the net.
|
Bristol_Jonesey
Max Output Level: 0 dBFS
- Total Posts : 16775
- Joined: 2007/10/08 15:41:17
- Location: Bristol, UK
- Status: offline
Re: Insane problems with this update
2016/12/04 07:48:38
(permalink)
Just to add to the confusion, I noticed in the CCC that ehre was an update to the "Cakewalk Loopmasters Content Collection" I have tried to update it several times but keep on getting this message:  Does anyone have a clue what this means or how to fix it? Cheers.
CbB, Platinum, 64 bit throughoutCustom built i7 3930, 32Gb RAM, 2 x 1Tb Internal HDD, 1 x 1TB system SSD (Win 7), 1 x 500Gb system SSD (Win 10), 2 x 1Tb External HDD's, Dual boot Win 7 & Win 10 64 Bit, Saffire Pro 26, ISA One, Adam P11A,
|