Ok, I think I've found the issue, and past this point I won't be wasting my time with Waveform any longer. I'm not a paid QA person so it's simply not worth the cost and energy to chase he issue down further.
For a brief instant before WF loses its marbles some error window pops up. This happens ONLY after playing SOME patches for a while. By switching around VST, I found that Collective wouldn't close the error window.
'CPU Overload'. Ok, interesting..
Simply inserting the MPK+ and letting it sit did nothing. Plunking one note then waiting did nothing. But on SOME patches about 4 notes, BOOM, error message snd ALL INPUTS vanish from WF until I restart it.
Installed the latest Ardour, performed the same steps, zero issues and no CPU overload. How Interesting.
So, alas, yes it's time to wave goodbye to WF. Ardour, while a pain to use in many ways and less refined than WF, is STABLE for me and I want to compose/perform music, not endlessly debug Other Peoples Code.
WF on Windows is excellent. Not on Linux. So be it.
For a brief instant before WF loses its marbles some error window pops up. This happens ONLY after playing SOME patches for a while. By switching around VST, I found that Collective wouldn't close the error window.
'CPU Overload'. Ok, interesting..
Simply inserting the MPK+ and letting it sit did nothing. Plunking one note then waiting did nothing. But on SOME patches about 4 notes, BOOM, error message snd ALL INPUTS vanish from WF until I restart it.
Installed the latest Ardour, performed the same steps, zero issues and no CPU overload. How Interesting.
So, alas, yes it's time to wave goodbye to WF. Ardour, while a pain to use in many ways and less refined than WF, is STABLE for me and I want to compose/perform music, not endlessly debug Other Peoples Code.
WF on Windows is excellent. Not on Linux. So be it.
Statistics: Posted by SuitcaseOfLizards — Tue Aug 13, 2024 3:34 pm