KVR Audio

speedymonk · Post by **speedymonk** » Thu Dec 03, 2020 3:02 am

pandashake wrote: Thu Dec 03, 2020 12:50 am Update: In Device Manager, I have Multimedia Audio Controller and Unknown device listed under Other devices. Can't for the life of me get it to pick up the name of the card.

Do you have the board's audio (built-in I presume) showing up? If so can you disable it and try again.

emulator01 · Post by **emulator01** » Mon Dec 21, 2020 4:48 pm

Hi all,

I am running Windows 10 Pro 1909 with EMU 0404 PCIe and everything runs fine with the mentioned workaround.
Upgrade to Windows 20H2 fails with Blue Screen after 2nd. re-boot.
The log shows that maybe this is caused by drivers.

I checked the installed drivers and some of the Creative Labs drivers are not signed.
Could this be the root cause?

Did someone of you the same upgrade without problems?

Thanks for help
Frank

pandashake · Post by **pandashake** » Mon Dec 21, 2020 7:52 pm

So I put the cards back in my old PC, and they work just fine. Did some further investigation and it turned out it my riser card went bad. Got another one on order, but if this doesn't work, I pulled the trigger on a Quantum 2626, so I'm good either way. haha

speedymonk · Post by **speedymonk** » Tue Dec 22, 2020 12:29 am

pandashake wrote: Mon Dec 21, 2020 7:52 pm So I put the cards back in my old PC, and they work just fine. Did some further investigation and it turned out it my riser card went bad. Got another one on order, but if this doesn't work, I pulled the trigger on a Quantum 2626, so I'm good either way. haha

Which riser card did you use?

pandashake · Post by **pandashake** » Tue Dec 22, 2020 12:33 am

I believe it was a Sintech card.

planetearth · Post by **planetearth** » Tue Dec 22, 2020 4:12 am

emulator01 wrote: Mon Dec 21, 2020 4:48 pm Hi all,

I am running Windows 10 Pro 1909 with EMU 0404 PCIe and everything runs fine with the mentioned workaround.
Upgrade to Windows 20H2 fails with Blue Screen after 2nd. re-boot.
The log shows that maybe this is caused by drivers.

I checked the installed drivers and some of the Creative Labs drivers are not signed.
Could this be the root cause?

Did someone of you the same upgrade without problems?

Thanks for help
Frank

I walked a friend through installing the drivers and PatchMix for an E-MU 1820m PCIe on his system, with no problems. He has a clean install of Win10 20H2, so I doubt that's having a problem with the Creative drivers not being signed. In fact, I'm not sure Creative ever submitted any of their drivers to be signed, since Microsoft charges for that and virtually no one who would use Creative products would care about or needs the extra "security" or "stability" that signing claims to offer.

You might want to try simply un-installing everything, cleaning your Registry with CCleaner (the free version), and re-installing everything, using the steps outlined above. Maybe something got screwed up during the 20H2 upgrade. (If you do use CCleaner, make sure you go into your Task Scheduler and turn off its automatic update checks.)

Steve

kodebode2 · Post by **kodebode2** » Tue Dec 22, 2020 8:10 am

When Microsoft forced me to upgrade to Windows 10 20H2, from Windows 10 1903, my EMU1212M stopped working.

Thankfully the install process which applies to 1903 also did the job for the 20H2 version, After I 1st uninstalled the drivers and app. Relieved.

speedymonk · Post by **speedymonk** » Wed Dec 23, 2020 3:49 pm

pandashake wrote: Tue Dec 22, 2020 12:33 am I believe it was a Sintech card.

That is what I have in mine. No issues...yet.

speedymonk · Post by **speedymonk** » Sat Dec 26, 2020 4:39 pm

Anyone know how close the specs are between the UA Apollo 4X series, Clarett 4pere thunderbolt and EMU 1820m are? I'm talking about dynamic range on line(synth) inputs, S/N, etc. Not sure what I am looking at to make a solid comparison. Any help appreciated.

mexced · Post by **mexced** » Mon Dec 28, 2020 11:21 am

Hi,

The download link for E-MU_Windows_10_Install.zip is not working anymore. Does somebody has this file?

speedymonk · Post by **speedymonk** » Tue Dec 29, 2020 2:49 am

mexced wrote: Mon Dec 28, 2020 11:21 am Hi,

The download link for E-MU_Windows_10_Install.zip is not working anymore. Does somebody has this file?

