I can set ASIO in REAPER, and all settings for the EMU audio card do show up. I can select "E-MU ASIO" for ASIO driver in Device preferences. I hear sound but there is intermittent noise using the ASIO driver, but not when using the WDM driver in REAPER.
You're talking about installing a ctasio64 driver. I did not install that driver, I installed the package as per Pg.1, and instructions there say to make a change to the registry (as I outlined in my post above). Given I can select "E-MU ASIO" in REAPER I assume the Creative Labs ASIO driver is the one that installed. In Device Manager > Properties > Driver file details I can see something is installed:
C:\Windows\SysWOW\ctasio.dll installed.
I was using the E-MU 1616m and 1010 audio card on a different Windows 10 pro PC successfully, but it was initially installed when it was 21H2 (current Windows 10 is 22H2), and I know I used the same method outlined on Pg.1 here but it's not working smooth for me on the 22H2 build.
Above April 11 you said, "replacing the CTASIO.dll with the newer ctasio64.dll fixed it" when encountering your issue. Can I ask where did you obtain the ctasio64.dll driver and how did you install it? Is there a download link for it and then you can just place it in C:\Windows\SysWOW64 ?
E-MU 1616m, 1212m, 1820m, 0404 Audio Interface - Complete Windows 10 (1903 & Above) Installation Guide
-
- KVRist
- 46 posts since 8 Nov, 2015
The E-MU installation package installs CTASIO.dll; it seems like this thread topic's package of fixes probably at least copies ctasio64 from that Xfi folder and places it on your computer, but I'm not positive. The manual registry hack seems like it's probably about making sure that's being activated. CTASIO seems to work, it has for me, so ctasio64 and the registry hack might be like something you do if you end up having problems, otherwise you just leave things alone.Aero312 wrote: Mon Apr 14, 2025 10:19 pm ...You're talking about installing a ctasio64 driver. I did not install that driver, I installed the package as per Pg.1, and instructions there say to make a change to the registry (as I outlined in my post above). Given I can select "E-MU ASIO" in REAPER I assume the Creative Labs ASIO driver is the one that installed. In Device Manager > Properties > Driver file details I can see there something called ctasio.dll installed...
Can I ask where did you obtain the ctasio64.dll driver and how did you install it?
I got that ctasio64.dll file from the package of stuff at first post.
Here's a link to the Reaper forum thread where I talk about how I installed ctasio64. But you should check to see if you already have that file in the two locations mentioned in that thread, last post. If so it might be a matter of doing the two other registry changes I mention - if your problem is about getting 64 bit ASIO going, which I kind of doubt: https://forum.cockos.com/showthread.php?t=299409
-
- KVRAF
- 2391 posts since 10 Jul, 2006 from Tampa
This sounds very good! I definitely wouldn't have thought it was almost 15-year-old software with probably even older samples. Were you using some real-time modulation/automated MIDI control of the sounds that come in at around 1:30 (you know, the sound that sounds like it's dozens of souls tripping over each other trying to escape Helleq1 wrote: Sat Apr 12, 2025 11:14 pmHere you go: https://drive.proton.me/urls/ECK5G2BR20#s531LEK6HfwH
).It seems a shame that eventually we probably won't be able to use Emulator X3 anymore, between Windows' tightening "security" plans and the problems we already have with it crashing.
I see you were hosting this with Proton. Do you use their email or any other services? I've read they take security and privacy seriously, but I've yet to talk to anyone who uses their services (and that's probably because they just don't know about them yet).
Steve
Here's some of my stuff: https://soundcloud.com/shadowsoflife. If you hear something you like, I'm looking for collaborators.
-
- KVRist
- 46 posts since 8 Nov, 2015
^ Yeah, I use Protonmail and put little things on their drive, just the free plan. Oh, I also use their free VPN. It has all seemed to work OK, I think I've been on it for...several years, maybe like 6? 7? Seems like they've gotten more commercial-like, always asking me to upgrade. But, what can you do.
On that emulator piece - it was all bone stock presets from the 'mophat' bank. I have a bunch of old songs in standard midi files that I need to work through, and I've been thinking of using Emulator for it. This was me just chocking-up a midi file and applying presets to it, barely picking and choosing - like I selected ones that were at the top of the list. I adjusted some of the volumes a little in the multisetup window, and auxiliary FX...
On not being able to use Emulator - you don't have to upgrade your computer, or you can always leave one alone for it. I don't plan on upgrading, I don't do updates either at this point. Moving to W11 23H2 updated to 2025/3 is about as up-to-date as I'll probably ever get. Maybe I'll buy a new computer some day, kind of doubt it though.
On that emulator piece - it was all bone stock presets from the 'mophat' bank. I have a bunch of old songs in standard midi files that I need to work through, and I've been thinking of using Emulator for it. This was me just chocking-up a midi file and applying presets to it, barely picking and choosing - like I selected ones that were at the top of the list. I adjusted some of the volumes a little in the multisetup window, and auxiliary FX...
On not being able to use Emulator - you don't have to upgrade your computer, or you can always leave one alone for it. I don't plan on upgrading, I don't do updates either at this point. Moving to W11 23H2 updated to 2025/3 is about as up-to-date as I'll probably ever get. Maybe I'll buy a new computer some day, kind of doubt it though.
-
- KVRAF
- 2391 posts since 10 Jul, 2006 from Tampa
My computer is virtually a museum piece now, and I was holding off going to Win10 as long as I could.eq1 wrote: Tue Apr 15, 2025 12:35 am ^ Yeah, I use Protonmail and put little things on their drive, just the free plan. Oh, I also use their free VPN. It has all seemed to work OK, I think I've been on it for...several years, maybe like 6? 7? Seems like they've gotten more commercial-like, always asking me to upgrade. But, what can you do.
On that emulator piece - it was all bone stock presets from the 'mophat' bank. I have a bunch of old songs in standard midi files that I need to work through, and I've been thinking of using Emulator for it. This was me just chocking-up a midi file and applying presets to it, barely picking and choosing - like I selected ones that were at the top of the list. I adjusted some of the volumes a little in the multisetup window, and auxiliary FX...
On not being able to use Emulator - you don't have to upgrade your computer, or you can always leave one alone for it. I don't plan on upgrading, I don't do updates either at this point. Moving to W11 23H2 updated to 2025/3 is about as up-to-date as I'll probably ever get. Maybe I'll buy a new computer some day, kind of doubt it though.
But it seems something has changed in Cakewalk (since neither Win7 nor Emulator X3 has seen an update in years). Now if I load a project with X3 and then close it, Cakewalk gets stuck and I have to force it to close. However, I'm able to open another project with X3 in it—but only certain ones, or Cakewalk will still crash just loading the project (but those crashes come with a window telling me that X3 is the real culprit in the crash).
So basically, I'm no better off—it's just a different type of crash.
Steve
Here's some of my stuff: https://soundcloud.com/shadowsoflife. If you hear something you like, I'm looking for collaborators.
-
- KVRist
- 36 posts since 5 Nov, 2012
So from the original install package (Pg 1 of this thread), inside the XFTI_PCDRV_L11_2_40_0018 folder, if you go to Drivers > wdm > common > amd64, you see in that folder there's a driver: ctasio64.dll and in the folder at Drivers > wdm > i386 you find ctasio.dll, which must be a 64-bit driver, and that's the one that installed. For me, the ctasio64.dll did not install in C:\Windows\SysWOW64 where you find other 64-bit drivers. I see even on my old Windows 10 PC where the E-MU gear works fine with ASIO drivers, ctasio64.dll is not installed. It has an old Intel Core 2 Quad CPU. My new PC has an Intel i7-8700 CPU. Is the 64 bit driver intended for amd CPUs given it's in a folder named "amd" ?
Last edited by Aero312 on Wed Apr 30, 2025 9:51 pm, edited 1 time in total.
-
- KVRist
- 46 posts since 8 Nov, 2015
"amd" in this context is about system architecture or something like that, CPU architecture, rather than company names (i.e. Intel vs. AMD), so amd in this case is what you'd want (Intel CPUs at some point started using the amd architecture, I think it has to do with how the CPU is connected to the 'south bridge', maybe?, or whether there is even a need for a south bridge, etc.).
-
- KVRist
- 36 posts since 5 Nov, 2012
I found ctasio64.dll was in my System32 folder but not in SysWOW64. I pasted it into SysWOW64.
--This did not fix noise issue.
Changed two entries of the original "CTASIO" driver in the registry:
HKLM/software/ASIO
HKLM/software/WOW6432Node/ASIO
Changed the two above to "CTASIO64"
Restarted the PC
-- This did not fix noise issue either. But now, opening REAPER there is a dialog box called "CTASIO Warning," which says "The Creative ASIO devices have changed. You may need to restart this program before using Creative ASIO devices." And it keeps opening every time I launch the REAPER application.
Where do you place the ctoss2k.dll file that you offered at the REAPER forum here: https://forum.cockos.com/showthread.php?t=299409
Interesting to note, on my old PC that was running Windows 10 Pro where the E-MU audio card was working fine with ASIO driver, I see CTASIO.dll is in both System32 and in SysWOW64 folders, but CTASIO64.dll is only in System32 and not in SysWOW64.
--This did not fix noise issue.
Changed two entries of the original "CTASIO" driver in the registry:
HKLM/software/ASIO
HKLM/software/WOW6432Node/ASIO
Changed the two above to "CTASIO64"
Restarted the PC
-- This did not fix noise issue either. But now, opening REAPER there is a dialog box called "CTASIO Warning," which says "The Creative ASIO devices have changed. You may need to restart this program before using Creative ASIO devices." And it keeps opening every time I launch the REAPER application.
Where do you place the ctoss2k.dll file that you offered at the REAPER forum here: https://forum.cockos.com/showthread.php?t=299409
Interesting to note, on my old PC that was running Windows 10 Pro where the E-MU audio card was working fine with ASIO driver, I see CTASIO.dll is in both System32 and in SysWOW64 folders, but CTASIO64.dll is only in System32 and not in SysWOW64.
-
- KVRist
- 46 posts since 8 Nov, 2015
^ I got that warning too when I switched to ctasio64. I don't recall what happened - probably because nothing happened, I did nothing special, and it went away.
On ctoss2k - since you did the 1st page automatic fix, seems like you should already have the swapped version in place. Mine is in Windows/system32/drivers. It might be in other places too, but I'm not looking. This is the only place where I swapped new for old, manually.
Have you done any basic Windows or Reaper realtime audio-like tweaks to tune performance? For example, I was getting crackling when playing sounds with Windows CPU power configuration set to minimum 5%, max 100% - as far as I can tell, and what everybody suggests, is that that needs to be set to 100% all the time, minimum set to 100%. How about EMU ASIO buffer setting - maybe it's too low? Personally, I'd start with the CPU setting, and then adjust the buffer latency - when I experimented a couple days ago the CPU setting made a huge difference. Before I did that, I adjusted the buffer setting higher, and it helped a little, but barely. After setting CPU minimum to 100%, I could adjust the latency real low (I have it set to 5ms, 4ms worked too; with the CPU min low, I had to adjust it up to like above 10ms to hear any change in the crackling, and even going higher didn't fix it)...
On ctoss2k - since you did the 1st page automatic fix, seems like you should already have the swapped version in place. Mine is in Windows/system32/drivers. It might be in other places too, but I'm not looking. This is the only place where I swapped new for old, manually.
Have you done any basic Windows or Reaper realtime audio-like tweaks to tune performance? For example, I was getting crackling when playing sounds with Windows CPU power configuration set to minimum 5%, max 100% - as far as I can tell, and what everybody suggests, is that that needs to be set to 100% all the time, minimum set to 100%. How about EMU ASIO buffer setting - maybe it's too low? Personally, I'd start with the CPU setting, and then adjust the buffer latency - when I experimented a couple days ago the CPU setting made a huge difference. Before I did that, I adjusted the buffer setting higher, and it helped a little, but barely. After setting CPU minimum to 100%, I could adjust the latency real low (I have it set to 5ms, 4ms worked too; with the CPU min low, I had to adjust it up to like above 10ms to hear any change in the crackling, and even going higher didn't fix it)...
-
- KVRist
- 36 posts since 5 Nov, 2012
ctoss2k.sys was already in System32 > drivers folder, same version and size as your download. I assume it will not fix the noise issue to replace this file.
Changed power plan to "High Performance" (CPU min at 100%)
--did not fix the issue. No change at all.
Device preferences in REAPER:
Request Block size 256 (that's what I've always used with ASIO drivers) Makes no difference to double this to 512.
ASIO Buffer Latency - makes no difference whether it's 5 ms or 50 ms. It does not affect the noise issue.
And with every change I try to make to device preferences, or when I launch REAPER. I keep getting the CTASIO Warning dialog box I posted above.
I really believe the problem is how the ASIO driver is installed.
Note also (if it matters) I am using a 1010 PCI card, not PCIe. Does it matter for installation on Pg1?
Changed power plan to "High Performance" (CPU min at 100%)
--did not fix the issue. No change at all.
Device preferences in REAPER:
Request Block size 256 (that's what I've always used with ASIO drivers) Makes no difference to double this to 512.
ASIO Buffer Latency - makes no difference whether it's 5 ms or 50 ms. It does not affect the noise issue.
And with every change I try to make to device preferences, or when I launch REAPER. I keep getting the CTASIO Warning dialog box I posted above.
I really believe the problem is how the ASIO driver is installed.
Note also (if it matters) I am using a 1010 PCI card, not PCIe. Does it matter for installation on Pg1?
-
- KVRist
- 46 posts since 8 Nov, 2015
^ Maybe you need to start over. I can't attest to the effectiveness of the 1st page automatic installation method, which is what you started with. All I can say is, I did it such and such ways, I have such and such system, and it works for me. I do know that a lot of people have used the '1st page method' and have been successful. Your old system worked. So? You know, how do we figure out what changed, what went wrong, between then and now? It's a maze...
I installed my E-MU on W10 22H2 before I moved to W11 23H2, same methods, and it worked. I'm on a ~2014 Dell Intel 4770 CPU. I did use modded Windows builds, doesn't seem like that'd make a difference between your results and mine.
Oh, did I miss that you're on a PCI card not PCIe, or did we just cross-post?. That seems like it could make a difference. I actually have a PCI card and a PCI slot - but I only tried it once long ago on W7. I use a PCIe card. I don't recall what the results were with the PCI card way back when, but no matter, doesn't seem like they'd be relevant to what you're doing now, on W10. But, in general, seems like getting the older PCI card to work well could pose an additional set of issues.
Note that I read not too long ago that the BETA driver is supposed to work for both PCI and PCIe - I think it says that in the readme file in the installation package. You might want to check that out and confirm. Info about that that you read in various places is inconsistent - I'd think if it says that in the installation package's readme file that that'd be the most reliable source of info... But otherwise, if it doesn't say that, you'd need to be using an even older PCI-only installation package.
I installed my E-MU on W10 22H2 before I moved to W11 23H2, same methods, and it worked. I'm on a ~2014 Dell Intel 4770 CPU. I did use modded Windows builds, doesn't seem like that'd make a difference between your results and mine.
Oh, did I miss that you're on a PCI card not PCIe, or did we just cross-post?. That seems like it could make a difference. I actually have a PCI card and a PCI slot - but I only tried it once long ago on W7. I use a PCIe card. I don't recall what the results were with the PCI card way back when, but no matter, doesn't seem like they'd be relevant to what you're doing now, on W10. But, in general, seems like getting the older PCI card to work well could pose an additional set of issues.
Note that I read not too long ago that the BETA driver is supposed to work for both PCI and PCIe - I think it says that in the readme file in the installation package. You might want to check that out and confirm. Info about that that you read in various places is inconsistent - I'd think if it says that in the installation package's readme file that that'd be the most reliable source of info... But otherwise, if it doesn't say that, you'd need to be using an even older PCI-only installation package.
-
- KVRist
- 36 posts since 5 Nov, 2012
I've been using the PCI card on another Windows 10 pro system. So if the driver in the install package has an issue with PCI or is intended for PCIe only, I think I would have encountered an issue on the old PC.
There's another modified set of install files on GitHub:
https://github.com/am-unklown/windows-d ... e-mu-audio
I am going to uninstall what I did thus far and try the GitHub installer.
There's another modified set of install files on GitHub:
https://github.com/am-unklown/windows-d ... e-mu-audio
I am going to uninstall what I did thus far and try the GitHub installer.
-
- KVRist
- 46 posts since 8 Nov, 2015
fyi, it does say that. Here's the opening text of the readme. And I've pasted the opening text of the readme for the other version, the non-beta, below that. Note the dates - beta says Feb 2010, the other says March 2011.eq1 wrote: Tue Apr 15, 2025 8:28 pm Note that I read not too long ago that the BETA driver is supposed to work for both PCI and PCIe - I think it says that in the readme file in the installation package. You might want to check that out and...
Code: Select all
Digital Audio Systems (DAS) Beta Driver version 2.3
Feb, 2010
This Beta driver applies to Windows XP, Windows Vista
Windows 7 32-bit and 64-bit versions.
This beta driver can be used with all E-MU PCI and
PCIe products:
0404PCI, 1212M PCI, 1616/1616M PCI, 1616/1616M CardBus,
0404PCIe, 1212M PCIe or 1616M PCIe Digital Audio System.
Should you encounter any difficulty with the installation,
please contact E-MU Customer Support at:
www.emu.com/support/custsup.asp
You should be aware of the following information before
installing the E-MU PatchMix DSP software and E-MU Digital
Audio System device drivers.Code: Select all
DAS Driver version Driver version 2.3
March, 2011
Thank you for purchasing the E-MU
0404/1212M/1616M PCIe Digital Audio System.
Should you encounter any difficulty with the installation,
please contact E-MU Customer Support at:
Should you encounter any difficulty with the installation, please contact E-MU Customer Support at: www.emu.com/support/custsup.asp
Or in : Japan at: http://japan.creative.com/support/contact/
You should be aware of the following information before
installing the E-MU PatchMix DSP software and E-MU Digital
Audio System device drivers.-
- KVRist
- 36 posts since 5 Nov, 2012
The one from Feb 2010 that specifically states it's for PCI is from GitHub I just got. The other one from March 2011 that only mentions PCIe is the installer on Pg1 of this thread?
GitHub installer ran okay. No safe mode necessary. I only got a warning about software not being signed, but I just selected to install anyway.
CTASIO Warning box is now gone.
In REAPER, at Preference > Device, I can select WaveOut and play a project with no odd noise whatsoever. --That suggests this is NOT a hardware issue with PCI because no matter what I selected if a hardware issue was present I wouldn't be able to play anything. I thought maybe it was the PCIe slot I'm using but if that was an issue I would still get noise using WaveOut.
But when I change the Audio system to ASIO, I can select "E-MU ASIO" for the audio driver, but again I'm getting the same result where I can play a file and hear it but I get noise every 3 seconds or so. This must be about how the E-MU ASIO driver is being installed or used while in REAPER.
GitHub installer ran okay. No safe mode necessary. I only got a warning about software not being signed, but I just selected to install anyway.
CTASIO Warning box is now gone.
In REAPER, at Preference > Device, I can select WaveOut and play a project with no odd noise whatsoever. --That suggests this is NOT a hardware issue with PCI because no matter what I selected if a hardware issue was present I wouldn't be able to play anything. I thought maybe it was the PCIe slot I'm using but if that was an issue I would still get noise using WaveOut.
But when I change the Audio system to ASIO, I can select "E-MU ASIO" for the audio driver, but again I'm getting the same result where I can play a file and hear it but I get noise every 3 seconds or so. This must be about how the E-MU ASIO driver is being installed or used while in REAPER.
Last edited by Aero312 on Tue Apr 15, 2025 10:02 pm, edited 5 times in total.