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

[rawl747]

speedymonk
KVRer
Contact speedymonk
4 posts since 15 Jul, 2020
Unread post Wed Jul 29, 2020 11:08 pm

Thanks for the input. I have a number of synth keyboards and tone modules I will be using to record into my DAW. The 1820m fits that bill. It works on Windows 10 1709 but I will get everything going full steam when I assemble all the new parts and run an intel i910900K processor. Have a PCIe to PCI adapter card that I know works. Doing it this way I shouldn't need any future machine upgrades for another 10 years (perhaps wishful thinking).

Still wondering if anyone on Windows 10 has got 96K or 192k to show up and work.

I will have to fire up the old PC with my 1820m to test the sampling rate for 96k or 192k. If I get a chance this weekend I will try to see on mine.

Rawl

[speedymonk]

Thank you.

[HURRICANEBOB]

So, I finally gave up on Windows 7, as I could not get Emulator X to authenticate from the original installation disc. I really wanted that (amazing)software, and use all of the sound banks as VST instruments in Cubase SX. I bit the bullet, wiped the computer and did a clean install of Windows XP Professional with Service Pack 3. Everything went flawlessly, except for the fact that it wouldn't connect to the internet using Windows Internet Explorer. Funny thing is, it would connect to bing.com and msn.com only. After a half day trying to figure this out I finally installed Firefox and it connected to the internet through my wireless LAN card without a hitch. Go figure! It turns out that this was due to the newer SSL security protocols... (I wanted to be able to connect to the internet so that I could install updates...) Installed the Emu 1212M sound card with daughter board, then Cubase SX2 with all the pertinent updates. I have the ASIO drivers set to 5 milliseconds with no problems at all. It's truly incredible that audio recording has remained virtually unchanged while video has rampantly changed over the last fifteen years. Everything that I could possibly need is there (except for the latest soft synths, of course...) and the fidelity is phenomenal. After all these years in storage I feel like a kid with a new toy!

[speedymonk]

Re-checked windows 7, 8 , XP 64 and windows 10 1709. Card works, but ONLY at 44.1 resolution. Using the latest BETA driver and Patch Mix 2.1 (2.2 makes no difference). Disappointing. Only sound card that has been on the drives. If I can't get this to go to at least 48.1 (using analogue L/R inputs and outputs) I may invest in a Focusrite Claret. Don't want to have to do that. Any tips/tricks?

[l_maseroni]

Hello friends, I have my 1616 working on windows 7 well for now. I hope to continue like this. Something that I find very annoying is not having a knob for the main mix. How have they solved it? I have a mackie vlz micro series console, I have connected the monitor output of the 1616 to the tape in of the console but it is an unbalanced connection. Should I invest in a monitoring control?

[rawl747]

Re-checked windows 7, 8 , XP 64 and windows 10 1709. Card works, but ONLY at 44.1 resolution. Using the latest BETA driver and Patch Mix 2.1 (2.2 makes no difference). Disappointing. Only sound card that has been on the drives. If I can't get this to go to at least 48.1 (using analogue L/R inputs and outputs) I may invest in a Focusrite Claret. Don't want to have to do that. Any tips/tricks?

Haven't gotten that old DAW machine out of the "closet" yet but I noticed you mentioned Focusrite. I went with a Scarlett 18120 when I went to a laptop as my DAW machine. I went with this for several reasons. First, it had MIDI In and Out and second it had a mixer GUI somewhat similar to the PatchMixDSP GUI for my 1820m. Plus the Focusrite can actually work without being connected to the PC. Their ASIO drivers are not bad and Focusrite as opposed to Creative, continues to support my "1st Generation" 18i20 even though they are onto the 3rd Generation now.

If I were going to rely on my 1820m, I would seriously think about going back to Windows 7 and just firewall that machine off from the internet so the lack of security updates for Win 7 would no longer be an issue.

Rawl

[speedymonk]

