E-MU 1616M & Windows 10 Anniversary update incompatible

My DAW uses E-MU 1616m PCIe microdock. It’s been working with the E-MU Win 7 drivers for the past year.

Now, with the Win 10 update, the E-MU hardware drivers no longer work. Error 10.

There is no way to roll back to the pre-update restore point.

Thankfully I’m on a dual-boot system and can drop back to Win 7.

Driver: Creative Labs / E-MU E-DSP Audio Processor (WDM) version 6.0.1.1245

I don’t like when «upgrades» break something that’s been working.

Will Microsoft fix what it broke?

Replies (18) 

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

1 person found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

What has the manufacturer’s support team said about when they will release Windows 10 drivers for this hardware?

Nothing on their site says anything about support beyond Windows 7.

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

You are correct, mfg official support includes Win 7 but nothing later.

Other threads show that beta versions of Win 10 sometimes did, sometimes did not work with the Win 7 drivers.

The released version of Win 10 did, however, work with the E-MU Win 7 drivers.

Something in the anniversary update caused the drivers no longer to work. What would be good, is if Microsoft / Windows 10 allowed users to roll back to a previous version of the OS. A restore point to pre- update is not allowed.

My W10 setup used to work and now it does not. What changed? Software from Microsoft. What is broken, IMO, is allowing informed users to decide how their system is administered.

1 person found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Presumably, the manufacturer knows more about their product than anyone who is just guessing. You may want to follow their lead and use a supported OS.

Making changes to Windows 10, in support of unsupported hardware, makes no sense at all.

Your issues with your 32 bit hardware and an industry that is moving to 64 bit architecture are not surprising. We saw the same things when the industry moved from 16 to 32 bit. It is just time for you to catch up.

2 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

That was entirely unhelpful and abusive to the poster who was looking for a solution @srfreeman.

You think each new step forward doesn’t (and should by industry standard practice) also have backwards compatibility?Did you forget about Windows 7? Windows 8? Windows 8.1? Windows 10?!

I own a E-MU 1212m PCI, it is one of the best audio I/O & DSP cards for the money ever made!

For the most part, it still works in Windows 10. WDM via the card directly is iffy, I’m looking for a workaround.

Currently patching I/O out into MOBO’s audio input (or additional sound card) seems the only way to get windows to capture sound at the cost of introduced line noise.

So instead of trying to be toxic, actually provide at least some minor help like that above or move on.

In the 90s, the internet was filled with great and helpful people, now boards like this are filled with toxicity. It needs to stop. Post reported.

E-MU 1616M & Windows 10 Anniversary update incompatible

My DAW uses E-MU 1616m PCIe microdock. It’s been working with the E-MU Win 7 drivers for the past year.

Now, with the Win 10 update, the E-MU hardware drivers no longer work. Error 10.

There is no way to roll back to the pre-update restore point.

Thankfully I’m on a dual-boot system and can drop back to Win 7.

Driver: Creative Labs / E-MU E-DSP Audio Processor (WDM) version 6.0.1.1245

I don’t like when «upgrades» break something that’s been working.

Will Microsoft fix what it broke?

Replies (18) 

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

In Windows 10, updates are not optional. At licensing, the user agrees that their system will be ready to receive updates without further notice.

If you were allowed to simply roll back the update to a point where the unsupported accessory worked, when do you think you would install the update again?

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

E-MU PCI & PCI-e cards were originally designed for XP and older
and even XP had to be told «continue anyway» with the driver install
because E-MU did not want to pay the MS tax for WHQL certification
which the drivers would be rejected for refusing to follow DRM schemes

beginning with vista MS moved into monitoring all audio in the CPU and user mode audio stack, and the drivers for vista and 7 are just a kludge fix,

MS is on the path to «update» everyone out of their hardware
each subsequent oranguten version number renders more hardware «unsupported» AKA «dead»
we saw the rumblings of this during testing where the x64 could not be installed on some systems with P-IV processors of a specific generation.
meanwhile XP x64, Vista x64, Win 7 x64, and 8.x x64 would install on and run

1 person found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

KVR Audio

Pro Audio Forum — VST, AU, AAX Plugin and Audio Software Discussion

E-MU 1616m, 1212m, 1820m, 0404 Audio Interface — Complete Windows 10 (1903 & Above) Installation Guide

Post by sherwoodsound » Tue Jul 30, 2019 9:14 am

This is a complete guide to setting up the E-MU 1212m/1616m audio interface on Windows 10 version 1903 and above. It will work for both PCI and PCI-Express and should work with the E-MU 1820/1820m/0404 audio interfaces too but you may need to rename the 2 instances of your device name in the EMU_Driver_Fix script file. Huge thank you to ClubHouseKey, whose information saved my business from any downtime. The E-MU 1616m PCI-Express is the audio interface I have and I will never get rid of it unless there is absolutely no way to keep using it. Amazing piece of hardware! If any new updates are posted in this thread then this first post will be edited accordingly.

E-MU 1212m/1616m — Complete Install Guide for Windows 10 (1903 & Above)
*Please perform each task in the exact order listed.*

