JonD

Best to just get in the habit of powering things on in the right sequence (ie. necessary hardware first). It might feel like a PITA in the beginning, but after awhile, you won't even notice.

Why? Many HW manufacturers stop driver development on their discontinued products. Presonus happens to be one of them. https://www.presonus.com/products/fp10/downloads Note that the last supported O.S. was Windows 7. Again, that doesn't mean the last released driver won't work under Win 8.1 or Win 10. It's certainly worth trying if you have a way to restore to a backed up system image if things go south.

Do you know for a fact that the Firepod works well with Win 10? I doubt there are Win 10-specific drivers for the Firepod, but that doesn't mean it won't work with Win 7/8 drivers under Win 10. So research that first (Obviously there's no point in updating the software if your Firepod won't work with the new O.S.).

Assuming there is a native (ASIO) driver. The reason most people use ASIO4ALL is they're using an onboard sound card with no native ASIO drivers -- or at best, poorly written ones. If that's the case here, OP should look into getting a proper audio interface. New ones can be had for as low as $50 (and lower if you buy used, on Ebay, for example).

How did you solve it?

The same DAW on my system doesn't have these problems, so what's your point? The only way to isolate what's causing them on HIS system is to troubleshoot (Which is why everyone else is offering HELPFUL suggestions)...

I'd start by doing some basic PC tweaks to optimize for DAW use. As outlined in this video: https://www.youtube.com/watch?v=-FAHqrphv9k I suspect after following those steps the problems will be gone, but if not, run Latency Mon, freely available from here: https://www.resplendence.com/latencymon

I've seen other CW users report different issues with MODO (which were resolved BTW), but not necessarily this issue. Bottom line, there ARE others here who are successfully running MODO Bass with Cakewalk. I'd start with that fact (instead of implying it doesn't work for anyone), and troubleshoot from there.

Are you running Windows 10? If you don't control the O.S. updates, Win 10 is notorious for causing problems - which is why it's best to disable the auto-update and only do so when you know it's safe OR have the ability to roll back to a previous system-state in case things go south. If you determine that the last OS update likely caused this problem, there are ways to roll back: https://www.howtogeek.com/235474/how-to-roll-back-builds-and-uninstall-updates-on-windows-10/ Have you consulted with or reported the issue to Izotope? If they have a user forum, that would be a better place to report your problem (since you are experiencing it with two different DAWS)

I know nothings about Macs, but with Windows, sometimes outdated drivers can work with the newer operating system. Have you tried the last available driver version to see if it works?

Have you tried both the VST2 and VST3 versions, and do they behave in the same way?

Did you try a reset/rescan of VSTs? Wouldn't hurt at this point.

Try a reinstall of either one and see if it changes anything.

Looks like something's gone wrong with your ASIO drivers. Temporarily disconnect your interface USB cable, then uninstall/reinstall the latest driver package. Reboot your PC, then reconnect the interface. (To a different USB port if available). Check your ASIO settings to see if the missing I/O issue has been corrected.

What do you mean by "latency"? You mention running a test which suggests latency mon... Is that what you mean? Or do you mean a lag in between the time you press a key and when you hear a note...?

Excellent. Glad it worked out!

Things to try: - Disconnect any bus-powered audio interfaces. Optionally, uninstall those drivers. - Do a CLEAN uninstall of Sonar using this guide: https://www.cakewalk.com/Support/Knowledge-Base/2007013392/SONAR-2015-Clean-Install-Instructions - Re-download the Sonar installers/patches from CW Command Center. Temporarily disable anti-virus during install process. Using Run as Administrator, install Sonar X3, reboot system, then install Sonar X3e. Reboot system again. - If you get this far without strange problems or error messages, you're probably good to go and can just reinstall interface drivers, enable antivirus, and proceed as normal.

The U.S. is still not doing widespread testing right now so there's simply no way to know how many infected there are here. I heard a Johns Hopkins Professor of Public Health guess that there could be anywhere from 50,000 to half a million people infected right now, just living their lives, out in public and unwittingly infecting more people... Let's look at Italy... Italy has been clamped down for a week or so -- and their hospitals are already overrun with patients with the viral symptoms. What does that suggest about what will happen here in the states in another week or two? Add to that there has been no widespread testing here, and and our borders are still mostly wide open. Bottom line -- no, the coming catastrophe HASN'T been overstated by mainstream media (BTW they're not the ones telling people to stock up on toilet paper), and if you're citing current U.S. COV19 trends as some sort of accurate metric of what's to come -- forgive me, but you've missed the forest for the trees, and/or must be listening to the wrong "news" organizations.

So... You have an older, Echo interface (Last drivers for Win 7/8, correct?). It was working fine until a recent CW update.... Updating O.S. to Win 10 increased instability. No tweaks have fixed the problems so far... Seems to me you have two options: 1) You have Macrium installed. Assuming it's for doing system images/backups, and that you have been using it.... Use Macrium to restore back to a point where it was working fine -- then stop running anymore CW updates. You could probably update to Win 8.1, but who knows if everything will remain as stable. 2) Get a newer audio interface and update to Win 10 to fully support it.

Agree with Starship. Wouldn't hurt to install Bandlab alongside Sonar and see how it behaves...

Everything up to date? Interface firmware/drivers, Win 10 updates... Any processes running in the BG that could be causing the problem? (Anti-virus, wi-fi, etc). Also, look in Startup for any unnecessary tasks.

I'd start by first uninstalling ASIO4ALL from your system. Connect your interface to a USB 2 (black) port if possible instead of USB 3 (blue), then try to install the drivers again, following the instructions outlined here: https://supportloudtech.netx.net/loud-public/#category/19805

Okay, I will check the image and if it's good, create the ISO file (Will be later tonight). I'll contact you further by PM, so we don't monopolize the forum.

Hi Bob, If you think it will help you, I'd be happy to upload the file. I don't currently have access to the PC, but I do have system images of the C: drive done early in the build. They are Macrium image files. I use the free version, so you could install the same to restore it. You'll only need to remove any applications and change the product key. If you need it as an ISO image, I'll have to convert it. Let me know. Jon

I literally built a Win 8.1 system with CbB a month ago with the standard Win 8.1 OS download from MS and it works just fine. I didn't have to do anything special other than let all the available updates install afterward. Have you tried the OS repair utility? There are also NET Framework repair tools out there (though I've never tried them). If those don't work, how about starting over with the MS Win 8.1 download? Yeah, you'll have to reinstall any applications, but it should be smooth sailing from there.