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

[planetearth]

I'll look at my SoundForge/E-MU ASIO settings tonight, but can you choose the Focusrite USB ASIO in SoundForge? I have FL Studio ASIO available in SoundForge, and it plays through the E-MU hardware. Of course, if your Focusrite USB ASIO is internally "wired" (via driver settings) to the Focusrite USB interface, this may not be an option.

Also, which version of Windows are you running?

I've heard about the E-MU issue with systems that have more than 4 GB of RAM (but not in a loooong time), but I have 24 GB in mine, and I haven't encountered that. I can see where using 32-bit drivers might create this issue, but if you're using the 64-bit drivers and 64-bit version of PatchMix, I'm not sure what's going on here....

Steve

[tobra]

I'll look at my SoundForge/E-MU ASIO settings tonight, but can you choose the Focusrite USB ASIO in SoundForge? I have FL Studio ASIO available in SoundForge, and it plays through the E-MU hardware. Of course, if your Focusrite USB ASIO is internally "wired" (via driver settings) to the Focusrite USB interface, this may not be an option.

That I can select "Focusrite USB ASIO". "Focusrite Clarett 4Pre" I bought three days ago because it is close to the characteristics of E-MU. I still think that the E-MU is an unsurpassed sound card, none after it can be compared to it in all specifications, and I have privately tested and measured the E-MU, which are at the top. No offense, this is just my opinion. But the measurements and tests show in favor of E-MU.

Also, which version of Windows are you running?

Windows 11 Pro x64, Version 24H2, OS build 26100.3194, Experience Windows Feature Experience Pack 1000.26100.48.0
Please note that this is the last version of Windows legally available to me from Microsoft.

I've heard about the E-MU issue with systems that have more than 4 GB of RAM (but not in a loooong time), but I have 24 GB in mine, and I haven't encountered that. I can see where using 32-bit drivers might create this issue, but if you're using the 64-bit drivers and 64-bit version of PatchMix, I'm not sure what's going on here....

Steve

My system is 64Bit. I have 32Gb of RAM. In my system that I described to you, it cannot be recorded by sending to "WAV". The recording is distorted, if I find free time I will record in wav format so you can hear the distortion. You have a picture of what I was describing in the post!



I could not find anywhere on the Internet the 64 bit version of the driver and the PatchMix DSP Application. If you have one, I would appreciate it in advance if you could give me the driver and application. My sound card is "E-MU 1616M PCI-e". I updated it when the PCI-e card came out, additionally I bought it in Germany from Thomann.

Best regards,
tobra

[planetearth]

It appears we have PatchMix set up differently, but I can bring audio in through the E-MU (via "DOCK In 1L/1R"), send it out via a SEND on the channel to an ASIO input ("ASIO IN 5/6 - HOST"), and bring that into SoundForge 13 (which is the latest version I have).

SoundForge is set for the E-MU ASIO, with the Record channel 1 and to set to ASIO In 5 and 6, which matches PatchMix's outputs. SoundForge is set to record 24-bit/48 kHz files.

With SoundForge in "monitor" mode, the audio passes through and back out to the E-MU, where it comes in via "WAVE 1/2", which is then sent to my mixer and then out to my speakers.

I set all this up based upon my mixer and what I needed for flexibility, but it was based upon one of the PatchMix templates initially.

Microsoft recently admitted to some problems created by a Windows update last month. The update appeared to create problems with external USB audio devices. I know that's not what you're experiencing here (assuming your E-MU is PCIe), but I thought I'd mention this in case you also have problems with the Focusrite.

Finally, if you're running at least PatchMix v2.20.00, you should be fine.