Thanks. I will likely bite the bullet for the Scarlett. Also has Midi I/O. There are some used ones which have Thunderbolt (probably 2). I don't need a huge number of inputs as I utilize a Mackie LM-3204 line mixer for my keyboards and synths. I have plenty of DSP power in all of those synths and keyboards combined so VSTs will be a very minor issue. Perhaps with drums.

I am trying to get away from having two separate computers. One new machine. Will have two distinct drives with Windows 10. One will be disabled for updates and be for audio recording only. The second on I will clone from my existing all-purpose Windows 10 drive. And the new Z490 motherboards for the Intel 10th gen chips will only support Windows 10. So "progress" appears to be forcing my hand. It will be a very nice and fast machine when it is finished. Waiting for the i9 10900K processor to become available at a decent price. I understand mid-September to early October would be a good time. to purchase. If not, I'll go with the i7 10700 at $400 or less. Availability, hopefully lower pricing and bios updates for the Z490 boards will be ready. I will also have my cash saved. I will also sign for an Amazon credit card. I can get the motherboard for $100 off as a result. Perhaps buy other stuff if less than New Egg or B&H, pay off the card and then cancel it. We will see.

Really wanted the EMU to work, but ..... time marches on. If I can get the 48k to work I might keep it for my needs. However, something with native 64 bit seems to be better...and no work-arounds.

[rawl747]

Speedymonk,

You are the second person I know with an Emu interface and a Mackie LM-3204 mixer! I thin you will like the Scarlett.

Rawl

[speedymonk]

Thank you. Love them both. Looks like the Scarlett will be moving in once I get the machine configured, etc. Thanks for the help. I am surprised that 48k doesn't work.Can't record or hear any sound. Maybe if I hooked a spdif to the keyboard. Anyway.... will make that audio final choice a little later.

[Easy_Does_It]

1616m user here, I have been struggling with recording daw output into OBS quite a bit. I now use this method

Thank you very much for the tip! Always open to new suggestions. I've actually tried different "virtual cable" options, including VoiceMeeter, in this process. I hadn't tried Reastream yet, and since I use Reaper anyway, it seemed like a great idea. Unfortunately, attempting to load Reastream as a filter results in OBS crashing every time. After searching a lot, I have yet to find a solution that works.

You inspired me to do some more research, and I stumbled on another similar method using Rearoute (another Reaper plugin). Here's the video for that:

Notice in the comments of the video, someone mentions having to also install the OBS "ASIO plugin". I did that, and sure enough, ASIO became an option in the Audio Capture menu in OBS. The link for that is here: https://github.com/Andersama/obs-asio/r ... ag/v2.0.2b

Using this method, I was able to connect Rearoute to OBS - I was finally getting my DAW audio piping into OBS! Wow! No virtual cable required! Ah but.. there's always a "but". Turns out, I listened back to the recorded video, and the audio is useless! The audio is coming in digitally garbled/distorted. Ugh...

So after playing with every possible setting in OBS, Rearoute, and Reaper, I still can't get that issue resolved. Everything is at the same sample rate of course, but I have a theory that it has something to do with the fact that my Windows and Reaper are 64-bit, but the E-mu Patchmix is 32-bit. The only other thing I can think is that maybe bitrate is an issue. But no setting in OBS or Reaper seems to make the problem go away.

In conclusion, I'm closer than I've ever been to this ridiculously elusive goal that seems like it should be simple to solve. If anyone has any other suggestions, I'm all ears. In any case, I wanted to report back my findings for everyone's information and thank you for your help.

[speedymonk]

Quick question. Thos of you who have the 1820m interface installed, if you get 48k or 96k, are you using digital SPDIF or analog or a combination of both. When using analog and opening a new session and selecting 48k, I am not I have insufficient hardware and am not even allowed an dock or Stereo 1,2 option. SPDIF or ADAT only.

[auron]

