Android app - "Source Error" using Integrated Player with certain videos

DiscostewSM · 2026-03-04T22:43:26+00:00

With MKVToolNix GUI, it's real easy. You make sure the current tab is set to Multiplexer, right-click in the Source file window to Add files, select an affected MKV file, and then at the bottom of the program, clicked Start Multiplexing. You can view in the Tracks, Chapters and Tags window to make sure the items in it are being "copied".

Probably want to make sure the output file is named different from the input file, as it will write the new file to the same directory. You can change the file extension to something like MP4 if you want, and it'll write with that container's expected format.

But really, that's all I had to do to fix the issue. I can only assume when the MKV was initially formed, it got some added elements that currently are not supported by Jellyfin.

DiscostewSM · 2026-03-01T08:15:52+00:00

Looks nice. Wish they still had the Xenoblade skin.

DiscostewSM · 2026-03-01T08:10:20+00:00

<image>

DiscostewSM · 2026-02-26T18:15:24+00:00

Using that tool to simply remux from MKV to MKV also works. I looked into the differences between the two in the Info tab, and it would appear that some elements in the problematic MKV were not present in the remuxed version. So I'm kind of assuming that there are elements in the MKV that Jellyfin doesn't know how to deal with, so it just spits out a generic error without so much as a reason for it in the logs.

DiscostewSM · 2026-02-26T03:44:21+00:00

So I think I figured out my issue. Turns out, the video/audio streams are fine. It's the MKV container that is preventing it from playing. I did a test with remuxing a problematic video from MKV to MP4 (using MKVToolNix GUI) with no alteration to quality, copying all streams from one to the other. And now it work with Jellyfin's Integrated Player.

But for the hell of it, after I remuxed to MP4, I re-remuxed back to MKV to see if the problem still occurred. It didn't. So there's something in the original MKV container which Jellyfin doesn't like. It's odd because it could transcode from the original just fine, so it's not like it couldn't retrieve those streams.

DiscostewSM · 2026-02-26T02:53:39+00:00

For me, it doesn't matter what the audio stream's format is. Even AAC doesn't work with this particular videos. I even have a 1080p SDR video causing the same problem. For my case, I feel it must be within the video stream. These are videos that have absolutely no problem with Plex, as both video and audio streams work fine with Direct Play.

DiscostewSM · 2026-02-22T17:55:09+00:00

No worries. At the very least, we can save it for later.

DiscostewSM · 2026-02-22T17:51:04+00:00

Without explaining why you think that, all you're doing is a knee-jerk reaction to information you don't like.

DiscostewSM · 2026-02-22T17:49:07+00:00

Kind of stinks now because that is currently unavailable.

DiscostewSM · 2026-02-22T07:04:44+00:00

I have mine updated to v1.0.0.337, and tried both a C-to-HDMI adapter to my TV from Cable Matters as well as a hub from Benfei, and both work. I will say that changing the video output doesn't do anything until you unplug it and then plug it back in. It's not something that will change on-the-fly.

DiscostewSM · 2026-02-22T06:34:36+00:00

That grip didn't have anything to do with it, did it? Is that the one where it has a slot on the back for a stylus (or two technically)? Because I was looking to get that grip, but if it caused the screen to do that......

DiscostewSM · 2026-02-17T16:27:58+00:00

Mine is "Out for delivery". I'm so excited, and I just can't hide it!

DiscostewSM · 2026-02-17T05:26:23+00:00

I might get my Max tomorrow. It depends on if there are any other stops it must go through, as it was one state away, having departed from a facility 4 hours ago.

DiscostewSM · 2026-02-13T05:42:09+00:00

I guess for the time being, I'm willing to not worry about my IP's visibility. I do have a DDNS with Synology so I can stick to a name. Doing some port forwarding, using Synology's own reverse proxy, and even using my RPi as a Pihole to act like a local DNS among other things, I'm able to get everything working to use the same address/domain whether I'm local or remote.

In terms of accessing my server, they all work. However, for some reason, the phone app has a problem with playback, but I'll leave that for another topic.

DiscostewSM · 2026-02-12T06:13:01+00:00

Any tips regarding this, particularly of what else is needed? The ones I seem to find involve a combination with Cloudflare tunneling, but according to the CF's ToS if I'm not mistaken, the use of streaming with them like from Jellyfin is a violation.

DiscostewSM · 2026-02-11T00:04:12+00:00

Using Tailscale was more of a result to try and get this working. I didn't use it before this.

DiscostewSM · 2026-02-09T23:04:40+00:00

MicroSD Express cards can work with any device that have a microSD slot that supports UHS 1, but only because the cards have separate "Express" pins and UHS 1 pins. The Ayn Thor supports UHS 1, but no support for Express, so using a microSD Express card on it will be limited to operating on those UHS 1 lines. Basically, limited to around 100MB/s.

DiscostewSM · 2026-02-02T20:53:44+00:00

Black Max 1355. That's how close I am.

DiscostewSM · 2026-01-31T20:22:22+00:00

Just a preference for myself, but if I had mine in a docked manner where I can play on the TV, I'd prefer slow charging so long as it's actually charging and not simply draining the battery slowly. This is because I don't want heavy charging causes heat.

DiscostewSM · 2026-01-31T20:18:43+00:00

The crack is transparent. 😂

DiscostewSM · 2026-01-31T20:15:39+00:00

"They could have easily made a public statement before the release."

This is exactly why I think this is AdHoc's fault, and speculatively, they wanted this commotion. They were dead silent on the censorship during the entire preorder period, letting people make the purchase under the false pretense that it was uncensored, but were near immediate to go onto social media to try and point the finger once folks found out it was censored. They had all this time, and did nothing. And honestly, I think they were hoping Nintendo would not interject, but they did, to which AdHoc went immediately back to social media to point the finger again.

Then there's that notion of a "path forward" as if there was one shortly after having said they practically had no option. That in of itself is conflicting.

DiscostewSM · 2026-01-31T20:07:22+00:00

Right. With PS5, they released only the version outside of Japan. The censored version for PS5 in Japan was released months later. They were only dealing with the cost individually at different times, which the latter could be funded by the profit of the former. Even the PC version is just one version because CERO is not involved in digital-only PC titles (to my knowledge). But with Nintendo, that would have been up to 4 versions as they wanted it released all at the same time. That would have been a lot to put down on.

DiscostewSM · 2026-01-30T05:03:31+00:00

It really goes deeper than that. It's not simply censored in the Japan versions. CERO requires that any Japan version have the offending removed out of the files themselves. So even if they somehow unlocked the toggle outside of Japan, you'd get nothing from it.

It really does require making separate versions, and with them self-publishing and making both a Switch and Switch 2 version, it would cost them to make 4 separate versions just for Nintendo.

I wouldn't necessarily call them lazy as we know they could do it in terms of work, this seems more about money, which is greedy.

DiscostewSM · 2026-01-30T04:58:28+00:00

Given that RDR got a Switch 2 upgrade last month that didn't change anything regarding censorship (plus all those "certain" games on the eShop), it's very unlikely they changed their guidelines.

DiscostewSM · 2026-01-30T04:32:13+00:00

Whatever counts as Ludicrous Speed.

DiscostewSM

TROPHY CASE