EMU 1212m/1616m on Windows 7 - The Thread to End All Other EMU Threads!

[pandashake]

Yesterday I saw the post of rawl747 with the update of the scripts. The work they do here is really wonderful.
I followed all the steps and tried the version xfti pcdrv l11 240 0019 and the 1820 still has problems. I got a pc with windows 7 32 bit, install the 1820 there with the EmuPMX_PCDrv_L6_2_10_00 drivers, since I think they were the most suitable for this environment and the problems are the same. The 1820 throws the message of insufficient hardware, then flashes there in the patchmix where it informs you that devices have connected, in this case the audiodock, all the channels are disabled and in the vumetros it sends a signal, some type of noise. Then I pass it to 44,100 and it stabilizes but it doesn't work anyway. In wiondows 7 to 44100 does not play sound or anything. In windows 10 play the best, record but with noise to fried.
I am thinking if it will be something electronic from 1820, could something that causes these problems be failing?

If you are running Windows 7 then you didn't need to do any of the stuff mentioned in this thread. That's only for Windows 10 1903 and above. You probably don't have 32 bit drivers in the Xfti drivers. Just use the regular 32 bit existing drivers for the patchmix and the 1212 should show up just fine.

[rawl747]

Fri Feb 28, 2020 9:55 am

l_maseroni wrote: ↑
Wed Feb 26, 2020 11:19 pm
Hi everyone. I have a 1212m version 1, the one that has a fireware port and is compatible with the 1820. It is working wonders, but on the other hand I got an 1820, connect it and it works badly. He walked 1 time in 44,100 but made noise like fried when I wanted to record with a microphone. The strange thing is that it made noise only when it received an impulse, but it was silent. then the second time the system started up it did not work, all the inputs in the patchmix were intermittently lit in red at any sampling frequency. The audiodock power cable did not originally come so I ordered to build one, will this work badly? in the manual it says that one end of the cable goes to 1212m, another to the power supply and another to a disk drive. I don't know where I would go, if this connection is really necessary. Will it be driver problem? use the process explained on page 13 of this thread.

The fact that the symptoms occurred even when you installed the hardware and original drivers in a Windows 7 machine tells us that it is probably not a driver issue causing your problem.
Couple things could be going on. Does your 1212m card have the 4-pin power connector on it, and if so, do you have it hooked up? The 1820 will need this hooked up to get the proper power supply to the dock. If you have done this, then I would suggest replacing the power caps in the dock itself as they notoriously go bad.

The fact that the symptoms occurred even when you installed the hardware and original drivers in a Windows 7 machine tells us that it is probably not a driver issue causing your problem.

Good point pandashake. There is a power cable from the PC's motherboard that needs to be connected to the 1010 card inside the PC.

I also had to replace some of the electrolytic capacitors in my 1820m AudioDock some years ago now. Electrolytic capacitors are the ones that look like little cans usually with plastic labeling shrunk onto the outside of the "can". This type of capacitor is notorious for failing prematurely. Signs of failure are bulging especially at the top and leakage of the electrolytic fluid. These are often the very first components to fail in any electronic device and can cause all sorts of strange symptoms.

So, please check both that your PCI board has power and the electrolytic capacitors in your 1820.

Rawl

[Easy_Does_It]

Update on my system:

After performing the additional 4th step as suggested by Freddie Stjerna (see my previous post for more info), everything worked just fine for an entire day with no issues.

Now, the following day, I have just restarted 4 times in a row, but the hardware isn't being recognized this time. It appears as though I have no hardware installed, as had happened previously. Except unlike the previous times, restarting doesn't seem to be accomplishing anything now.

---

I will continue to follow this thread out of curiosity and a sliver of hope, but it looks like I'm about to starting plotting how to spend a bunch more money I wasn't planning to spend. Thanks Microsoft/Creative.

At the risk of sounding preachy, I want to take this moment to point out that technologically, there is absolutely nothing preventing the capability of these machines to function properly within a Windows 10 environment. (Most of us have been doing it a while.) It is only negligence and/or planned obsolescence from these companies that brings us to our current state. This phenomenon is a great example of why we keep filling landfills with junk. Wouldn't it be nice to live in a world where people actually valued and took care of what they have instead of endlessly disposing of otherwise valuable objects? I guess that wouldn't satisfy the shareholders.
Thanks for coming to my Ted Talk. /End rant

[pandashake]

Update on my system:

After performing the additional 4th step as suggested by Freddie Stjerna (see my previous post for more info), everything worked just fine for an entire day with no issues.

Now, the following day, I have just restarted 4 times in a row, but the hardware isn't being recognized this time. It appears as though I have no hardware installed, as had happened previously. Except unlike the previous times, restarting doesn't seem to be accomplishing anything now.

---

