Hi Ted! My "unfavorable" settings in the recording parameter menu (all midi input devices, all channels, midi through auto routing) are causing a cpu load of 104% according to "top" - didn't know that is possible :-) Choosing only one midi input device, one fixed midi channel and midi auto routing to off solves this problem. Thank you and cheers, Michael ============================= Try using the "top" command (at the command line) to make sure Rosegarden is to blame. It will show you the processes that are using the most CPU.
Ted. ============================= Hi there! Does anybody experience this behaviour too: Since the latest commitments (code version 1589x - 15904) the cpu load rises strongly (in my case 45-60% and more) when Rosegarden is idle and in QJackCtl a lot of xruns are generated. After loading a song into Rosegarden and starting to play this song the CPU load falls again (maybe 5%) and no more xruns are generated. I am using Debian 10 with a RT-kernel. Ardour and other Softwares behave properly, so I think it is Rosegarden. I didn't see this behaviour before the latest ALSA-Midi-Port commitments where added (code version 1588x). Greetings Michael _______________________________________________ Rosegarden-user mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
