caffeineshock 18 Posted November 17, 2023 Posted November 17, 2023 (edited) heyho. ive got an issue with emby and playback of higher-bitrate-videofiles Situation: playback of dolby-vision stream with higher bitrate (lets say 60mbit) with more than sufficient bandwith and device that are capable of playback (nvidia shield pro on a philips 77 oled 807. the issue is new. it worked in the past without any issues) as soon as i start the playback the dolby-vision on my tv triggers, emby shows regular playback on the dashboard it buffers or something, idk then it drops down to hdr10 on the tv emby dashboard reports "recovery from playback error" but thats not the end SOMEHOW ffmpeg transcodes to the wrong directory. i set up E:\temp (which is a ssd-cached drive-array) to be the temp for everything: emby temp, transcode temp etc BUT it transcodes into %appdata%\emby-server (running windows here) this leads to the ssd where the vm is running to be overwhelmed (not the fastest + a few vms are running on this ssd) and (i think) to be the root of the issue: stutter during playback. every 10-30 seconds the movie starts buffering for a few seconds which is pretty awfull so my questions are: why des ffmpeg transcode into the wrong directory? why does it transcode at all? it does not have to. sound and video are supported by the whole chain (shield + tv + avr). it didnt do that in the past. i was able to transcode 5 60mbit streams at once and play a few directly if needed. but now i struggle playing a single one. WTF thanks for the help p.s. i really would like not to publicate the logs as i dont like certain informatins that are there being public. in case they are needed (i saved them) i can send them to one of the mods / admin / support team Edited November 17, 2023 by caffeineshock
Luke 42078 Posted November 17, 2023 Posted November 17, 2023 Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!
Luke 42078 Posted November 17, 2023 Posted November 17, 2023 The server is most likely being denied write access to whatever temp folder you configured. 1
caffeineshock 18 Posted November 18, 2023 Author Posted November 18, 2023 hmmm strange. thats new. it definetly has permission to access it. it runs as user X which is the owner of the directory. yeah i will check that. but it should not matter as its just a symptom of the actual issue: why is the trnscoding happening in the first place? nvidia shield and the tv do support it, its enabled, everywhere. it even pops up for a short moment on the tv and then it starts transcoding. why. the only reason i could think of is one of the devices does not suupport dv but, which? the well tested shield that officially supports dv? the tv that officially supports it? i dont get it
caffeineshock 18 Posted November 18, 2023 Author Posted November 18, 2023 (edited) okay, thx for the hint @Luke solved the directory issue. indeed, emby was not able to access the unc path. idk why. mounted locally, done. sadly, not the root of the issue with unsupported DV @Lukeyeahh.... i would like to avoid giving everyone access to the data. can i just pm you the logs? Edited November 18, 2023 by caffeineshock
GrimReaper 4740 Posted November 18, 2023 Posted November 18, 2023 Out of curiosity, is your server local or remote, as your screenshots show remote playback (btw, you might want to mask that remote address)?
caffeineshock 18 Posted November 18, 2023 Author Posted November 18, 2023 @GrimReaper Remote. But it's not a bandwidth issue. Got hdr10 material with 60mbit that works without any trouble. But dv 50mbit soea cause trouble Idc about my public ip but thanks it's not about security
GrimReaper 4740 Posted November 18, 2023 Posted November 18, 2023 1 minute ago, caffeineshock said: Remote. But it's not a bandwidth issue. Got hdr10 material with 60mbit that works without any trouble. But dv 50mbit soea cause trouble I understand, just wanted to confirm it's not local so you could do in-LAN playback test for comparison purposes.
caffeineshock 18 Posted November 18, 2023 Author Posted November 18, 2023 (edited) 6 minutes ago, GrimReaper said: I understand, just wanted to confirm it's not local so you could do in-LAN playback test for comparison purposes. I could access the files through vpn What do you want me to do exactly? Edited November 18, 2023 by caffeineshock
GrimReaper 4740 Posted November 18, 2023 Posted November 18, 2023 3 minutes ago, caffeineshock said: I could can access the files through vpn Nah, just wanted to eliminate/minimize possible network interference, but actual conditions would still be the same. What you could do, though, is sideload standard Android app to your Shield and see how does that compare? https://emby.media/emby-for-android.html 1
caffeineshock 18 Posted November 18, 2023 Author Posted November 18, 2023 2 minutes ago, GrimReaper said: Nah, just wanted to eliminate/minimize possible network interference, but actual conditions would still be the same. What you could do, though, is sideload standard Android app to your Shield and see how does that compare? https://emby.media/emby-for-android.html Good idea I'll try an external player as well...tomorrow. maybe vlc or similar P.s. it really is not a bandwidth issue.
ebr 16177 Posted November 18, 2023 Posted November 18, 2023 15 hours ago, caffeineshock said: why is the trnscoding happening in the first place? Hi. For the reason it states right there. The player encountered an error trying to direct play so we are using a different method to try and get past that error. Can you please play that item until the playback change occurs and then follow the instructions to send a log from the app?
caffeineshock 18 Posted November 19, 2023 Author Posted November 19, 2023 16 hours ago, ebr said: Hi. For the reason it states right there. The player encountered an error trying to direct play so we are using a different method to try and get past that error. Can you please play that item until the playback change occurs and then follow the instructions to send a log from the app? yeah ofc the player encountered an error. the quesstion is why. thats why the topic exists^^ as i mentioned, i would like to avoid publishing the log (dont like the world to see all the informations like usernames, domain, ip of the server, directories, files and so on. would take a lot of time to edit them out). but i would not have any problems sending them directly to someone from the emby-team
caffeineshock 18 Posted November 19, 2023 Author Posted November 19, 2023 On 11/18/2023 at 1:49 AM, GrimReaper said: Nah, just wanted to eliminate/minimize possible network interference, but actual conditions would still be the same. What you could do, though, is sideload standard Android app to your Shield and see how does that compare? https://emby.media/emby-for-android.html would you look at that! the app for "reguar android" works fine. just tested the android-tv app again, still the issue. but fpor the regular app the dolby vision logo notification pops up and does not fail back to hdr 10 same user, same server, same file. so there is something wrong with the emby-app. 1
caffeineshock 18 Posted November 19, 2023 Author Posted November 19, 2023 cleared cache, uninstalled the android-tv-emby, reinstalled, set limit to 1000mbit (so no limit), started theh movie and the same issue so there might be an issue with the latest android tv version in combination with the shield since the regular android app does not produce this issue so its not the server. emby android tv version fresh from the playstore so its the latest version (according to app settings its 2.0.98g) any idea whats broken?
GrimReaper 4740 Posted November 19, 2023 Posted November 19, 2023 16 hours ago, ebr said: Can you please play that item until the playback change occurs and then follow the instructions to send a log from the app? 24 minutes ago, caffeineshock said: as i mentioned, i would like to avoid publishing the log (dont like the world to see all the informations like usernames, domain, ip of the server, directories, files and so on. would take a lot of time to edit them out). but i would not have any problems sending them directly to someone from the emby-team In-app logs are sent directly to the Devs, nothing is published, just follow instructions in the link above.
caffeineshock 18 Posted November 19, 2023 Author Posted November 19, 2023 (edited) 12 minutes ago, GrimReaper said: In-app logs are sent directly to the Devs, nothing is published, just follow instructions in the link above. yeah app logs do, sure. but server logs dont. thats what ive been talking about did send it right now: playback of: Star Wars: Der Aufstieg Skywalkers 9:57 (germany) | UTC its 8:57 user thats was logged in: anatol Edited November 19, 2023 by caffeineshock
ebr 16177 Posted November 19, 2023 Posted November 19, 2023 Hi. There is an issue of some sort with the audio track on that item: 11-19 09:57:06.508 29703 29703 E EventLogger: Caused by: com.google.android.exoplayer2.audio.AudioSink$InitializationException: AudioTrack init failed 0 Config(48000, 6396, 1531250) Format(2, Deutsch Dolby TrueHD Atmos 7.1 (mixed by Moe123), null, audio/true-hd, null, -1, de, [-1, -1, -1.0], [8, 48000]) It appears you played a different item with the other app above as it was a DTS-HD track and this is TrueHD.
caffeineshock 18 Posted November 19, 2023 Author Posted November 19, 2023 4 hours ago, ebr said: Hi. There is an issue of some sort with the audio track on that item: 11-19 09:57:06.508 29703 29703 E EventLogger: Caused by: com.google.android.exoplayer2.audio.AudioSink$InitializationException: AudioTrack init failed 0 Config(48000, 6396, 1531250) Format(2, Deutsch Dolby TrueHD Atmos 7.1 (mixed by Moe123), null, audio/true-hd, null, -1, de, [-1, -1, -1.0], [8, 48000]) It appears you played a different item with the other app above as it was a DTS-HD track and this is TrueHD. I tried all of the available audio tracks down to ac3 with the same result. You want me to create a log where I try different tracks?
ebr 16177 Posted November 20, 2023 Posted November 20, 2023 Hi. When it worked with the standard app, were you actually getting a bitstream of DTS-HD at the target device or was it being decoded by the app?
caffeineshock 18 Posted November 20, 2023 Author Posted November 20, 2023 2 hours ago, ebr said: Hi. When it worked with the standard app, were you actually getting a bitstream of DTS-HD at the target device or was it being decoded by the app? i probably just went for the defaul selection while testing before just did the test with all the available options: emby android tv: no matter which audio track i select, ac3 dts or dolby atmos, i fall back to hdr10. even tried with and without subtitels (just in case, you never know). emby for android: no matterr which audio track i select, ac3 dts or dolby, dolby visions stays. no fallback to hdr10. im really not sure who decodes the stream but i think its the tv (app runs on nvidia shield, bitstreams (i guess) to tv via hdmi 2.1 which then passes it to the avr which does not matter since the shield does not know of its existence ^^)
Luke 42078 Posted November 20, 2023 Posted November 20, 2023 Are you happy continuing to use the standard app?
caffeineshock 18 Posted November 20, 2023 Author Posted November 20, 2023 3 minutes ago, Luke said: Are you happy continuing to use the standard app? i already had the thought. it looks slightly "wrong" on a huge tv screen. obviously not made for it. right now its the only solution (if i want to watch in DV). solving the issue would be great ofc but its not a life and death situation^^ you guys really have no idea? -.-
Luke 42078 Posted November 20, 2023 Posted November 20, 2023 Just now, caffeineshock said: i already had the thought. it looks slightly "wrong" on a huge tv screen. obviously not made for it. right now its the only solution (if i want to watch in DV). solving the issue would be great ofc but its not a life and death situation^^ you guys really have no idea? -.- It is made for a TV. Why do you think it isn't?
caffeineshock 18 Posted November 20, 2023 Author Posted November 20, 2023 wait i think we talk about 2 different things. the app that works is the regular android one, the other thats broken is for android tv. or do i missunderstand something
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now