I will continue to follow this thread out of curiosity and a sliver of hope, but it looks like I'm about to starting plotting how to spend a bunch more money I wasn't planning to spend. Thanks Microsoft/Creative.

At the risk of sounding preachy, I want to take this moment to point out that technologically, there is absolutely nothing preventing the capability of these machines to function properly within a Windows 10 environment. (Most of us have been doing it a while.) It is only negligence and/or planned obsolescence from these companies that brings us to our current state. This phenomenon is a great example of why we keep filling landfills with junk. Wouldn't it be nice to live in a world where people actually valued and took care of what they have instead of endlessly disposing of otherwise valuable objects? I guess that wouldn't satisfy the shareholders.
Thanks for coming to my Ted Talk. /End rant

Is your OS 32bit or 64?

[l_maseroni]

Fri Feb 28, 2020 9:55 am

l_maseroni wrote: ↑
Wed Feb 26, 2020 11:19 pm
Hi everyone. I have a 1212m version 1, the one that has a fireware port and is compatible with the 1820. It is working wonders, but on the other hand I got an 1820, connect it and it works badly. He walked 1 time in 44,100 but made noise like fried when I wanted to record with a microphone. The strange thing is that it made noise only when it received an impulse, but it was silent. then the second time the system started up it did not work, all the inputs in the patchmix were intermittently lit in red at any sampling frequency. The audiodock power cable did not originally come so I ordered to build one, will this work badly? in the manual it says that one end of the cable goes to 1212m, another to the power supply and another to a disk drive. I don't know where I would go, if this connection is really necessary. Will it be driver problem? use the process explained on page 13 of this thread.

The fact that the symptoms occurred even when you installed the hardware and original drivers in a Windows 7 machine tells us that it is probably not a driver issue causing your problem.
Couple things could be going on. Does your 1212m card have the 4-pin power connector on it, and if so, do you have it hooked up? The 1820 will need this hooked up to get the proper power supply to the dock. If you have done this, then I would suggest replacing the power caps in the dock itself as they notoriously go bad.

The fact that the symptoms occurred even when you installed the hardware and original drivers in a Windows 7 machine tells us that it is probably not a driver issue causing your problem.

Good point pandashake. There is a power cable from the PC's motherboard that needs to be connected to the 1010 card inside the PC.

I also had to replace some of the electrolytic capacitors in my 1820m AudioDock some years ago now. Electrolytic capacitors are the ones that look like little cans usually with plastic labeling shrunk onto the outside of the "can". This type of capacitor is notorious for failing prematurely. Signs of failure are bulging especially at the top and leakage of the electrolytic fluid. These are often the very first components to fail in any electronic device and can cause all sorts of strange symptoms.

So, please check both that your PCI board has power and the electrolytic capacitors in your 1820.

Rawl

Yes, I have the 4-pin power cable. It is not the original, I made myself build a new one 3 days ago, in theory it should be working fine. I'm going to have them check the 1820 somewhere that they have knowledge about audio boards, they told me that this type of electronics is delicate to manipulate. I am inclined 100% that there is a physical problem in 1820. I keep you updated! by the way there are plans of the integrated of these emu?

[Easy_Does_It]

Update on my system:

I've noticed that over the span of this troubleshooting (mis)adventure, my computer has frozen during Windows startup several times. This leads me to speculate that the issue is occurring when the system is initially checking for hardware, which could partially explain why it sometimes fails to 'see' the hardware.

Backing up from the E-MU specific issues, I'm seeing that E-MU users are far from the only ones experiencing problems with their audio devices and the new Windows update. It's been suggested by some here that Windows may be trying to install its own version of the drivers, hence the hangup. I found instructions for preventing Windows from automatically installing drivers for a particular device. (This is distinctly different from preventing ALL drivers from updating, as it only affects the devices you choose.) The instructions can be found here:
https://www.howtogeek.com/263851/how-to ... c-drivers/

I performed this procedure for all four of the E-MU drivers (simultaneously), and when I hit 'OK' on the final step, Patchmix restarted itself and during that process my computer froze again. I did a hard restart, and everything started up normally. Here's where it gets interesting... Once Windows and desktop were up and running again, the Patchmix software loaded by itself. Now your experience may vary, but on my end, ever since some Windows update a couple of years ago, I've had to manually click to open Patchmix when starting up my system. Yet, now it's opening by itself, like it used to (for years) before this whole issue began.

I have now cold booted the machine 4 times in a row, and everything appears to be running fine again, including the auto-load of Patchmix. It seems like a good sign... It may be my imagination, but startup seems slightly smoother/faster now too. Almost like Windows is skipping whatever step it was taking to try to grab control of the drivers on startup.

----

For review, I've done the following in this order:

1. Follow sherwoodsound's instructions, including 'optional' step of editing the registry. Note – I did have to edit the device name in the script to get it working. Please see my previous post on that.
viewtopic.php?f=16&t=529349

