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

[nfsking2]

Hi guys,

I don't know if anyone is using 1616m PCIe on the latest Windows 11 on AMD platform.

I actually own two sets of 1616m PCIe, both of them work fine in recent years with the E-MU driver fix method on Intel platforms with Windows 11 64bit.

I recently brought one of them to another city and installed it on an AMD platform, everything seemed to be fine, but the only problem was that I could not get any sound from any Windows software, neither MME/DirectSound output nor ASIO output.

The hardware itself seemed to work properly, because when I plugged a mic or a line-in device to the dock, the peak meter in PatchMix panel indicated that there was an input signal, and it can be sent to the Phone output on the dock so I could actually heard it.

However, if I send the signal to any Windows software, or try to play any sound from any Windows software, it doesn't work.

For example, the Adobe Audition would not receive any input signal even if I have sent the signal to ASIO input.

Also, I tried to use foobar2000 to play music through ASIO, then sent the signal to Dock's Phone output and S/PDIF output, eventhough the foobar2000 worked fine, but there was no any output from the dock, and the peak meter for the ASIO output and Main Mix in the PatchMix panel had no response.

It also could not output the Windows system sound.

No error messages appeared in any software or Windows system, nor in PatchMix.

I wonder if anyone has had this problem or know the solution?

Do you also have an AMD video card in that system? Regardless, you might want to start by disabling any on-board audio devices in the system's BIOS. Then disable (don't just uninstall) any other audio devices in Device Manager. You don't want to un-install them, because you don't want Windows to re-install them when you reboot. Then check your PatchMix settings again, to make sure the E-MU device is chosen.

Steve

Hi Steve,

Thanks for your reply as well as advices.

I have a nVidia GPU instead of an AMD one, and I have tried disabling on-board devices (including the integrated sound card) in the BIOS, or forcing the PCIe version to fall back to PCIe 3.0, all of which have failed to resolve the issue.

[planetearth]

I'm referring to plug-ins made by Waves, Native Instruments, and many others who no longer support Windows XP or any 32-bit operating system or DAW. Many of those companies also don't support Windows 7 or 8, even if you're using the 64-bit version of those OSes. So unless you have the old installers, you might not be able to install old versions of plug-ins from those companies. And in some cases (such as with Native Instruments), even if you can install an old plug-in, they won't let you authorize it, because they've disabled authorizing old plug-ins.

Proteus X2 will work on Windows XP, or even the 32-bit version of Windows 7. I haven't used it in almost a decade, because it didn't work with my 64-bit DAW (it's a known issue). I don't think you need to authorize or register Proteus X2 with E-MU, since they've been gone for over a decade, and it was basically free even when E-MU existed. But if you do have to authorize or register it, good luck—E-MU's registration servers are gone. Even Creative Labs (who bought E-MU) won't let you authorize or register any E-MU software. (People have gotten around that, but that's a different topic, and I don't think you'll have to deal with it for Proteus X2.)

Steve

[planetearth]

Hi guys,

I don't know if anyone is using 1616m PCIe on the latest Windows 11 on AMD platform.

I actually own two sets of 1616m PCIe, both of them work fine in recent years with the E-MU driver fix method on Intel platforms with Windows 11 64bit.

I recently brought one of them to another city and installed it on an AMD platform, everything seemed to be fine, but the only problem was that I could not get any sound from any Windows software, neither MME/DirectSound output nor ASIO output.

The hardware itself seemed to work properly, because when I plugged a mic or a line-in device to the dock, the peak meter in PatchMix panel indicated that there was an input signal, and it can be sent to the Phone output on the dock so I could actually heard it.

However, if I send the signal to any Windows software, or try to play any sound from any Windows software, it doesn't work.

For example, the Adobe Audition would not receive any input signal even if I have sent the signal to ASIO input.

Also, I tried to use foobar2000 to play music through ASIO, then sent the signal to Dock's Phone output and S/PDIF output, eventhough the foobar2000 worked fine, but there was no any output from the dock, and the peak meter for the ASIO output and Main Mix in the PatchMix panel had no response.

It also could not output the Windows system sound.

No error messages appeared in any software or Windows system, nor in PatchMix.

I wonder if anyone has had this problem or know the solution?

Do you also have an AMD video card in that system? Regardless, you might want to start by disabling any on-board audio devices in the system's BIOS. Then disable (don't just uninstall) any other audio devices in Device Manager. You don't want to un-install them, because you don't want Windows to re-install them when you reboot. Then check your PatchMix settings again, to make sure the E-MU device is chosen.

Steve

Hi Steve,

Thanks for your reply as well as advices.

I have a nVidia GPU instead of an AMD one, and I have tried disabling on-board devices (including the integrated sound card) in the BIOS, or forcing the PCIe version to fall back to PCIe 3.0, all of which have failed to resolve the issue.

I assume the device shows up properly in Device Manager, but if it doesn't, you should start there. Otherwise, I would use something like the free Revo Uninstaller to completely uninstall PatchMix. Revo is more thorough than the app's own uninstall routine, but you have to set it to "Advanced" when it asks which removal method you want to use. (And don't reboot after removing PatchMix until Revo has shown you what's left behind so that you can remove that as well.) And even at that, Revo might leave some things behind. It might be worth going through the Windows Registry to delete all keys referring to "PatchMix" (but be sure to back up the Registry first!).