1. Download the E-MU_Windows_10_Install.zip file from https://1drv.ms/u/s!Ar-KCv7xikVOh23zeXTESuD8k2ih.
2. Extract the zip file to your main Windows 10 drive and change the name of the folder to » temp«. (C:\temp)
3. Remove all current E-MU Drivers and PatchMix software.
4. Install the EmuPMX_PCDrv_US_2_30_00_BETA drivers and RESTART INTO SAFE MODE by holding the shift key when clicking on Restart. Choose Troubleshoot, Advanced Options, Start-up Settings and click Restart. When the start-up options appear, press F4.
5. Once in safe mode right-click on the start button and open Windows PowerShell (Admin). Type into the PowerShell window

to run a modified version of ClubHouseKey‘s script. This will replace our windows files with the updated files. Performing this step in a normal Windows environment will either cause the script to not run at all due to script settings within Windows or some files will not get overwritten because they’re in use.

Restart Windows normally and then install the EmuPMX_PCApp_US_2_20_00 PatchMix Software.

You should now have successfully installed your E-MU Audio Interface.

If ASIO isn’t working then click on Start and type regedit and click on Registry Editor. Go to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run, right-click AsioThk32Reg and choose Modify. Change CTASIO.DLL to CTASIO64.DLL.

I hope this guide helps everyone that wants to keep their 1212m/1616m running.

Martin
Producer, Sherwood Sound Studios

Thank you for the kind words. I’m glad we’re all continuing to use our EMU audio interfaces far beyond their official OS compatibility. Maybe one day Creative will update us with a driver package that just contains the steps we have here, but I doubt it. As of 10th April 2021, this Installation Guide still works perfectly.

I just wanted to offer a few basic practices to keep your systems clean, fresh and working smoothly, especially when Windows 10 updates can ruin our EMU audio interfaces.

• Pause Windows Updates for the entire 35 days so you can update manually when not in a critical working period.
• Clean install Windows 10 (not as an update) via a USB stick at least once a year, or at your own convenience when a new Windows 10 version is released. This will keep your system running smoothly. Remember to backup your files stored on this drive first.
• Keep all non-OS/program files on a separate drive away from the Windows OS drive (C:). Not only will this improve performance, but it will also help if there is a failure on the OS drive.
• Backup any non-OS/program drive regularly, preferably after completing a project. If possible, run these drives in a RAID 1 array so if one drive fails you can replace it without losing data.

If this is any help to you at all, please leave a like.

Тема: Решение для аудиокарт E-MU (и не только) на Windows 10

Опции темы

Решение для аудиокарт E-MU (и не только) на Windows 10

Известная проблема, когда на ОС Windows 10 карты e-mu (PCI точно) могут работать только в режиме 48000, в других режимах звук отсутствует. Это касается WDM, через ASIO же доступен весь спектр частот. Соответственно, можно работать с наиболее ходовой частотой 44100. Но, такая же дискретизация будет автоматом выставлена и в windows, а не только в патчмиксе, что отключает весь остальной звук (браузерный, системный и т.п).

Соответственно, нам нужен софт, который принимает системный поток и выводит его через asio. На данный момент, мне известно о двух подобных программах, а именно: O Deus ASIO Link Pro и Voicemeeter. Первая более функциональна, но платная ($50), а вторая условно бесплатна, и так же прекрасно справляется со своей задачей.

Инструкция по настройке:

Re: Решение для аудиокарт E-MU (и не только) на Windows 10

День добрый. А J River Media Center не тестировали? Там тоже были средства по перехвату wdm потока и перенаправления на звуковую по asio.

Re: Решение для аудиокарт E-MU (и не только) на Windows 10

Нет, не пробовал. В принципе, джей ривер, это широкий комплекс, а voicemeeter или o deus более специализированные средства, ничего лишнего, так сказать.

Re: Решение для аудиокарт E-MU (и не только) на Windows 10

А в Windows 7 всё нормально работает?

Re: Решение для аудиокарт E-MU (и не только) на Windows 10

MAXIM_A в win 7 частоты выставляются все так что по данному вопросу в ней делать ничего не надо

Есть еще один вопрос для всех систем с большой (более 4 гб) памятью , при попытке вывести звук через HOST WAVE (нужен для SPECTRALAB и еще ряда программ)нормально работает только до 4 гб оперативной памяти , если использовать больший обьем то сигнала с него нет, были предложения искусственно ограничивать обьем используемой оперативки ( в этом случае все работает стабильно) , кто-нибудь заставил E-MU выводить звук на HOST WAVE с используемой оперативной памятью 8-16 гб?

———- Сообщение добавлено 24.01.2016 в 01.16 ———- Предыдущее сообщение было 23.01.2016 в 22.09 ———-

сам спросил , сам и ответил вообщем можно сделать следующее : скачать (в продолжение темы с того же сайта) http://vb-audio.pagesperso-orange.fr/Cable/index.htm ( Virtual Hi-Fi Cable And ASIO Bridge ) ,установить ну и далее на микшере вместо HOST WAVE отправляем HOST ASIO ну и потом на том-же спектралабе (или еще каких программах) в опциях входного устройства используем не Wave E-MU ,а hi-hi cabel output .

