GSIF 2.0 in 3538h doesn't work!

meroveus · Apr 1, 2005, 01:13 AM

(I didn't post this in the 3538c thread since I'm using 3538h)

The old GSIF 1.7 drivers in 3537 work fine with GigaStudio 3, but the new GSIF 2 drivers in 3538h do not.

When I start GS, I get the error message "Gigastudio did not startup properly, do you want to start in diagnostic mode?"
Whether I press yes or no, the result is the same, GS will start up but i get no sound.

Whether I use a midi keyboard or the software keyboard in GS, the cpu indicators do not register at all when pressing keys, nor is there any sound output.

I can arm a track for recording but resulting wav file is completely empty, although right size.

Interestingly if I go to edit the instrument file while in GS, I get this message "System is running properly!"
I can then audition the samples of the instrument, but still any keys which are pressed do not sound.

If I try to shutdown XP, I get a bluescreen:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
which points out the offending module as
nstation.sys which is a part of GS3.

In summary, it seems that the MIDI part of the GSIF2.0 is not working, although I haven't tested the audio in, and can't yet test the audio out.

All the other aspects of 3538h such as ASIO, WDM, and MIDI in and out work fine.

(Thanks Eugene!

)

EDIT:
(postscript) The problem was solved by reinstalling Gigastudio.
GSIF 2 audio out now works.

Haven't yet had a chance to test the GSIF audio in and MIDI.

meroveus · Apr 1, 2005, 09:44 PM

And I forgot: my system is a dual PIII 850 with an Audigy1 and XP SP2.

lucioblues · Apr 2, 2005, 12:05 AM

Gigastudio 3 is a buggy stuff. I'm using it on 3538h, as a sampler for Sonar, and it's working. But the setup was a nightmare. And sometimes it hangs everything. Using Rewire with it is like to be in hell.

Maybe, in your case like mine, it's not kx's fault.

meroveus · Apr 2, 2005, 11:58 AM

Thanks for letting me know, lucioblues. I have hope now that someone has GSIF 2 working.

Yeah it can be buggy. Once every two weeks or so, using the 3537 drivers, GS3 would hang at the splash screen and I would have to reboot. But once running, it was stable. That is the extent of my problems.
Some people _never_ experience problems with GS.

Anyway, since you have got it working, maybe I should reinstall GS3.

But I can't help but think the interaction between dual cpus and the kx drivers may be the problem.

**Eugene Gavrilov** · May 18, 2005, 02:04 PM

please note that SMP/HT machines are NOT officially supported by Tascam/Giga
for me, Giga3 works fine provided I re-assign CPUs ('processor affinity' feature)

E.

meroveus · May 21, 2005, 12:19 PM

Nice to know that you use GigaSudio, Eugene,

It used to be the case that SMP was not supported.
But now...

"More improvements with Hyper Threading compatibility have been made,
This includes dual processor machines.
Note: GigaStudio is coded to provide performance benefits on Hyper Threading enabled PCs in the following ways:
. Projects with heavy VST usage will benefit.
. HT may provide more polyphony than nonHT systems."
(taken from the GS3 3.04 change history.)

What caused GS3 to protest, was installing the 3538 drivers over the top of the 3537 drivers.
GS3 didn't like having the rug pulled from under it, when it saw that GSIF1.7 had now changed to GSIF2.0! Problem was solved simply by reinstalling GigaStudio.

The outputs and MIDI work fine but sill haven't tested the inputs.
Running beautifully stable with buffers set to 32 samples.

You are to be congratulated on making such fine drivers.

cheers

Damian

