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

Configure and optimize you computer for Audio.
grandfilou.
KVRer
8 posts since 13 Jun, 2019

Post Thu Jun 13, 2019 10:00 am

how sad :[ I would have given it to you. Then I would suggest NOT to update as long as there is no reliable solution :

Gladiathor
KVRer
5 posts since 12 Jun, 2019

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

Post Thu Jun 13, 2019 11:02 am

Scusate se scrivo in italiano.
Io sono riuscito.
Dovete mettere i files in c:\ e non c:\temp.
Disabilitare la scheda audio e tutti i files aperti di Creative.
Aprire con notepad il file emu_driver_fix.ps1 copiare e incollare dentro powershell dopo averlo aperto come amministratore.
A me funziona perfettamente tranne patchMix che devo lanciarlo manualmente perchè non si avvia in automatico.
Grazie ClubHouseKey.
La mia scheda è 1616m PCIe

machuk
KVRer
1 posts since 13 Jun, 2019

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

Post Thu Jun 13, 2019 3:21 pm

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.
ClubHouseKey wrote:
Thu May 30, 2019 6:06 pm
Driver fix for EMU 1820 and probably all other EMU cards on Windows 10 1903.

Here are some instructions:

1. Uninstall any existing EMU drivers and PatchMix versions.
2. Install 2.30 beta drivers (EmuPMX_PCDrv_US_2_30_00_BETA.exe) and reboot.
4. Download XFTI_PCDRV_L11_2_40_0018.exe, then extract it with 7-Zip to a temp folder like C:\temp. Example file structure should look like this: c:\temp\XFTI_PCDRV_L11_2_40_0018\setup.exe
5. Unzip the attached ScriptFiles.zip to c:\temp. You should now have FilesToReplace.csv, EMU_Driver_Fix.ps1, and the XFTI_PCDRV_L11_2_40_0018 folder together in c:\temp.
6. Open an Elevated powershell window and change directory to c:\temp.
7. Run .\EMU_Driver_Fix.ps1 from the Elevated powershell window. The script does 3 things: 1) Disables the EMU card in device manager so we can overwrite some of the driver files. 2) Reads the csv, loops through each entry, and overwrites the necessary files. 3) Re-enables the EMU card in device manager.
8. Install PatchMix 2.20 (EmuPMX_PCApp_US_2_20_00.exe) and reboot.
9. Your card should be fully functional now.

Links:

EmuPMX_PCDrv_US_2_30_00_BETA.exe - E-MU beta drivers for Windows Vista x64 compatibility. These can support most models.
https://support.creative.com/downloads/ ... adId=12479 (https://support.creative.com/downloads/download.aspx?nDownloadId=12479)

EmuPMX_PCApp_US_2_20_00.exe - E-MU PatchMix software meant for the 1616M PCIe model
https://support.creative.com/downloads/ ... adId=11912 (https://support.creative.com/downloads/download.aspx?nDownloadId=11912)

XFTI_PCDRV_L11_2_40_0018.exe - Updated Creative X-Fi drivers for Windows 10 1903
https://support.creative.com/downloads/ ... dId=100256 (https://support.creative.com/downloads/download.aspx?nDownloadId=100256)

I encourage you to check out the script and csv before running it. If there is any concern about running a script, you can manually replace the files as listed in the csv, however it is 111 files.

My initial discovery of this method happened by a happy accident as I was examining Creative's X-Fi drivers which they fixed for 1903. I noticed many similarities to the EMU drivers, including many leftover references to the EMU products. I force installed the Creative drivers to be used with a virtual device (a Voicemeeter/VBAN virtual soundcard) and after a reboot magically my EMU started working. I came up with the method above after painstakingly examining what exact combination of these files it took to get success as I wanted something repeatable and shareable. I believe in 1903 MS has fixed a flaw, enforced a best practice, or enhanced the audio stack in a way that broke what EMU/Creative had done in the past.

Good luck!
Thank you!! This works for me. E-mu 1820 Windows 1903.

The only thing that I had to do before run the script was (on powershell window):
Set-ExecutionPolicy RemoteSigned
...otherwise the script won't run

phantomsmasher
KVRer
2 posts since 14 Jun, 2019

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

Post Fri Jun 14, 2019 8:39 am

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.
ClubHouseKey wrote:
Thu May 30, 2019 6:06 pm
Driver fix for EMU 1820 and probably all other EMU cards on Windows 10 1903.

Here are some instructions:

