E-MU 1616m, 1212m, 1820m, 0404 Audio Interface - Complete Windows 10 (1903 & Above) Installation Guide
-
- KVRer
- 7 posts since 16 Jun, 2004
I've followed the instructions several times and I keep getting the error below.
Anyone help?
~Cheers
https://drive.google.com/file/d/1MUpFbZ ... sp=sharing
Anyone help?
~Cheers
https://drive.google.com/file/d/1MUpFbZ ... sp=sharing
-
- KVRer
- 1 posts since 23 Jan, 2021
Good day.
I have Windows 10 64 bit 20H2 and E-MU 0404 PCI.
I installed everything as in the manual.
The default sound (WDM) in Windows is ok.
Problem: There is no sound (FL Studio, Adobe Audition) when I select the E-MU Asio device.
Operating frequency set to 48 kHZ.
I have Windows 10 64 bit 20H2 and E-MU 0404 PCI.
I installed everything as in the manual.
The default sound (WDM) in Windows is ok.
Problem: There is no sound (FL Studio, Adobe Audition) when I select the E-MU Asio device.
Operating frequency set to 48 kHZ.
-
- KVRer
- 6 posts since 31 Jan, 2021
Hi!
Registered just for this thread. Thanks a lot people for doing the work and enabling us to run these oldie but goldie soundcards. I'm having issues with my 0404USB right now, I hope someone might be able to help.
I didn't do a Windows update like everyone else here but I updated my drivers from an older version (mistake). Used the 1.40 beta version from Creative site. It would not work correctly would crash the whole card. Direct monitor light would turn off and button would not work.
Then tried the 1.30 official. Soundcard seems otherwise OK but the mic inputs don't work properly. I get distortion, low gain and hiss. The inputs might work for a little bit, but then there's a click sound and it goes mute.
Have uninstalled and reinstalled. Firmware updated also the unit when installing the drivers. Set the sample rate to 48khz (only one that works). I'm pretty much at my wits end. Any help would be greatly appreciated!
Registered just for this thread. Thanks a lot people for doing the work and enabling us to run these oldie but goldie soundcards. I'm having issues with my 0404USB right now, I hope someone might be able to help.
I didn't do a Windows update like everyone else here but I updated my drivers from an older version (mistake). Used the 1.40 beta version from Creative site. It would not work correctly would crash the whole card. Direct monitor light would turn off and button would not work.
Then tried the 1.30 official. Soundcard seems otherwise OK but the mic inputs don't work properly. I get distortion, low gain and hiss. The inputs might work for a little bit, but then there's a click sound and it goes mute.
Have uninstalled and reinstalled. Firmware updated also the unit when installing the drivers. Set the sample rate to 48khz (only one that works). I'm pretty much at my wits end. Any help would be greatly appreciated!
-
- KVRer
- 5 posts since 8 Dec, 2016
I'm a very grateful user of this thread's advice THANK YOU!
I've just realised that I can't drop effects from the Effects palette onto inserts. Is this a known problem? It could be a problem with drivers, but tbh it seems a lot more like a problem with a change to the drag-and-drop API in windows 10?
I've just realised that I can't drop effects from the Effects palette onto inserts. Is this a known problem? It could be a problem with drivers, but tbh it seems a lot more like a problem with a change to the drag-and-drop API in windows 10?
-
- KVRer
- 5 posts since 8 Dec, 2016
Can't insert effects problem more info: the inserts areas can receive inserts (I can add peakmeters to new strips for example), but nothing is moving with the mouse pointer when I try to drag from the 'Effects Palette.' Is it just that most people are using their DAW cpu-mediated effects?
Later: I've found that the .session file is actually xml. Very civilized. So are the .corePrefects files. And there are enough examples for me to set them using notepad. So I save my own session, then open with notepad and paste in bits clipped from the "session template" examples in C:\Program Files (x86)\Creative Professional\E-MU PatchMix DSP\Session Templates\ As long as my time is worth nothing and there's an example of every effect I want to use, I'll be sound as a pound!
Lets see if this xml example is acceptable (this example is from the middle of my .session, with the 'coreeffect lines added':
<strip prefader="no">
<insertschain>
<peakmeter bypassed="no" bypasspresolo="no" solo="no"/>
<coreeffect abbrevname="S_REVERB" bypassed="no" bypasspresolo="no" name="Stereo Reverb" piaguid="{93FDD454-C5F9-4339-8230-ED29E83D0363}" solo="no" sourcepreset="Large Room 1" wetdrymix="1.00000">
<param name="Decay Time" type="continuous" value="5.222972"/>
<param name="Early Reflections Level" type="continuous" value="86.486488"/>
<param name="Early/Late Reverb Balance" type="continuous" value="27.270269"/>
<param name="Late Reverb Delay" type="continuous" value="52.87838"/>
<param name="Diffusion" type="continuous" value="46.396397"/>
<param name="High Freq Damping" type="continuous" value="-1.391891"/>
<param name="Low Freq Damping" type="continuous" value="-1.626126"/>
</coreeffect>
<send bypassed="no" bypasspresolo="no" sendASIOoutput="3" solo="no"/>
</insertschain>
<auxsend value="-132.00000"/>
<auxsend value="-132.00000"/>
<level value="0.00000"/>
<pan value="-90.00000"/>
<pan value="90.00000"/>
<mute value="no"/>
<solo value="no"/>
<mutepresolo value="no"/>
<username value="Chan1-2"/>
<input index="0" type="ASIO"/>
</strip>
Later: I've found that the .session file is actually xml. Very civilized. So are the .corePrefects files. And there are enough examples for me to set them using notepad. So I save my own session, then open with notepad and paste in bits clipped from the "session template" examples in C:\Program Files (x86)\Creative Professional\E-MU PatchMix DSP\Session Templates\ As long as my time is worth nothing and there's an example of every effect I want to use, I'll be sound as a pound!
Lets see if this xml example is acceptable (this example is from the middle of my .session, with the 'coreeffect lines added':
<strip prefader="no">
<insertschain>
<peakmeter bypassed="no" bypasspresolo="no" solo="no"/>
<coreeffect abbrevname="S_REVERB" bypassed="no" bypasspresolo="no" name="Stereo Reverb" piaguid="{93FDD454-C5F9-4339-8230-ED29E83D0363}" solo="no" sourcepreset="Large Room 1" wetdrymix="1.00000">
<param name="Decay Time" type="continuous" value="5.222972"/>
<param name="Early Reflections Level" type="continuous" value="86.486488"/>
<param name="Early/Late Reverb Balance" type="continuous" value="27.270269"/>
<param name="Late Reverb Delay" type="continuous" value="52.87838"/>
<param name="Diffusion" type="continuous" value="46.396397"/>
<param name="High Freq Damping" type="continuous" value="-1.391891"/>
<param name="Low Freq Damping" type="continuous" value="-1.626126"/>
</coreeffect>
<send bypassed="no" bypasspresolo="no" sendASIOoutput="3" solo="no"/>
</insertschain>
<auxsend value="-132.00000"/>
<auxsend value="-132.00000"/>
<level value="0.00000"/>
<pan value="-90.00000"/>
<pan value="90.00000"/>
<mute value="no"/>
<solo value="no"/>
<mutepresolo value="no"/>
<username value="Chan1-2"/>
<input index="0" type="ASIO"/>
</strip>
-
- KVRer
- 5 posts since 8 Dec, 2016
@eggthewho can you clarify if you are on Windows 10? and if you followed the instructions on page 1 of this thread? There is a different thread for Windows 7 problem havers, if that's what you mean by not doing a windows update?
-
- KVRer
- 6 posts since 31 Jan, 2021
Atcrank, thanks a lot for the message!
I'm on WIN10. Commented about the updates just because everyone else seemed to have trouble after them. My problems came when I updated to the BETA version of software from Creative site.
I tried doing this via the instructions but unfortunately it seems these drivers are not for the 0404USB version, I think they are only for PCI card models? Installation says "unable to find supported device" and exits.
I managed to get the interface working today for about 2 minutes. After uninstalling software + drivers and reinstalling the older software version + updating firmware. The mic inputs worked and recorded normally but after 2 min sound died again. Db levels went from -6db to around -35db with really bad static noises. And while this happens to the mics the system sound is perfectly working still.
Can this even be a software/driver issue? I'm starting to think it's a power supply failure, maybe that messes the phantom power. But then again why did it happen when I updated soft/firmware and would the system sound still work?
I really appreciate any help here! TIA!
I'm on WIN10. Commented about the updates just because everyone else seemed to have trouble after them. My problems came when I updated to the BETA version of software from Creative site.
I tried doing this via the instructions but unfortunately it seems these drivers are not for the 0404USB version, I think they are only for PCI card models? Installation says "unable to find supported device" and exits.
I managed to get the interface working today for about 2 minutes. After uninstalling software + drivers and reinstalling the older software version + updating firmware. The mic inputs worked and recorded normally but after 2 min sound died again. Db levels went from -6db to around -35db with really bad static noises. And while this happens to the mics the system sound is perfectly working still.
Can this even be a software/driver issue? I'm starting to think it's a power supply failure, maybe that messes the phantom power. But then again why did it happen when I updated soft/firmware and would the system sound still work?
-
- KVRer
- 6 posts since 31 Jan, 2021
Tried to edit the above but couldn't. Just to add, if I turn on direct monitoring, I get a loud static bang if I touch the mic at the slightest. 0404USB leds also go nuts into the red immidiately. Oh and I've tried both channels they are the same. Also tried with different mics.
- KVRAF
- 2391 posts since 10 Jul, 2006 from Tampa
eggthewho wrote: Thu Feb 04, 2021 4:45 pm Atcrank, thanks a lot for the message!
I'm on WIN10. Commented about the updates just because everyone else seemed to have trouble after them. My problems came when I updated to the BETA version of software from Creative site.
I tried doing this via the instructions but unfortunately it seems these drivers are not for the 0404USB version, I think they are only for PCI card models? Installation says "unable to find supported device" and exits.
I managed to get the interface working today for about 2 minutes. After uninstalling software + drivers and reinstalling the older software version + updating firmware. The mic inputs worked and recorded normally but after 2 min sound died again. Db levels went from -6db to around -35db with really bad static noises. And while this happens to the mics the system sound is perfectly working still.
Can this even be a software/driver issue? I'm starting to think it's a power supply failure, maybe that messes the phantom power. But then again why did it happen when I updated soft/firmware and would the system sound still work?I really appreciate any help here! TIA!
You're correct: the PCIe drivers won't work for the USB version of the 0404. And it's unlikely that anything in the PCIe drivers could have adversely affected the USB version of the 0404 to cause what you're seeing here, since the drivers didn't install. Even a firmware update on the device shouldn't have caused any hardware issues, since (I believe) all the 0404 units use the same firmware, just different drivers.eggthewho wrote: Thu Feb 04, 2021 4:58 pm Tried to edit the above but couldn't. Just to add, if I turn on direct monitoring, I get a loud static bang if I touch the mic at the slightest. 0404USB leds also go nuts into the red immidiately. Oh and I've tried both channels they are the same. Also tried with different mics.
That said, what you're describing here doesn't sound like a software issue. Software issues are usually easy to reproduce and generally don't present as grounding or amplifier issues, which it sounds like you're having in the second post. Basically, this does sound more like a power supply issue.
The capacitors in these old devices tend to fail long before we're ready to give up on them. I had to replace a few capacitors in my PCIe 1820m, but it wasn't very difficult to do, and it cost about $8. (And for what it's worth, when my caps failed, the unit would send a loud pop out through the output and the meters would peg in the red when I turned on the computer.)
If you're fairly comfortable opening up the unit, you can inspect the capacitors yourself. Any that are near the power supply may appear to be bulging or have "scorch marks" somewhere on them. These are the ones you'd need to replace. But keep in mind that they (or another component) may be failing without exhibiting any signs at all.
There are websites where people have documented what they've swapped out (and how). If you decide to try to replace the capacitors, I'll find some links for you.
Steve
Here's some of my stuff: https://soundcloud.com/shadowsoflife. If you hear something you like, I'm looking for collaborators.
-
- KVRer
- 6 posts since 31 Jan, 2021
planetearth wrote: Thu Feb 04, 2021 9:58 pmeggthewho wrote: Thu Feb 04, 2021 4:45 pm Atcrank, thanks a lot for the message!
I'm on WIN10. Commented about the updates just because everyone else seemed to have trouble after them. My problems came when I updated to the BETA version of software from Creative site.
I tried doing this via the instructions but unfortunately it seems these drivers are not for the 0404USB version, I think they are only for PCI card models? Installation says "unable to find supported device" and exits.
I managed to get the interface working today for about 2 minutes. After uninstalling software + drivers and reinstalling the older software version + updating firmware. The mic inputs worked and recorded normally but after 2 min sound died again. Db levels went from -6db to around -35db with really bad static noises. And while this happens to the mics the system sound is perfectly working still.
Can this even be a software/driver issue? I'm starting to think it's a power supply failure, maybe that messes the phantom power. But then again why did it happen when I updated soft/firmware and would the system sound still work?I really appreciate any help here! TIA!
You're correct: the PCIe drivers won't work for the USB version of the 0404. And it's unlikely that anything in the PCIe drivers could have adversely affected the USB version of the 0404 to cause what you're seeing here, since the drivers didn't install. Even a firmware update on the device shouldn't have caused any hardware issues, since (I believe) all the 0404 units use the same firmware, just different drivers.eggthewho wrote: Thu Feb 04, 2021 4:58 pm Tried to edit the above but couldn't. Just to add, if I turn on direct monitoring, I get a loud static bang if I touch the mic at the slightest. 0404USB leds also go nuts into the red immidiately. Oh and I've tried both channels they are the same. Also tried with different mics.
That said, what you're describing here doesn't sound like a software issue. Software issues are usually easy to reproduce and generally don't present as grounding or amplifier issues, which it sounds like you're having in the second post. Basically, this does sound more like a power supply issue.
The capacitors in these old devices tend to fail long before we're ready to give up on them. I had to replace a few capacitors in my PCIe 1820m, but it wasn't very difficult to do, and it cost about $8. (And for what it's worth, when my caps failed, the unit would send a loud pop out through the output and the meters would peg in the red when I turned on the computer.)
If you're fairly comfortable opening up the unit, you can inspect the capacitors yourself. Any that are near the power supply may appear to be bulging or have "scorch marks" somewhere on them. These are the ones you'd need to replace. But keep in mind that they (or another component) may be failing without exhibiting any signs at all.
There are websites where people have documented what they've swapped out (and how). If you decide to try to replace the capacitors, I'll find some links for you.
Steve
Thanks a lot for the detailed response Steve! I would surely appreciate any links for which caps to look for. I'm no wizard with a soldering iron but relatively persistant.
The things making me think it's not a hardware issue are that the system sounds work perfectly still as I'm writing this. And the fact that the mic inputs recorded perfectly fine for couple of minutes after the re-installed soft/firmware yesterday. I'll try to manage a second try later today if I can. I think I'll also go out and buy a new power supply, this one actually isn't the original either. Original blew out some years ago, but the specs are be same with this replacement one.
Thanks again!
-
- KVRer
- 6 posts since 31 Jan, 2021
Just a quick reply to this. Opened the 0404 USB today, inspected everything but found nothing strange visually. No caps bulging, nothing unusual met the eye. Also tried a different power supply, problem persisted. I found good info about the 0404 on DIYaudio, but I'm still a bit hesitant to start swapping caps because this issue started straight after software update. FWIW I still cannot run the 1.40 BETA version, it freezes the unit completely. Dunno why because everyone else is commenting this is the best available version for unit.
- KVRAF
- 2391 posts since 10 Jul, 2006 from Tampa
Well, look at these links to see if what these people describe sounds similar to what you're experiencing.eggthewho wrote: Fri Feb 05, 2021 10:53 pm Just a quick reply to this. Opened the 0404 USB today, inspected everything but found nothing strange visually. No caps bulging, nothing unusual met the eye. Also tried a different power supply, problem persisted. I found good info about the 0404 on DIYaudio, but I'm still a bit hesitant to start swapping caps because this issue started straight after software update. FWIW I still cannot run the 1.40 BETA version, it freezes the unit completely. Dunno why because everyone else is commenting this is the best available version for unit.
http://dp.nonoo.hu/repairing-my-emu-1820/
https://www.badcaps.net/forum/showthread.php?t=10362 (You need a free account for this one, but there are useful photos here, including a couple that show very small scorch marks on the failing capacitors. Marks that would have been easy to miss if the board hadn't been removed from the case.)
Some Gearslutz.com posts: https://www.gearslutz.com/board/music-c ... blems.html (The first post here talks about intermittent issues similar to what you're describing.)
https://forum.cockos.com/showthread.php?t=135850
Those are the only sites still up from the ones I used for reference four years ago when I fixed mine. (They were all pretty old when I was visiting them then, too.) But since failing hardware components can present in different ways (and not always consistently), there are posts on each of these where people experience similar things to what you're describing here.
Hope this helps.
Steve
Here's some of my stuff: https://soundcloud.com/shadowsoflife. If you hear something you like, I'm looking for collaborators.
-
- KVRer
- 6 posts since 31 Jan, 2021
planetearth wrote: Sat Feb 06, 2021 2:19 amWell, look at these links to see if what these people describe sounds similar to what you're experiencing.eggthewho wrote: Fri Feb 05, 2021 10:53 pm Just a quick reply to this. Opened the 0404 USB today, inspected everything but found nothing strange visually. No caps bulging, nothing unusual met the eye. Also tried a different power supply, problem persisted. I found good info about the 0404 on DIYaudio, but I'm still a bit hesitant to start swapping caps because this issue started straight after software update. FWIW I still cannot run the 1.40 BETA version, it freezes the unit completely. Dunno why because everyone else is commenting this is the best available version for unit.
http://dp.nonoo.hu/repairing-my-emu-1820/
https://www.badcaps.net/forum/showthread.php?t=10362 (You need a free account for this one, but there are useful photos here, including a couple that show very small scorch marks on the failing capacitors. Marks that would have been easy to miss if the board hadn't been removed from the case.)
Some Gearslutz.com posts: https://www.gearslutz.com/board/music-c ... blems.html (The first post here talks about intermittent issues similar to what you're describing.)
https://forum.cockos.com/showthread.php?t=135850
Those are the only sites still up from the ones I used for reference four years ago when I fixed mine. (They were all pretty old when I was visiting them then, too.) But since failing hardware components can present in different ways (and not always consistently), there are posts on each of these where people experience similar things to what you're describing here.
Hope this helps.
Steve
Thanks Steve again for the reply!
Been continuing this struggle, unfortunately no good news yet. What I've gathered is:
I'm running WIN10 20H2 version. I didn't notice this feature update, it was automatic. It was done just around a week days before I did the EMU BETA update and run into problems.
My E-MU is the 0404 USB version. Most of your links were for the 1820m I believe. I could not find a "power section" on the board of the 0404 as there clearly is on the 1820m.
I'm still wondering if this could be a driver error.. mainly because it happened when doing the software update. And also because both the mic inputs channels went bad at the same time. I tried another power supply, also resoldered the power plug connector. Neither did any good. I also tried installing the software (both BETA and latest official) in safe mode + as an admin.
Could it be that the 0404USB needs the same procedure as described in this thread for the PCI EMU versions? My "Microphone 0404USB" device is showing a Microsoft driver being installed on device manager. Can this be correct?
As for the hardware issue side, there are loud whistles audible when I toggle on/off phantom power on the EMU.
Would much appreciate any help!
You do not have the required permissions to view the files attached to this post.
-
peterfiabigron peterfiabigron https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=496173
- KVRer
- 1 posts since 16 Feb, 2021
Hello,
I'm new member to this very useful site.
First of all thank you for this content and solution. I utilized ClubHouseKey's script for my EMU 1212m and worked perfectly on win 10.
I recently bought a 1616m cardbus+expresscard version, from which I use the microdock m together with the 1010 PCIe card from the 1212m system. (win 10)
I have a very frustrating problem. After installation and inserting ASIO 1/2, 3/4, 5/6 strips I have good signals on their peak meters coming from a VSTi softwer (hauptwerk virtual pipe organ, multichannel). Both with and without inserting sends on those strips to the physical analoug outs (dock out 1/2, 3/4, 5/6) I have very low sound volume coming from the speakers on every analog channel (on 1212m I had perfect volume with similar settings, speakers should be perfectly ok, a pair of behringer thruth b2031a and a pair of passive ok quality speakers with hifi amp, both perfectly working with 1212m system). Also the main and monitor mix has the same good signal level receiving (same as ASIO strips), but I have to give too much gain (with frequent cliping) to even hear normal sound level from speakers (both with -10 and +4db it is much below the acceptable).
Do any of you have something in mind what can cause this problem and what could be the solution?
Many thanks!
I'm new member to this very useful site.
First of all thank you for this content and solution. I utilized ClubHouseKey's script for my EMU 1212m and worked perfectly on win 10.
I recently bought a 1616m cardbus+expresscard version, from which I use the microdock m together with the 1010 PCIe card from the 1212m system. (win 10)
I have a very frustrating problem. After installation and inserting ASIO 1/2, 3/4, 5/6 strips I have good signals on their peak meters coming from a VSTi softwer (hauptwerk virtual pipe organ, multichannel). Both with and without inserting sends on those strips to the physical analoug outs (dock out 1/2, 3/4, 5/6) I have very low sound volume coming from the speakers on every analog channel (on 1212m I had perfect volume with similar settings, speakers should be perfectly ok, a pair of behringer thruth b2031a and a pair of passive ok quality speakers with hifi amp, both perfectly working with 1212m system). Also the main and monitor mix has the same good signal level receiving (same as ASIO strips), but I have to give too much gain (with frequent cliping) to even hear normal sound level from speakers (both with -10 and +4db it is much below the acceptable).
Do any of you have something in mind what can cause this problem and what could be the solution?
Many thanks!
-
engineering_red engineering_red https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=499686
- KVRer
- 1 posts since 1 Mar, 2021
Hi!
My Windows 10 system decided to update to 20H2 version and I lost EMU driver and PatchMix. I tried to install it in exact manner as always (the guide from the first post), but it didn't help. In Device Manager I saw only "Multimedia Audio Controller". I renamed the 2 instances of the device name in the EMU_Driver_Fix script file — nothing. Tried a few times thinking I've overlooked something else, didn't help. So I rolled back to a previous working version 1909 and disabled updates for now. If anyone has the same issue or you have found the solution, please, let me know.
Thank you!
My Windows 10 system decided to update to 20H2 version and I lost EMU driver and PatchMix. I tried to install it in exact manner as always (the guide from the first post), but it didn't help. In Device Manager I saw only "Multimedia Audio Controller". I renamed the 2 instances of the device name in the EMU_Driver_Fix script file — nothing. Tried a few times thinking I've overlooked something else, didn't help. So I rolled back to a previous working version 1909 and disabled updates for now. If anyone has the same issue or you have found the solution, please, let me know.
Thank you!