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

Configure and optimize you computer for Audio.
Post Reply New Topic
RELATED
PRODUCTS

Post

kodebode2 wrote: Sun Sep 06, 2020 1:33 am
boombaxx wrote: Sat Sep 05, 2020 7:52 pm anyone want to buy a 12/12m pci
What does it come with?

1. Daughter card,
2. MIDI cables - how many?
3. Software Disks - which ones?

And how much - including postage. I'm in the UK
missing one midi cable all the rest is there 50 posted im in uk 2

Post

2004 update WARNING;
Oops,.. I ran the windows 2004 update and it killed my drivers. Yah, i forgot. A while back I built a 1903 system and using one of the earlier fixs got my 1820 working,.. Yayyy. But then I foolishly ran the 2004 update and it killed my drivers again,... Booo!!! Without fully understanding the process I tried the older fix and was unsuccessful. In frustration I just rebuilt with 1809. Hopefully I'll find the time to attempt either a fresh build or update to 2004 and test the latest procedure;
E-MU 1820/1820m/1212m/1616m - Complete Install Guide for Windows 10 (1903 & Above)
Originally posted by ClubHouseKey
Modified by rawl747 2020FEB18 with minor changes 20200831
Thank you every one involved for sharing.
I will post results when available.

Post

Just in case anyone has dual boot for Windows 10 x86 32-bit, I was able to edit FilesToReplace.csv to use the x86 files instead.
You do not have the required permissions to view the files attached to this post.

Post

FilesToReplace.zip
Just in case anyone has dual boot for Windows 10 x86 32-bit, I was able to edit FilesToReplace.csv to use the x86 files instead.
You do not have the required permissions to view the files attached to this post.

Post

I applied this patch on version 2004 of Windows 10 and yes, it does work but it's horribly buggy. Not only do I have to install strange possibly "Russian hacked" binaries from who knows where, but they don't actually work consistently. I often get buzzing of my audio and hangs in the audio stream. In extreme circumstances the OS will crash. This really isn't an acceptable solution. Version 1809 is the last version of Windows 10 that reliably supported the EMU1212M and that worked on the Stock EMU drivers not this crazy Russian hack. I wouldn't even go there, but I'm not in the best financial situation and I shouldn't have to pay crazy $$$ just because Microsoft and EMU decide to bail on me. With that said, I guess my best bet right now would be to try to get my hands on one of the multitrack TASCAM USB interfaces. TASCAM seems to do an excellent job of supporting their products...

Post

sherwoodsound wrote: Tue Jul 30, 2019 9:14 am This is a complete guide to setting up the E-MU 1212m/1616m audio interface on Windows 10 version 1903 and above.
Thank you for the topic. After update to Win 10 version 2004 I had to go through the procedure and now all work fine. I have both the E-MU0404 (with Emu drivers) and Audigy 2 ZS (with kxProject drivers) installed simultaneously - in such situation the Emu card must be installed as last one.

Post

I have never installed the Emu 04/04 on my current pc which is windows 10 do i just run you link and if so does it have all the drivers etc and will future updates of windows 10 mess up the installation. Thanks Pete

Post

PBC2112 wrote: Thu Oct 01, 2020 7:05 am I have never installed the Emu 04/04 on my current pc which is windows 10 do i just run you link and if so does it have all the drivers etc and will future updates of windows 10 mess up the installation. Thanks Pete
No, the process is much more complex than just clicking a link.

Post #1 on page #1 describes seven steps. Read them. You need to reboot a couple of times and do some manual actions.

On this very page you could read that updates of Windows have messed things up.
We are the KVR collective. Resistance is futile. You will be assimilated. Image
My MusicCalc is served over https!!

Post

Hello,
I wanted to thank everyone for these steps. I have my 1820m working almost perfectly on Win10 2004.

The one thing that doesn't seem to work for me is the send to Wave L/R. I have Wave L/R as a main send on Aux 1. When I turn up aux 1 on the strip I want to send I don't get any output at all.
Wave Inputs work fine.

I'm not sure if this is a driver issue or if maybe I am missing something in my setup. Does anyone use Wave output and have it working?

**UPDATE - Apparently all I needed to do was post a question to get it to work... Actually in the device properties of the E-MU E-DSP Wave device in windows I turned off Exclusive mode and now Wave output is working but all I get is heavy distortion.

Post

KelValis wrote: Sat Oct 03, 2020 8:12 pm Hello,
I wanted to thank everyone for these steps. I have my 1820m working almost perfectly on Win10 2004.

The one thing that doesn't seem to work for me is the send to Wave L/R. I have Wave L/R as a main send on Aux 1. When I turn up aux 1 on the strip I want to send I don't get any output at all.
Wave Inputs work fine.

