Emby on LG have this loading icon bug

[Lanaria 0]

So I've had no problems with Emby until this night. Two of the films I have on my PC is in "MKV" format. I have no idea if that's the issue or not. Playing them with Emby on the PC works fine, subtitles and everything.
When I try to play it on my LG TV, the media does play but the loading icon is still there as seen on the image I've inserted. When I click on play/pause it goes blank for a couple of seconds and plays it again without the loading icon. But instead the player itself gets frozen. The time remaining and how much time has gone doesn't change and the subtitles doesn't load.
Now I wouldn't care about this issue if I didn't need the subtitles. But unfortunately, the films/shows I have is in a foreign language.

What's the issue? Is it the TV/Emby app not supporting the codec of MKV?

Thank you in advance!
 

[Lanaria 0]

I tried reinstalling the app on my TV and using the Android app with Chromecast but nothing worked.

[Happy2Play 8278]

 @Lanaria

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

 

 

[Lanaria 0]

8 minutes ago, Happy2Play said:

 @Lanaria

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

 

 

I've described everything I can. This is the log file from the last time I played the media on my TV. I hope this helps in some way ffmpeg-remux-313abe3d-1de5-4941-b861-650250fdf37c_1.txt

[Lanaria 0]

16 minutes ago, Lanaria said:

I've described everything I can. This is the log file from the last time I played the media on my TV. I hope this helps in some way ffmpeg-remux-313abe3d-1de5-4941-b861-650250fdf37c_1.txt

Another log I didn't see until now, sorry.

ffmpeg-transcode-a57fc65a-2f70-465a-bc25-f44a62456a86_1.txt

[visproduction 122]

Lan,

The ffmpeg transcode shows this info:

• Media titled: 'Collective Invention 2015...' is 1 hour 33 minutes 45 seconds long.
• The video has 135,000 frames 
• ts size seems to be frames = 72
• That would mean your entire encoding would have 135,000 / 72 = 1875 ts files which comes to 6.17 seconds per ts file
• You started encoding the first frame at 03:12:44 hours
• Your encoder speed allowed you to get to frame 326 which would be 17.3% of the video, or 33 minutes 50 seconds of the video.
• It took you 3 minutes 42 seconds to get to that point and then you canceled the encoding.
• At that speed 100% encoding would complete after about 21 minutes 20 seconds with your current settings and hardware 
  
  So, why does the player not start to play at 17.3% of the video?  Does it need to encode everything first to get audio to work?  I don't use this encoder and I do not know it's limitations.
  
  Obviously, if you want to encode faster at your current settings you need higher end hardware and matching cooling... Or the other option is to reduce your quality settings until the encoding speed matches your needs.
  
  I would be interested to hear if my assumptions are correct or am I missing something.
  
  Snippits from ffmpeg transcode txt file:
   

  03:12:44.128 [libx264 @ 000001e59ed5c840] 264 - core 159 r2991 1771b55 - H.264/MPEG-4 AVC codec - 
  Copyleft 2003-2019 - http://www.videolan.org/x264.html - options: cabac=1 ref=1 deblock=1:0:0 
  analyse=0x3:0 me=hex subme=0 psy=1 psy_rd=1.00:0.00 mixed_ref=0 me_range=4 chroma_me=1 trellis=0 
  8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=0 threads=18 lookahead_threads=3 
  sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 
  b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=1 keyint=72 keyint_min=37 
  scenecut=0 intra_refresh=0 rc_lookahead=10 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 
  qpstep=4 vbv_maxrate=30196 vbv_bufsize=60393 crf_max=0.0 nal_hrd=none filler=0 ip_ratio=1.40 aq=1:1.00
  ...
  
  03:12:44.067       title           : Collective.Invention.2015.BDRemux.1080p_by_vedigo
  03:12:44.067       BPS             : 24502246
  03:12:44.067       BPS-eng         : 24502246
  03:12:44.067       DURATION        : 01:33:45.000000000
  03:12:44.067       DURATION-eng    : 01:33:45.000000000
  03:12:44.067       NUMBER_OF_FRAMES: 135000
  ...
  03:12:44.684 SegmentComplete=video:0 Index=0 Start=0.000000 End=3.000000 
  Duration=3.00000 offset_pts=0 start_pts=0 Frames=72 filename=E0C4B9_0.ts
  ...
  03:15:02.620 [segment @ 000001e59f0b0c40] Opening 'C:\Users\Lanaria\AppData\Roaming\Emby-Server\
  programdata\transcoding-temp\E0C4B9\E0C4B9_326.ts.tmp' for writing
  03:15:02.995 
  
  [q] command received. Exiting.

   

