GigaStudio Solo with Pulsar 1 card - Error

Tkay · Post by **Tkay** » Fri Feb 23, 2007 10:29 pm

Hi. When I try to load GigaStudio Solo, I get a scope error (using Scope 4 Software).

"Scope Driver Ioctl (1036) returned error code -99"

The card is working fine by itself - just installed. But when I try and load Gigastudio, I receive the message.

Any ideas? I've looked to see what the driver is but I can't seem to find it.

Thanks, Thomas

ChrisWerner · Post by **ChrisWerner** » Fri Feb 23, 2007 11:13 pm

Hi and welcome Thomas

I can´t help you out on this problem, ´cause I don´t use Giga, but here are some that have no problems using Giga and Scope. I am sure they will come up with something.

Tkay · Post by **Tkay** » Fri Feb 23, 2007 11:16 pm

Thanks Chris. It seems like it might be a driver problem. But I don't see on the Creamware site where I can download the newest drivers.

Thanks,

Thomas

Post by **garyb** » Fri Feb 23, 2007 11:26 pm

you have a gsif dest module loaded in the routing window before opening giga? there's no new driver needed.

Tkay · Post by **Tkay** » Sat Feb 24, 2007 6:07 am

I tried to Google the error but found nothing concerning scope/pulsar.

Post by **garyb** » Sat Feb 24, 2007 9:59 am

the error code indicates an error in user protocol.............

if you describe the steps from turning on your computer to using giga, i'm sure we can find out where.

Tkay · Post by **Tkay** » Sat Feb 24, 2007 6:21 pm

Your response reminded me that perhaps I should have Pulsar up and running with a Giga Driver installed in the mixer. So I did that. When I chose it, it automatically routed it to the mixer.

So now I'm back to installing GigaStudio. I make it throught the install and reboot the computer. It actually takes me to the troubleshooting prompt saying that the last time I used GigaStudio, it was not shut off correctly. I ran a test and saw that it saw the Pulsar.

Long story short, I register with Gigastudio and it pops up the same message again. As I'm trying to shut out of it, it gives me another message.

"Cannot start software because board(s) or driver not properly installed. Please check installation."

I have already been playing with some synths in Pulsar. It seems fine. Any ideas?

Thanks,

Thomas

Post by **garyb** » Sat Feb 24, 2007 8:21 pm

giga is very particular and the warning messages can give you the wrong impression. you must have everything right once and the restart and the error messages will be gone. it definitely works, however. scope must be up, the giga dest must be present before opening giga, then you should be able to set up prefs in giga. oh, one other thing...you must have at least one sequencer midi dest module in you project before opening giga so that giga will be able to receive midi.

Tkay · Post by **Tkay** » Sun Feb 25, 2007 10:03 am

"giga dest must be present before opening giga"

Do you mean the GSIF source? That is going into the Mixer.

Pulsar Midi A Source > Midi In on the STM 1632.
Nothing is Midi Out on the STM 1632.

Thomas

Post by **garyb** » Sun Feb 25, 2007 1:49 pm

excuse me, giga source....

the only reason to have midi connected to the mixer is to automate mixer knobs, sliders and buttons. as i said, you need a sequencer midi dest(at least one) to send midi to giga.

dawman · Post by **dawman** » Mon Feb 26, 2007 10:30 am

Brotha' Man Tkay,
Let me know how it goes w/ your set up. I have been using GS a long time w/ Creamware. 2 x SFP / Giga DAW's. The MIDI Sequencer Dest. Module is crucial. The GSIF module also has a control surface which allows more channels into SFP also. I'm sure you will enjoy the strength of these two awesome applications. Once they are set up, and the paths / destinations are learned, it will work w/o crashing or problems 4 a long time.

Tkay · Post by **Tkay** » Mon Feb 26, 2007 8:10 pm

" giga dest must be present before opening giga"

I have a Giga Source going to the board, which I can only imagine are my Giga Outputs. I do not, however, see a Giga Destination as an option.

"you need a sequencer midi dest(at least one) to send midi to giga."

Again, I don't see a Giga In. Please excuse my ignorance. I've actually had an earlier system up and working so I'm really perplexed. But then again, I'm not as much of a tech as I'd like to be.

"The MIDI Sequencer Dest. Module is crucial."

What goes into the Midi Sequenser Dest Module??? Again, I'm sure I come off as the ignorant I am. Thanks for everyone's patience.

Thomas

Post by **garyb** » Mon Feb 26, 2007 8:55 pm

as i already admitted, i lied.

you need a gsif source module and a sequencer midi dest. the sequencer midi dest is the midi input for giga(gigastudio is the destination of the midi). each sequncer midi dest module can carry 16 midi channels. you may use as many as needed. think of the connections on the modules as the hardware connectors of the hardware(software) sampler(giga). again, for giga to know how many ports to configure, the modules must be present in your project before opening gigastudio.

Post by **hubird** » Mon Feb 26, 2007 9:02 pm

To be clear:
Sequencer Midi Destination module is for sending Midi to your sequencer.

The midi should come from your Midi Source module (presenting your hardware Scope Midi input plug).

Play (send midi) from your Midi keyboard via SFP to your VSTis (f.e. Giga).

If you need to route some Midi information from your sequencer to SFP, to play a SFP synth or controll a parameter of a plugin etc., , load a Sequencer Midi source module in SFP.

By choosing the right track/midi channel in your sequencer, you can determin what synth should react to your midi playing

Of course you can also connect your Midi Source module directly to your SFP synth, but I'd prefer the route via the sequencer, as it's more flexable and clean.
You then add latency tho.

But you know all this already for sure

edit: Gary was availabe yet

Tkay · Post by **Tkay** » Mon Feb 26, 2007 10:08 pm

Okay - here is the latest setup (that didn't work)

Midi A Source > Sequencer Midi Dest 1

I tested that I have sound via this source by playing a Pulsar synth.

When I try and then pull up GigaSampler, it:

1) Gives me an option to run dianostics mode because the system was not shut down properly.

2) Gives me this error:

"The following plugin, 'C:\Installers\DirectX\DSETUP.dll" crashed the system. Giga Studio will now disable the plugin."

I click ok and keep moving until it gives me the same errors again.

#*$%#$%

Thomas

Post by **garyb** » Mon Feb 26, 2007 10:45 pm

as i said, giga is very cranky that everything is right. the dx warning has nothing to do with scope.

diagnostic mode is not important. after avoiding that, go to settings and be sure that the scope ports are selected. restart giga. it should work. i know it's frustrating right now, but persevere, it does work and you will understand it if you don't give up. reading the manuals might help(the giga section in the scope manual and the giga quickstart).

dawman · Post by **dawman** » Tue Feb 27, 2007 2:21 am

Try finding about your internal settings in Giga @ www.learngigastudio.com
Remember, If Giga is in standalone mode, or rewired, that makes a big difference also.
If you are using the Solo version, once you get settled in, upgrade to Orchestra just to get GigaPulse , as it is a great addition to your arsenal.

Tkay · Post by **Tkay** » Mon Aug 20, 2007 4:02 pm

I never got it working. Too much going on. Blah blah. That said, I don't want to buy another card when I really love Pulsar and what it brings.

So I went - finally - into the manual and read that "this module is not yet supported under Windows 2000/XP." (In the I/O & Drivers PDF).

Is GigaStudio Solo Supported in XP? I hope so.

Thanks, Thomas

PlanetZ forums - scopeusers.com

GigaStudio Solo with Pulsar 1 card - Error

GigaStudio Solo with Pulsar 1 card - Error

Pathetic, but....