Check your private message from me.

mexced · Post by **mexced** » Tue Dec 29, 2020 10:05 am

If somebody has a problem downloading the file. Try your phone it worked for me. I tried 3 different computers and also different dns providers. And a vpn. Strange enough with my phone i could download the file.

yuk · Post by **yuk** » Tue Dec 29, 2020 11:09 am

After upgrading to Windows 10 20H2 from Windows 10 1903, my E-MU 1820m stopped working. "E-MU E-DSP" driver was not installed and "Multimedia Audio Controller " was listed on device manager. There was an error message "the installation of this device is forbidden by system policy".

I went to Computer Configuration > Administrative templates > System > Device Installation > Device Installation Restrictions, then click "Prevent installation of devices that match any of these device IDs" and disable it.

After that, I was able to install the driver according to the procedure.

deholloway · Post by **deholloway** » Wed Jan 13, 2021 3:12 pm

Huge thanks to all that have contributed to the resurrection of E-MU soundcards under recent versions of Windows 10. I can report success with a 1616m using the OP's instructions following a fresh installation of 20H2 x64. I seem to have all sample rates and routing options available, though I have not had cause to test everything.

I have a few DAWs at my disposal (Ableton, Bitwig, Cubase, Reaper, Studio One), most being lite rather than full versions. I also have some standalone instruments, e.g. NI Kontakt 6 and Guitar Rig 5. There is only one of these that is not working properly for me: Bitwig 8-Track. Here, the WASAPI output works fine but ASIO output is unusable. Audio is heavily distorted and sounds like there's a bit-crusher on the signal. Clipping is not occurring, changes made in the software are reflected in PatchMix correctly, but the end product is awful. I also run Windows 7 x64 on the same system (dual boot) and experience the identical problem.

So, has anyone had success running Bitwig with an E-MU card? Or is it just me? I recently contacted Bitwig Support and they wrote that it's possible the E-MU driver just doesn't support the ASIO SDK version and functions that Bitwig Studio needs. This makes me wonder what is so special about Bitwig's ASIO requirements – all the other DAWs seem to cope fine.

Many thanks!

PlatinumAudiolab · Post by **PlatinumAudiolab** » Mon Jan 18, 2021 3:50 am

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

I also wanted to give a big thanks to everyone who helped in this thread. It's crazy to me that such great hardware is (nearly) forced to be discarded simply down to the OS.

Everything's running flawlessly on Win10 20H2. I have all of my audio/midi inputs/outputs in my favorite DAWS exactly how I had them in my Win7 install and all resolutions/bitrates are working as they should be.

For me, I had it all laid out ahead of me prior to building a new system to help ensure there weren't any issues. And it looks like that paid off.

I have a PCI 1820m and before upgrading I tried finding a motherboard with a PCI slot (didn't want to dink around with an adapter card) that supports all of the current gen CPUs, M2, DDR4, etc and didn't break the bank. I landed on B360M-D3H GSM and so far it seems a really solid choice.

Going into the Win10 install I followed the OP instructions to a T. Here are what I found to be the crucial parts of the whole process:

1.) Going into the BIOS and disabling the onboard audio (this could always mess with any part of the process).

2.) In Win10 sound settings disabling any other audio drivers that might get installed (in my case, NVidia likes to install an HDMI audio driver that interfaces with whatever the GPU is hooked up to. Not needed, so I disabled it)

3.) After the initial EMU install, finding the device name in device manager ("E-MU E-DSP" in my case) and updated the name in the EMU_Driver_Fix.ps1 file using Notepad++

4.) After installation, preventing windows update from goofing any of the EMU drivers at any point in the future by following the instructions at https://www.howtogeek.com/263851/how-to ... c-drivers/ (https://www.howtogeek.com/263851/how-to-prevent-windows-from-automatically-updating-specific-drivers/) ... for me I added the drivers "Speakers (E-MU E-DSP)", "Wave (E-MU E-DSP)", and "E-MU E-DSP" to the update prevention list.

I feel like I read through this whole thread, printed out the key parts and sat on the whole deal for months because I was afraid it would suck my life away in a vortex of troubleshooting hell but actually it all went quite smoothly. I spent a lot more time troubleshooting an odd bug in my older Cubase install. Anyways glad it seems to be all over and thanks to everyone who chimed in!

E-MU 1616m, 1212m, 1820m, 0404 Audio Interface - Complete Windows 10 (1903 & Above) Installation Guide