KVR Audio

FJazz · Post by **FJazz** » Sun Aug 23, 2020 9:23 am

Hello Rawl,

First THANKS ALL for the SUPER GOOD work on this forum!
Hopefully Creative will come up with some solid Win10 drivers for all the EMU (OLD) sound cards.

I'm really not a computer/windows wizzard but a musician that want to record audio with Cubase 10.5

In the screenshot I have some questions, when you reply on that I will clear all creative drivers/dirs etc and run the all README steps from ClubHouseKey once again.
Hopefully

that will fix the cubase ASIO issue.

I will reply what happend after the clean install.

FJazz

speedymonk · Post by **speedymonk** » Sun Aug 23, 2020 2:06 pm

You circled the info from clubhousekey's fix. Go to your device manager and see what it says. Mine said E-MU E-DSP only. If yours is that way, edit the script file to reflect that. Delete the Audio Processor(WMD) section in both instances. Keep the quotation marks. Save the file. Whatever your device manager says it is, edit the script file to reflect that.

rawl747 · Post by **rawl747** » Sun Aug 23, 2020 6:16 pm

speedymonk
KVRer
Contact speedymonk
15 posts since 15 Jul, 2020
Unread post Sun Aug 23, 2020 10:06 am

You circled the info from clubhousekey's fix. Go to your device manager and see what it says. Mine said E-MU E-DSP only. If yours is that way, edit the script file to reflect that. Delete the Audio Processor(WMD) section in both instances. Keep the quotation marks. Save the file. Whatever your device manager says it is, edit the script file to reflect that.

There are currently 4 PowerShell scripts in my "extended" download. There are 2 scripts for the "long name" and 2 scripts for the "short name". One each "long name script" that uses _0018 X-Fi drivers and One each that uses _0019 X-Fi drivers.

So, no editing of scripts is needed if you are using my extended version download.

I will be also uploading and providing a link to a new extended version that included the XFRL_PCDRV_L11_3_00_2022 drivers. These are for the X-Fi HD interface. As soon as I am able to test these, I will upload the revised download. It will include six (6) PowerShell scripts - a "long name script" and a "short name script" for the XFRL_PCDRV_L11_3_00_2022 drivers along with a new CSV file that contains the list of files that get copied.

Re: EMU 1212m/1616m on Windows 7 - The Thread to End All Other EMU Threads!
by FJazz » Sun Aug 23, 2020 5:23 am

Hello Rawl,

First THANKS ALL for the SUPER GOOD work on this forum!
Hopefully Creative will come up with some solid Win10 drivers for all the EMU (OLD) sound cards.

I'm really not a computer/windows wizzard but a musician that want to record audio with Cubase 10.5

In the screenshot I have some questions, when you reply on that I will clear all creative drivers/dirs etc and run the all README steps from ClubHouseKey once again.
Hopefully that will fix the cubase ASIO issue.

I will reply what happend after the clean install.

FJazz

FJazz,

Thanks. Please see the reply above to "speedymonk".

If a clean install works then great. But I will be uploading a new version of my "extended" download that will include newer drivers. I suggest until then that you choose the "long name script" if you still are showing the extended Device name as your screenshot showed.

Rawl

FJazz · Post by **FJazz** » Sun Aug 23, 2020 9:29 pm

Thanks Speedmonk and Rawl

,

@Rawl, I will wait untill the "new version with the newer drivers" are available to download

that this version will be the final 1 after that I will turn OFF Windows Update!

FJazz

FJazz · Post by **FJazz** » Mon Aug 31, 2020 8:42 am

Hello Rawl,

How is it with the new version with the "XFRL_PCDRV_L11_3_00_2022 drivers"?
It would be sooo nice to use Asio within Cubase again

Thanks and keep up the good work

speedymonk · Post by **speedymonk** » Mon Aug 31, 2020 2:13 pm

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. My real world and the manual seem to differ. I'd like to know how you circumnavigated this. Thank you. (I also posted on the EMU page to cover my bases).

rawl747 · Post by **rawl747** » Mon Aug 31, 2020 3:36 pm

FJazz
KVRer
Contact FJazz
4 posts since 18 Aug, 2020
Unread post Mon Aug 31, 2020 4:42 am

Hello Rawl,

How is it with the new version with the "XFRL_PCDRV_L11_3_00_2022 drivers"?
It would be sooo nice to use Asio within Cubase again

Thanks and keep up the good work

I worked on this over the weekend and am still struggling to get the drivers to properly load. I had previously created a group policy to prevent updates to the Emu drivers and had to disable that before I could re-install any drivers. So to those that have put such a policy in place and still need to re-install Emu drivers, remember to disable the policy until you have successfully re-installed the drivers and then re-enable the policy. Details on creating such a policy can be found here:

