i needed drivers updated on the sound blaster live card

Community forum for discussions completely unrelated to MediaMonkey.

Moderator: Gurus

helenharry
Posts: 1
Joined: Mon Jan 07, 2019 1:56 am

i needed drivers updated on the sound blaster live card

Post by helenharry » Mon Jan 07, 2019 2:01 am

okay i got the program slim drivers. it works it found drivers i needed that i could not find anyway else. with out going to each driver file and clicking update driver.

it also found some that were missing so i updated all them on this computer but still not fixing the display errors in mm 4 .

but the reason for this post is on the other computer it found i needed drivers updated on the sound blaster live card.
so i had the program get them and install them.

now the sound driver is called kX project? and has 1 through 7 devices listed in the sound card options?
and is asio? my usb sound driver also changed to an asio one? what the hockey sticks is going on here?

Peke
Posts: 11660
Joined: Tue Jun 10, 2003 7:21 pm
Location: Serbia
Contact:

Re: i needed drivers updated on the sound blaster live card

Post by Peke » Mon Jan 07, 2019 8:20 pm

Hi,
This would be very hard to tell without debugging your PC completely, but from your questions and your own answers I would say that you have serious compatibility issues, that unfortunately broke on MMW.

Keep us posted on results.
Best regards,
Pavle
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
Image
Image
How to add SCREENSHOTS to forum

pushpull
Posts: 229
Joined: Mon Aug 14, 2006 9:01 pm
Location: Formerly WNY, now Portlandia
Contact:

Re: i needed drivers updated on the sound blaster live card

Post by pushpull » Mon Jan 07, 2019 10:54 pm

helenharry wrote:
Mon Jan 07, 2019 2:01 am
so i had the program get them and install them.
now the sound driver is called kX project? and has 1 through 7 devices listed in the sound card options?
and is asio? my usb sound driver also changed to an asio one? what the hockey sticks is going on here?
I suspect that your driver fetching software went and retrieved this driver.

Here is a Github link that seems applicable as well.

Post Reply