jk022847 1 Posted December 30, 2018 Posted December 30, 2018 (edited) Using the latest beta version of Emby Server through a Nvidia Shield, I'm having a lot of trouble playing a ripped copy of Lilo and Stitch. I know the movie works because it works in all other media players (Plex, VLC, Kodi, etc). The video is a MKV that I converted a few years ago. Media information is attached along with the elbyserver.txt log and ffmpeg transcode log. I'm mostly curious what happened and if needed can do a re-convert or send the file somewhere. Lilo and Stitch.txt embyserver.txt ffmpeg-transcode-5a694c05-5172-43b6-bd99-bd8dd2243ef3_1.txt Edited December 30, 2018 by jk022847
jk022847 1 Posted December 31, 2018 Author Posted December 31, 2018 (edited) Just as an update, I tried to re-rip the movie (from the source DVD) again for testing. The movie failed to play again with the same errors in the ffmpeg log. Edited December 31, 2018 by jk022847
Luke 42077 Posted December 31, 2018 Posted December 31, 2018 Yea there are some QSV errors that I'd like @softwork'z input on. Thanks.
jk022847 1 Posted December 31, 2018 Author Posted December 31, 2018 Yea there are some QSV errors that I'd like @softwork'z input on. Thanks. Sounds good. Mostly I wanted to test again just in case I did something wrong since it had been a few years. If you all end up needing a copy of the video, let me know and I can upload somewhere.
jk022847 1 Posted January 1, 2019 Author Posted January 1, 2019 That would be great, thanks ! Thanks Luke. Is there someone I can send the link to download, preferably privately. I'd like to avoid sharing the download link out in a public forum.
jk022847 1 Posted January 1, 2019 Author Posted January 1, 2019 You can pm it to me. Thanks. Just sent you a PM.
softworkz 5066 Posted January 2, 2019 Posted January 2, 2019 Using the latest beta version of Emby Server through a Nvidia Shield, I'm having a lot of trouble playing a ripped copy of Lilo and Stitch. I know the movie works because it works in all other media players (Plex, VLC, Kodi, etc). The video is a MKV that I converted a few years ago. Media information is attached along with the elbyserver.txt log and ffmpeg transcode log. I'm mostly curious what happened and if needed can do a re-convert or send the file somewhere. Does it work when you disable the 'DXVA2 Intel® UHD Graphics 630 - MPEG-2' decoder?
jk022847 1 Posted January 3, 2019 Author Posted January 3, 2019 (edited) I'm not sure what changed here, but I cannot reproduce the issue today. I tested again before disabling the decoder and the movie direct streamed/played. I forced a transcode on it by lowering the allowable bit rate and it played properly even with the above decoder enabled. I do have emby server automatic updates enabled so maybe an update was pushed? Regardless, everything seems to be operating correctly now so I suppose we can consider this fixed. Thanks again for reading the thread/helping. Edited January 3, 2019 by jk022847
Luke 42077 Posted January 3, 2019 Posted January 3, 2019 Did you reboot your system, or apply a windows update, or hardware driver update? Any of those could impact it Also does the ffmpeg log produce the same command line as before?
jk022847 1 Posted January 3, 2019 Author Posted January 3, 2019 Did you reboot your system, or apply a windows update, or hardware driver update? Any of those could impact it Also does the ffmpeg log produce the same command line as before? No recent Windows updates, driver updates, reboots, etc. I'm not sure what you mean by the ffmpeg command line log, but I've attached it. I just checked the logs and Emby Server was updated to 3.6.0.82 this morning at 7:00am (from 3.6.0.81), so maybe that was it? ffmpeg-directstream-c6aca36d-d0fe-42cd-b56c-1b187507db4c_1.txt
Luke 42077 Posted January 3, 2019 Posted January 3, 2019 It's now stream copying the original video instead of transcoding. As a test, try lowering the in-app quality setting to something like 4 mbps, and then you should see the problem again. Thanks.
jk022847 1 Posted January 3, 2019 Author Posted January 3, 2019 (edited) It's now stream copying the original video instead of transcoding. As a test, try lowering the in-app quality setting to something like 4 mbps, and then you should see the problem again. Thanks. Yeah, that's the confusing part. It wasn't direct playing before. Up until yesterday, it was transcoding. I lowered it to 1.5mbps just now which forced a transcode but it is playing correctly. Attached the log from just now as well. ffmpeg-transcode-09ede9d2-71d1-479e-b4e5-ebb91c085eaa_1.txt Edited January 3, 2019 by jk022847
Happy2Play 9780 Posted January 3, 2019 Posted January 3, 2019 (edited) The log in the first post had subtitle burnin and previous log had no subs. Edited January 3, 2019 by Happy2Play
jk022847 1 Posted January 3, 2019 Author Posted January 3, 2019 (edited) The log in the first post had subtitle burnin and previous log had no subs. Good catch. I turned on subtitles (this is the same file as previous) and lowered the quality to 1.5mbps. The video plays but is mostly unwatchable. Similar errors in the logs as previous. Disabling the DXVA2 Intel® UHD Graphics 630 - MPEG-2' decoder and everything is completely watchable (same subtitles and 1.5mbps bit rate). Both logs are attached. Sorry for the confusion here everyone. decoder enabled ffmpeg-transcode-1a21fba4-3f67-4b7e-9f3f-dad0213f29b5_1.txt decoder disabled ffmpeg-transcode-2f22fb8b-1ed5-4c35-b857-40acba7c7cf8_1.txt Edited January 3, 2019 by jk022847
softworkz 5066 Posted January 3, 2019 Posted January 3, 2019 Disabling the DXVA2 Intel® UHD Graphics 630 - MPEG-2' decoder and everything is completely watchable (same subtitles and 1.5mbps bit rate). Thanks, that confirms my initial suspicion. It's an edge case cause by mixed hardware accelerations in combination with subtitle burn-in. Better support for using mixed hwa's is planned for the future, but for now we'll probably need to disable DXVA decoding for this special case.
Solution softworkz 5066 Posted January 3, 2019 Solution Posted January 3, 2019 Will be fixed in the next version (= disable DXVA decoding for this special case) 1
jk022847 1 Posted January 3, 2019 Author Posted January 3, 2019 Will be fixed in the next version (= disable DXVA decoding for this special case) Awesome! Thanks to everyone that has helped with this.
Luke 42077 Posted January 6, 2019 Posted January 6, 2019 @@jk022847 have you retested this on the latest beta? thanks.
jk022847 1 Posted January 6, 2019 Author Posted January 6, 2019 @@jk022847 have you retested this on the latest beta? thanks. I just tried it a few times and it has worked perfectly every time. Thanks again to everyone that has helped with this. The level of support has been amazing.
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