Is microtube broken again? A bug report and status thread!

[dumol]

@Mister_Magister

Because the adaptation was fixed, so it is the device aka adaptation for that specific device. end of story.

I use device as an stand in for “device’s sailfishos port” because we’re talking about sailfishos here. It is the device.

That would be a more sensible wording. And it’s true it could be one explanation. But I’m highly skeptic the Jolla guys still work on the XA2 adaptation, 7 years after launching it. Most probably some fixes higher up the software stack had a positive impact on the XA2, like you have already exemplified above, regarding video streaming. So it was almost certainly not the device, even if you use the term to refer to the device’s adaptation.

@Mister_Magister

Or perhaps you mean to tell me that when some specific device does not support hardware decoding it’s also microtube’s fault? It’s same as if that hardware decoding is not working fully correctly as it was the case with xa2. There’s absolutely nothing to fix on microtube’s side because it’s adaptation’s fault.

I’ve exemplified much higher above that Pico Player, among others, always played 1080p60 without hiccups on my device. Even microTube seemed to be using hardware acceleration at all times on my XA2, although video playing was stuttering with Sailfish versions older than 5.1. One hint was that the hiccups were happening even at 480p, which should have been smooth with software decoding. When hardware acceleration for video decoding stopped working on my XA2 in the native browser, it was very noticeable, and I’ve reported it upstream. This wasn’t the case here.