1. Uninstall any existing EMU drivers and PatchMix versions.
2. Install 2.30 beta drivers (EmuPMX_PCDrv_US_2_30_00_BETA.exe) and reboot.
4. Download XFTI_PCDRV_L11_2_40_0018.exe, then extract it with 7-Zip to a temp folder like C:\temp. Example file structure should look like this: c:\temp\XFTI_PCDRV_L11_2_40_0018\setup.exe
5. Unzip the attached ScriptFiles.zip to c:\temp. You should now have FilesToReplace.csv, EMU_Driver_Fix.ps1, and the XFTI_PCDRV_L11_2_40_0018 folder together in c:\temp.
6. Open an Elevated powershell window and change directory to c:\temp.
7. Run .\EMU_Driver_Fix.ps1 from the Elevated powershell window. The script does 3 things: 1) Disables the EMU card in device manager so we can overwrite some of the driver files. 2) Reads the csv, loops through each entry, and overwrites the necessary files. 3) Re-enables the EMU card in device manager.
8. Install PatchMix 2.20 (EmuPMX_PCApp_US_2_20_00.exe) and reboot.
9. Your card should be fully functional now.

Links:

EmuPMX_PCDrv_US_2_30_00_BETA.exe - E-MU beta drivers for Windows Vista x64 compatibility. These can support most models.
https://support.creative.com/downloads/ ... adId=12479 (https://support.creative.com/downloads/download.aspx?nDownloadId=12479)

EmuPMX_PCApp_US_2_20_00.exe - E-MU PatchMix software meant for the 1616M PCIe model
https://support.creative.com/downloads/ ... adId=11912 (https://support.creative.com/downloads/download.aspx?nDownloadId=11912)

XFTI_PCDRV_L11_2_40_0018.exe - Updated Creative X-Fi drivers for Windows 10 1903
https://support.creative.com/downloads/ ... dId=100256 (https://support.creative.com/downloads/download.aspx?nDownloadId=100256)

I encourage you to check out the script and csv before running it. If there is any concern about running a script, you can manually replace the files as listed in the csv, however it is 111 files.

My initial discovery of this method happened by a happy accident as I was examining Creative's X-Fi drivers which they fixed for 1903. I noticed many similarities to the EMU drivers, including many leftover references to the EMU products. I force installed the Creative drivers to be used with a virtual device (a Voicemeeter/VBAN virtual soundcard) and after a reboot magically my EMU started working. I came up with the method above after painstakingly examining what exact combination of these files it took to get success as I wanted something repeatable and shareable. I believe in 1903 MS has fixed a flaw, enforced a best practice, or enhanced the audio stack in a way that broke what EMU/Creative had done in the past.

Good luck!
Hello, worked for me as well, both for 1820 and for my 1212M, many thanks :-)

phantomsmasher
KVRer
2 posts since 14 Jun, 2019

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

Post Fri Jun 14, 2019 11:20 am

