Jump to content

Google TV Streamer refuses to directplay beetlejuice beetlejuice


Recommended Posts

Posted

I tested other movies as well but this one just gets transcoded

 

It works fine on plex with same device

 

Also i tried many dolbyvision/hdr10 movies and they directplay without issues. 

 

Works on fine with shield tv 2019 model

 

https://pastebin.com/hhbBRUnT

Posted

Hi. And what does the stats in the player or the dashboard on your server say the transcoding reason is?

Posted

Dashboard says recovering from playback error while client says just direct play error it doesnt specify why thou

Posted

Hi, occasionally this can happen with certain videos. That's why we have the automatic recovery to still allow it to keep playing with transcoding.

Posted

it tries to play it but it will fail at somepoint. Here is the log for that. i also reripped that movie just in case there is problems with file but still does same. My android phones and shield tv will play that movie with emby without any issues but my roommates Google TV Streamer has issues with this movie atleast

ffmpeg-transcode-ad0ff8f1-ca07-4c48-895a-b435d92cbbf7_1.txt

Posted

Will do when i get home from work

Posted

Okay logs sended from the app to you way few minutes ago. It yet again tries to play it but even with transcoding it will just error out

Posted

Hi. Is this a DV/HDR item?  I'm guessing the exact format isn't actually supported on the device:

format_supported=NO_EXCEEDS_CAPABILITIES

But the version of Exo in the TV app cannot discover this before trying playback.  The other app not only has a newer version of Exo but also has custom modifications we've added to deal with unsupported HDR formats more gracefully.

Posted

Yes it is dv/hdr movie but this is only one i have issues with. My other dv/hdr titles work without issues and all of them are 4k uhd rips from my discs

Posted

Something about this one is different.  Perhaps the DV profile.

Posted

Yep its most probable reason for it and app doesnt do fallback to hdr10. I guess i could just remove dv layers hence dv aint anyways supported with android tv and i have samsung tv anyways so no dv support

Posted (edited)
4 hours ago, TomPPaZ said:

Yep its most probable reason for it and app doesnt do fallback to hdr10. I guess i could just remove dv layers hence dv aint anyways supported with android tv and i have samsung tv anyways so no dv support

Relating to this one. Apparently issue is dolby vision profile 7 that has BL+EL+RTP you can see this in makemkv before you rip.

 

One easy workaround is just to install jellyfin-ffmpeg and dovi_tool and run

cd /pathtomovie

/usr/lib/jellyfin-ffmpeg/ffmpeg -y -hide_banner -stats -fflags +genpts+igndts -loglevel error -i "dv_video.mkv" -map 0 -bsf:v hevc_metadata=remove_dovi=1 -codec copy -max_muxing_queue_size 2048 -max_interleave_delta 0 -avoid_negative_ts disabled hdr10_video.mkv

 

and after this just

mv hdr10_video.mkv nameofthemovie.mkv

 

note that this only works with dovi movies that have multi layers like profile 7

this basically removes EL and RTP metadata so its plain HDR10 after that

 

leaving this just in case someone else runs into same issues before this issue gets fixed

Edited by TomPPaZ
Missing info
Posted

Hi.  Can you try searching for our standard android app (Just "Emby" on Amazon and "Emby for Android on Google) on the same device's app store and see how that compares?

Thanks.

 

Posted

It plays the file it HDR nut video itself lags a lot. Its more like watching powerpoint instead of movie so that didnt solve issue.

Posted

OK we'll take a look at it. Thanks.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...