Typo. 2004. May load 1709, but likely the same issue. Will save the pennies to get the Focusrite I guess. Most of the new hardware arrived yesterday. Just awaiting the Fractal case.
Thank you!
E-MU 1616m, 1212m, 1820m, 0404 Audio Interface - Complete Windows 10 (1903 & Above) Installation Guide
-
- KVRist
- 53 posts since 15 Jul, 2020
-
- KVRAF
- 2391 posts since 10 Jul, 2006 from Tampa
You'll definitely have the same issue, since it's a problem with Windows 10 in general, not a specific version of Windows 10; it's an incompatibility with the old E-MU drivers. And if you "roll back" to an early version of Windows 10, Microsoft will nag the hell out of you to upgrade. Every day. Sometimes more than once.speedymonk wrote: Sat Aug 15, 2020 1:43 pm Typo. 2004. May load 1709, but likely the same issue. Will save the pennies to get the Focusrite I guess. Most of the new hardware arrived yesterday. Just awaiting the Fractal case.
Thank you!
Focusrite makes a good audio interface, and they're still giving away useful plug-ins every few months to all Focusrite hardware owners. Can't beat that!
Steve
Here's some of my stuff: https://soundcloud.com/shadowsoflife. If you hear something you like, I'm looking for collaborators.
-
- KVRist
- 53 posts since 15 Jul, 2020
Thanks. I have already disabled any updates on the 2004 drive. Shouldn't have the nagging about updates. Have 1709 disc. At least with that one I won't have to do the fix. Could clone the 2004 as it only has basic windows 10 and the EMU loaded on it. Probably just do fresh and load my other recording software. Will close everyday drive to the M.2 NVME 1T drive. The audio gets the 500g version. Have several 7200 RPM discs between 2T and 500G I can use for additional storage.
-
- KVRer
- 1 posts since 20 Aug, 2020
Just upgraded to Windows 10, and was crossing my fingers that this would work.
After following all of the instructions from Easy_Does_It's post from February 28th 2020 things appear to be working! Thanks everyone who has put effort into figuring this out for the rest of us!
A couple small issues I ran into:
1) I only have the "Home" version of Windows 10 which apparently does not let you prevent automatic driver updates (3rd step in Easy_Does_It's post). Hoping that doesn't screw things up in the future, but I don't know where it would find drivers to update to...
2) When PatchMix came up initially it didn't have any outputs enabled, and so there was no audio coming from the speakers. I created a new session and enabled all the inputs and outputs. After doing that it instantly started working. Yay!
Thanks again!
After following all of the instructions from Easy_Does_It's post from February 28th 2020 things appear to be working! Thanks everyone who has put effort into figuring this out for the rest of us!
A couple small issues I ran into:
1) I only have the "Home" version of Windows 10 which apparently does not let you prevent automatic driver updates (3rd step in Easy_Does_It's post). Hoping that doesn't screw things up in the future, but I don't know where it would find drivers to update to...
2) When PatchMix came up initially it didn't have any outputs enabled, and so there was no audio coming from the speakers. I created a new session and enabled all the inputs and outputs. After doing that it instantly started working. Yay!
Thanks again!
-
- KVRist
- 53 posts since 15 Jul, 2020
You can Google how to permanently disable. I believer you go to start, click on run. Type services.msc and hit enter. Go to the frop down and highlight Windows update. Click to open. Use drop down to stop. When done, right click properties and choose disable. Sav and get out.rcaia wrote: Fri Aug 21, 2020 5:34 am Works great! I have my old E-MU 1212m/0404 PCI up and running on Windows 10 v2004 build 19041.450.
Thanks for the fix and very clear instructions...
-
- KVRist
- 53 posts since 15 Jul, 2020
Built new computer. i710700k in Z490 Vision D board 32 g ram. Air cooled (Corsair). Did the "fix" for the EMU on Windows 10 3004. works better and more stable than it ever was. Still only record at 44.1 but..... I will bide my time before doing anything else. Disable all future Windows updates on the NVME M.2 1T drive. This is for recording only.
About had a heart attack when I went to restore my main Windows drive with everyday stuff after there was a glitch in porting it over to the new machine. Works first time then wouldn't allow me to open up after signing in. No problem, right? Went to the Windows system image backup I made just before doing this stuff. Worked until the 60% mark and said it was corrupted.
Took it to local computer geeks who also said it was corrupted and didn't even charge me a bench fee. Recommended someone else. They said the backup is fine, but the hard drive may have some problems. Running extensive tests on it. Will likely only get charged a diagnostic fee. If it is bad, I'll get a fresh hard drive (probably solid state) and do the image restore and port to the new system. They said even thouhg I was using an AMD machine and going to Intel, windows can figure it out,
Happ camper on two fronts-- EMU works and have no lost my data.
About had a heart attack when I went to restore my main Windows drive with everyday stuff after there was a glitch in porting it over to the new machine. Works first time then wouldn't allow me to open up after signing in. No problem, right? Went to the Windows system image backup I made just before doing this stuff. Worked until the 60% mark and said it was corrupted.
Took it to local computer geeks who also said it was corrupted and didn't even charge me a bench fee. Recommended someone else. They said the backup is fine, but the hard drive may have some problems. Running extensive tests on it. Will likely only get charged a diagnostic fee. If it is bad, I'll get a fresh hard drive (probably solid state) and do the image restore and port to the new system. They said even thouhg I was using an AMD machine and going to Intel, windows can figure it out,
Happ camper on two fronts-- EMU works and have no lost my data.
-
- KVRer
- 3 posts since 23 Aug, 2020
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.
From the entire list of FilesToReplace.csv, in order for the card to work under Win10 x64, only the ctoss2k.sys file needs to be replaced, not necessarily from safe mode, but from normal mode. Sequencing:- install EmuPMX_PCDrv_US_2_30_00_BETA.exe and EmuPMX_PCApp_US_2_20_00.exe reboot
- unload PatchMix (it will not let you replace the file)
- unpack the archive into cd c: \ temp \
- in the command line (Windows PowerShell) from the administrator run:
cd c: \ temp \
./EMU_Driver_Fix.ps1
- launch PatchMix, it will see the microdoc
- to make asio work: regsvr32 c: \ Windows \ System32 \ ctasio64.dll
https://yadi.sk/d/jew5QPQmIO4abQ (https://yadi.sk/d/jew5QPQmIO4abQ)
Replacing 1 file gives more stability, no cracking.
You can manually replace ctoss2k.sys from normal mode:
- unload PatchMix (it will not let you replace the file)
- disable E-MU E-DSP Audio Processor (WDM) in Device Manager
- open through the explorer C: \ Windows \ system32 \ drivers \, copy the file XFTI_PCDRV_L11_2_40_0019 \ Drivers \ wdm \ win2k_xp \ amd64 \ ctoss2k.sys into it
- enable E-MU E-DSP Audio Processor (WDM) in Device Manager
- launch PatchMix, it will see the microdoc
Sometimes this method does not work, writes no access, no rights.
-
- KVRer
- 3 posts since 23 Aug, 2020
There is another option to replace ctoss2k.sys in the driver installer e-mu, works, requires no other action.
-
BatChainPuller BatChainPuller https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=473316
- KVRer
- 2 posts since 28 Aug, 2020
Curious to know if anyone else has had this nifty workaround broken in the newest Windows 10 update. Ever since my computer was upgraded on the 24th to build 19041.450 my PatchMix software reports that I do not have sufficient hardware installed.
-
- KVRist
- 53 posts since 15 Jul, 2020
Perhaps just re-do the "fix". I ran mine on 2004 and aside from only getting 44.1, loads fine.BatChainPuller wrote: Fri Aug 28, 2020 9:24 pm Curious to know if anyone else has had this nifty workaround broken in the newest Windows 10 update. Ever since my computer was upgraded on the 24th to build 19041.450 my PatchMix software reports that I do not have sufficient hardware installed.
-
BatChainPuller BatChainPuller https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=473316
- KVRer
- 2 posts since 28 Aug, 2020
Yes! Thanks! That did the trick (again!)speedymonk wrote: Sat Aug 29, 2020 2:33 pm Perhaps just re-do the "fix". I ran mine on 2004 and aside from only getting 44.1, loads fine.
-
- KVRist
- 53 posts since 15 Jul, 2020
Yay!
-
- KVRist
- 53 posts since 15 Jul, 2020
Those of you that use the 1820m.... Can you tell me your setup in patchmix (hardware, too)that allows you to operate at 48, 96 and 192? I can only go at 44.1? I don't use virtual instruments but run analog synths through a Mackie LM3204. I have three synths (Korg Trinity Plus, EMU 6400 sampler and Proteus 2000 that have spfdif outs. Just nothing to send back into figured the A/D-D/A converters would take care of that. My real world and the manual seem to differ. I'd like to know how you circumnavigated this. Thank you.