[Lanaria 0]

12 minutes ago, visproduction said:

Lan,

The ffmpeg transcode shows this info:

• Media titled: 'Collective Invention 2015...' is 1 hour 33 minutes 45 seconds long.
• The video has 135,000 frames 
• ts size seems to be frames = 72
• That would mean your entire encoding would have 135,000 / 72 = 1875 ts files which comes to 6.17 seconds per ts file
• You started encoding the first frame at 03:12:44 hours
• Your encoder speed allowed you to get to frame 326 which would be 17.3% of the video, or 33 minutes 50 seconds of the video.
• It took you 3 minutes 42 seconds to get to that point and then you canceled the encoding.
• At that speed 100% encoding would complete after about 21 minutes 20 seconds with your current settings and hardware 
  
  So, why does the player not start to play at 17.3% of the video?  Does it need to encode everything first to get audio to work?  I don't use this encoder and I do not know it's limitations.
  
  Obviously, if you want to encode faster at your current settings you need higher end hardware and matching cooling... Or the other option is to reduce your quality settings until the encoding speed matches your needs.
  
  I would be interested to hear if my assumptions are correct or am I missing something.
  
  Snippits from ffmpeg transcode txt file:
   

  03:12:44.128 [libx264 @ 000001e59ed5c840] 264 - core 159 r2991 1771b55 - H.264/MPEG-4 AVC codec - 
  Copyleft 2003-2019 - http://www.videolan.org/x264.html - options: cabac=1 ref=1 deblock=1:0:0 
  analyse=0x3:0 me=hex subme=0 psy=1 psy_rd=1.00:0.00 mixed_ref=0 me_range=4 chroma_me=1 trellis=0 
  8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=0 threads=18 lookahead_threads=3 
  sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 
  b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=1 keyint=72 keyint_min=37 
  scenecut=0 intra_refresh=0 rc_lookahead=10 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 
  qpstep=4 vbv_maxrate=30196 vbv_bufsize=60393 crf_max=0.0 nal_hrd=none filler=0 ip_ratio=1.40 aq=1:1.00
  ...
  
  03:12:44.067       title           : Collective.Invention.2015.BDRemux.1080p_by_vedigo
  03:12:44.067       BPS             : 24502246
  03:12:44.067       BPS-eng         : 24502246
  03:12:44.067       DURATION        : 01:33:45.000000000
  03:12:44.067       DURATION-eng    : 01:33:45.000000000
  03:12:44.067       NUMBER_OF_FRAMES: 135000
  ...
  03:12:44.684 SegmentComplete=video:0 Index=0 Start=0.000000 End=3.000000 
  Duration=3.00000 offset_pts=0 start_pts=0 Frames=72 filename=E0C4B9_0.ts
  ...
  03:15:02.620 [segment @ 000001e59f0b0c40] Opening 'C:\Users\Lanaria\AppData\Roaming\Emby-Server\
  programdata\transcoding-temp\E0C4B9\E0C4B9_326.ts.tmp' for writing
  03:15:02.995 
  
  [q] command received. Exiting.

   

Well the thing is I let the TV or Emby do it's own thing. I didn't even know the encoding stuff was such a important thing.  I have another media in MP4 format and that one loads without any issues. 
So is the point to wait until it's done loading or similar? Or is there an unknown issue here?

[Lanaria 0]

