I never said that he is intentionally lying. He can be misinformed or mistaken, and in good faith believe that this is the explanation. Doesn’t mean he’s right.
Based on my past experience with non-native app ‘wrappers’ for development, which can cause things to be less responsive/smooth and more resource intensive
Yes, they can cause performance issues. What’s the actual evidence that this is the case here? It shouldn’t be too difficult to verify this theory and establish, what exactly this OpenGL wrapper is doing that causes the slowdown.
Also, being a developer myself, I can tell you that it is extremely common that when you opt for non-native solutions and have to do ‘wrappers’, you tend to have performance issues.
The OpenGL API is a native API provided by Apple. It’s deprecated, it wraps around the newer Metal API, but it doesn’t prove anything.
When he was still with Plex, @DaveBinM shared that it wasn’t a codec issue
Then we can close this topic, because according to @DaveBinM the fix has already been delivered in the form of a new audio engine and there is nothing left to discuss.
Unless we work for Plex and have access to the codebase, we are all guessing. There is nothing wrong with that. I don’t get all the pushback to being able to do that here.
Deduction operates with facts. We don’t have facts, so what you’re doing is called speculation, not deduction.
Again, correlation does not imply causation. Plex does not use Metal, Plex has issues. Infuse uses Metal, Infuse does not have issues. Based on that alone, we cannot conclude, that Plex has issues because it does not use Metal.
I never denied you the right to believe what @Achilles is saying, it’s you who seem to have a problem with me not blindly believing him. You asked me why I don’t believe him, I explained (for the second time). I don’t see the point in continuing this discussion.
Fact is that Infuse uses Metal and has no issues. Fact is that this is an Apple specific issue. Fact is that the native ‘old player’ has no issues. Fact is that @Achilles claimed to know that the wrapper/shim is the cause, and I believe him.
With these facts above, I am deducing that the fact that Plex does not use Metal is causing some issues with the sync.
You are comparing three absolutely different players, and then somehow coming to a conclusion that the root cause is the API used for rendering. A video player is a complex program, there are many moving parts.
It’s the first time I’m hearing this. Can you elaborate?
They are all video players, how they work or don’t work, and why and with what API’s is all relevant in troubleshooting and debugging the one that doesn’t work. We also have people who worked closely with the devs that worked on the wrapper/shim.
Sure, but until now I was being told that the problem is in the deprecated OpenGL API. Now all of a sudden you’re claiming that the problem is on the client’s side (which I actually find more plausible). But how do you know that? What exactly the client is doing wrong? Unless you know, you are speculating again about what could cause the problem. Such speculations are good as a starting point, but they need to be verified.
As much as I hate to get involved in what in the end is a meaningless argument, I commend anyone who wants to argue about this to watch the Apple Developer videos on migrating from OpenGL to Metal. Here is one from WWDC. Pay particular attention to the part where the gentleman talks about OpenGL not being deterministic concerning when rendering will actually occur. This can easily become the basis for audio sync issues which will vary based upon the video content being rendered. Sound familiar?
I am not a graphics expert by any stretch, however I do have a great deal of C and assembler experience. The analysis provided by @Achilles makes a good deal of sense to me. Not that any of this really matters, because none of us are going to fix it–that’s up to Plex.
Unless of course, someone here wants to contribute the code to move mpv to Metal…
I do know what’s going on with the AppleTV player as does @DaveBinM as a former employee and @Achilles as an extremely technically competent current alpha and beta tester.
I do recommend folks stop speculating about things to which they are not privy .
And this is why stupid conversations keep happening. Because the company/people who control/know the problem don’t communicate properly to their paying community.