2. Do one more registry edit as suggested by Freddy Stjerna (third post on this page, step 4 only):
https://answers.microsoft.com/en-us/win ... 13a?page=3

3. Go through the procedure of preventing Windows from automatically updating the four E-MU drivers, as outlined in this guide:
https://www.howtogeek.com/263851/how-to ... c-drivers/

----

All the signs are good for now. I will report back with an update one way or another.

[Easy_Does_It]

Is your OS 32bit or 64?

System:
Windows 10 Pro 64-bit, version 1909 (as of this post)
ASUS Z170-A motherboard
E-MU 1820m
10 input / 8 output at 48k
Reaper DAW

[rawl747]

Fri Feb 28, 2020 6:03 pm

Update on my system:

I've noticed that over the span of this troubleshooting (mis)adventure, my computer has frozen during Windows startup several times. This leads me to speculate that the issue is occurring when the system is initially checking for hardware, which could partially explain why it sometimes fails to 'see' the hardware.

Backing up from the E-MU specific issues, I'm seeing that E-MU users are far from the only ones experiencing problems with their audio devices and the new Windows update. It's been suggested by some here that Windows may be trying to install its own version of the drivers, hence the hangup. I found instructions for preventing Windows from automatically installing drivers for a particular device. (This is distinctly different from preventing ALL drivers from updating, as it only affects the devices you choose.) The instructions can be found here:
https://www.howtogeek.com/263851/how-to ... c-drivers/

I performed this procedure for all four of the E-MU drivers (simultaneously), and when I hit 'OK' on the final step, Patchmix restarted itself and during that process my computer froze again. I did a hard restart, and everything started up normally. Here's where it gets interesting... Once Windows and desktop were up and running again, the Patchmix software loaded by itself. Now your experience may vary, but on my end, ever since some Windows update a couple of years ago, I've had to manually click to open Patchmix when starting up my system. Yet, now it's opening by itself, like it used to (for years) before this whole issue began.

I have now cold booted the machine 4 times in a row, and everything appears to be running fine again, including the auto-load of Patchmix. It seems like a good sign... It may be my imagination, but startup seems slightly smoother/faster now too. Almost like Windows is skipping whatever step it was taking to try to grab control of the drivers on startup.

----

For review, I've done the following in this order:

1. Follow sherwoodsound's instructions, including 'optional' step of editing the registry. Note – I did have to edit the device name in the script to get it working. Please see my previous post on that.
viewtopic.php?f=16&t=529349

2. Do one more registry edit as suggested by Freddy Stjerna (third post on this page, step 4 only):
https://answers.microsoft.com/en-us/win ... 13a?page=3

3. Go through the procedure of preventing Windows from automatically updating the four E-MU drivers, as outlined in this guide:
https://www.howtogeek.com/263851/how-to ... c-drivers/

----

All the signs are good for now. I will report back with an update one way or another.

Thanks for the update and the specific instructions on editing policy to prevent future driver updates.

Has ANYONE managed to get the 32 bit ASIO drivers to work? Such as in the 32 bit version of Kontakt 5 or the 32 bit version of IL MiniHost Modular?

Otherwise, my 64 bit ASIO drivers for my 1820m continue to hum right along. (pun intended)

Rawl

[rawl747]

By the way, the Hardware IDs for my 1820m card are:

PCI\VEN_1102&DEV_0004&SUBSYS_40011102&REV_03
PCI\VEN_1102&DEV_0004&SUBSYS_40011102
PCI\VEN_1102&DEV_0004&CC_040100
PCI\VEN_1102&DEV_0004&CC_0401

Curious if these are the same for everyone?

[Easy_Does_It]

Yep, my drivers have identical names.

[Easy_Does_It]

Well my friends, it's been just under a full week since my last report, and guess what? My system is running GREAT! Zero issues with start-up or anything else whatsoever. Patchmix auto-loading on start-up every time like a champ.

I can hardly believe it myself. All these years with the E-MU and I thought it really was the end. Yet now my machine is not only fully functional, it seems smoother and more stable than it has ever been before! (Particularly when running my DAW with plugins, etc.)

Wow. Just wow. And thank you from the bottom of my frugal, audio loving heart. To everyone who shared their knowledge and techniques, you just saved me several thousand dollars and a whole lot of time, effort, and stress. And you helped keep some still useful equipment from sitting collecting dust. I am so happy right now and so grateful to everyone who's contributed to this thread. I hope more E-MU lovers can benefit from these threads in the future like I (we) have.

If (knock on wood) I need to revisit this issue in the future, I'll be back on this thread to report the problem and get help again. But hopefully we can continue to use our awesome audio interfaces in peace from now on. Cheers and happy music making/enjoying to you all!