All that said, I'm not sure what you meant in your post by "E-MU has a problem, if the computer has more than 4GB of RAM, it cannot transfer to wav". (I thought I knew what you were referring to, but after reading your post again, I'm not sure.) PatchMix just passes audio to your recording software; it doesn't save files. I have heard of some corruption in 4 GB audio files on Win10 with E-MU hardware/software, but I haven't been able to find anything else about it. But if you set PatchMix up to send audio to SoundForge, you should be able to save any file at any size (assuming your hard drive is formatted as NTFS, which I'm sure yours is).

All of this is on a Windows 7 system, currently. I can see if I can reproduce your settings, but I haven't had any issues with this setup. I know Win10 introduced some issues, and WIn11 certainly hasn't helped, but people are still using E-MU PCIe cards on Win10 and Win11, so it should work for you. It may just be an issue of setting PatchMix up slightly differently.

Steve

[felipe38]

Can someone please help me?
I have the 0404 EMU, I always used it on Win10 with the tips in this post, but I formatted the computer and now I can't install the driver anymore.
Every time I try to install, it says that the driver version is older, I've already deleted everything from the EMU on the computer, I even went to the device manager and clicked on the EMU and uninstalled the device, but the problem persists.
Does anyone know how I can solve it? Thanks.

[ssimlai]

Anyone has experience successfully installing and using E-MU Proteus X2 in Windows XP 64-bit, using EMU hardware? Need to know soon please.

[planetearth]

I responded to your post about this on Gearspace. Here's what I posted:

Are you asking about the Proteus VX or Emulator X2? There was no "Proteus X2".

Both the Proteus VX and Emulator X2 will run as standalone audio apps in Windows XP (64-bit)—assuming your system is generally stable and has legitimate (and tested) 64-bit Windows XP drivers. If you're trying to use either one within a 64-bit DAW, Emulator X2 (and X3) will work, and Emulator X3 has a 64-bit version. Proteus VX will work with jBridge (https://jstuff.wordpress.com/jbridge/).

E-MU provided 64-bit drivers and a 64-bit version of PatchMix for 64-bit systems. They should work with 64-bit Windows XP, but that was the first 64-bit "consumer" operating system Microsoft made, so it may not adhere to "rules for 64-bit apps" as much as it should, or it may not be fully 64-bit in places where E-MU expected it to be. Their 64-bit drivers and apps were actually developed for the 64-bit version of Vista; they were somewhat "updated" for the 64-bit version of Windows 7.

Steve

[ssimlai]

Oh yes I did read your message. There is a Proteus X2, which I own and of which I posted photo.

[ssimlai]

This is a photo screenshot of mu product Proteus X2. I can post the manual too.

[planetearth]

Interesting. I haven't seen a "Proteus 2" before.

But nothing else I said changes: The standalone 32-bit and 64-bit apps will run on a 64-bit OS; they run on 64-bit versions of Windows Vista, Win7, Win10 and Win11. (They may also run on 64-bit versions of Win8, but that really wasn't out long enough to hear from enough people trying to get it to run there.)

If you have both the 32- and 64-bit versions, go with the 64-bit. It could load larger libraries, and it's more compatible in general.

As far as deciding to use the 32-bit or 64-bit version of the plug-in, I'd still say 64-bit. But since I see you have Emulator X3, I'd definitely say just go with that. It reads and writes Proteus libraries, but it goes deeper into editing the samples, if you want. The standalone version can even sample from your desktop, which is pretty cool. And the 64-bit version of Emulator X3 works within DAWs, with no "bridging" required.

Depending upon which release of Emulator X3 you have, you might have to make a minor change to the Registry to get the effects to work properly. I haven't seen that affect too many people however, so you may be fine.

Steve

[eq1]

Just wanted to keep the dream alive a bit longer (i.e. E-MU audio devices forever) and report a couple things here. Not sure if there's a W11 thread, that's what I'm using at this point. I've posted in this one before though, as I recall, so this is where I'm posting now.

In a nut shell, I recently moved from Windows 7 to Windows 11 (with a brief try of 10). I'm on older hardware (like 2014 Dell PC). I opted for Win 11 23H2, and it's a 'de-bloated' version, using an autounattend 'answer' file. I've been using an E-MU 1616m PCIe version for a long time.

I had no problems installing the E-MU on 11 (or the W10). The only non-standard thing I did, initially, was replace the CTOSS2k.sys in Windows/System32/drivers folder with the allegedly newer ctoss2k.sys file that at some point migrated from Titanium Xfi or something like that (that "some point" was probably the start of the W7 E-MU thread). I also used the non-BETA version of the E-MU driver package. So, as I recall, I installed the driver package, simply swapped ctoss2k for CTOSS2k, restarted, and then installed PatchMix. That was it. Everything generally worked.

I say "generally" because, for one, I use the E-MU in Reaper, and I have had some glitches - that's really why I came here, to report a sort of non-typical fix for a non-typical issue. For two, these audio devices have a lot of functionality, and there's a lot of potential scenarios for their usage, and I haven't done everything with it. But, at this point, I've done quite a lot. I've used inputs to record, MIDI input and outs, 44.1/48k and as I recall 96k too sample rates; SPIDF outs, multitrack with plugins... Generally no big issues.

Anyway, here's a link to a thread I created at the Reaper forum that talks about one issue I came across and documents a solution: https://forum.cockos.com/showthread.php?t=299409

Reaper would crash when I'd close the TDR Nova plugin with it active, during playback. Turned out to be an E-MU issue, and replacing the CTASIO.dll with the newer ctasio64.dll fixed it. I imagine there might be other similar situations that others might come across where this fix might be the answer. It's not too difficult to do, but it was a pain to actually narrow the problem down to being E-MU audio related.

[Markus2]

@eq1 would you please be so kind as to upload the newer ctoss2k.sys file as I may not have it (my version is dated 30.04.2019 187kB). Thanks in advance.

Markus

[eq1]

The ctoss2k.sys and asio64.dll files are in the package of stuff linked in the first post of this thread. I've also attached them here.

[planetearth]

The ctoss2k.sys and asio64.dll files are in the package of stuff linked in the first post of this thread. I've also attached them here.

Thanks for your post, for these files, and for trying to keep the E-MU interfaces working!

I know Microsoft is working on a virtual overhaul of Windows 11's audio and MIDI subsystems. (Some of their "enhancements" will be added to Windows 10, too.) I don't know if any of these changes will ultimately break the ability to load old E-MU/Creative drivers and software, but I hope it doesn't. Emulator X3 is already unstable on my system, and that's a shame, because it was an extremely deep and powerful sampler. (And yes, unlike almost all other "sampler" software, Emulator X3 could actually sample.)

Steve

[eq1]

...Emulator X3 is already unstable on my system, and that's a shame, because it was an extremely deep and powerful sampler. (And yes, unlike almost all other "sampler" software, Emulator X3 could actually sample.)

I use Emulator X3 as well. I haven't used it that much, but last couple days I've done some stuff with it, as a VST in Reaper. It generally works - last night it was working great, actually. I was using it in multi mode, with like 8 channels of MIDI on a track, and flipping between sounds. It was all quite snappy, fluid, and surprisingly easy to work with.

It does crash once in a while, under some kind of edge cases, will just take Reaper down with it. I'll have to use it more though to really see how dire that could be, as I've only just started to get my system as a whole up and running smoothly, plus I've only just swapped that asio file (which I'm hoping might make a difference).

I'm using an X3 I downloaded from archive.org, I think it has DRM/copy protection stripped out. I used it as a standalone app a while back, messed a little bit with samples, that seemed to work fine.

[planetearth]

...Emulator X3 is already unstable on my system, and that's a shame, because it was an extremely deep and powerful sampler. (And yes, unlike almost all other "sampler" software, Emulator X3 could actually sample.)

I use Emulator X3 as well. I haven't used it that much, but last couple days I've done some stuff with it, as a VST in Reaper. It generally works - last night it was working great, actually. I was using it in multi mode, with like 8 channels of MIDI on a track, and flipping between sounds. It was all quite snappy, fluid, and surprisingly easy to work with.

It does crash once in a while, under some kind of edge cases, will just take Reaper down with it. I'll have to use it more though to really see how dire that could be, as I've only just started to get my system as a whole up and running smoothly, plus I've only just swapped that asio file (which I'm hoping might make a difference).

I'm using an X3 I downloaded from archive.org, I think it has DRM/copy protection stripped out. I used it as a standalone app a while back, messed a little bit with samples, that seemed to work fine.

In my case, if I load a project that had Emulator X3 in it as a plug-in, it usually works OK, even in "multi" mode, as you described. But if I close that project and try to open another one with X3, Cakewalk crashes, with an error pointing to the X3. Even if I try to load another project that no longer has X3 in it, Cakewalk crashes. So even if I use X3, record the audio from it, load that .WAV file as a standard audio track, and remove Emulator X3 from the project and save it, Cakewalk will still crash. It's like X3 left some kind of bad mojo in the project that I can't remove.

To me, this is a shame, because there were some great early '90s Emulator CD-ROMs with some really cool (and, admittedly, dated) samples from that era. The "Virtuoso" discs were very versatile (for their time), and with all the real-time control (and built-in effects) possible with the X3, you could get some great sounds—if the plug-in was stable.

For what it's worth, I think X3 is basically always in "multi" mode, since it's always ready to receive on all channels. The only real "limitation" is your amount of RAM. Kind of like my Kurzweil K2000...which is also showing its age.

Steve