Postby SomeRandomGuy » 08 Sep 2019 13:44
I have what appears to be the same issue, which was annoying enough to make me sign up for this forum... (I'm running the standard DLed 3.0.8, and I don't have debug logs like the ones posted above, so while I am not 100% sure it's the same issue, it seems likely.) But I'm not at all sure it's VLC's fault... or not entirely.
I see this problem consistently and continuously, about once every 30-60 seconds, with 720p video (I haven't tried anything else), in both normal and full-screen mode, using both h.264 and h.265 encoded files. Input bitrates for the h.264 are up to about 4mbps, and for the h.265 up to 3mbps but usually lower. When it occurs, I lose perhaps a half second of video, but audio seems unaffected.
I first thought that this was a new issue with 3.0.8, because I haven't seen it until very recently. But then I downloaded 3.0.7 and 3.0.6 and they are showing the same problem. They very definitely did NOT show this problem when I was originally using them (which was when they were current versions).
Since I have the 32GB 2.9GHz MBP 15" 2018 model, I am really damn sure it's not insufficient CPU resources or RAM. And it's not the encoding, since winding back 10 seconds (or 3 seconds) always produces good playback the second time.
You know what's different now, though? The MacOS version. Running 10.14.4 I did not see this problem. Running 10.14.6 (WITH supplemental update), I do. I can't swear to the state of 10.14.5, but I am 95% certain it was OK.
Unfortunately I do not have a 10.14.4 or .5 system handy that I can boot to verify that this is the problem. Can anyone else?
The more I think about this the more I think it's the OS. It really does feel like the scheduler starving the VLC process, or something like that- though that's a pretty impressively screwed up scheduler if so, making VLC drop 15 frames at a time. Next time I watch something I'll try renicing the VLC process, though that's a long shot.
Could anyone else with this problem please post their OS version (indicate if you've installed the supplemental updates) and what hardware they're using? I note the two other posters are both running 10.14.6, though they didn't say if they'd installed the supplemental update.
Going very far out on a limb here, I wouldn't be surprised if either of these were true:
1) Only affects systems with T2 chips (since there haven't been so many reports)
2) Only affects 10.14.6 with supplemental update (since that messed with the EFI, IIRC)
... but in any case, there's only one way to find out. Post data!
Thanks.