Unable to play media on certain clients

[Carlo 4561]

Check and see if both files are in that folder.
If so rename the mp4 to old or something for now and rescan library so only the mkv shows up.

[jpkeenanjr 2]

2 minutes ago, cayars said:

How did you do the remux?

If you used the command I gave you it would have ended up an MKV file but the log above shows MP4.

The original was -z.mp4, the copy was just .mp4

[Carlo 4561]

Did you try the new file in Emby playing back yet?

[jpkeenanjr 2]

I was using the pop-up control in the AndroidTV client to pick which of the two files to play.  But I renamed the old one, scanned the Library, and tried again.  This time there was no pop-up since there was only one playable file. Same result.  Logs uploaded at 12:48, username Joe.

 

[ebr 16177]

Yeah, 100's of lines of the same error as before.

What happens if you re-package to an mkv?

[jpkeenanjr 2]

Same command but with the filename extension as the only change?  Does that really change the format?

 

[Carlo 4561]

yes just change it to mkv.

It sometimes helps but the problem with this file may not be able to be fixed with a remux.  About to find out.

[jpkeenanjr 2]

No change.  And I confirmed that the client was seeing the MKV file...

 

 

[Luke 42078]

30 minutes ago, jpkeenanjr said:

No change.  And I confirmed that the client was seeing the MKV file...

 

 

Hi, can we look at a log example from that? Thanks.

[jpkeenanjr 2]

2 minutes ago, Luke said:

Hi, can we look at a log example from that? Thanks.

Client or server?

 

I think these are the right server logs

ffmpeg-directstream-a10d92e3-9ccf-4242-abb8-d7711ba7f117_1.txt embyserver.txt

Edited February 1, 2021 by jpkeenanjr
added logs

[Luke 42078]

Are you still running into this?

[jpkeenanjr 2]

Nothing has changed.  Same problem on same clients.  

[Carlo 4561]

This appears to be an issues with the media itself so doubtful it's going to fix itself without replacing the media.

[jpkeenanjr 2]

Since it works on some clients and not others, I don't think the media is actually broken.  It's clear there's something about the encoding that some clients can deal with and others can't, but I can't reprocess the media to fix that unless you can tell me what specifically about it is causing some clients to choke.

 

[Carlo 4561]

Can you post the info shown at the bottom of the screen in the web app on the detain screen for this file?
That will let us see most of the high level file specs quite easy and maybe something will be obvious.

[jpkeenanjr 2]

That's in the first post in the thread.

 

[Carlo 4561]

Thanks didn't realize it was still the same file.  Nothing special at all about this file and it should be very common.

That leads me to personally think it's the file itself more so.

[ebr 16177]

16 hours ago, jpkeenanjr said:

Since it works on some clients and not others, I don't think the media is actually broken

The media can still be "broken" with respect to the proper specs for the format.  Many long-time video players have developed work-arounds for common problems or incorrect encodings but many of the newer, streaming-based players do not and require that the spec be adhered to much more closely.