grandfilou. wrote:
Thu Jun 13, 2019 1:30 am
hey there. Yesterday I upgraded to to win10 1903 x64 and now my Patchmix Software shows an error at starting it up. I already tried the solution provided by ClubHouseKey but i think im doing it wrong. The driver itself installs fine but im not sure how to run that script within powershell- it just shows red lines telling me that its not able to find/replace/ files.... :[ Any help is greatly appreciated!
oh im using the emu1212m PCI
Hey, I was scratching my head with this for a minute myself, after discovering this wonderful thread. The red lines are due to your system not allowing running scripts for security reasons. Before running it, try typing "Set-ExecutionPolicy RemoteSigned" and confirming it. After having run the script, you can reenable the policy by typing "Set-ExecutionPolicy Restricted"

grandfilou.
KVRer
8 posts since 13 Jun, 2019

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

Post Fri Jun 14, 2019 11:34 am

hey thx for your reply! Seems like i missed that part or did it wrong (i think i choose the wrong policie or so) and gave up too early. Maybe i give it another try this weekend. Thank you

tobra
KVRer
13 posts since 6 Jun, 2019

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

Post Sun Jun 16, 2019 4:57 am

grandfilou. wrote:
Thu Jun 13, 2019 1:30 am
hey there. Yesterday I upgraded to to win10 1903 x64 and now my Patchmix Software shows an error at starting it up. I already tried the solution provided by ClubHouseKey but i think im doing it wrong. The driver itself installs fine but im not sure how to run that script within powershell- it just shows red lines telling me that its not able to find/replace/ files.... :[ Any help is greatly appreciated!
oh im using the emu1212m PCI
You need to place the folders properly. When you unpack everything you need in the directory "ScriptFiles" copy the directory "XFTI_PCDRV_L11_2_40_0018". Afterwards, read in the Control Panel, which is the name of the driver. If the names ("E-MU E-DSP") in the script file are not the same then they will not do it properly.

Code: Select all

Get-PnpDevice -FriendlyName "E-MU E-DSP" | Disable-PnpDevice -Confirm:$false -Verbose
$FilesToReplace = Import-Csv $PSScriptRoot\FilesToReplace.csv
ForEach ($FiletoReplace in $FilesToReplace) {
    $SourcePath = $PSScriptRoot + "\" + $FileToReplace.SourceFile
    $DestinationPath = $FileToReplace.DestinationPath
    Copy-Item -Path $SourcePath -Destination $DestinationPath -Force -Confirm:$false -Verbose
}
Get-PnpDevice -FriendlyName "E-MU E-DSP" | Enable-PnpDevice -Confirm:$false -Verbose
You can read about it here
If you need to change the name, you must do the same as me. I suggest that you download the program I set up it is easy to use and the structure of the file does not change, in this case file "EMU_Driver_Fix.ps1"

grandfilou.
KVRer
8 posts since 13 Jun, 2019

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

Post Sun Jun 16, 2019 8:21 am

thx for your explanation. I gave it another try but it didnt work as expected. :?
Could somebody post a screenshot of the folder (-structure), and/or possibly a screenrecording of that powershell procedure? would be really helpful
i attached a screenshot of the device manager. the drivers name corresponds to the one in the script, right? :roll: :roll:
You do not have the required permissions to view the files attached to this post.

tobra
KVRer
13 posts since 6 Jun, 2019

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

Post Sun Jun 16, 2019 11:22 am

Download the script from my post. Because the script file is fixed to "E-MU E DSP Audio Processor (WDM)".

Download all necessary files as described by member ClubHouseKey. Install the driver as described by the member ClubHouseKey.

The directory setting would be like this.

1. Create a "temp" folder on the hard disk "C:\temp". The ScriptFiles file you downloaded move to "temp" folder which you have previously made.
2. Unpack the file ScriptFiles, right-click on the file ScriptFiles and select the option to "Extract All..." you will get this as shown in the picture.

Image

3. Move file "XFTI_PCDRV_L11_2_40_0018" into the "ScriptFiles" directory. If you do not have the 7z program download it.
4. Right-click on the file "XFTI_PCDRV_L11_2_40_0018" and select the option to 7-zip --> Extract to "XFTI_PCDRV_L11_2_40_0018\" and now you should have this as shown in the picture.

Image

5. Run Windows Power Shell.

Image

6. Now you need to go to the directory "C:\temp\ScriptFiles". Enter the command >Set-Location C:\temp\ScriptFiles< (without ><) enter.
7. Now you need to activate the script file, enter the command >.\EMU_Driver_Fix.ps1< (without ><) enter. Now it should be good if you followed the instructions. Next, follow the instructions that the member described ClubHouseKey.
8. Install PatchMix 2.20 (EmuPMX PCApp US 2 20 00.exe) and reboot.
9. Your card should be fully functional now.

I think I helped you at least a little bit. :wink:

grandfilou.
KVRer
8 posts since 13 Jun, 2019

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

Post Sun Jun 16, 2019 1:06 pm

wow thank you for that! Ill try it another time this week. and :party: sorry for spamming the thread!!^ :hihi:

candlee33
KVRer
2 posts since 17 Jun, 2019

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

Post Mon Jun 17, 2019 7:10 am

hello
this is my first post.
pls help!!!

Windows Version 1903
i have the e-mu 0404 pci with the same Problems.i follow the instructions ,but i cannot fix it.
Maybe a zip file for my Card ?

thx all

tobra
KVRer
13 posts since 6 Jun, 2019

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

Post Mon Jun 17, 2019 8:15 am

candlee33 wrote:
Mon Jun 17, 2019 7:10 am
hello
this is my first post.
pls help!!!
When you started the script file in the PowerShell window, what was written in red letters?
Please read my post.
What is written to you in the Control Panel, which is the driver?
You need to write a bit more about what failed, to see where you made a mistake.

ClubHouseKey
KVRer
28 posts since 18 Apr, 2019

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

Post Mon Jun 17, 2019 8:26 am

tobra wrote:
Mon Jun 17, 2019 8:15 am
candlee33 wrote:
Mon Jun 17, 2019 7:10 am
hello
this is my first post.
pls help!!!
When you started the script file in the PowerShell window, what was written in red letters?
Please read my post.
What is written to you in the Control Panel, which is the driver?
You need to write a bit more about what failed, to see where you made a mistake.
I agree. The main issues seem to be 1) Powershell exection policy, and 2) Making sure the device name written in the script matches what is reported in Device Manager.

If I could do it over again I would have written the script to match any device with E-MU in the name.

tobra
KVRer
13 posts since 6 Jun, 2019

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

Post Mon Jun 17, 2019 8:40 am

@ ClubHouseKey, I followed your instructions and was not successful for the first time. I followed what PowerShell wrote. When I corrected the name of the driver script file it did everything without problems. Now I enjoy my favorite sound card E-MU1616m PCI-e. Thank you for that.

My post where I wrote about the problem.

ClubHouseKey
KVRer
28 posts since 18 Apr, 2019

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

Post Mon Jun 17, 2019 8:45 am

tobra wrote:
Mon Jun 17, 2019 8:40 am
@ ClubHouseKey, I followed your instructions and was not successful for the first time. I followed what PowerShell wrote. When I corrected the name of the driver script file it did everything without problems. Now I enjoy my favorite sound card E-MU1616m PCI-e. Thank you for that.

My post where I wrote about the problem.
That’s great to hear! Thank you for sharing your updated script and helping others to get their cards working. :hug:

Return to “Computer Setup and System Configuration”