But I did just notice you are using the Bob Moog Tribute expansion? I am using legit Omnisphere, but I did try using a shared version of that library. I'll leave it sit unused for some hours and maybe it will happen. I have standalone open and no other audio apps open. Omnisphere is one of those for me, really only just behind Alchemy. I never use the standalone version, and also when I am working in a project nearing completion I often start rendering and then disabling cpu hungry synth instances. I have never had it do this and I use it all the time. And also, I am on intel and you are on Silicon. The problem about these is they are hard to duplicate problems. Only Omnisphere has this problem on my mac. It is not a DAW problem because as I said, standalone randomly losing output with no reasons too. The diagnostic button shows equal numbers with windows release, and the STEAM library is full (90 gb).
So if it happens in omni instance, there are no ways and i need to delete it and reload another instance: and this "bug" can disappear in new instance, I can play omni for hours without issues. Another interesting thing, the sound can come back, but it will disappear again. The interesting thing, I can hear sound by clicking small play button in the lower left corner of plugin, but the master output of omnisphere shows no signal. There are no classic wavetable/soundsource errors, all working correct since 2022, and i just can load another instance of omni, and play the same patch without any problem. I've never noticed that earlier, but nowadays the plugin (standalone or VST, no matter) randomly losing output, so no sound as a result. Omnisphere was installed on this computer in December 2022 (2.6 by The Pirate), updated by latest MORIA releases a couple months ago. Omnisphere 2.8 - soundsources, patches and moog all up to date. MacBook Pro 2021 (M1 Pro chip), Ventura 13.5.1