Two days ago Ulf fixed an issue that turned out to be a midi routing problem. Soon afterwards i started having (Dorico Not Responding ) problems.
1)I am currently using 15 instances of Omnishere, is that a problem? If so how many instances is the limit?
2) Freezes every couple minutes of use. I tried saving the latest project after a freeze and it will not save.
3) The pads in omnishere once i strike a note on my midi control keyboard will behave as stuck. Only the pads and a few other patches i tried, but not all patches. Other patches behave as normal.
4) It was working alright for about one day and then suddenly started behaving weird as described.
5) I checked the CPU usage and its at about 32%, is that high?
Any help would be appreciated.
BTW, i am using Windows 11 on a new computer that was designed for music production.
-chris
If you’re getting freezes every couple of minutes, that’s probably due to the time it takes to serialise the state of each instance of Omnisphere when auto-saving the project. Try reducing the auto-save time interval in Preferences. Unfortunately there’s nothing we can do about the time it takes to save the data from a plug-in. I don’t know anything about Omnisphere, but if it’s a multi-timbral plug-in, perhaps you can use a single instance with multiple channels instead of multiple instances?
If you’re using MIDI inputs and outputs on your system, make sure that you haven’t got a MIDI feedback loop going on: if you have the same MIDI port used both as an output and an input, bad things will happen. Check on the Play page of Preferences that you don’t have any MIDI outputs activated as MIDI inputs.
Thank you. I will check that out. One thing that i am trying at the moment is to break the project into several flows instead of one long flow. This will allow me to reduce the instances needed for each flow. This is working on the theory that many instances of Omnisphere was overwelming the program.
-chris