Apr 1, 2005, 01:13 AM	#1
meroveus DriverHeaven Junior Member Join Date: Jul 2002 Posts: 63 Rep Power: 0	GSIF 2.0 in 3538h DOES work! (I didn't post this in the 3538c thread since I'm using 3538h) The old GSIF 1.7 drivers in 3537 work fine with GigaStudio 3, but the new GSIF 2 drivers in 3538h do not. When I start GS, I get the error message "Gigastudio did not startup properly, do you want to start in diagnostic mode?" Whether I press yes or no, the result is the same, GS will start up but i get no sound. Whether I use a midi keyboard or the software keyboard in GS, the cpu indicators do not register at all when pressing keys, nor is there any sound output. I can arm a track for recording but resulting wav file is completely empty, although right size. Interestingly if I go to edit the instrument file while in GS, I get this message "System is running properly!" I can then audition the samples of the instrument, but still any keys which are pressed do not sound. If I try to shutdown XP, I get a bluescreen: DRIVER_IRQL_NOT_LESS_OR_EQUAL which points out the offending module as nstation.sys which is a part of GS3. In summary, it seems that the MIDI part of the GSIF2.0 is not working, although I haven't tested the audio in, and can't yet test the audio out. All the other aspects of 3538h such as ASIO, WDM, and MIDI in and out work fine. (Thanks Eugene! ) EDIT: (postscript) The problem was solved by reinstalling Gigastudio. GSIF 2 audio out now works. Haven't yet had a chance to test the GSIF audio in and MIDI. Last edited by meroveus; Apr 12, 2005 at 01:52 PM.

Apr 2, 2005, 12:05 AM	#3
lucioblues DriverHeaven Junior Member Join Date: Jun 2003 Posts: 81 Rep Power: 0	Gigastudio 3 is a buggy stuff. I'm using it on 3538h, as a sampler for Sonar, and it's working. But the setup was a nightmare. And sometimes it hangs everything. Using Rewire with it is like to be in hell. Maybe, in your case like mine, it's not kx's fault. __________________

Apr 1, 2005, 09:44 PM	#2
meroveus DriverHeaven Junior Member Join Date: Jul 2002 Posts: 63 Rep Power: 0	And I forgot: my system is a dual PIII 850 with an Audigy1 and XP SP2.

Apr 2, 2005, 11:58 AM	#4
meroveus DriverHeaven Junior Member Join Date: Jul 2002 Posts: 63 Rep Power: 0	Thanks for letting me know, lucioblues. I have hope now that someone has GSIF 2 working. Yeah it can be buggy. Once every two weeks or so, using the 3537 drivers, GS3 would hang at the splash screen and I would have to reboot. But once running, it was stable. That is the extent of my problems. Some people _never_ experience problems with GS. Anyway, since you have got it working, maybe I should reinstall GS3. But I can't help but think the interaction between dual cpus and the kx drivers may be the problem.

May 18, 2005, 02:04 PM	#5
Eugene Gavrilov kX Project Lead Programmer and Coordinator Join Date: Dec 2002 Posts: 3,040 Rep Power: 60	please note that SMP/HT machines are NOT officially supported by Tascam/Giga for me, Giga3 works fine provided I re-assign CPUs ('processor affinity' feature) E.

May 21, 2005, 12:19 PM	#6
meroveus DriverHeaven Junior Member Join Date: Jul 2002 Posts: 63 Rep Power: 0	Nice to know that you use GigaSudio, Eugene, It used to be the case that SMP was not supported. But now... "More improvements with Hyper Threading compatibility have been made, This includes dual processor machines. Note: GigaStudio is coded to provide performance benefits on Hyper Threading enabled PCs in the following ways: . Projects with heavy VST usage will benefit. . HT may provide more polyphony than nonHT systems." (taken from the GS3 3.04 change history.) What caused GS3 to protest, was installing the 3538 drivers over the top of the 3537 drivers. GS3 didn't like having the rug pulled from under it, when it saw that GSIF1.7 had now changed to GSIF2.0! Problem was solved simply by reinstalling GigaStudio. The outputs and MIDI work fine but sill haven't tested the inputs. Running beautifully stable with buffers set to 32 samples. You are to be congratulated on making such fine drivers. cheers Damian