Sounddiver not recognising my C

[oddbods finger]

Hi,
I've just purchased a C desktop after selling my troublesome B.
Hurrah!!...very pleased indeed.
Problem is though Sounddiver won't recognise my new C.
It use to work OK with my B.

I uninstalled the old copy Sounddiver from my PC before re-loading it from the included CD.
I also tried the 'midi loop' type test but it failed!

My Midi connections seem to be OK.
I can record and send midi from a soft sequencer and I tested midi transmission with Midiox.

Any pointers?
Anyone else suffered this?

Cheers

[marc]

Hi,
I've just purchased a C desktop after selling my troublesome B.
Hurrah!!...very pleased indeed.
Problem is though Sounddiver won't recognise my new C.
It use to work OK with my B.

I uninstalled the old copy Sounddiver from my PC before re-loading it from the included CD.
I also tried the 'midi loop' type test but it failed!

My Midi connections seem to be OK.
I can record and send midi from a soft sequencer and I tested midi transmission with Midiox.

Any pointers?
Anyone else suffered this?

Cheers

assuming the midi communication works i'd check the sysex ID and make sure that the port settings are OK. add the virus c manually and adjust the in/out ports.

let me know if it helps

marc

[oddbods finger]

Thanks for your reply,

Well the ID is set to 1 on my Virus and Sounddiver displays 1 as well.

The Midi Monitor in Sounddiver displays data when I turn the knobs.

The Sounddiver 'Loopback' test fails though.
I assume you connect my PC's Midi Out port to it's Midi In port for this.
Correct?

So I assume the problem is the PC or Sounddiver end of things not the Virus.

Not sure how to adjust the In/Out ports as you suggest........or rather what to adjust them to.

[tk]

Thanks for your reply,

Well the ID is set to 1 on my Virus and Sounddiver displays 1 as well.

The Midi Monitor in Sounddiver displays data when I turn the knobs.

The Sounddiver 'Loopback' test fails though.
I assume you connect my PC's Midi Out port to it's Midi In port for this.
Correct?.

yes. Loopback displays also a message to connect in and out via a MIDI cable.

So I assume the problem is the PC or Sounddiver end of things not the Virus.

Not sure how to adjust the In/Out ports as you suggest........or rather what to adjust them to.

Connect:
PC MIDI OUT -> Virus MIDI IN
Virus MIDI OUT -> PC MIDI IN

otherwise you will not gain anything from sounddiver, because it needs to communicate bidirectional with the virus.

scanning should also work then.

-tk

[oddbods finger]

Connect:
PC MIDI OUT -> Virus MIDI IN
Virus MIDI OUT -> PC MIDI IN

otherwise you will not gain anything from sounddiver, because it needs to communicate bidirectional with the virus.



Thanks, but ....I do realise this!!!:wink:

It doesn't work though.
After scanning it says it can't locate my Virus.
I have manually set it up for Virus C.
The ID appears to be OK


yes. Loopback displays also a message to connect in and out via a MIDI cable.

OK, but when I do this the and initiated the test, it fails.
It says something like "No Data Received"

Any other ideas?

[tk]

have you checked the device id in the virus?

you might try to change it from omni to 1 or vice versa.

-tk

[oddbods finger]

It is set to 1

[Mash-up]

i had the same problem, if i remember correctly i reinstalled my midi interface driver.

[amassaro]

I have the same problem. The access virus is not found automatically, however I am able to add it manually. The loopback test still fails though. I am using an M-audio 5-in/5-out midi hub (think its the motu lite?). I have the Virus out and in connected to the midiman in and out. I also notice I am only able to play patches in banks A and B through the sound diver program, everything else is greyed out. Has anyone else seen that?

[303lovesit]

Sound Diver sucks Ass... :twisted: