buggsy 0 Posted August 16, 2019 Share Posted August 16, 2019 I am new to Emby, and I am having a reoccurring issue where my playback of a show (nightly local news) is pixilating and freezing. This has happened 2 nights in a row at nearly the same time during the recording. It is still currently recording while I am watching, and I have not gotten to live yet (35 minute show and freezing around 20 minutes). This also has happened at least 3 times in the week and half I have been using Emby (switched from Plex due to problems they have not fixed to playback during recording that has been going on for months). I have had a few successful playbacks during recording, but the wife gets quite frustrated when we cannot get through the news, hopefully you can feel my pain. We are using FireTv. However, I just tried to play last nights recording on my computer and it freezes in the same place. I am pasting a snippet of the log below, the errors just keep going. Could I have a setting wrong, or??? I am not even sure what to try. I can't really seem to find a definitive guide on configuring my system. Which is a Synology DS918+ and is up to date, I have tons of storage (only using 10%), but I have not added any m.2 cache to the system (it is stock other than expanded hd space). Any suggestions would be greatly appreciated (I have searched and can't find any topics that seem to relate, so I hope it is something I can adjust on my end to fix it). My transcoding settings are basically the defaults, except I have change the thread count from Auto to 2. here is the log snippet: [segment @ 0x17fb3c0] Opening '/var/packages/EmbyServer/target/var/transcoding-temp/0edac696d738c571f5d75d3a4ff432ad353.ts.tmp' for writingelapsed=00:00:29.98 frame= 1008 fps= 34 q=29.0 size= 17879kB time=00:17:39.21 bitrate= 138.3kbits/s throttle=off speed=35.3xelapsed=00:00:30.50 frame= 1031 fps= 34 q=29.0 size= 17974kB time=00:17:40.05 bitrate= 138.9kbits/s throttle=off speed=34.8xelapsed=00:00:31.00 frame= 1054 fps= 34 q=29.0 size= 18068kB time=00:17:40.68 bitrate= 139.5kbits/s throttle=off speed=34.2xelapsed=00:00:31.50 frame= 1072 fps= 34 q=29.0 size= 18297kB time=00:17:41.32 bitrate= 141.2kbits/s throttle=off speed=33.7xelapsed=00:00:32.00 frame= 1090 fps= 34 q=29.0 size= 18542kB time=00:17:41.97 bitrate= 143.0kbits/s throttle=off speed=33.2x[segment @ 0x17fb3c0] Opening '/var/packages/EmbyServer/target/var/transcoding-temp/0edac696d738c571f5d75d3a4ff432ad.m3u8.tmp' for writingSegmentComplete=video:0 Index=353 Start=1059.058000 End=1062.061000 Duration=3.003000 offset_pts=0 start_pts=1059058000 Frames=90 filename=0edac696d738c571f5d75d3a4ff432ad353.ts[segment @ 0x17fb3c0] Opening '/var/packages/EmbyServer/target/var/transcoding-temp/0edac696d738c571f5d75d3a4ff432ad354.ts.tmp' for writingelapsed=00:00:32.54 frame= 1107 fps= 34 q=29.0 size= 18815kB time=00:17:42.45 bitrate= 145.1kbits/s throttle=off speed=32.6xelapsed=00:00:33.05 frame= 1125 fps= 34 q=29.0 size= 18965kB time=00:17:43.12 bitrate= 146.1kbits/s throttle=off speed=32.2x[mpeg2video @ 0x177b900] 00 motion_type at 25 67[mpeg2video @ 0x177b900] 00 motion_type at 3 45[mpeg2video @ 0x177b900] 00 motion_type at 5 46[mpeg2video @ 0x177b900] mb incr damaged[mpeg2video @ 0x177b900] 00 motion_type at 4 48[mpeg2video @ 0x177b900] 00 motion_type at 20 49[mpeg2video @ 0x177b900] 00 motion_type at 26 50[mpeg2video @ 0x177b900] 00 motion_type at 53 51[mpeg2video @ 0x177b900] 00 motion_type at 23 52[mpeg2video @ 0x177b900] 00 motion_type at 55 53[mpeg2video @ 0x177b900] 00 motion_type at 23 54[mpeg2video @ 0x177b900] 00 motion_type at 37 55[mpeg2video @ 0x177b900] 00 motion_type at 11 56[mpeg2video @ 0x177b900] 00 motion_type at 2 57[mpeg2video @ 0x177b900] 00 motion_type at 38 58[mpeg2video @ 0x177b900] 00 motion_type at 3 59[mpeg2video @ 0x177b900] ac-tex damaged at 2 60[mpeg2video @ 0x177b900] 00 motion_type at 6 61[mpeg2video @ 0x177b900] ac-tex damaged at 25 62[mpeg2video @ 0x177b900] 00 motion_type at 11 63[mpeg2video @ 0x177b900] 00 motion_type at 38 64[mpeg2video @ 0x177b900] 00 motion_type at 24 65[mpeg2video @ 0x177b900] 00 motion_type at 30 66[mpeg2video @ 0x177b900] 00 motion_type at 3 67[mpeg2video @ 0x177b900] Warning MVs not available[mpeg2video @ 0x177b900] concealing 2760 DC, 2760 AC, 2760 MV errors in P frame[mpegts @ 0x17593c0] PES packet size mismatchError while decoding stream #0:1: Error number -16976906 occurred[mpeg2video @ 0x177b900] 00 motion_type at 9 54[mpeg2video @ 0x177b900] 00 motion_type at 4 55[mpeg2video @ 0x177b900] ac-tex damaged at 8 56[mpeg2video @ 0x177b900] 00 motion_type at 3 57[mpeg2video @ 0x177b900] invalid cbp 0 at 18 58[mpeg2video @ 0x177b900] 00 motion_type at 29 59[mpeg2video @ 0x177b900] 00 motion_type at 56 60[mpeg2video @ 0x177b900] 00 motion_type at 12 61[mpeg2video @ 0x177b900] invalid cbp 0 at 16 62[mpeg2video @ 0x177b900] 00 motion_type at 3 63[mpeg2video @ 0x177b900] mb incr damaged[mpeg2video @ 0x177b900] 00 motion_type at 38 65[mpeg2video @ 0x177b900] 00 motion_type at 37 66[mpeg2video @ 0x177b900] 00 motion_type at 53 67[mpeg2video @ 0x177b900] 00 motion_type at 61 21[mpeg2video @ 0x177b900] 00 motion_type at 1 22[mpeg2video @ 0x177b900] 00 motion_type at 14 23[mpeg2video @ 0x177b900] invalid cbp 0 at 74 24[mpeg2video @ 0x177b900] 00 motion_type at 11 25[mpeg2video @ 0x177b900] mb incr damaged[mpeg2video @ 0x177b900] Invalid mb type in P-frame at 42 27[mpeg2video @ 0x177b900] invalid cbp -1 at 44 28[mpeg2video @ 0x177b900] 00 motion_type at 3 29[mpeg2video @ 0x177b900] 00 motion_type at 13 30[mpeg2video @ 0x177b900] invalid cbp 0 at 24 31[mpeg2video @ 0x177b900] slice mismatch[mpeg2video @ 0x177b900] invalid cbp 0 at 24 33[mpeg2video @ 0x177b900] ac-tex damaged at 17 34[mpeg2video @ 0x177b900] 00 motion_type at 29 35[mpeg2video @ 0x177b900] mb incr damaged[mpeg2video @ 0x177b900] 00 motion_type at 23 37[mpeg2video @ 0x177b900] mb incr damaged[mpeg2video @ 0x177b900] 00 motion_type at 2 39[mpeg2video @ 0x177b900] 00 motion_type at 11 40[mpeg2video @ 0x177b900] 00 motion_type at 6 41[mpeg2video @ 0x177b900] ac-tex damaged at 16 42[mpeg2video @ 0x177b900] 00 motion_type at 17 43[mpeg2video @ 0x177b900] 00 motion_type at 2 44[mpeg2video @ 0x177b900] Invalid mb type in P-frame at 29 45[mpeg2video @ 0x177b900] 00 motion_type at 4 46[mpeg2video @ 0x177b900] 00 motion_type at 63 47[mpeg2video @ 0x177b900] 00 motion_type at 70 48[mpeg2video @ 0x177b900] invalid cbp -1 at 19 49[mpeg2video @ 0x177b900] invalid cbp 0 at 3 50[mpeg2video @ 0x177b900] Invalid mb type in P-frame at 9 51[mpeg2video @ 0x177b900] 00 motion_type at 1 52[mpeg2video @ 0x177b900] 00 motion_type at 4 53[mpeg2video @ 0x177b900] Warning MVs not available[mpeg2video @ 0x177b900] concealing 5639 DC, 5639 AC, 5639 MV errors in P frameelapsed=00:00:34.11 frame= 1182 fps= 35 q=29.0 size= 19456kB time=00:17:44.83 bitrate= 149.7kbits/s dup=43 drop=0 throttle=off speed=31.2x[mpegts @ 0x17593c0] PES packet size mismatch[ac3 @ 0x17fcec0] exponent -1 is out-of-range[ac3 @ 0x17fcec0] error decoding the audio blockError while decoding stream #0:1: Error number -16976906 occurred Link to comment Share on other sites More sharing options...
Luke 36816 Posted August 17, 2019 Share Posted August 17, 2019 Hi there, can you please attach the complete emby server and ffmpeg logs? Thanks ! Link to comment Share on other sites More sharing options...
PristDean 13 Posted August 17, 2019 Share Posted August 17, 2019 Hey, I have the same issue, already posted here: https://emby.media/community/index.php?/topic/76260-pixelation-picture-breakup/ I use a HD Homerun with quad tuners, plus a Synology NAS DS218+ with a Nvidia Shield to playback To me it seems as if Emby needs a very strong uninterrupted signal to work seamlessly with a live TV broadcast, appears it struggles with transcoding a weak or interrupted signal. I have experienced the HD Homerun app working when Emby will not on a live TV signal. I believe Emby are looking at improving resilience, but long and short here is ensure your live TV signal strength is as strong as it can possibly be in the meantime Link to comment Share on other sites More sharing options...
buggsy 0 Posted August 19, 2019 Author Share Posted August 19, 2019 I am thinking that PristDean's suggestion may be correct... I have had a nice strong signal for a year but I believe something has changed and it may not be so strong anymore and the weak signal may be causing my issues. I have ordered a new OTA antenna for my attic (to replace the little plastic sheet attached to my wall)... I should have it in a couple days and I will follow up then. Thanks!! Link to comment Share on other sites More sharing options...
Luke 36816 Posted August 27, 2019 Share Posted August 27, 2019 @@buggsy let us know how you get on. Thanks ! Link to comment Share on other sites More sharing options...
PristDean 13 Posted August 30, 2019 Share Posted August 30, 2019 An update on this subject from me. Yesterday I moved my arial from one side of the house to the other and replaced the cable. I now reported from my HD HomeRun: Virtual Channel 103 ITV HD Frequency 618.000 MHz Program Number 17603 Modulation Lock tt8qam256 Signal Strength 100% Signal Quality 100% Symbol Quality 100% Streaming Rate 4.127 Mbps It stays constant too.... apart from the streaming rate, which fluctuates between 2Mbps and 10Mbps. There is the occasional 'pause' still seen in playback, but no more pixelation. Long & short for me is signal strength is everything.... but resilience to cater for variations in streaming could be improved within Emby Link to comment Share on other sites More sharing options...
Luke 36816 Posted August 31, 2019 Share Posted August 31, 2019 That's interesting, thanks for the feedback. We will look at improving it. 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