Update: I somehow managed for it to work. I am really confused by it but here's how it went out. I played the media and the same thing started happening. But this time I waited for a longer time to see if anything happens, nothing did happen. Then I pressed play/pause, thinking it was over. To my surprise after pressing play/pause the media played as normal, subtitles working and everything. It didn't give me any indication that I should wait or do something else while it was "loading". This was completely by chance or mistake and that is why I'm really confused about the whole thing. 
I am not going to mark it as solved in case there is a workaround to this. It is a really annoying bug which I think it needs a bit of attention. 

[Lanaria 0]

46 minutes ago, Lanaria said:

Update: I somehow managed for it to work. I am really confused by it but here's how it went out. I played the media and the same thing started happening. But this time I waited for a longer time to see if anything happens, nothing did happen. Then I pressed play/pause, thinking it was over. To my surprise after pressing play/pause the media played as normal, subtitles working and everything. It didn't give me any indication that I should wait or do something else while it was "loading". This was completely by chance or mistake and that is why I'm really confused about the whole thing. 
I am not going to mark it as solved in case there is a workaround to this. It is a really annoying bug which I think it needs a bit of attention. 

15 minutes into the media and it randomly started freezing/stuttering. It's like when you trying to watch a YouTube video with bad Internet. The media was "buffering" for a few seconds and played itself again. Now it just keeps happening over and over.

Here is the log file for this time. 

I changed my Wi-Fi network and so far I'm not experiencing any issues yet. It's just weird hence the fact that I have played a lot of medias before this.

ffmpeg-remux-84e6530a-a13a-4e83-b912-30aa0a8d9f40_1.txt

Edited July 21, 2022 by Lanaria
Another update

[visproduction 122]

Lan,

Encoding in media streaming is an actual profession.  There are a couple of things that affect encoding.  TV's and various software playback combinations can handle some audio / video compression formats (codecs) and just play back without encoding, but some audio / video codecs cannot be played directly.  When that happens Emby kicks in and starts encoding the media into the audio / video codecs that the player needs.

I hope that make sense.

So, this means that some audio / video codecs are direct playable and need no encoding at all.  If you have media like that, it just starts to play. Otherwise, it needs to encode first and then play.  Audio / video codec that works on any Internet Browser and also directly playback to TV. 

• Video Mpeg4 AVC h.264 (or x.264) - All browsers
• Video Mpeg4 4CC h2.64 - All new browsers
• Audio AAC (FDK) LC up to 128 kbps - All browsers
• Audio AAC (FDK) HE-AAC up to 640 kbps - All browsers

Only a few browsers handle h.265 HEVC video codec, or each user needs to purchase a plugin for their own computer.  But even if the user's browser is set to handle HEVC video codec, Emby may not recognize that you can direct play it.  With audio any media with AC3 will probably need to be reencoded for browser playback.  Smart TV's can handle Hevc video and AC3 audio if it's fed to them, but most  browsers cannot. Getting TV or browser playback some of these codec needs to be setup just right. In most case, any user will not bother any extra setup. 

I don't use Emby encoding myself.  Instead, I pre encode all content to Mpeg4 AVC x264 and Audio AAC (FDK) HE-AAC 640 kbps.  Then my content never needs encoding.  I am not working with live TV.

When I pre encode my content I use a very high quality setting but at a reasonable bit rate for each video size.  This is not practical for live media, because my 3rd party encoding typically takes 5 to 10 times longer than the content for 1080P on a decent i7 Intel notebook.  5 times the length of a movie to encode has no practical use for a media server that needs to encode.  But remember, I pre encode everything, so encoding on the fly never needs to happen.  Another point is that most all media you see play in a browser online is already in this codec combination. so any copy of online media doesn't need reencoding to be included in a media server.

The power of Emby encoding is that it doesn't matter what source you pull from, Emby will automatically encode it and make it work in playback.  You still might have damaged video that plays locally on some player but has too many internal errors to encode correctly.  That is why it's important to test any process with a master test quality video.  If something is not working, it is often the fault of damaged media.  Playing media back on some other player does not confirm the media is good.

That's a lot of detail.  Hopefully that makes some sense and helps.

•  

Edited July 21, 2022 by visproduction

[Luke 37050]

We're looking into the issue. Thanks for reporting.