It was already fixed in their nightly builds, and it’s an extremely mature video & audio player, i get most open source projects can’t pounce on any tiny issue. But like the most mature open source player should be able to resolve a serious playback issue in their stable build in less than a month. Either by applying the fix that fixed it in their nightly builds, or by reverting to a previous version of whatever is causing it that had it working well in earlier versions. I get the open source mantra of “you’re not the client”, but VLC is good & big enough to manage this kind of stuff a lot better.
Well… I’d point you to this very nice blog post to help rationalize why it can take a long time.
https://snarky.ca/the-social-contract-of-open-source/
It was already fixed in their nightly builds, and it’s an extremely mature video & audio player, i get most open source projects can’t pounce on any tiny issue. But like the most mature open source player should be able to resolve a serious playback issue in their stable build in less than a month. Either by applying the fix that fixed it in their nightly builds, or by reverting to a previous version of whatever is causing it that had it working well in earlier versions. I get the open source mantra of “you’re not the client”, but VLC is good & big enough to manage this kind of stuff a lot better.