JonD

Try closing Sonar/CbB, then restart using RUN AS ADMINISTRATOR and see if that changes anything.

You says this deletion/substitution happens with EZ Keys, but how about with other VSTs? If this is happening with any VST under similar circumstances, could be the track is receiving MIDI program changes from somewhere.

If you're looking for VST rompler with a wide array of sounds, I recommend Xpand!2 which has over 2500 presets, and is definitely worth the $15 cost: https://www.pluginboutique.com/products/1560

Did you keep a pre-mastered set of your wav-files? Traditionally - and I'm talking since analog recording days - there are three general phases to production: 1) Tracking 2) Mixing 3) Mastering The idea being, you save (at least) these distinct sets of files so that if you needed to go back and fix your mix or master, you wouldn't have to start completely over -- just go back to the previous saved set. Of course, if you mastered as you mixed, unfortunately you wrote over older mix files and there won't be anything to re-master. I'm almost afraid to ask.....

The manufacturer webpage describes a system tray utility called the "ipMIDI Monitor" which manages your MIDI ports. Is that telling you anything?

Looks similar to the issue described here: http://forum.cakewalk.com/New-Update-Messed-up-Breverb-m3804019.aspx

Excellent strategy. EVERY DAW user should rely on system backups. I suggest doing them fairly often. I do a system backup image about once a month or just before a major software change or update. In the past 20 years or so I've been using system backups, I've never been more than 10-20 minutes away from a working system (regardless of the software glitch)... I'm constantly amazed when I find out a longtime DAW user uses no system backup at all - the equivalent of operating without a safety net. (I guess they enjoy occasionally spending hours troubleshooting only to give up in frustration then spend a week reinstalling/activating all of their software).

Jan 2023? Lol. That only gives me OVER TWO SOLID YEARS OF CONTINUING TO WORK ON MY ROCK-SOLID SYSTEM until I have to think about updating. What was I thinking?

You don't say why you "hate Windows 8", but I'm rock solid here on Windows 8.1 (I have another machine with Win 10 as well). I use the free classic shell utility which makes Win 8.1 look like Win XP or Win 7, as I don't care for the Metro GUI. In any case, I will go against the grain and suggest you stay with Win 8.1, then install CbB, as unlike with Win10, there are no mystery updates that will break something and suddenly render your system unusable (until you troubleshoot and fix the problem). Also, more older interfaces still work with Win 8.1 while it's a crap-shoot with Win 10. Bottom line, Win 8.1 is much more predictably solid than Win 10 in my experience. With Win 10 you will likely spend more time trying to figure out why CbB suddenly isn't working the same as it did yesterday due to an MS update.

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!