Once everything is thoroughly removed, reboot the PC and re-install the final version of PatchMix (which Creative still lists on their site, I believe).

It could just be that something on the AMD motherboard is using the same IRQ or DMA as the E-MU card, but that would show up as an issue in Device Manager, not PatchMix. Still, you can view the hardware devices and resources by connection in Device Manager. You might want to try those to see if anything else is using the same connection. Make sure "Show hidden devices" is selected before you do it. And look for any devices that are "ghosted"; they'll look like a much lighter version of the icon they would otherwise use. In general, you can (and should) delete any ghosted devices, since they can still reserve IRQ and DMA access and keep other devices from working properly.

Steve

[Godek]

This is a complete guide to setting up the E-MU 1212m/1616m audio interface on Windows 10 version 1903 and above.

Thank you sooooo much for this Guide!!! It works also in 2024

Greetz

Godek

[asiaticgreen]

Still working...thanks to the OP!

[Sture]

Greetings and Big Thanks from Stockholm, Sweden!

I have been using the EMU-1820 for many years and after a couple of clean-ups and re-installations it is once again working well thanks to Steve and all who has provided the informations here in this forum and the instructions and scripts to get the card and dock working!

I followed the instructions and also changed the name in the script to "EMU DSP" as this is what appeared in the device manager.

I have one questions to you if anyone has tried the latest XFi drivers 2.40 0019?
I suppose the EMU_Driver_Fix script can be updated from 0018 to 0019 and and pointed at a new catalog containing the 0019 driver?
- Is it needed and would it bring any advantages in terms of Win10 future updates?
- Would I still need to perform the uninstalls and re-installs of drivers, PatchMix and the script every time Windows sends us a later update of Win10?

Big Thanks again for the great work and support! Rock On!
Sture

[Sture]

Hi, I really would appreciate if anybody could answer my question if it makes sense to try to update to the latest X-Fi drivers 2.40 0019 instead of 0018?

Kind regards from Sweden!

[planetearth]

Hi, I really would appreciate if anybody could answer my question if it makes sense to try to update to the latest X-Fi drivers 2.40 0019 instead of 0018?

Kind regards from Sweden!

I don't think anyone has looked that deeply into all the files that come with the X-Fi driver to see which one(s) (if any) would cause a problem with the E-MU. (Most people seem to be happy the E-MU works at all, and they don't mess with it.) And there's no way to know which file(s) (again, if any) would be incompatible with a Windows 10 or 11 update that Microsoft hasn't released yet.

On the one hand, Windows 11 seems to be limiting more "old code" than Windows 10 did—though I haven't seen anything specific to support this. I only know through the apps Windows 11 says aren't safe to run now.

On the other hand, if v2.40 0018 already works for you, why risk breaking something by updating it? Unless you've seen something specific in release notes about the update that you're fairly sure will fix some problem you're having, I wouldn't risk it. But that may be just me, because I wouldn't want to have to spend an afternoon trying to get all the files and Registry entries related to v2.40 0019 out of the computer before I could re-install v2.40. 0018.

Steve

[Sture]

Big Thanks Steve!
Makes a lot of sense to stick with the 0018 files of course. However I saw a comment that the 0019 files could be more "robust" with future Win10 updates hopefully not having to re-install everything after every Win10 update.

All the best!
Sture

[planetearth]

Big Thanks Steve!
Makes a lot of sense to stick with the 0018 files of course. However I saw a comment that the 0019 files could be more "robust" with future Win10 updates hopefully not having to re-install everything after every Win10 update.

All the best!
Sture

Yes, the 0019 updates probably could be more "robust" regarding future Win10 updates. But you might want to consider where you got that info before you make a decision. If you got the info from here, GearSpace.com, or another site where people are genuinely trying to help keep your E-MU running — and if those people also seem to know what they're talking about regarding Windows 10 — then an update might not hurt you.

Of course, you could also just download the update and wait until your E-MU starts to show a problem—especially if that's after a Windows update (assuming it ever does, and I hope it doesn't!). At that point, you'd have almost nothing to lose by trying the update. Until then, the 0018 version may serve you just fine. (And this is coming from a guy who's almost always among the first to install an update to anything! "Oh, a new version? It must be better!" )

Steve

[Sture]

Hi Steve, great piece of advice and I agree with every word. I am not installing any voluntary Win10 updates to keep my system running. When I can't avoid a future update I might try the 0019 update as you say I have nothing to lose.
Rock on!

Sture

[Sture]

And I briefly listened to some of your music and it is great! I will be checking back later to listen to them all!

[planetearth]

And I briefly listened to some of your music and it is great! I will be checking back later to listen to them all!

Thank you! Be sure to post some of yours, too!

Steve

[Debutante]

do you HAVE to reinstall for every update win11 does?

[planetearth]

do you HAVE to reinstall for every update win11 does?

No, not unless Microsoft makes a change that affects the E-MU drivers. That said, you may want to keep in mind that Microsoft is implementing MIDI 2.0 into Windows 11 now, and that will almost certainly change the way Windows 11 works with MIDI—but that doesn't necessarily mean anything will "break".

Steve