Quick Sign In:  

Forum: General Discussion

Topic: Technical question (Att: Nor & Sky)

This topic is old and might contain outdated or incorrect information.

HoffmanPRO InfinityMember since 2006
Does anyone know if when you install the driver for a cord like the M Audio Uno for Midi, if this can conflict with other drivers on your lappy?

Nor/Sky, I think this may have been my big problem. I believe the driver from the UNO was screwing up my Firebox. I uninstalled the UNO (even though I threw the cord out after last weekend), and it seems better.

Is uninstalling enough to get rid of everything dealing with the UNO?

I'm just looking for tech opinion if that driver could have messed up my soundcard functioning.

thanks,

B
 

Posted Sun 28 Jan 07 @ 8:36 pm
sbangsPRO InfinityMember since 2004
drivers can conflict yes

midi channels can aslo be linked to your soundcard if you have ever noticed the slider for synthesiser this is used by the midi synthesiser

and when you have somthing like a midi keyboard it acts as a midi in channel and your sound card is an output on the channels

so its possible that it could have messed up these channels

just brain storming :)

my new keyboard came with a funked up driver which i dumped

i then used Nt midi yoke to send midi singals

might wana try that

http://www.virtualdj.com/addons/tools.html

its in my dm2 tool package dump all the other files and just use midi yoke :)


 

Posted Sun 28 Jan 07 @ 8:48 pm
HoffmanPRO InfinityMember since 2006
is this why my midi X-SESSIOn did not mess up my FIREBOX becuase it did not install drivers. the UNO did however.

hmmmm
 

Posted Sun 28 Jan 07 @ 8:53 pm
sbangsPRO InfinityMember since 2004
is it just a plug and play midi device?
 

Posted Sun 28 Jan 07 @ 8:57 pm
HoffmanPRO InfinityMember since 2006
yeah I guess the X-session was just that b/c I don't recall installing drivers.
 

Posted Sun 28 Jan 07 @ 9:19 pm
sbangsPRO InfinityMember since 2004
did it come with a install disk or any thing like that

might be usign a default windows driver when its not ment to ?
 

Posted Sun 28 Jan 07 @ 9:27 pm
cstollPRO InfinityMember since 2004
No, the X-Session is PnP, straight forward - your Firebox issue is something else. It could have been as simple as a power surge of some sort OR some of the other items mentioned in other posts like - connector going bad.

I wish I could give you some advice as to why you experienced the problem that you have, but I don't own a firebox.

cstoll
 

Posted Mon 29 Jan 07 @ 12:14 pm
hum... strange, Norway hasn't replied yet :pp
 

Posted Mon 29 Jan 07 @ 12:27 pm
Might he be out of e mails? Norway, where are you? :))
 

Posted Mon 29 Jan 07 @ 12:28 pm
sbangsPRO InfinityMember since 2004
hes been kidnapped=)
 

Posted Mon 29 Jan 07 @ 12:28 pm
Hoffman wrote :



Nor/Sky, I think this may have been my big problem. I believe the driver from the UNO was screwing up my Firebox. I uninstalled the UNO (even though I threw the cord out after last weekend), and it seems better.

Is uninstalling enough to get rid of everything dealing with the UNO?

B



Noone answers your questions better than yourself Hoffman ;) I think you are right on target here.. ;)
 

Posted Mon 29 Jan 07 @ 6:33 pm
Phenryll wrote :


Norway, where are you? :))




Still in Norway;) lol
 

Posted Mon 29 Jan 07 @ 6:34 pm
ouf, i am relieved :pp
 

Posted Mon 29 Jan 07 @ 7:47 pm
HoffmanPRO InfinityMember since 2006
Thanks Nor & others,

I feel that was it, even though I am not being overconfident. Some people have agreed that it is very possible the DRIVER for the M Audio UNO cable interferred with the driver for the Firebox; cauing a DJ's worst nightmare with a laptop/software.

I uninstalled the UNO = no problems since.

Even just talking to you guys helps so much even if you don;t know exactly the anseer. It gets the person w/the problem to think.

thanks !!!!!


Have a great week.

B
 

Posted Tue 30 Jan 07 @ 1:01 am


Hope all runs well ;) If not post back...

Drivers can interfear, specially if asigned to same port (2 midi drivers on same usb).
Usually it doesnt, but it can.

The fix is force Windows to see the right drivers.

But since you have it running good now, lets leave it there:)
 

Posted Tue 30 Jan 07 @ 1:13 am


(Old topics and forums are automatically closed)