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

[auron]

So when you say "almost perfectly", can you record at higher resolution than 44.1? I can't. Wants me to go to ADAT. If you can record at higher resolution, can tell me how you have set the routings? Would like to go up to 96K at times. I am running the 1820 m. audio feeds from my Mackie LM3204 mixer to the 1820 m 1L/1R inputs and then out to the amplifier.

Thank you.

Hello,
I have tried up to 96K and it is working. I use the Product Default session. I have my mixer going into Line A, LineB, 1L/1R and 2L/2R which output to ASIO 1/2 - ASIO 7/8.
I use ProTools and these input show up in the I/O and are all selectable. The only thing I had to change was the output bus in ProTools. The 48k patchmix session uses ASIO out 31/32 by default and the 96k session uses 15/16.

Sorry if that wasn't very helpful.
I can record and playback in ProTools and everything sounds great. I just want to be able to use the Wave L/R out to send to Skype or whatever without having it just be buzzing and crackling.

Well, I must be cursed on this thing. I use the product defaults and yet get the red lines/red out on the channel strips such as 1L/1R, etc. My mixer goes into 1L/1R. Even switched to 3?l/3R and no go. Unable to go a routing. I get 44.1 and no more.

Using 17 10700K, Gigabyte Z490 vision D, 1T NVME 2 drive, Cakewalk by Bandlab, Soundforge 14. Can record MIDI and audio into Bandlab no problem, as long as it is 44.1. Same with Soundforge. Anything else...nada.

I have 2l/2R inputs from computer to listen to you tube, etc. No issues. all inputs routed to Outputs 4 (stereo) as suggested to monitor.

Do you have any spdif or adat strips on your patchmix session? Long ago someone mentioned if you have any issues with sample rates , dont occupy your patchmix with unnecessary strips . It could reduce issues. Another issue would be , that every time you select default patchmix session, it will give you at least 1 spdif strip as well.

[speedymonk]

So when you say "almost perfectly", can you record at higher resolution than 44.1? I can't. Wants me to go to ADAT. If you can record at higher resolution, can tell me how you have set the routings? Would like to go up to 96K at times. I am running the 1820 m. audio feeds from my Mackie LM3204 mixer to the 1820 m 1L/1R inputs and then out to the amplifier.

Thank you.

Hello,
I have tried up to 96K and it is working. I use the Product Default session. I have my mixer going into Line A, LineB, 1L/1R and 2L/2R which output to ASIO 1/2 - ASIO 7/8.
I use ProTools and these input show up in the I/O and are all selectable. The only thing I had to change was the output bus in ProTools. The 48k patchmix session uses ASIO out 31/32 by default and the 96k session uses 15/16.

Sorry if that wasn't very helpful.
I can record and playback in ProTools and everything sounds great. I just want to be able to use the Wave L/R out to send to Skype or whatever without having it just be buzzing and crackling.

Well, I must be cursed on this thing. I use the product defaults and yet get the red lines/red out on the channel strips such as 1L/1R, etc. My mixer goes into 1L/1R. Even switched to 3?l/3R and no go. Unable to go a routing. I get 44.1 and no more.

Using 17 10700K, Gigabyte Z490 vision D, 1T NVME 2 drive, Cakewalk by Bandlab, Soundforge 14. Can record MIDI and audio into Bandlab no problem, as long as it is 44.1. Same with Soundforge. Anything else...nada.

I have 2l/2R inputs from computer to listen to you tube, etc. No issues. all inputs routed to Outputs 4 (stereo) as suggested to monitor.

Do you have any spdif or adat strips on your patchmix session? Long ago someone mentioned if you have any issues with sample rates , dont occupy your patchmix with unnecessary strips . It could reduce issues. Another issue would be , that every time you select default patchmix session, it will give you at least 1 spdif strip as well.

