I just loaded 2708 RC2 and I am a bit disappointed so far.
STS3000 - BSOD! (Was the same in RC1)
VDAT and VRCS on DSP 2 no longer sync together - DOH!
Jimmy I think you might be wise to wait awhile!
New Scope 5.1 RC2 in the FTP
-
doktorfuture
- Posts: 50
- Joined: Mon Dec 28, 2009 7:13 pm
Re: New Scope 5.1 RC2 in the FTP
Have there been any functional changes in 5.1, up to RC2?
Personally I will be glad to just have it work in a stable and integrated way with 64 bit systems. I'm salivating towards that.
But any additional bug fixes or new features would be good too -- anyone know what's new?
Best,
Paul
Personally I will be glad to just have it work in a stable and integrated way with 64 bit systems. I'm salivating towards that.
But any additional bug fixes or new features would be good too -- anyone know what's new?
Best,
Paul
Re: New Scope 5.1 RC2 in the FTP
From what I can see - not much is new.
I have had a couple of BSOD:
- The STS samplers do it for me. It appears to be something to do with it memory calcs I think.
- I have also had another BSOD, but not sure what caused that one. There was no STS's in the project at the time.
I had a strange effect on one project where I had a couple of delay plugs in inserts in a Spacef Mod Mixer. When I reloaded the project (and before I had opened any sequencer) I got this pulsating delay noise from the channels with the delays in them. Removed the delay plugs and it went away. These are the standard Sonic Core Delay plugs.
VDAT still cannot sync via MTC, although I am able to sync via ASIO 2 into Samplitude 11 (Not into Cubase 5). Vdat however no longer becomes a 'slave' to VRCS (on DSP 2). That appears to be a backward step.
I know this all looks bad, but in general I am really enjoying SCOPE on Win 7 64 Bit and it is the way of the future. Its worth the transition!
I have had a couple of BSOD:
- The STS samplers do it for me. It appears to be something to do with it memory calcs I think.
- I have also had another BSOD, but not sure what caused that one. There was no STS's in the project at the time.
I had a strange effect on one project where I had a couple of delay plugs in inserts in a Spacef Mod Mixer. When I reloaded the project (and before I had opened any sequencer) I got this pulsating delay noise from the channels with the delays in them. Removed the delay plugs and it went away. These are the standard Sonic Core Delay plugs.
VDAT still cannot sync via MTC, although I am able to sync via ASIO 2 into Samplitude 11 (Not into Cubase 5). Vdat however no longer becomes a 'slave' to VRCS (on DSP 2). That appears to be a backward step.
I know this all looks bad, but in general I am really enjoying SCOPE on Win 7 64 Bit and it is the way of the future. Its worth the transition!
Re: New Scope 5.1 RC2 in the FTP
I installed it a few days ago and so far it seems all good (it's on another drive that i can boot when i want, so it doesn't touch anything of the current xp/32bit install).
The thing I noticed immediately is that the asio drivers on the 64bits version work much better for me than the same on scope 5 32 bit (you must know that I use a board of 1999 and that the more recent ones (Generation II from year 2000-2001 i think) have improved the pci bandwith). . In 32 bits i have pci overflows in loops, and on 64 bits, i have and overflow on launching and quiting cubase , that's all (so i resync and it is done, even without quiting cubase or anything).
It would be perfect if there was a 16bit asio driver like in scope 4, but at the same time, the 2 occurences of pci overflows is not a problem at all for working, I managed to run some of my important projects in cubase and with modular mixer and all seems fine to me so far. It wasn't possible for me to do anything on scope5-32bits because i could not resync after an overload. I noticed in the past that better ram gave me better behavior on the pci side of things, so may be the 64bits gives even better handling of those pci stuff (or may be uit is not the same module, i am not too sure which is the scope 5 version i am using on the 32bit install, it's a pretty young one).
I managed to load all my recent and important projects, which are made of a 16 channels/5 aux modular mixer + vinco, BB2 AUx Delay, Masterverb, a couple of experimental filters... no problem at all so far.
I am going to save a few euros on ram too, the amount of ram cubase can now access is far from enough..I can load more than twice the number of plugin, and it is CPU that is overloaded before the ram... . if i add another 4gb of ram, then it would never be used because cpu would not follow and would play only crackles and audio glitches but it is not yet mainstream music... the additional ram would be welcome with a much more powerful cpu... but now it is useless. I would need something that is more than twice the power of the current dualcore... and that's expensive (even some Quad Core are more expensive than i7...)....
i would say, go for it... install on a drive that you can boot when you need and that will become your main boot once the w7x64 setup is complete (it takes times to reinstall things, find drivers etc).... and don't buy ram before your are sure you will need it and that your cpu will follow the extra plugins without audio glitches (i guess, load the ram at 90-95% and if you hear something else than "crrrrrrrrrrrrrrrrrrrrrrrrrr" then may be your cpu is enough to deal with a lot more ram).
The thing I noticed immediately is that the asio drivers on the 64bits version work much better for me than the same on scope 5 32 bit (you must know that I use a board of 1999 and that the more recent ones (Generation II from year 2000-2001 i think) have improved the pci bandwith). . In 32 bits i have pci overflows in loops, and on 64 bits, i have and overflow on launching and quiting cubase , that's all (so i resync and it is done, even without quiting cubase or anything).
It would be perfect if there was a 16bit asio driver like in scope 4, but at the same time, the 2 occurences of pci overflows is not a problem at all for working, I managed to run some of my important projects in cubase and with modular mixer and all seems fine to me so far. It wasn't possible for me to do anything on scope5-32bits because i could not resync after an overload. I noticed in the past that better ram gave me better behavior on the pci side of things, so may be the 64bits gives even better handling of those pci stuff (or may be uit is not the same module, i am not too sure which is the scope 5 version i am using on the 32bit install, it's a pretty young one).
I managed to load all my recent and important projects, which are made of a 16 channels/5 aux modular mixer + vinco, BB2 AUx Delay, Masterverb, a couple of experimental filters... no problem at all so far.
I am going to save a few euros on ram too, the amount of ram cubase can now access is far from enough..I can load more than twice the number of plugin, and it is CPU that is overloaded before the ram... . if i add another 4gb of ram, then it would never be used because cpu would not follow and would play only crackles and audio glitches but it is not yet mainstream music... the additional ram would be welcome with a much more powerful cpu... but now it is useless. I would need something that is more than twice the power of the current dualcore... and that's expensive (even some Quad Core are more expensive than i7...)....
i would say, go for it... install on a drive that you can boot when you need and that will become your main boot once the w7x64 setup is complete (it takes times to reinstall things, find drivers etc).... and don't buy ram before your are sure you will need it and that your cpu will follow the extra plugins without audio glitches (i guess, load the ram at 90-95% and if you hear something else than "crrrrrrrrrrrrrrrrrrrrrrrrrr" then may be your cpu is enough to deal with a lot more ram).
-
lagoausente
- Posts: 552
- Joined: Wed Feb 09, 2005 4:00 pm
- Location: Spain
Re: New Scope 5.1 RC2 in the FTP
STS sampler don´t workr ok on 5.1. I spent 198 eur on this update to get nices BSOD. Incredible.