Gigastudio 3.12 plus Scope and Cubase SX clicks

An area for people to discuss Scope related problems, issues, etc.

Moderators: valis, garyb

Post Reply
Crickstone
Posts: 244
Joined: Mon Oct 25, 2004 4:00 pm
Location: Canada

Post by Crickstone »

Hi there,
Having problems with GS3 when Cubase is running, clicking noise with heavier velocities piano samples. When GS3 and Scope are running alone there doesn't seem to be a problem. Also when powercore firewire inserts are used with GS3 there is distortion but that may be for another forum. Is Cubase not set-up properly. Tried lower the output from Giga but it still happens...any suggestions?
User avatar
valis
Posts: 7680
Joined: Sun Sep 23, 2001 4:00 pm
Location: West Coast USA
Contact:

Post by valis »

You're using 24bit ASIO drivers with Cubase (SX?) and gsif 2 drivers with Giga? Single cpu, multi-core? Hyperthreading on or off? What ULLI?
Crickstone
Posts: 244
Joined: Mon Oct 25, 2004 4:00 pm
Location: Canada

Post by Crickstone »

I'm running AMD 64 with the regular GSIF drivers from Creamware which are I believe only version one. I've played with the ULLI but that doesn't seem to matter. I have three drives C for GS3 and Cubase and other programs etc. and two others for samples and audio. No problems when I run GS3 with just Scope but as soon as Cubase is in the picture there is kinda of a crack on harder played chords.. 24 bit ASIO pops up in Cubase when I reset..tried the Midi Volume in Cubase as well...
Crickstone
Posts: 244
Joined: Mon Oct 25, 2004 4:00 pm
Location: Canada

Post by Crickstone »

I just switched Cubase to the ASIO Multimedia driver and apart from the ridculous latency there was no clicks or electronic pops on matter how hard I hit the board or if I did squash chords....where do I go from here?
User avatar
garyb
Moderator
Posts: 23380
Joined: Sun Apr 15, 2001 4:00 pm
Location: ghetto by the sea

Post by garyb »

most computers are too slow to run cubase asio low latency and gs3, with ANY card. gs3 is a resource pig! tascam suggests giga to be run on it's own machine. you can try setting scope priority to "low" or "below normal" in the task manager.
Post Reply