Just tried that. No go. Tried to switch from 44.1 to 48k . Get the red strips and no routings other than PCI SPDIF ADAT. Everything the manual says should happen doesn't. No SPFIF coax plugged in to the card and card resolution set to internal. Loaded a default 48K session and SPDIF does come up but if I were to remove it, the session would look exactly the same as a product default 44.1.

I find this very odd.

[auron]

Just tried that. No go. Tried to switch from 44.1 to 48k . Get the red strips and no routings other than PCI SPDIF ADAT. Everything the manual says should happen doesn't. No SPFIF coax plugged in to the card and card resolution set to internal. Loaded a default 48K session and SPDIF does come up but if I were to remove it, the session would look exactly the same as a product default 44.1.

I find this very odd.

Yes indeed, very odd. i have a different problem , it is the "opposite problem". I can't select 44.1 khz , doesnt matter what patchmix session (default or my own...) . so i have some old projects at 44.1 khz and installed "voicemeeter" which is pretty cool. Voicemeter allows me to use 44.1 khz in cubase (select voicemeeter asio as a sound device) and send the audio stream to the 48 khz patchmix. voicemeeter allows me to use the obs studio asio input capture which is kinda cool. Sorry sounds complicated but voicemeeter seems to be a savior .

https://vb-audio.com/

[speedymonk]

Well, I must be cursed on this thing. I use the product defaults and yet get the red lines/red out on the channel strips such as 1L/1R, etc. My mixer goes into 1L/1R. Even switched to 3?l/3R and no go. Unable to go a routing. I get 44.1 and no more.

Using 17 10700K, Gigabyte Z490 vision D, 1T NVME 2 drive, Cakewalk by Bandlab, Soundforge 14. Can record MIDI and audio into Bandlab no problem, as long as it is 44.1. Same with Soundforge. Anything else...nada.

I have 2l/2R inputs from computer to listen to you tube, etc. No issues. all inputs routed to Outputs 4 (stereo) as suggested to monitor.

If you have done all the steps with replacing the files and still have the red lines issue, perhaps your cable to the audio dock isn't working? My original cable was doing that back in the day and I replaced it with a heavy duty Cat 6 network cable. It seems to work well.

I can find a different cable. This one works fine at 44.1. A second cable doesn't even let the audio dock light up (except for the Christmas Tree.) I can open a saved working session but still no go. I put the other cable back and it is fine. Will see if I can find a heavy duty CAT 6 cable.

Will let you know. Thank you.

[speedymonk]