I'm not sure if this is a driver issue or if maybe I am missing something in my setup. Does anyone use Wave output and have it working?

**UPDATE - Apparently all I needed to do was post a question to get it to work... Actually in the device properties of the E-MU E-DSP Wave device in windows I turned off Exclusive mode and now Wave output is working but all I get is heavy distortion.
So when you say "almost perfectly", can you record at higher resolution than 44.1? I can't. Wants me to go to ADAT. If you can record at higher resolution, can tell me how you have set the routings? Would like to go up to 96K at times. I am running the 1820 m. audio feeds from my Mackie LM3204 mixer to the 1820 m 1L/1R inputs and then out to the amplifier.

Thank you.

Post

speedymonk wrote: Sun Oct 04, 2020 1:53 pm So when you say "almost perfectly", can you record at higher resolution than 44.1? I can't. Wants me to go to ADAT. If you can record at higher resolution, can tell me how you have set the routings? Would like to go up to 96K at times. I am running the 1820 m. audio feeds from my Mackie LM3204 mixer to the 1820 m 1L/1R inputs and then out to the amplifier.

Thank you.
Hello,
I have tried up to 96K and it is working. I use the Product Default session. I have my mixer going into Line A, LineB, 1L/1R and 2L/2R which output to ASIO 1/2 - ASIO 7/8.
I use ProTools and these input show up in the I/O and are all selectable. The only thing I had to change was the output bus in ProTools. The 48k patchmix session uses ASIO out 31/32 by default and the 96k session uses 15/16.

Sorry if that wasn't very helpful.
I can record and playback in ProTools and everything sounds great. I just want to be able to use the Wave L/R out to send to Skype or whatever without having it just be buzzing and crackling.

Post

I'll see if I can duplicate. Have tried the default settings. Get "Not sufficient EMU hardware". Using Cakewalk by Bandlab as by DAW.

Post

shawn_eary wrote: Mon Sep 21, 2020 3:31 am I applied this patch on version 2004 of Windows 10 and yes, it does work but it's horribly buggy. Not only do I have to install strange possibly "Russian hacked" binaries from who knows where, but they don't actually work consistently. I often get buzzing of my audio and hangs in the audio stream. In extreme circumstances the OS will crash. This really isn't an acceptable solution. Version 1809 is the last version of Windows 10 that reliably supported the EMU1212M and that worked on the Stock EMU drivers not this crazy Russian hack. I wouldn't even go there, but I'm not in the best financial situation and I shouldn't have to pay crazy $$$ just because Microsoft and EMU decide to bail on me. With that said, I guess my best bet right now would be to try to get my hands on one of the multitrack TASCAM USB interfaces. TASCAM seems to do an excellent job of supporting their products...
Please see my earlier post, there is absolutely no need to use the executables from the initial post which started this thread. Downloading any executables from strange sources is not advised.

What I recommend is that you look into the zip file downloaded from the link in the 1st post of this thread only for information, so you have the exact names of the files which you need to search for from the Internet, and download directly from EMU, Creative Labs, or a trusted repository, and you can create the required directory structure expected by the ps1 files.

The only thing you need is the ctoss2k.sys file from the recent Creative Labs sound card driver.

So let me spell out the new process, based on the best of my own learnings.

1. Uninstall any EMU drivers and apps for your EMU soundcard.

2. Reboot into normal mode.

3. Install the EMU driver from the following file, i.e download and run the executable :

EmuPMX_PCDrv_US_2_30_00_BETA.exe

You can find this if you google. and you can download it without any risk from this link directly from EMU/Creative Labs

https://support.creative.com/downloads/ ... adId=12479

4. Install the EMU app i.e PatchMix from the following file, i,e download and run this executable :

EmuPMX_PCApp_US_2_20_00.exe

You can find this here at the link below directly from EMU/Creative Labs

https://support.creative.com/downloads/ ... adId=11912

5. You can at this point in time either go into Safe Mode, or go into Device Manager and disable the EMU E-DSP device which you will find under Sound, Video and Game Controllers. Either of these achieves the same thing, ensuring that the driver files can be replaced.

6. Using a zip program like 7zip, extract the recent executable, the driver for the more recent Creative Labs card which is compliant with Windows 10, including recent versions.

The file name is : XFTI_PCDRV_L11_2_40_0018.exe

And you can find a "safe" copy from a french software driver repository here, as it is no longer on the Creative Labs site :

https://www.touslesdrivers.com/index.ph ... code=60725

Assuming you unzippeed it to a location directory c:\XFTI_PCDRV_L11_2_40_0018

Then simply go into a CMD or Powershell as an administrator and

