shpitz461 4 Posted October 8, 2018 Author Share Posted October 8, 2018 I have postings all throughout, why do you feel I'm ignoring it? I said 'in a way' Maybe 'less enthused' would be a better word, after all, I've reported this 5 months ago. Regardless, I would appreciate if we can get a resolution, I'd be happy to help with testing builds. Doofus suspects it has something to do with the parameters passed by ET to MPV, we can start there. I'm not sure if all parameters are passed using 'playbackhandler.js' or some are hardcoded within ET. Link to comment Share on other sites More sharing options...
shpitz461 4 Posted October 8, 2018 Author Share Posted October 8, 2018 Actually, the underlying problem may be ffmpeg. The only time I don't see errors is when I use cuda. The mpv standalone seems to be able to roll over them, and continue. But possibly how the stream is being served in emby, may be affecting mpv's ability to do that. How does ffmpeg come into play in our scenario? I'm direct-playing the file, there is no ffmpeg running on my Emby Server while playing the mk3d movie... Link to comment Share on other sites More sharing options...
shpitz461 4 Posted October 8, 2018 Author Share Posted October 8, 2018 @@shpitz461 try this. Use d3d11 copyback, and then put this in your mpv.conf hwdec-image-format=yuv420p This is just a test, don't leave it in there for all videos. If it works, I'll try and make an auto-profile to apply it only to these specific videos. EDIT: Scratch that. I can't get it to work in the standalone. Can't select D3D copyback since it says Windows 8+ and I'm running Windows 7. Link to comment Share on other sites More sharing options...
Guest asrequested Posted October 8, 2018 Share Posted October 8, 2018 (edited) How does ffmpeg come into play in our scenario? I'm direct-playing the file, there is no ffmpeg running on my Emby Server while playing the mk3d movie...mpv is built on ffmpeg, and they add their algorithms to work with ffmpeg. I keep forgetting you're using Windows 7 Edited October 8, 2018 by Doofus Link to comment Share on other sites More sharing options...
Guest asrequested Posted October 27, 2018 Share Posted October 27, 2018 (edited) So I'm pretty sure that this is an ffmpeg bug, that electron is bumping heads with. I've just run a bunch more tests with the latest git build. I was trying to find a config that would eliminate the 'out of range' issue. I was not able to. CUDA works differently to the other hwdec. CUDA works directly with the GPU. The other options are fed to the GPU from ffmpeg, so CUDA essentially circumvents that, and works correctly. So until ffmpeg sorts it, and the mpv guys use that to build with, I don't see a way to make it work. The other slight possibility is that the new electron builds, get sorted. But until Luke can figure out the issue with why electron 3.0.x is freezing Theater, I can't really test this. Edited October 27, 2018 by Doofus Link to comment Share on other sites More sharing options...
shpitz461 4 Posted October 27, 2018 Author Share Posted October 27, 2018 But if mpv plays it fine outside of ET then how can we conclude it's mpv's fault? We need to have a minimal number of parameters passed to mpv via ET and try to establish a baseline. Link to comment Share on other sites More sharing options...
Guest asrequested Posted October 27, 2018 Share Posted October 27, 2018 But if mpv plays it fine outside of ET then how can we conclude it's mpv's fault? We need to have a minimal number of parameters passed to mpv via ET and try to establish a baseline. It looks like it's ffmpeg, not mpv. Without 3rd party involvement (in this case, electron), mpv just rolls over the 'out of range' elements. My supposition is that electron is interfering with that. The same commands are issued to mpv as an external player, and it plays. But inside Theater, where electron is running, it freezes. Electron is moving very fast with development. But right now, using anything above 2.0.x, causes problems with Theater. Link to comment Share on other sites More sharing options...
shpitz461 4 Posted October 27, 2018 Author Share Posted October 27, 2018 Oh, I see. Link to comment Share on other sites More sharing options...
shpitz461 4 Posted December 6, 2019 Author Share Posted December 6, 2019 So it's been a year and a half, is there anything we can try to eliminate this issue? Link to comment Share on other sites More sharing options...
Guest asrequested Posted December 6, 2019 Share Posted December 6, 2019 Until the re-design of the UI happens, I think we're on hold. mpv has had hundreds of updates. I haven't tested this in a while. It might be interesting to see if any of them have made a difference. The demuxers have had some development, and I suspect that's where this issue might lay. Unless it's ffmpeg upstream. I'll try to test it over the weekend. 1 Link to comment Share on other sites More sharing options...
Guest asrequested Posted December 7, 2019 Share Posted December 7, 2019 Sadly, no change in Theater. Almost no errors in the standalone, though. Hmmmm....... I wonder if it's because it's using a pipe and ffmpeg doesn't like it..... Link to comment Share on other sites More sharing options...
Luke 37065 Posted December 7, 2019 Share Posted December 7, 2019 It's not using a pipe. Link to comment Share on other sites More sharing options...
Guest asrequested Posted December 7, 2019 Share Posted December 7, 2019 (edited) It's not using a pipe. I beg to differ... [ 0.008][v][ipc] Starting IPC master [ 0.008][d][ytdl_hook] loading mp.defaults [ 0.008][d][stats] loading mp.defaults [ 0.008][v][ipc] Listening to IPC pipe. [ 0.009][d][ytdl_hook] loading @ytdl_hook.lua [ 0.009][v][ipc_0] Client connected I don't see this in the standalone log Edited December 7, 2019 by Doofus Link to comment Share on other sites More sharing options...
Luke 37065 Posted December 7, 2019 Share Posted December 7, 2019 Well we're giving it a window id to render on, so that's probably related to how it handles that. Link to comment Share on other sites More sharing options...
Guest asrequested Posted December 7, 2019 Share Posted December 7, 2019 Aren't you using --input-ipc-server https://mpv.io/manual/master/#options-input-ipc-server Link to comment Share on other sites More sharing options...
Luke 37065 Posted December 7, 2019 Share Posted December 7, 2019 No. Link to comment Share on other sites More sharing options...
Luke 37065 Posted December 7, 2019 Share Posted December 7, 2019 But maybe nodempv is. Link to comment Share on other sites More sharing options...
Guest asrequested Posted December 7, 2019 Share Posted December 7, 2019 Here it is in the playbackhandler. Line 951 if (isWindows()) { mpvInitOptions.socket = "\\\\.\\pipe\\emby-pipe"; mpvInitOptions.ipc_command = "--input-ipc-server"; Link to comment Share on other sites More sharing options...
Luke 37065 Posted December 7, 2019 Share Posted December 7, 2019 Ah so we are. Link to comment Share on other sites More sharing options...
Guest asrequested Posted December 7, 2019 Share Posted December 7, 2019 I'm thinking that's causing some issues.... Link to comment Share on other sites More sharing options...
Luke 37065 Posted December 7, 2019 Share Posted December 7, 2019 Well I'd have to look at what we're using it for but I'm sure it's there for a reason. It's probably needed to communicate with the player during playback. Link to comment Share on other sites More sharing options...
Guest asrequested Posted December 7, 2019 Share Posted December 7, 2019 Maybe....but that's the issue, here. Without that, I'll bet it will play. With it, ffmpeg doesn't like it, and you get this until ffmpeg crashes. [ 1.798][e][ffmpeg/video] h264: sps_id 1 out of range [ 2.798][e][ffmpeg/video] h264: sps_id 1 out of range [ 3.799][e][ffmpeg/video] h264: sps_id 1 out of range [ 4.800][e][ffmpeg/video] h264: sps_id 1 out of range [ 5.800][e][ffmpeg/video] h264: sps_id 1 out of range [ 6.803][e][ffmpeg/video] h264: sps_id 1 out of range [ 7.804][e][ffmpeg/video] h264: sps_id 1 out of range [ 8.806][e][ffmpeg/video] h264: sps_id 1 out of range Link to comment Share on other sites More sharing options...
Guest asrequested Posted December 7, 2019 Share Posted December 7, 2019 Testing in standalone with input-ipc-server=\\.\pipe\tmp\mpv-socket A quick look at the logs, and the error is reproduced. I'll see what happens at the 26 minute mark....... Link to comment Share on other sites More sharing options...
Guest asrequested Posted December 7, 2019 Share Posted December 7, 2019 Well, the same errors occur, but it plays through. So that would imply that something in emby is what is not liking this. Link to comment Share on other sites More sharing options...
Guest asrequested Posted December 7, 2019 Share Posted December 7, 2019 (edited) Here's where it starts 2019-12-06 19:24:00.005 Info SessionManager: Playback start reported by app Emby Theater 3.0.10 playing Wonder Woman. Started at 0 ms 2019-12-06 19:24:00.005 Info HttpServer: HTTP Response 204 to 10.1.1.13. Time: 7ms. http://10.1.1.14:8096/emby/Sessions/Playing 2019-12-06 19:24:00.006 Info PlaybackReporting - EventMonitorEntryPoint: _sessionManager_PlaybackStart : Entered 2019-12-06 19:24:00.006 Info PlaybackReporting - EventMonitorEntryPoint: Adding PlaybackInfo to playback_trackers : HTPC-6a8eb582a4af42d1bcef357a756df9b8-1046373 And here's about where it ends 2019-12-06 19:50:28.845 Debug ImageProcessor: Getting image size for item Video \\Htpc\d\Temp Movie Library\Wonder Woman 3D\poster.jpg 2019-12-06 19:50:28.852 Info HttpServer: HTTP Response 200 to 10.1.1.13. Time: 9ms. http://10.1.1.14:8096/emby/Users/6a8eb582a4af42d1bcef357a756df9b8/Items/1046373 2019-12-06 19:50:28.853 Info HttpServer: HTTP GET http://10.1.1.14:8096/emby/Users/6a8eb582a4af42d1bcef357a756df9b8. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) EmbyTheater/3.0.10 Chrome/78.0.3904.92 Electron/7.0.1 Safari/537.36 2019-12-06 19:50:28.853 Info HttpServer: HTTP Response 200 to 10.1.1.13. Time: 1ms. http://10.1.1.14:8096/emby/Users/6a8eb582a4af42d1bcef357a756df9b8 2019-12-06 19:50:29.250 Info HttpServer: HTTP POST http://10.1.1.14:8096/emby/Items/1046373/PlaybackInfo?UserId=6a8eb582a4af42d1bcef357a756df9b8&StartTimeTicks=0&IsPlayback=false&AutoOpenLiveStream=false&MaxStreamingBitrate=120000000&DirectPlayProtocols=File%2CHttp%2CRtp%2CRtmp%2CRtsp%2CFtp. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) EmbyTheater/3.0.10 Chrome/78.0.3904.92 Electron/7.0.1 Safari/537.36 2019-12-06 19:50:29.250 Info HttpServer: HTTP GET http://10.1.1.14:8096/emby/Items/1046373/ThemeMedia?UserId=6a8eb582a4af42d1bcef357a756df9b8&InheritFromParent=true&EnableThemeSongs=false&EnableThemeVideos=false. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) EmbyTheater/3.0.10 Chrome/78.0.3904.92 Electron/7.0.1 Safari/537.36 Edited December 7, 2019 by Doofus Link to comment Share on other sites More sharing options...
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