Sounddiver problem!

[Psypher]

Hi....
Anybody had problems with the Sounddiver?

I am using KX Project drivers and my Sounddiver don?t see 2 of the channels (like Midi out 1 and MIDI out 2) and I wanna use one of these!
I can see them in other sequencers, so I know they are there, but why does it turn them off or don?t see them!?

[Juho L]

Originally Posted by Psypher

Anybody had problems with the Sounddiver?

*spontaneous laughter*

I would rearrange that sentence like this: "Anybody hadn't any problems with SoundDriver?". I'm still bitter for that bloody program.

[Psypher]

OK...Didn?t know that it was so buggy! Thought Emagic made nice program!?

But no one have ever heard about disappearing MIDI ports in Sounddiver!? Or maybe something about those KX drivers, but don?t think the problem occur because of those...?

[Juho L]

Originally Posted by Psypher

OK...Didn?t know that it was so buggy! Thought Emagic made nice program!?

The usual problem is that the SoundDriver doesn't recognise your Virus at all or identifies your Virus faulty. I'm not sure but there might be an update for the SoundDriver on Access' site.

[tk]

Originally Posted by Juho L

The usual problem is that the SoundDriver doesn't recognise your Virus at all or identifies your Virus faulty. I'm not sure but there might be an update for the SoundDriver on Access' site.

If sounddiver fails to recognize a virus, usually the midi interface is to blame. There are a lot of interfaces that work perfectly, some that just fail to do anything (I won't list names here).

When you update your Virus OS, you should also update your Sounddiver Module. Updates are provided at http://www.access-music.de/?go=sdupdates.

btw:
I don't know any program called Sounddriver (except maybe drivers of your soundcard), I just know SoundDiver (like DIVING in to sounds, not Driving a car). Ususal mistake.

-tk

[saba]

As far as I know, the kX drivers aren't very suitable for audio production. Perhaps their MIDI interfacing is to blame.
________
PRILOSEC SETTLEMENT INFORMATION

[Juho L]

Originally Posted by tk

If sounddiver fails to recognize a virus, usually the midi interface is to blame. There are a lot of interfaces that work perfectly, some that just fail to do anything (I won't list names here).

Hmm... Just before that software did its nasy deeds to my user bank it had some trouble in recognising my Virus and there were some other weird stuff. Probably it was just my computer that didn't want to co-operate and now I'm a bitter old man... right.

btw:
I don't know any program called Sounddriver (except maybe drivers of your soundcard), I just know SoundDiver (like DIVING in to sounds, not Driving a car). Ususal mistake.

Hoho. Strange. I've always read it as SoundDriver. Well Driver or Diver I'd still rather get a plague than let that software touch my patches ever again.

[Caelum 7]

That program freaking sucks, I always get hangups that force me to hard reboot my damn computer. I've been using Midiquest for quite some time, and have never had a problem. My Virus is a KB, so I don't know if they have a driver for the C model, though.

[Ash]

It recognises my indigo 2 fine. But when I request banks it always gets stuck on a patch like Bank B, patch 56, and comes up with an error saying my Indigo isnt responding.

[draft_730]

i have exxactly thr same prob with my indigo II, it starts loading the first few patches .... and suddenly gives the no response masage