[toonertik]

[rawl747]

Well my friends, it's been just under a full week since my last report, and guess what? My system is running GREAT! Zero issues with start-up or anything else whatsoever. Patchmix auto-loading on start-up every time like a champ.

Easy_Does_It,

Good to hear! Does your E-MU E-DSP ASIO driver show up in your 32 bit audio synths?

Rawl

[Easy_Does_It]

Does your E-MU E-DSP ASIO driver show up in your 32 bit audio synths?

Mind clarifying a bit? Not sure exactly what you're asking.

I'm running Reaper 64-bit using the E-MU drivers ASIO, with all of its inputs and outputs (that I've set up in Patchmix) available in Reaper. Patchmix still runs as a 32-bit program.

Reaper allows bridging, so I'm able to run any 32-bit plugin in addition to the 64-bit ones. However, the dated plugins, like Creative's own Proteus VX, have some limited/glitchy functionality in Reaper. Though it can be run independently and piped into Reaper as audio without issues. More modern 32-bit plugins tend to run in Reaper just fine. There are some that can get hung up or make digital noise at times, but that's likely because I mostly use free plugins and you get what you pay for.

[rawl747]

Thu Mar 05, 2020 10:17 pm

rawl747 wrote: ↑
Thu Mar 05, 2020 5:30 pm
Does your E-MU E-DSP ASIO driver show up in your 32 bit audio synths?

Mind clarifying a bit? Not sure exactly what you're asking.

I'm running Reaper 64-bit using the E-MU drivers ASIO, with all of its inputs and outputs (that I've set up in Patchmix) available in Reaper. Patchmix still runs as a 32-bit program.

Reaper allows bridging, so I'm able to run any 32-bit plugin in addition to the 64-bit ones. However, the dated plugins, like Creative's own Proteus VX, have some limited/glitchy functionality in Reaper. Though it can be run independently and piped into Reaper as audio without issues. More modern 32-bit plugins tend to run in Reaper just fine. There are some that can get hung up or make digital noise at times, but that's likely because I mostly use free plugins and you get what you pay for.

E_D_I,

Glad to clarify. When I run the 64 bit version Cubase Pro v10 the E-MU E-DSP shows up as a choice (which I pick) in the list of ASIO drivers. And, I have JBridged some of my older 32 bit only VST plugins allowing them to run in my 64 bit Cubase. Not much different than what you have described. The fact that a bridged 32 bit VST works in our 64 bit DAW's isn't a valid test for my question since in these cases, the 64 bit DAW is using an E-Mu driver that shows up in that DAW's list of ASIO drivers. It tells us nothing about what shows up in the list of ASIO drivers in a 32 bit DAW or other music synth or host program.

I also sometimes sometimes use 32 bit versions of Cubase on my E-Mu system. I also sometimes run a 32 bit stand-alone version of a synth. Plus I like to use the free (both 32 and 64 bit) beta versions of IL MiniHost Modular (from the folks who brought us Frooty Loops & FL Studio) to run VST's lacking a stand alone interface in what is essentially a stand alone environment. I find IL MiniHost Moduler quite useful when I want to work with or play a VST but don't need to record and want to avoid the longer loading time of Cubase which works through my extensive list of VST plugins before it is ready to load one of them.

So, if I start the 32 bit stand-alone version of a music synth or the 32 bit version of Cubase or of IL MiniHost I no longer see anything E-mu in the list of ASIO drivers since applying "the fix". Back when the system in question was a Win 7 machine, E-Mu ASIO drivers would show up in both 32 bit and 64 bit versions of all my audio programs. And my recollection is that the E-Mu ASIO driver would show in the ASIO list using the "long name", not "E-MU E-DSP".

I hope this clarifies my question. In order to answer it on your PC, you will need to run a 32 bit audio program and look at the ASIO choices in that app's configuration to see if any E-Mu driver shows up.

I don't know if there is a 32 bit version of Reaper or if so if you have it installed. If so then that would work. I can give you a link to download IL MiniHost Modular from the IL site. It will include both 32 bit and 64 bit versions. BTW, it also works as a VST inside Cubase so probably inside Reaper as well and can be quite useful if only just to test a VST without loading your DAW. Or, if you still have a 32 bit stand-alone music synth that can use ASIO drivers installed on your system, you could load that and look at its ASIO configuration to see if an E-Mu driver is still in the list of ASIO driver choices.

I have spent some time trying to find a way to fix this problem on my system. I have tried a number of registry hacks, etc. to no avail. Confirmation that it is a problem on your system as well would tell me (and others who might care) whether this is an isolated problem on my PC or is perhaps a general problem that is fallout from this whole E-Mu driver fiasco.

I would really appreciate if you could check your system using one of the 3 methods I described above.

Thanx,
Rawl