https://www.maketecheasier.com/block-dr ... windows10/

Among other places.

I re-installed and now the driver has a triangle with an exclamation point over it next to the "E-mu DSP" device in "Devices". I have encountered similar issues in the distant past having to do with IRQ conflicts with other PCI cards plugged into the motherboard. The E-mu 1010 card that is part of my 1820m interface does not share IRQ's "well" with others. I recall having to pull other cards from the PCI bus, fire the PC back up and install the original drivers and then after powering down, re-insert the other PCI cards. This would force the E-mu 1010 card to have priority over the IRQ's it needed and wouldn't share and the re-inserted cards had to find other IRQ's to operate. I hope this is not what is happening now since I really don't want to have to take this box apart.

I can post what I have and let you tinker with it if you want since I have other things on my plate as well. Let me know if you want me to do that.

Rawl

rawl747 · Post by **rawl747** » Mon Aug 31, 2020 3:43 pm

speedymonk
KVRer
Contact speedymonk
19 posts since 15 Jul, 2020
Post Mon Aug 31, 2020 10:13 am

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. My real world and the manual seem to differ. I'd like to know how you circumnavigated this. Thank you. (I also posted on the EMU page to cover my bases).

Do you have ASIO drivers for your E-mu 1820m showing up in your DAW software? If not then this could explain the issue with no 48KHz mode support. My recollection regarding the Microsoft replacement drivers is that they only support 44.1KHz and there is no ASIO driver as part of them. If memory serves, I could switch between 44.1 and 48 modes with the last working patched drivers which of course include a working ASIO driver.

As I mention in my post to FJazz, I have been working on re-installing the drivers for my 1820m and am still struggling with that process. My intent is to test the _0022 drivers but so far I am still fighting the good fight.

Rawl

speedymonk · Post by **speedymonk** » Mon Aug 31, 2020 4:21 pm

1. Yes for ASIO drivers

Thank you.

rawl747 · Post by **rawl747** » Tue Sep 01, 2020 5:04 am

FJazz (and everyone else following),

My test of the _0022 drivers failed. When I copied them over using the PowerShell script, I got the triangle with a ! over the top of it next to the E-mu DSP device entry in Devices under the "Sound, video and game controllers entry. When i re-ran the script for the _0019 drivers everything came back to normal or as normal as it will ever be with Windows 10 update 1909.

I did have to make the Registry edit for the CTASIO64 driver. I also ran it manually from an Command Console "As Administrator" using the same command that is in the "Run" entry. After that the E-mu ASIO drivers showed up in 64 bit Cubase 10.

speedymonk,
I can switch between 44.1 and 48KHz with no problems. My 1820m never had any other rate displays other than these two. It never had a 96KHz rate available on its front panel.

I will now re-enable the Group Policy to prevent these drivers from getting automatic updates from Microsoft.

The bottom line is that the _0019 drivers still seem to work with Windows 10 Build 1909. There is a new feature update that I have snoozed for 365 days...

I will upload a new set of files that have some minor typographical changes but the previous set of files should still work until I clean up the files and upload them.

Cheers,
Rawl

tlainhart · Post by **tlainhart** » Tue Sep 01, 2020 12:59 pm

rawl747 wrote: Tue Sep 01, 2020 5:04 am
I will now re-enable the Group Policy to prevent these drivers from getting automatic updates from Microsoft.

Hi Rawl -

I've disabled automatic updates in general in my Windows 10 installation (after the update that killed our drivers, then remediated with clubhousekey and your guidance). Are you saying that there's a Group Policy that can be modified that will disallow the update of the CT drivers, while allowing other Windows updates to proceed?

Thanks -- Todd

rawl747 · Post by **rawl747** » Tue Sep 01, 2020 2:55 pm

tlainhart » Tue Sep 01, 2020 8:59 am

rawl747 wrote: ↑Tue Sep 01, 2020 1:04 am

I will now re-enable the Group Policy to prevent these drivers from getting automatic updates from Microsoft.
Hi Rawl -

I've disabled automatic updates in general in my Windows 10 installation (after the update that killed our drivers, then remediated with clubhousekey and your guidance). Are you saying that there's a Group Policy that can be modified that will disallow the update of the CT drivers, while allowing other Windows updates to proceed?

Yes, I AM saying that. The link I provided showed how to do this. You have to start up the group policy editor - gpedit to do so. You will need the "Hardware ID's" from the E-mu DSP device which you can get from Device Manager. You paste these into the box of ID's for which you wish to turn off updating in gpedit. This will inhibit any updates for drivers for the hardware id's entered. There are 4 Hardware ID's for the E-mu DSP drivers.