———- Сообщение добавлено 01.16 ———- Предыдущее сообщение было 01.16 ———-

———- Сообщение добавлено 01.21 ———- Предыдущее сообщение было 01.16 ———-

E-mu E-DSP soundcard problem after installing Windows 10

I have today (31/7) installed Windows 10, but my E-mu E-DSP soundcard isn’t working now. I’ve tried all the basic suggestions, but nothing has helped. The hardware IDs for the card are as follows:

PCI\VEN_1102&DEV_0008&SUBSYS_40051102&REV_00
PCI\VEN_1102&DEV_0008&SUBSYS_40051102
PCI\VEN_1102&DEV_0008&CC_040100
PCI\VEN_1102&DEV_0008&CC_0401

I’m not particularly PC-savvy, so any help explained in simple terms would be most welcome.

Replies (20) 

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Thank you for posting your query at Microsoft community.

Have you installed all the drivers after upgrading to Windows 10. If not then I would suggest you to visit the manufacturer website and download and install all the drivers including network and graphic drivers. Please check if there are any pending Windows updates and install them as well.
You may also run the in-built troubleshooter and check if it helps. Type control panel on the search tab in the task bar>type control panel> on the search tab(top right corner)>type troubleshooting> on the right>click on view all>choose hardware and devices> follow the on screen steps.
Please let us know how it goes.

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thanks, Rohit, for your response. However, I eventually decided to revert to Windows 7. This was partly because I didn’t think Windows 10 was all it was cracked up to be, but mainly because in the meantime I had read up on the multitude of privacy issues with W10 (and I was already annoyed at having to constantly sign in and to have a ‘Microsoft identity’). I even (finally. ) managed to connect to a Microsoft technician, but he turned out to be the most clueless individual I have ever come across — that’s three hours of my life I could have spent more productively. He didn’t resolve my issue and he disconnected before explaining why he hadn’t been able to. Ignorant ****.

In the end, I managed to find the original installation disk for my soundcard, so was able to do the uninstal/reinstall process, which worked fine. I’m sure that this would have worked in Windows 10 too. I thought I didn’t have the disk, so was very relieved to find it, especially as my soundcard is no longer supported on the Creative website.

So to anyone having the same issue I would say find your original soundcard driver/software disk, uninstall the current version on your machine and then reinstall from the disk. Hope that works for everyone.

10 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

12 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

The only thing I can think of is try downloading the Windows 8.1 drivers (32bit or 64 bit depending) directly from the sound cards website.

I use an M-Audio soundcard that Is working as expected in Win 10 that had no drivers for it other than Win 8.1 drivers and they are working just fine.

Shutdown the computer, remove the card & reboot.

open a command prompt as admin and type.

Set Devmgr_show_nonpresent_devices=1 (and hit enter)

Devmgmt.msc (and hit enter)

Under view, select «Show hidden devices»

Go to Sound, video and game controllers, right click delete ALL GREYED OUT devices, maybe even expand all entries and look for the EMU card and do the same, but for NOTHING else

Find the card, right click uninstall and make sure to select uninstall device drivers if that option is presented (and it should for some of the entries.

Reboot the machine. Shut the machine down, install the card, boot, install Win 8.1 drivers.

Hope that helps

3 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

12 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

4 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I also ran into problems with my E-MU E-DSP card (1212M PCI, v1) after upgrading to Windows 10. I’ve looked around the web and seen several folks with the same issue. No matter how you install the drivers, the cards only work for Windows WDM (MME for some programs) with the sample rate set to 48kHz, (44.1, 88, 176 and 192 kHz will not work with Windows).

E-MU has discontinued these products and all driver development. The last set of drivers were from 2011 and they worked flawlessly for me under Windows 8.1. They install under Windows 10 but work as described above.

One caveat is that ASIO input/output still works fine so if you’re using an audio program that supports the E-MU ASIO drivers, you’re ok. I also found that the music player program foobar2000 works ok if you use its old «kernel streaming» output component.

As for using programs that support WDM or MME, I found a workaround for my specific system. My motherboard’s built-in Realtek HD audio features an optical S/PDIF output. I connected a toslink optical cable from it to the ADAT optical input on my 1212m card. I then opened the Patchmix Session Settings dialog box and in the I/O tab switched the Optical Input setting to S/PDIF. Then in Patchmix, I added a S/PDIF input strip.

This works perfectly. I usually work in a sample rate of 88.2 kHz. although the Realtek driver only supports 96kHz output, the E-MU card accepts both 88.2 and 96kHz signals when set to 88.2. Thus, my Windows WDM and MME sound is output via the optical S/PDIF and into the 1212M where it plays back perfectly. At the same time my ASIO programs work fine.

So this works for me. E-MU will obviously not be doing any new drivers for these products, so I’m hoping Microsoft will fix whatever they did in Windows 10 audio that caused the E-MU drivers to stop working. As I wrote above, they worked perfectly on my system with Windows 8.1 64-bit.