SUCCESS!!!!! Changed Cat 6 cables. Had done this before but used a completely different one in my cable bin. I get 44.1, 48, 96 and 192 (which I won't use). Thank you Kelvalis! That puts off me upgrading to a newer sound card for now. May still save for the focusrite Clarett thunderbolt used, but don't really want to spend nearly $800 for the one I want. UA audio apollo 4X is too expensive (great specs) but no Midi and no coax SPDIF. So......the EMU lives!

UPDATE: This morning when I powered on, the EMU went back to no audiodock light and red outs. Rebooted a few times, changed rate to 48 and back and reloaded saved session, rebooted and then all was well. Weird but working at this juncture. I'll keep saving money toward the Focusrite but hope I won't need to make that jump just yet. we'll see how windows updates and if the "fix" continues to work.

[KelValis]

That's awesome! Glad to hear it's working again.

Auron: are you able to use voice meeter to go out from patchmix to something like Skype or zoom? I was trying it when all I could get from the wave out was distortion but voice meeter didn't even pick up my Asio outputs.

Thanks

[auron]

No wave in skype is distorted. Same is when i use obs studio and the wave driver.

[Cagor]

Hi,
and again another lucky man... It really works perfectly for me.

Many, many thanks
Klaus

[toonertik]

SUCCESS!!!!! Changed Cat 6 cables. Had done this before but used a completely different one in my cable bin. I get 44.1, 48, 96 and 192 (which I won't use). Thank you Kelvalis! That puts off me upgrading to a newer sound card for now. May still save for the focusrite Clarett thunderbolt used, but don't really want to spend nearly $800 for the one I want. UA audio apollo 4X is too expensive (great specs) but no Midi and no coax SPDIF. So......the EMU lives!

UPDATE: This morning when I powered on, the EMU went back to no audiodock light and red outs. Rebooted a few times, changed rate to 48 and back and reloaded saved session, rebooted and then all was well. Weird but working at this juncture. I'll keep saving money toward the Focusrite but hope I won't need to make that jump just yet. we'll see how windows updates and if the "fix" continues to work.

This sounds like a problem I had.
It's well known that a couple of the dock's capacitors break down and need replacing.

I replaced mine with some good Panasonics...

All working great now.
It's not a difficult diy if you can solder.

Google capacitor probs with EMU 1820.

Edit.. I found this particularly usefull.
https://www.badcaps.net/forum/showthread.php?t=52032

[speedymonk]

SUCCESS!!!!! Changed Cat 6 cables. Had done this before but used a completely different one in my cable bin. I get 44.1, 48, 96 and 192 (which I won't use). Thank you Kelvalis! That puts off me upgrading to a newer sound card for now. May still save for the focusrite Clarett thunderbolt used, but don't really want to spend nearly $800 for the one I want. UA audio apollo 4X is too expensive (great specs) but no Midi and no coax SPDIF. So......the EMU lives!

UPDATE: This morning when I powered on, the EMU went back to no audiodock light and red outs. Rebooted a few times, changed rate to 48 and back and reloaded saved session, rebooted and then all was well. Weird but working at this juncture. I'll keep saving money toward the Focusrite but hope I won't need to make that jump just yet. we'll see how windows updates and if the "fix" continues to work.

This sounds like a problem I had.
It's well known that a couple of the dock's capacitors break down and need replacing.

I replaced mine with some good Panasonics...

All working great now.
It's not a difficult diy if you can solder.

Google capacitor probs with EMU 1820.

Edit.. I found this particularly usefull.
https://www.badcaps.net/forum/showthread.php?t=52032

I checked the caps before. Also have a cap checker. No bulges, etc. Looks like they should. The cable change is working just fine. No Christmas Tree effect anymore. All recording resolutions available. Still ratholing money for an eventual upgrade as insurance, but hopefully that won't be needed. Happily recording now at 48k and possibly 96k if feeling frisky.

[toonertik]

I checked the caps before. Also have a cap checker. No bulges, etc. Looks like they should. The cable change is working just fine. No Christmas Tree effect anymore. All recording resolutions available. Still ratholing money for an eventual upgrade as insurance, but hopefully that won't be needed. Happily recording now at 48k and possibly 96k if feeling frisky.

Cool... but also they don't have to bulge to be fckd, so bear this in mind should the prob reappear and I guess if you have a cap checker, you know how to solder... might be worth a change just in case. The caps EMU used were not of a very good quality.

I'm never frisky I guess.. as I only record at 48/ 44.1Hz

[speedymonk]

I checked the caps before. Also have a cap checker. No bulges, etc. Looks like they should. The cable change is working just fine. No Christmas Tree effect anymore. All recording resolutions available. Still ratholing money for an eventual upgrade as insurance, but hopefully that won't be needed. Happily recording now at 48k and possibly 96k if feeling frisky.

Cool... but also they don't have to bulge to be fckd, so bear this in mind should the prob reappear and I guess if you have a cap checker, you know how to solder... might be worth a change just in case. The caps EMU used were not of a very good quality.

I'm never frisky I guess.. as I only record at 48/ 44.1Hz

Since the cable change, everything has been stable. No "not enough hardware messages", etc. Comes right up on boot up just like it is supposed to do.

[dhirk]

Works again for 1616m after new 20H2 update! thank you for that! again!

[auron]

delete

[auron]

speedymonk wrote: ↑

Since the cable change, everything has been stable. No "not enough hardware messages", etc. Comes right up on boot up just like it is supposed to do.

What cable you have used? could you give me a link? I saw some cables out there , maybe it is better i replace my cable as well.