I am saddened by a fellow Scope users troubles.
If I ever heard a mastering quality VST sequencer, I would buy another. Cubase 4,Sonar etc. are great for a scratch demo IMO, but the trouble they cause far outweighs their necessity in my rig.
I play live for a bulk of my income, and when I do record it's usually on a console using another DSP based application.
I find that when everything involved in a production is DSP based, w/ select hardware, i.e. sequencers, reverbs, and analog consoles, it's a smooth quality experience.
The fact that Scope / Gigastudio DAW's work w/ 100% stability live is a testament to it's usefullness.
Hope You Have Better Luck In The Future.
Frustrated with Scope - anybody feel the same?
-
CarvinGuitarFreak
- Posts: 130
- Joined: Wed Sep 20, 2006 4:00 pm
Hi midiman,
I can understand your frustration with Creamware, I had a mind numbing experience with midi. Cured by not using midi on scope and having an midiman.
I do agree with you that creamware is sometimes and inexplicably problematic compared with other audio cards but there are always work arounds because what scope offers is worth it.
I ended up building a system around scope (for music making) and dont use it for any other purpose... this seems to the best bet (I think)... one for audio and one for play? Its a good life
CGF
I can understand your frustration with Creamware, I had a mind numbing experience with midi. Cured by not using midi on scope and having an midiman.
I do agree with you that creamware is sometimes and inexplicably problematic compared with other audio cards but there are always work arounds because what scope offers is worth it.
I ended up building a system around scope (for music making) and dont use it for any other purpose... this seems to the best bet (I think)... one for audio and one for play? Its a good life
CGF
yes and to do this:garyb wrote:slow gui=resource problems. turn off the xp eyecandy and it should all run smoothly.
Go to the main menu->Run and type: msconfig
Then go to services and find "themes"
Uncheck it
Apply the changes and exit msconfig
I suggest to disable the menù effects also and setting the color depth to 16bit if the graphic power is limited
Welcome to the dawning of a new empire
Given the motherboard he's listing I suspect that he's got enough graphics power, although disabling ugly themes isn't a bad idea. One might wonder if he is running an ATI/Nvidia gaming card and could benefit from Doubledawg. I suspect spacef was on the right path when he listed the latency of manipulating a control being somewhat related to the fact that the UI not only has to do some calculations in cpu, but also in communicating to the card. However anyone that ran Scope on win98 does know that the UI is a bit slower on Xp. Not so much to be unusable though with today's cpu's especially so if it is EXTREMELY sluggish something else is wrong.
In regards to the keyfile prompts, are all of you running 4.5? I'm still on Scope4 and have done dozens of installs of Scope/Xp over the years and have never ever had this issue. A bit of digging around in cset.ini and/or Scope's saved keyfile (Scope.rgy) might reveal the cause of this but it till take collaborative effort to track down.
To be able to change projects in Scope while cubase is running you simply need to go into Cubase's driver panel and enable 'release ASIO driver in background' so that when Scope is the 'foreground' Cubase lets go of the asio driver. Since this is something a Scope user will likely NOT want enabled while working simply going into Cubase's drivers and choosing a non-scope driver for a short period will have the same net effect. Which leads to the next point...
Scope does seem to have unresolvable issues with the WAV driver on certain system configurations (see the suggestion to do tech research and build a scope specific box). To have non-scope drivers available and/or audio that works for 'gaming' I've used onboard sound (as others here do) and Sblives over the years. Sblives are my preferred method because they're extremely cheap for the 4-channel or 5-channel versions ($10-$20), quite hackable on the hardware level (you can tap into the board and integrate Spdif or ADAT yourself) and the kx drivers give a tremendous level of control over the routing within the card. No EAX/2 or other current 3d-audio support I can live with, but if you are primarly a gamer and casual 'myspace/youtube' etc user you might decide to use the stock windows drivers. I cannot stand the creative labs drivers you download from their site, waaaay too much crap included.
In regards to the keyfile prompts, are all of you running 4.5? I'm still on Scope4 and have done dozens of installs of Scope/Xp over the years and have never ever had this issue. A bit of digging around in cset.ini and/or Scope's saved keyfile (Scope.rgy) might reveal the cause of this but it till take collaborative effort to track down.
To be able to change projects in Scope while cubase is running you simply need to go into Cubase's driver panel and enable 'release ASIO driver in background' so that when Scope is the 'foreground' Cubase lets go of the asio driver. Since this is something a Scope user will likely NOT want enabled while working simply going into Cubase's drivers and choosing a non-scope driver for a short period will have the same net effect. Which leads to the next point...
Scope does seem to have unresolvable issues with the WAV driver on certain system configurations (see the suggestion to do tech research and build a scope specific box). To have non-scope drivers available and/or audio that works for 'gaming' I've used onboard sound (as others here do) and Sblives over the years. Sblives are my preferred method because they're extremely cheap for the 4-channel or 5-channel versions ($10-$20), quite hackable on the hardware level (you can tap into the board and integrate Spdif or ADAT yourself) and the kx drivers give a tremendous level of control over the routing within the card. No EAX/2 or other current 3d-audio support I can live with, but if you are primarly a gamer and casual 'myspace/youtube' etc user you might decide to use the stock windows drivers. I cannot stand the creative labs drivers you download from their site, waaaay too much crap included.
-
Neil B
". You can't change project (or latencty) unless you close Cubase first. This is so frustrating. I often want to load a different project because I already have the wiring all set up for a certain sound that I want to record into Cubase - but I can't !! "
I don't know which version of Cubase you have, and others have already replied, but I seem to remember that all you have to do is to turn audio off, load a new project and then turn it back on again (5.1/32).
I don't know which version of Cubase you have, and others have already replied, but I seem to remember that all you have to do is to turn audio off, load a new project and then turn it back on again (5.1/32).
SX3Neil B wrote:". You can't change project (or latencty) unless you close Cubase first. This is so frustrating. I often want to load a different project because I already have the wiring all set up for a certain sound that I want to record into Cubase - but I can't !! "
I don't know which version of Cubase you have, and others have already replied, but I seem to remember that all you have to do is to turn audio off, load a new project and then turn it back on again (5.1/32).
-
irrelevance
I have a dual boot operating system so as to get more from my pc. One stripped and streamlined XP boot strictly for music and the other more bloated XP affair for games, internet etc. Works well for me. Very easy although a bit more time consuming to set up and back up. But once it's done it's plane sailing. 
Works perfectly! plus no need to check "release ASIO driver".valis wrote: To be able to change projects in Scope while cubase is running you simply need to go into Cubase's driver panel and enable 'release ASIO driver in background' so that when Scope is the 'foreground' Cubase lets go of the asio driver. Since this is something a Scope user will likely NOT want enabled while working simply going into Cubase's drivers and choosing a non-scope driver for a short period will have the same net effect. Which leads to the next point...
.
Now the only thing that needs improvment is the new proj. loading time...
Of course you can change wiring with everything on. That's not what I meant.garyb wrote:there's no need to load another project just to change wiring. the only reason to close cubase is because the sequencer midi or asio modules are removed or changed in size. you can load effects, synths, mixers or change patching to your heart's content with cubase open....i do it all the time....
I have various scope projects with identical ASIO and MIDI interfaces but different instruments chanining and fx and so on. I like to think of this as a "mega" preset, or a library of instruments, all the set up with their compressors, eqs, side-chains, fx's and so on. I wouldn't load a new scope project just to disconnect a single wire...
no offense, but wow, that's lazy....
Scope IS a studio full of hardware. try changing all that with rack gear. the fact that you can have those setups is a miracle. the reason you can't relode the asio modules with cubase open is because of the way asio works. for it to be stable and low latency, the app and driver must be in communication. the asio poerts ARE the HARDWARE jacks on a virtual multitrack recording machine(cubase). removing the asio modules with the program open is the same as making the jacks disappear and reappear on an actual hardware recorder. this would be a destruction of physical reality, a paradox. the software feels the same.
Scope IS a studio full of hardware. try changing all that with rack gear. the fact that you can have those setups is a miracle. the reason you can't relode the asio modules with cubase open is because of the way asio works. for it to be stable and low latency, the app and driver must be in communication. the asio poerts ARE the HARDWARE jacks on a virtual multitrack recording machine(cubase). removing the asio modules with the program open is the same as making the jacks disappear and reappear on an actual hardware recorder. this would be a destruction of physical reality, a paradox. the software feels the same.
agreedgaryb wrote:no offense, but wow, that's lazy....
Scope IS a studio full of hardware. try changing all that with rack gear. the fact that you can have those setups is a miracle. the reason you can't relode the asio modules with cubase open is because of the way asio works. for it to be stable and low latency, the app and driver must be in communication. the asio poerts ARE the HARDWARE jacks on a virtual multitrack recording machine(cubase). removing the asio modules with the program open is the same as making the jacks disappear and reappear on an actual hardware recorder. this would be a destruction of physical reality, a paradox. the software feels the same.
thats how it is.
in cubase:
just load your new scope project, go to cubase vst setup. and reselect ASIO Scope driver and finally after a short delay of ~ 3 seconds you have your connection backed up.
its really not difficult and and this is no fault.
do your games still work while you load a new project? (just joking ....
)concerning the gaming statement:
thats the same as if you would buy a f1-car with 800ps and wonder why there is no baby seat avaiable as accessoire.
what I mean: this card was never build with gaming in mind. If it works its fine, if not use a 20€ soundcard or onboard sound. no big deal.
I see your point. It's still nice though to be able to make all virtual jacks disappear and reappeargaryb wrote:no offense, but wow, that's lazy....
Scope IS a studio full of hardware. try changing all that with rack gear. the fact that you can have those setups is a miracle. the reason you can't relode the asio modules with cubase open is because of the way asio works. for it to be stable and low latency, the app and driver must be in communication. the asio poerts ARE the HARDWARE jacks on a virtual multitrack recording machine(cubase). removing the asio modules with the program open is the same as making the jacks disappear and reappear on an actual hardware recorder. this would be a destruction of physical reality, a paradox. the software feels the same.
I can live with the gaming issue, I realize it's a petty thinghifiboom wrote:agreedgaryb wrote:no offense, but wow, that's lazy....
Scope IS a studio full of hardware. try changing all that with rack gear. the fact that you can have those setups is a miracle. the reason you can't relode the asio modules with cubase open is because of the way asio works. for it to be stable and low latency, the app and driver must be in communication. the asio poerts ARE the HARDWARE jacks on a virtual multitrack recording machine(cubase). removing the asio modules with the program open is the same as making the jacks disappear and reappear on an actual hardware recorder. this would be a destruction of physical reality, a paradox. the software feels the same.
thats how it is.
in cubase:
just load your new scope project, go to cubase vst setup. and reselect ASIO Scope driver and finally after a short delay of ~ 3 seconds you have your connection backed up.
its really not difficult and and this is no fault.
do your games still work while you load a new project? (just joking ....
concerning the gaming statement:
thats the same as if you would buy a f1-car with 800ps and wonder why there is no baby seat avaiable as accessoire.
what I mean: this card was never build with gaming in mind. If it works its fine, if not use a 20€ soundcard or onboard sound. no big deal.
no doubt, it'd be nice if it followed your exact thoughts. not just any thoughs, but the one's you really meant it to follow......midiman wrote:I see your point. It's still nice though to be able to make all virtual jacks disappear and reappeargaryb wrote:no offense, but wow, that's lazy....
Scope IS a studio full of hardware. try changing all that with rack gear. the fact that you can have those setups is a miracle. the reason you can't relode the asio modules with cubase open is because of the way asio works. for it to be stable and low latency, the app and driver must be in communication. the asio poerts ARE the HARDWARE jacks on a virtual multitrack recording machine(cubase). removing the asio modules with the program open is the same as making the jacks disappear and reappear on an actual hardware recorder. this would be a destruction of physical reality, a paradox. the software feels the same.
really though, sorry if i came off as arrogant or snobbish(i might be a little), i understand the desire to have it like you want it.