Seems like this project is not being maintained, but felt it due diligence to report this issue in case others run into a similar thing. Due to the interaction with Apple Music, running this widget can cause system-wide graphical hitches of 15-30ms every second. This is easy to see in the game I develop as high frame time frames:
But it is not limited to just games - it will cause the system mouse cursor to skip a frame, and any graphic updates (scrolling in browsers, etc.) to also hitch at the same interval.
This can be alleviated by changing the update interval of the widget (add export const refreshFrequency = 20000; anywhere in the main script file) but is likely impossible to resolve completely without upstream fixes.
I haven't had a chance to dive deeper, but what I can say is that it is the result of the execution of the osascript getTrack.scpt and seems to occur whenever music is accessed (or even just the filesystem, potentially). Looks like it could be a potential issue at ubersicht's end, although I have not noticed this in any other widget I run.
Seems like this project is not being maintained, but felt it due diligence to report this issue in case others run into a similar thing. Due to the interaction with Apple Music, running this widget can cause system-wide graphical hitches of 15-30ms every second. This is easy to see in the game I develop as high frame time frames:
But it is not limited to just games - it will cause the system mouse cursor to skip a frame, and any graphic updates (scrolling in browsers, etc.) to also hitch at the same interval.
This can be alleviated by changing the update interval of the widget (add
export const refreshFrequency = 20000;anywhere in the main script file) but is likely impossible to resolve completely without upstream fixes.I haven't had a chance to dive deeper, but what I can say is that it is the result of the execution of the
osascript getTrack.scptand seems to occur whenever music is accessed (or even just the filesystem, potentially). Looks like it could be a potential issue at ubersicht's end, although I have not noticed this in any other widget I run.