Here is the link to the web page describing how to enable such a group policy:

https://www.maketecheasier.com/block-dr ... windows10/

So, if you have this policy enabled for your Emu and you then need to re-install the drivers for it for any reason later, you will need to disable this policy before you can re-install the drivers. Otherwise, the driver installation program will run but nothing actually gets installed.

Also, the Win 10 updates that seem to cause the most trouble are the feature updates that come out every spring and fall. Feature updates can be delayed for up to 365 days. Security updates probably should not be turned off...for security reasons.

Rawl

tlainhart · Post by **tlainhart** » Tue Sep 01, 2020 3:37 pm

rawl747 wrote: Tue Sep 01, 2020 2:55 pm
tlainhart » Tue Sep 01, 2020 8:59 am

rawl747 wrote: ↑Tue Sep 01, 2020 1:04 am

I will now re-enable the Group Policy to prevent these drivers from getting automatic updates from Microsoft.
Hi Rawl -

I've disabled automatic updates in general in my Windows 10 installation (after the update that killed our drivers, then remediated with clubhousekey and your guidance). Are you saying that there's a Group Policy that can be modified that will disallow the update of the CT drivers, while allowing other Windows updates to proceed?
Yes, I AM saying that.

...

Also, the Win 10 updates that seem to cause the most trouble are the feature updates that come out every spring and fall. Feature updates can be delayed for up to 365 days. Security updates probably should not be turned off...for security reasons.

Rawl

Excellent - thank you!

I know that I eventually will have to update Win10, but I was thinking that I would/should upgrade my interface as well - most likely one of the Focusrites you've been recommending. That you're an 1820m and Patchmix user, and that you've moved to Focusrite satisfactorily narrows the field for me.

-- Todd

auron · Post by **auron** » Wed Sep 02, 2020 5:44 pm

rawl747 wrote: Tue Sep 01, 2020 5:04 am FJazz (and everyone else following),

My test of the _0022 drivers failed. When I copied them over using the PowerShell script, I got the triangle with a ! over the top of it next to the E-mu DSP device entry in Devices under the "Sound, video and game controllers entry. When i re-ran the script for the _0019 drivers everything came back to normal or as normal as it will ever be with Windows 10 update 1909.

Cheers,
Rawl

I tried the _0022 drivers as well and it didnt work, but the _0019 does. But have a closer look to the files , in the _0022 driver folder there are files missing look at the picture. A lot of them are those .dat files which are also in that csv-list. So maybe that folder must be mixed together with the _0019 folder.

By the way i am using a EMU 1820m on a MSI PC Mate mainboard (B350) which can work with old pci cards.

rawl747 · Post by **rawl747** » Wed Sep 02, 2020 5:49 pm

OK Gang,

Here is the latest version of the Temp.rar file for Emu interfaces:

http://www.mediafire.com/file/3wqxm6tkm ... p.rar/file

I made some minor corrections to the scripts and to the README.txt file. But after testing the "XFRL_PCDRV_L11_3_00_2022 drivers" FJazz asked about I decided not to include them since I couldn't get any success with them. It appears that these are for a slightly different variant that uses the same X-Fi Titanium "name" but includes an "HD" in that name when looking on the Creative support web site pages. There is apparently enough difference that makes them unusable for our purposes.

I did however find out that the "XFTI_PCDRV_L11_2_40_0019" drivers do still work on my Windows 10 Update 1909 system. I also determined two other things in my testing:

1. Both 44.1KHz AND 48KHZ modes work on my 1820m interface and I can easily switch between them using the PatchMixDSP GUI program.

2. Wave audio from the PC DOES show up in the PatchMixDSP GUI AND in Cubase with the ASIO driver loaded.

I also determined that under the Windows 10 Device Manager E-mu shows up in two different places:

1. "E-mu DSP" shows a single entry under "Sound, video and game controllers". This is the actual hardware driver entry.

2. Under "Audio inputs and outputs" two entries appear AFTER the PatchMixDSP GUI properly loads:
a. Speakers (E-mu DSP)

b. Wave (E-mu DSP)

If you don't get both of these showing up then perhaps that is why some of you aren't able to get Wave audio from other applications showing up in PatchMixDSP. I tested it with a video file playing in VNC media player.

For those of you who wish to create a group policy that will prevent your E-mu drivers from getting updated automatically by Windows 10 updates here is a link to the tutorial I followed to create and enable one on my system:

https://www.maketecheasier.com/block-dr ... windows10/

My 1820m lives on and your E-mu interface should be able to as well.

Rawl