This is my first post to this mailing list so please excuse me if it’s already been asked:
Sometimes I find that WSJT-X isn’t fully decoding messages in the background after a few minutes. Sometimes this doesn’t happen for days but lately this has been happening to me everyday. I’ve spent about a week digging in and seeing what’s wrong. I like to leave WSJT-X in the background so that it can provide spots to PSKReporter (via GridTracker). It seems that sometimes Apple’s timer coalescing (App Nap) is most likely the culprit as almost all QT apps behave similarly. I have witnessed the app napping and therefore is no longer able to decode. I was wondering if that can be disabled or user selectable in a future version of WSJT-X? I believe something like this is all that’s necessary: [[NSProcessInfo processInfo] beginActivityWithOptions:NSActivityLatencyCritical | NSActivityUserInitiated reason:@"Disable App Nap”] … process data ... [[NSProcessInfo processInfo] endActivity:activity]; Without this, the app partially decodes (which results in no decodes) when in the background. You can see the waterfall is not as plump (i.e. not processing for the full period). Anyway, any help would be appreciated. Best, Alex K6LOT p.s. WSJT-X v2.4.0 MacOSX 11.1 on Intel MacBook Pro. (Problem also happened on MacOSX 15.17.x)
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