1616m user here, I have been struggling with recording daw output into OBS quite a bit. I now use this method

So after playing with every possible setting in OBS, Rearoute, and Reaper, I still can't get that issue resolved. Everything is at the same sample rate of course, but I have a theory that it has something to do with the fact that my Windows and Reaper are 64-bit, but the E-mu Patchmix is 32-bit. The only other thing I can think is that maybe bitrate is an issue. But no setting in OBS or Reaper seems to make the problem go away.

In conclusion, I'm closer than I've ever been to this ridiculously elusive goal that seems like it should be simple to solve. If anyone has any other suggestions, I'm all ears. In any case, I wanted to report back my findings for everyone's information and thank you for your help.

So have you tried in your patchmix to put a send onto the asio strip sending it to the wave in (wave in means the mme/wave input for windows)? I think there is only one send available in patchmix. I use this all the time for giving me a loopback functionality.

Edit: forget it, same issue. And i tried it also with screen recorder from power director. Garbled sound as well. So this means the wave driver is not reliable enough. With my Yamaha AG 03 soundcard no problem ever with sort of this recordings.

[FJazz]

Hello,

I'm new here and good to read that I can maybe can get back my EMU 1820M back to work again.
I have followed all the needed instructions and as far as I can see no MB or Win10 errors ACCEPT I cannot use ASIO on Cubase 10.5. I get this error: Recording Error: ASIO driver is not running.

My PC specs:

Operating System: Windows 10 Pro 64-bit (10.0, Build 18363) (18362.19h1_release.190318-1202)
Language: Dutch (Regional Setting: Dutch)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: H61M-D2H-USB3
BIOS: Award Modular BIOS v6.00PG (type: BIOS)
Processor: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz (8 CPUs), ~3.8GHz
Memory: 16384MB RAM
Available OS Memory: 16368MB RAM

-------------
Sound Devices
-------------
Description: Luidsprekers (4- High Definition Audio Device)
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0889&SUBSYS_1458A002&REV_1000
Manufacturer ID: 1
Product ID: 65535
Type: WDM
Driver Name: HdAudio.sys
Driver Version: 10.00.18362.0356 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 4-9-2019 00:00:00, 425472 bytes
Other Files:
Driver Provider: Microsoft
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

Description: Luidsprekers (E-MU E-DSP)
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: PCI\VEN_1102&DEV_0004&SUBSYS_40011102&REV_03
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: ctaud2k.sys
Driver Version: 6.00.0240.0026 (English)
Driver Attributes: Final Retail
WHQL Logo'd: No
Date and Size: 23-2-2010 00:00:00, 712832 bytes
Other Files:
Driver Provider: Creative
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
=====
In the screenshot the cubase error and screen of patchmix

Please help me out with my ASIO issue so hopefully I can use my 15 year old EMU 1820M again

[tlainhart]

Sorry that I can't help with specifics here. Except to perhaps give you hope, as I'm using an 1820m with an older Gigabyte MB, Windows 10, Cubase 10.5 (and other Steinberg products) and can use the E-MU ASIO driver.

I'm not using the very latest Windows 10 update (having disabled updates), but am using the update that caused all of the trouble with the E-MU/Creative drivers that we've been discussing.

If you're able to use audio through the the E-MU DSP, then I think that you're almost there - there's some other conflict going on that's not allowing 10.5 to see the driver. I would try some other ASIO-enabled products to see if that offers a clue.

[rawl747]

FJazz
KVRer
Contact FJazz
1 posts since 18 Aug, 2020
Unread post Sat Aug 22, 2020 7:56 am

Hello,

I'm new here and good to read that I can maybe can get back my EMU 1820M back to work again.
I have followed all the needed instructions and as far as I can see no MB or Win10 errors ACCEPT I cannot use ASIO on Cubase 10.5. I get this error: Recording Error: ASIO driver is not running.

My PC specs:

