Echo Audio Drivers

[Charo Lemucchi]

Iheard from several of you that there were no issues, so I took the plunge. Unfortunately, I'm having issues with fx plugins and virtual midi instruments causing dropouts, and since I heard that there were no issues from some of you so long ago, I thought I'd check again.

Here's the caveat: I froze my DAW at Windows 10 1803. It was the version that came with my PC when I bought it. The 1809 update worked fine, but the 1903 update resulted in problems. (Example: Input Echo, Dropouts)

However I don't claim that later versions of Windows 10 are incompatible with the ECHO drivers, just that, on my DAW, with my update history, I seemed to hit a problem that was resolved by rolling back.

That's what I'm thinking is going on with me hanging onto my Echo audio interface. I procrastinated upgrading to W10 so I could keep my outdated audio interface. I just want to be 100% sure (or close to) that is my dropout issue before I buy a new interface and decommission my second Echo Layla.

That's what I'm thinking is going on with me hanging onto my Echo audio interface. I procrastinated upgrading to W10 so I could keep my outdated audio interface. I just want to 100% (or close to) that is my dropout issue before I buy a new interface and decommission my second Echo Layla.

I did all my homework prior to the upgrade, but something fishy is going on because although I get project load toast messages, I don't get dropout toast messages. I've posted about that a couple times and it remains a mystery.

I sure hope someone can help get you going again. I talked myself out of regressing to windows 7 multiple times!! I knew it was close to a must do soon upgrade. I have also thought about a new sound card since mine is even older that your!! lol!! To get the bang of my old card - 8 ins-outs SPDIF, ADAT..... I will just cost more than I need to spend right now. My computer is a really old i7. I have thought many times about moving up. Just need to go slow and figure out what would help the most and do that first. I have other friends that use Echo products. They don't seem to have problems on win 10 and BL Cakewalk.

I had an echo 3g for a long time and we'll into windows 10 builds.. I don't recall when I decommissioned it...I think about this time in 2018. Mine worked well.enough but the phantom power was shot on both inputs and I had moved over to studio.one by then and decided to spring for a presonus studio 1824. It is better, even though it is usb but it is. It as night and day as you would think, being at least ten years newer. Still, I think it was a good move. I still have the 3g if anyone needs an extra one! I will sell it for a good price.

Registered just to ask this: Those of you who are still successfully using Layla 3G with Windows 10, which driver version are you using?

So far I've tried 8.6 which didn't work at all, and the v1.6 which came with the original install CD kind of worked but the sound was extremely garbled and overdriven. I'm not super keen on going through every driver one by one, so here I am asking.

Thank you in advance!

UPD: Almost none of the 8.X drivers get recognized at all. And I've discovered that Vista driver v8.1 does the same thing as the v1.6 (except it at least installs the Echo 3G Console aside from the drivers, which is a step forward). Could it be that the issue lies not in the drivers but elsewhere? Like I said, the sound is extremely distorted, but if I play a song the rhythm is still recognizable, so it's not just white noise. Any suggestions would be really appreciated.

Caveat: The 1903 update caused me some issues with audio recording that eventually led to my reverting to Factory-delivered Windows version on my DAW. It does not necessarily mean that there is an incompatibility with ECHO Layla 3G drivers and Windows 1903 and later, just that I cannot vouch for those configs.

One possibility is, PCI card-driven interfaces work best with the older motherboards. While the newer boards have PCI slots, they are often bridged, and that can present its own data-streaming problems. (This is not an absolute, as some newer boards work just fine with PCI-based audio, but it can definitely be a factor).

I've been using Ubuntu 16.04 on a Lenovo ideapad Y410P for about a month and a half, and for the duration I've been having audio issues, despite to this day making sure I have installed all updates. I run a dual boot with Windows 10 and have no problems in Windows, so I'm pretty sure this is an Ubuntu or Linux issue.

Every once in a while-- I see no correlation in the times it happens-- my audio suddenly goes fuzzy & garbled with a slight echo. If I had to define it further I'd call it a swampy metallic sound. It is still possible to make out what sounds are playing, but they are very distorted. This problem sometimes will stop by itself-- I see no correlation in the times it stops-- or I can restart my computer.

The audio issue continues to arise on the same laptop sporadically, however I can quickly fix it by using the terminal to run alsamixer. In alsamixer, press f6, then simply click on a master volume control. The audio immediately returns to normal.

Apparently the default for AudioPulseMinLength is correct in the config file but was mistakenly set to 100 in the actual code. The solution is to edit /etc/speech-dispatcher/speechd.conf and uncomment the following line:

I discovered that FireFox was forking off some "speech-dispatcher" processes (via the Audio Mixer... dialog underneath the speaker icon on the top bar) and so I edited /etc/speech-dispatcher/speechd.conf and uncommented the line for DisableAutoSpawn

I have been experiencing somewhat the same issues with my 17.10 install. There is an option in my sound menu to allow volume to go above 100%, which makes the sound garbled and incoherent, (but nowhere near as bad as you describe).

I've suffered from this echo/crackling/popping audio/sound issue that is widely reported online for a good 10 years and have had it carry through multiple osx versions, and multiple macbooks via time machine. I gave up on trying to fix it but it drives me absolutely nuts and I'm desperate for a solution.

It appears always after streaming or playing anything for 45-55mins approximately. Can be netflix, youtube, soundcloud, watching a video via vlc or other programs, playing a mix in itunes, using traktor dj, using ableton. Anything using audio for 45-55mins straight.

I've tried many things but the only temporary fix I've found is to quit 'coreaudiod' in the activity monitor. This is obviously a pain as it comes back after another 45mins and has meant I can never use my laptop properly for live music or performance situations has been really frustrating. It happens both with and without using a portable soundcard.

In the past when I was using the most up to date osx I asked apple but just got past around with rubbing. Since I've always just been told to update my osx and they won't help me unless I do that. The issue is, like many, lots of my plugins for my music app Ableton 9 and the program itself (used in years of my music projects) won't work in anything after high sierra due to it using 64bit as apposed to 32bit. So it is not possible for me to do this. I've even had to buy an older 'refurbished' macbook over the latest brand new ones to keep all these files still useable. Aside from this, as mentioned this has been an issue that has carried over through osx versions and my other mac laptops via my time machine and upon searching, this issue still seems to be happening to people even with new osx versions anyway.

I've searched high and low for a fix and had given up but figured I'd try and bring this up once more to incase someone has worked out a resolution as I'm desperate and just straight up sick of it. Any help will be greatly appreciated.

To me it sounds like you are using some third party audio software which may include audio drivers. These third party audio drivers may be interfering with the normal operation of macOS. Try booting into Safe Mode to see if you have the same problem since Safe Mode disables third party drivers.

Try using a grounded AC cord with the power adapter for your laptop instead of the default duckhead adapter which Apple supplies. It is possible you may have an electrical wiring issue in your home or with a surge/power strip. Here is the grounded AC cord for the US region, but each region has their own version for the correct plug to fit the electrical outlet.

Also make sure all connected devices are connected to the same electrical circuit. If you plug in the power cords to two different electrical outlets even if they are in the same room, those electrical outlets may be on a different electric circuit (aka powered by a different circuit breaker/fuse and also that circuit may be incorrectly wired). If this happens, it can introduce audio noise.

3a8082e126