presonus studio one nebula 1.3.601 locks entire system
Posted: Thu Oct 03, 2013 2:23 pm
Hi there,
Eventually this is my only problem since 1.3.601, so I thought I might as well ask it. I have no idea if and where there is a list for 'known problems' so I don't know if this is mentioned somewhere else or not, but let's go:
I'm on Windows 7 x64, using Nebula 3 Pro x64. I had 1.3.505 working fine in both Reaper and Presonus Studio One (v2.6), both the x64 versions. I'm on a laptop with a Core i7-2670qm and an AMD HD6990 gpu.
1.3.601 is now working OK in my Reaper installation, specially since the full setup versions were posted to the 'My Downloads' section yesterday. The upgrades were not working OK. (Full setup from 1.3.492, upgrade to 1.3.505 and it's still working. Upgrade to 1.3.601 and it crashes Reaper. Full setup 1.3.601 in one go and it works OK...).
But there seems to be problems with my Presonus Studio One, still. The full setup of 1.3.601 installed versions in VstPlugins\Acustica (the older filenames, Nebula3CoreII64.dll etc...) and versions in VstPlugins\Acustica64 (the Nebula3.dll naming conventions). So in Studio1 I see 'Nebula3CoreII64' (normal and Reverb) and 'Nebula3' (normal and reverb). The 'Nebula3' refuse to be placed on a track. If I drag them from the 'Effects' window to the inserts of the track, my PC seems to 'think' for a second and then nothing. I can try and try and try again but it just refuses to be inserted.
If I drag the 'Nebula3CoreII64' plugin to a track, it seems to work OK. Nebula shows, is loading, and after a second ends up in the 'Init' program. I select a program from OwnHammer and start playing back. The sound is 'clicky'. There is a lot of static in it. Now, eventually (can be two seconds, can be a few minutes, but often before 5 minutes or less) my PC starts to lock up. The start button refuses to respond, I get messages about 'Windows Explorer has stopped responding', but I can't click the 'cancel' or 'close' buttons because the dialog itself is not responding.
If I hit ctrl-alt-delete, the screen turns black with a single vertical 1-pixel wide blue line somewhere in the screen, nothing else. The only way the use the PC again is to force it off (holding the power button a few seconds) and turn it back on.
Normally, a problem like this would be related to my PC. But it only happens if I use Studio One with Nebula on a track. Nebula on reaper works fine. Studio One without Nebula works fine. It's only Studio One + Nebula that causes it.
Weird thing, I didn't have these problems with 1.3.505 (for which the setup + upgrades have been removed from the 'My Downloads'?? While 1.3.492 is still there?). So I can't even downgrade.
Is there a chance it might have something to do with video drivers or something else from my system? Or is it really a bug in Nebula?
Eventually this is my only problem since 1.3.601, so I thought I might as well ask it. I have no idea if and where there is a list for 'known problems' so I don't know if this is mentioned somewhere else or not, but let's go:
I'm on Windows 7 x64, using Nebula 3 Pro x64. I had 1.3.505 working fine in both Reaper and Presonus Studio One (v2.6), both the x64 versions. I'm on a laptop with a Core i7-2670qm and an AMD HD6990 gpu.
1.3.601 is now working OK in my Reaper installation, specially since the full setup versions were posted to the 'My Downloads' section yesterday. The upgrades were not working OK. (Full setup from 1.3.492, upgrade to 1.3.505 and it's still working. Upgrade to 1.3.601 and it crashes Reaper. Full setup 1.3.601 in one go and it works OK...).
But there seems to be problems with my Presonus Studio One, still. The full setup of 1.3.601 installed versions in VstPlugins\Acustica (the older filenames, Nebula3CoreII64.dll etc...) and versions in VstPlugins\Acustica64 (the Nebula3.dll naming conventions). So in Studio1 I see 'Nebula3CoreII64' (normal and Reverb) and 'Nebula3' (normal and reverb). The 'Nebula3' refuse to be placed on a track. If I drag them from the 'Effects' window to the inserts of the track, my PC seems to 'think' for a second and then nothing. I can try and try and try again but it just refuses to be inserted.
If I drag the 'Nebula3CoreII64' plugin to a track, it seems to work OK. Nebula shows, is loading, and after a second ends up in the 'Init' program. I select a program from OwnHammer and start playing back. The sound is 'clicky'. There is a lot of static in it. Now, eventually (can be two seconds, can be a few minutes, but often before 5 minutes or less) my PC starts to lock up. The start button refuses to respond, I get messages about 'Windows Explorer has stopped responding', but I can't click the 'cancel' or 'close' buttons because the dialog itself is not responding.
If I hit ctrl-alt-delete, the screen turns black with a single vertical 1-pixel wide blue line somewhere in the screen, nothing else. The only way the use the PC again is to force it off (holding the power button a few seconds) and turn it back on.
Normally, a problem like this would be related to my PC. But it only happens if I use Studio One with Nebula on a track. Nebula on reaper works fine. Studio One without Nebula works fine. It's only Studio One + Nebula that causes it.
Weird thing, I didn't have these problems with 1.3.505 (for which the setup + upgrades have been removed from the 'My Downloads'?? While 1.3.492 is still there?). So I can't even downgrade.
Is there a chance it might have something to do with video drivers or something else from my system? Or is it really a bug in Nebula?