Operating System: Windows 10 Pro 64-bit (10.0, Build 18363) (18362.19h1_release.190318-1202)
Language: Dutch (Regional Setting: Dutch)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: H61M-D2H-USB3
BIOS: Award Modular BIOS v6.00PG (type: BIOS)
Processor: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz (8 CPUs), ~3.8GHz
Memory: 16384MB RAM
Available OS Memory: 16368MB RAM

-------------
Sound Devices
-------------
Description: Luidsprekers (4- High Definition Audio Device)
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0889&SUBSYS_1458A002&REV_1000
Manufacturer ID: 1
Product ID: 65535
Type: WDM
Driver Name: HdAudio.sys
Driver Version: 10.00.18362.0356 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 4-9-2019 00:00:00, 425472 bytes
Other Files:
Driver Provider: Microsoft
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

Description: Luidsprekers (E-MU E-DSP)
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: PCI\VEN_1102&DEV_0004&SUBSYS_40011102&REV_03
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: ctaud2k.sys
Driver Version: 6.00.0240.0026 (English)
Driver Attributes: Final Retail
WHQL Logo'd: No
Date and Size: 23-2-2010 00:00:00, 712832 bytes
Other Files:
Driver Provider: Creative
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
=====
In the screenshot the cubase error and screen of patchmix

Well...

>Description: Luidsprekers (4- High Definition Audio Device)
This is your "regular" audio - no ASIO.

>Description: Luidsprekers (E-MU E-DSP)
This SHOULD BE your Emu but this driver:

>Driver Name: ctaud2k.sys

I believe is the replacement driver that Microsoft Windows Update put in place of the Creative Professional driver you need to be installed for ASIO under Cubase.

You stated that you followed all the directions but were they the ones originally from ClubHouseKey? If so, did you modify them to use the _0019 version (XFTI_PCDRV_L11_2_40_0019.exe) of the X-Fi Titanium drivers? The last Win 10 update seemed to make the _0018 version of the X-Fi drivers no longer load properly.

The only way I know of getting a working ASIO driver working again is to follow the instructions from ClubHouseKey that include a PowerShell script and drivers for the X-Fi Titanium using this last version of the drivers. Even that may not be enough.

Looking at the Creative Pro site for X-Fi Titanium support and drivers, Creative considers the X-Fi Titanium line as an "Archived" product. This may mean no more updates to the drivers for this card. There are also posts on Reddit about actual X-Fi Titanium owners having the same sort of driver problems following Windows update 1909. If there is no fix from Creative to the X-Fi Titanium drivers for the 1903 and subsequent Win 10 updates then since these are the source of the drivers that we have used to "patch" the 1820 and 1616 drivers I suspect we will all be out of luck going forward.

Clubhousekey did post about this set of drivers:

XFRL_PCDRV_L11_3_00_2022.exe:
https://support.creative.com/downloads/ ... dId=100264

But I haven't tried them yet and therefore have not modified the scripts to reference them.

In case you didn't know, the reason why the X-Fi Titanium drivers have worked as a source for this patch is that the Titanium interface line used the same chipset that these old Emu cards used.

But typical of Creative, I expect they will abandon support for the X-Fi Titanium line just like they did with the Emu line. That is why I plan to never buy another Creative product by choice.

The RAR package of driver files, modified PowerShell scripts for both the _0018 and _0019 driver files, CSV files for both driver sets and some instructions are still available for download:

https://www.mediafire.com/file/gxbi032yye7a9ab/temp.rar

If I get a chance, I will check out the _0022 drivers although the name of the file

XFRL_PCDRV_L11_3_00_2022.exe
versus
XFTI_PCDRV_L11_2_40_0019.exe

May or may not indicate hardware differences.

And Yes, my old 1820m PC is failing to provide ASIO drivers in Cubase once again after it's last Win 10 update.

Now you may realize why I have a Focusrite Scarlett 18i20 for my current DAW workstation :-}

Rawl


Rawl