copy c:\XFTI_PCDRV_L11_2_40_0018\Drivers\wdm\win2k_xp\amd64\ctoss2k.sys
C:\Windows\system32\drivers\ctoss2k.sys

If you did this in normal mode, by disabling the EMU driver in device Manager, then enable the EMU Driver.

If you did this last step 6 in Safe Mode, simply reboot into normal mode.

Job done, at no risk.

If you are worried about downloading from the French site, there is a newer version of the driver

XFTI_PCDRV_L11_2_40_0019.exe, which you can find on the Creative labs site and use the ctos2k.sys from this new driver(extract as described above for the 0018 version), it might just work.. I have not tried it but I think it will do the job also. simply extract as above and copy the ctoss2k.sys to the C:\Windows\system32\drivers\ctoss2k.sys.

Actually I just did this and it worked ok. the 0019 version of the XFTI driver - using only its ctoss2k.sys file, which you can download from Creative labs here :

https://support.creative.com/Downloads/ ... wDetails=1

So all in all the three files you need can all be downloaded directly from Creative labs, with absolutely no risk of any viruses.

do find however that the 0018 driver's ctoss2k.sys, works a lot better IMHO than than the one from the 0019 version of the driver.. I may be wrong... I am reverting to the 0018 version of the ctoss2k.sys. The risk is minor as the driver is signed by Creative Labs and Microsoft, so it should be safe to install.., cos if it has been tampered with, the install will flag this up as the signature will no longer be valid with the contents...

1.

EmuPMX_PCDrv_US_2_30_00_BETA.exe

You can find this if you google. and you can download it without any risk from this link directly from EMU/Creative Labs, and the install process is pretty simple. I

https://support.creative.com/downloads/ ... adId=12479

2.

EmuPMX_PCApp_US_2_20_00.exe

You can find this here at the link below directly from EMU/Creative Labs

https://support.creative.com/downloads/ ... adId=11912

3.

https://support.creative.com/Downloads/ ... wDetails=1

Post

KelValis wrote: Sun Oct 04, 2020 4:14 pm
speedymonk wrote: Sun Oct 04, 2020 1:53 pm So when you say "almost perfectly", can you record at higher resolution than 44.1? I can't. Wants me to go to ADAT. If you can record at higher resolution, can tell me how you have set the routings? Would like to go up to 96K at times. I am running the 1820 m. audio feeds from my Mackie LM3204 mixer to the 1820 m 1L/1R inputs and then out to the amplifier.

Thank you.
Hello,
I have tried up to 96K and it is working. I use the Product Default session. I have my mixer going into Line A, LineB, 1L/1R and 2L/2R which output to ASIO 1/2 - ASIO 7/8.
I use ProTools and these input show up in the I/O and are all selectable. The only thing I had to change was the output bus in ProTools. The 48k patchmix session uses ASIO out 31/32 by default and the 96k session uses 15/16.

Sorry if that wasn't very helpful.
I can record and playback in ProTools and everything sounds great. I just want to be able to use the Wave L/R out to send to Skype or whatever without having it just be buzzing and crackling.
Well, I must be cursed on this thing. I use the product defaults and yet get the red lines/red out on the channel strips such as 1L/1R, etc. My mixer goes into 1L/1R. Even switched to 3?l/3R and no go. Unable to go a routing. I get 44.1 and no more.

Using 17 10700K, Gigabyte Z490 vision D, 1T NVME 2 drive, Cakewalk by Bandlab, Soundforge 14. Can record MIDI and audio into Bandlab no problem, as long as it is 44.1. Same with Soundforge. Anything else...nada.

I have 2l/2R inputs from computer to listen to you tube, etc. No issues. all inputs routed to Outputs 4 (stereo) as suggested to monitor.

Post

speedymonk wrote: Tue Oct 06, 2020 2:36 pm
Well, I must be cursed on this thing. I use the product defaults and yet get the red lines/red out on the channel strips such as 1L/1R, etc. My mixer goes into 1L/1R. Even switched to 3?l/3R and no go. Unable to go a routing. I get 44.1 and no more.

Using 17 10700K, Gigabyte Z490 vision D, 1T NVME 2 drive, Cakewalk by Bandlab, Soundforge 14. Can record MIDI and audio into Bandlab no problem, as long as it is 44.1. Same with Soundforge. Anything else...nada.

I have 2l/2R inputs from computer to listen to you tube, etc. No issues. all inputs routed to Outputs 4 (stereo) as suggested to monitor.
If you have done all the steps with replacing the files and still have the red lines issue, perhaps your cable to the audio dock isn't working? My original cable was doing that back in the day and I replaced it with a heavy duty Cat 6 network cable. It seems to work well.

Post Reply

Return to “Computer Setup and System Configuration”