Pulsar II, Gigastudio, emagic MT-4 problems

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

Moderators: valis, garyb

Post Reply
jweisbin
Posts: 7
Joined: Wed Sep 10, 2003 4:00 pm
Location: New York City
Contact:

Post by jweisbin »

I was trying to help someone who has a Pentium 4 2.5ghz (I don't know the mobo used - Carillon is the company that sells these boxes), Win XP home, Pulsar II card (driver 3.1b), Emagic MT-4 midi interface, and Gigastudio 160 2.5300 (I upgraded him to 2.5400 then back down to 2.5300 after I couldn't fix it). I've never used Creamware stuff before, and, though I have lots of experience with many other cards, I found this to be the most complex and confusing setup program I've ever
encountered, although I guess it does alot more than the other cards do. After looking at the manual for 10 minutes, I still couldn't figure out how to connect the midi input to be useable by Gigastudio - the cursor would not change to a connection symbol the way the manual said it should. I gave up on that. Unfortunately, although I have the manual, I don't have access to his machine until I need to fix it.

He had been having problems with his MT-4 (usb midi 4-port - piece of crap, IMHO) occasionally not responding, causing no midi to get into Gigastudio, but also, for some reason, causing Giga to not be able to send audio, even when clicking the graphic keyboard, no sound will go out. Checking settings in Giga, all outputs are greyed out in this case. His fix has been to re-install the MT-4 drivers, sometimes it
takes 2-3 times. This time however, I had tried to switch to the Creamware midi in, which I couldn't, then back to the MT-4's, no amount of re-installing the MT-4 drivers would un-grey the audio outputs in Giga. I left, 15 minutes later he called me
and told me it suddenly was magically working. Could it just be that it takes a loooong time for the Creamware card to get recognized? Any help would be most appreciated.
jweisbin
Posts: 7
Joined: Wed Sep 10, 2003 4:00 pm
Location: New York City
Contact:

Post by jweisbin »

I'm replying to my own post because I've had a few replies from other sources, and wanted to get some feedback here. the concensus seems to be that the Pulasr's built-in midi, even when working, is not implemented well, and can cause problems. Also, The midi implementation in general is causing similar problems with other users, even those using other midi interfaces (spercifically the midiman types). I'm wondering if upgrading to the Pulsar version 3.1c drivers might help (I don't want to do this unless I have to, because this guy uses his machine intensively and can't afford to be down), and if anyone has any thoughts on this, please let me know.
Post Reply