Jump to content


Photo

Status on official LG app

LG app official

  • Please log in to reply
539 replies to this topic

#461 pastorn OFFLINE  

pastorn

    Member

  • Members
  • 27 posts
  • Local time: 02:47 AM

Posted 27 March 2019 - 07:03 AM

@rbjtech: Thank you for your reply!

 

Case 1: Three logs. Not sure why. Could first log (video copy) be failed attempt, rejected by the app? Second log is playing (beginning of movie) and third is where I have forwarded the movie to see what language the dialogue is in? There was no playback in HDR here, only transcoded video. So 1a (video copy) never played.

Case 2: None of these played, the app reported "no compatible streams available".

 

The above means that I can not use transcode mode at all, I have to force direct play. When doing so (un-ticking the boxes in transcode options) I get perfect video (4K/HDR) but I get the last audio track in the list which can be anything from commentary track to thai dialogue. I can switch to another track but when I choose TrueHD it again switches to the last audio track. This should not be case, I believe (?). Another weird thing is that when forcing direct play "stats for nerds" is unavailable which is unpracticle for diagnostics and should also not be the case, I suppose…?

 

My LG Oled is configured to put out optical audio in LPCM which I believe is the same situation for audio decoding as playing via the internal speakers? So I am not looking for putting out Atmos/TrueHD bitstreamed, I just want the TrueHD track to be decoded in the TV and sent out in a lossless format to my stereo. I believe this was the case with the previous version of the Emby LG app. But I can not revert to it...

 

 

PS: I had no subs activated in any of these cases. And I am aware that only external SRT subtitles work. This has been tried also now and does not affect the behaviour so I think this is unrelated to subs.  DS



#462 rbjtech OFFLINE  

rbjtech

    Advanced Member

  • Members
  • 464 posts
  • Local time: 12:47 AM
  • LocationLondon, UK

Posted 27 March 2019 - 10:46 AM

What LG TV is this being tested on - model number ?

 

I've tested this on an LG C8 OLED - and don't have these issues at all.


Edited by rbjtech, 27 March 2019 - 10:47 AM.


#463 pastorn OFFLINE  

pastorn

    Member

  • Members
  • 27 posts
  • Local time: 02:47 AM

Posted 27 March 2019 - 11:35 AM

The B6!

Wish I had another SmartTV to test on to know if it’s the client or the server side of it, but no such luck. But didn’t have any problem with previous version of the app...

/Martin

#464 rbjtech OFFLINE  

rbjtech

    Advanced Member

  • Members
  • 464 posts
  • Local time: 12:47 AM
  • LocationLondon, UK

Posted 27 March 2019 - 12:00 PM

Also just read your point about the sub colour - and whilst I can't confirm that colour used to work on the old version (as I never used it) - it does not work on my TV either - but italics and underline do ..

 

1
00:03:25,247 --> 00:03:27,124
normal:Look who we have here. Works fine
 
2
00:03:32,296 --> 00:03:33,923
<b>bold:You have our money?</b>      May work, but as it's so bright anyway (HDR) I'm not sure it's any more bold than a normal sub  ..  ;)
 
3
00:03:38,469 --> 00:03:39,470
<i>italic:Search him.</i>   Works fine
 
4
00:03:41,060 --> 00:03:43,395
<u>underline:Not if I shoot you.</u> Works fine
 
5
00:03:45,998 --> 00:03:50,458
<font color="#808080">colour:Coaxium is precious.</font> Doesn't work - just retina burning white ...  :o
 
Lets hope this can be restored - as I agree with you subs are FAR too bright - I've never tested as I've never had any HDR movies using SRT subtitles .. 


#465 rbjtech OFFLINE  

rbjtech

    Advanced Member

  • Members
  • 464 posts
  • Local time: 12:47 AM
  • LocationLondon, UK

Posted 27 March 2019 - 12:14 PM

 

My LG Oled is configured to put out optical audio in LPCM which I believe is the same situation for audio decoding as playing via the internal speakers? So I am not looking for putting out Atmos/TrueHD bitstreamed, I just want the TrueHD track to be decoded in the TV and sent out in a lossless format to my stereo. I believe this was the case with the previous version of the Emby LG app. But I can not revert to it...

 

I don't believe this is the case - I've just set mine to Optical - PCM (instead of Auto) and it still converts to AC3 but now only sends a 2.0 channel stereo to my AVR (Dolby Pro Logic), which I believe is the correct behaviour.  'Auto' sends the full Dolby Digital 5.1 bitstream as reported by my AVR.   But both convert from True-HD to AC3 fine without any video conversion or HDR loss.


Edited by rbjtech, 27 March 2019 - 12:15 PM.


#466 pastorn OFFLINE  

pastorn

    Member

  • Members
  • 27 posts
  • Local time: 02:47 AM

Posted 28 March 2019 - 02:02 AM

@rbjtech:  Nice work in investigating subtitle support! :-)  Maybe this should be documented somewhere? I consistently used #808080 (half brightness) for HDR movies in the previous movies of the app, mainly to avoid having a single line of subtitles light up the entire room in a dark scene, ruining the viewers night vision... :ph34r:  Do you still see settings for subtitle size? I am not 100% sure about this but I think there was a setting (like 5 options?) in the previous version of the app but now I don't see it anymore...?

 

For SDR movies I felt full brightness for the subtitles was okay since the color settings in the TV is normally different. This could obviously depend on your color settings in the TV, though. If you're running SDR movies with some "HDR effect mode" perhaps the problem is the same (?).

 

The alternative would obviously be if one could choose between a few different colors in the Emby App but then there would have to be two settings; one for SDR and one for HDR. Perhaps too complicated... The previous support for color coded SRT files was a completely satisfactory solution (at least to me) since the files are unique for each movie and tweaking them with color took like 10s with a proper editor.

 

Could you try (if you have the time) un-ticking the transcode boxes on the server (forcing direct play), try a movie with TrueHD track as default and see if you also get the last audio track instead of the second one, and "stats for nerds" disappear?

 

Have a good day!

 

Best regards

Martin



#467 rbjtech OFFLINE  

rbjtech

    Advanced Member

  • Members
  • 464 posts
  • Local time: 12:47 AM
  • LocationLondon, UK

Posted 28 March 2019 - 06:36 AM

@rbjtech:  Nice work in investigating subtitle support! :-)  Maybe this should be documented somewhere? I consistently used #808080 (half brightness) for HDR movies in the previous movies of the app, mainly to avoid having a single line of subtitles light up the entire room in a dark scene, ruining the viewers night vision... :ph34r:  Do you still see settings for subtitle size? I am not 100% sure about this but I think there was a setting (like 5 options?) in the previous version of the app but now I don't see it anymore...?

 

Could you try (if you have the time) un-ticking the transcode boxes on the server (forcing direct play), try a movie with TrueHD track as default and see if you also get the last audio track instead of the second one, and "stats for nerds" disappear?

 

Have a good day!

 

Best regards

Martin

 

The only other official .SRT formatting is screen location (co-ordinates) - I don't see anything else about size. https://en.wikipedia.org/wiki/SubRip

 

I removed the transcode option from the user - and my testing also confirms what you get - it it (unreliably) plays the last track and stats for nerds disappears ..

 

In my case - my file has 1:h265 2:TrueHD 3: AC3 and 4:DTS

 

On the first attempt, I could see my AVR flash on and off the DTS indicator for a few seconds, but fail to produce any sound.  Video did not play.

On the second attempt, the AVR switched to DTS and played the Audio and Video fine.  But no stats for nerds to confirm but AVR indicator shows it's playing the last DTS track.

On the third attempt, I could see my AVR flash on and off the DTS indicator, but fail to produce any sound.  Video did not play.

On the fourth attempt, the AVR switched to DTS and played the Audio and Video fine.  

 

So it's consistent - but wrong as it probably should be picking the next track (AC3 in my case) 

 

But to be clear, all this only happens when I force remove transcoding, normally it just converts True-HD to AC3 on the fly (even though there is a perfectly good AC3 or DTS stream there that 'could' have been used)

 

I hope that helps you and the Dev's understand this a little better and hopefully track down the bug.


Edited by rbjtech, 28 March 2019 - 06:38 AM.


#468 rbjtech OFFLINE  

rbjtech

    Advanced Member

  • Members
  • 464 posts
  • Local time: 12:47 AM
  • LocationLondon, UK

Posted 28 March 2019 - 07:44 AM

To add,  it looks like LG have just released a new firmware (20/03/2019) which may change the 'Dolby Atmos' support - will have a play later but unfortunately I don't have an Atmos AVR...  :unsure:

 

SW File (Version 04.10.31) Detailed applicable model list : Please check with reference Tab exactly

d applicable model list : Please check with reference Tab exactly

* SW information  

1. Improvement  
 1) Improved issue of external AV Receiver "Not Supported" error when playing Dolby Atmos content.   
 2) To improve issue of Macro Block Noise. 

 

Edit - updated via USB, well good news is Emby is still working as it was before so the update hasn't broken anything (which is a relief) but need somebody with an Atmos AVR to determine what improvements they made and if Emby can make use of them.

 


Edited by rbjtech, 28 March 2019 - 10:15 AM.


#469 yuny14utv OFFLINE  

yuny14utv

    Newbie

  • Members
  • 5 posts
  • Local time: 01:47 AM

Posted 28 March 2019 - 04:55 PM

This might be awesome news? Can anyone test Dolby Atmos with external sound with the latest firmware?



#470 kwilcox OFFLINE  

kwilcox

    Advanced Member

  • Members
  • 464 posts
  • Local time: 06:47 PM

Posted 28 March 2019 - 07:26 PM

what version of WebOS are you running @rbjtech?



#471 rbjtech OFFLINE  

rbjtech

    Advanced Member

  • Members
  • 464 posts
  • Local time: 12:47 AM
  • LocationLondon, UK

Posted 28 March 2019 - 08:38 PM

what version of WebOS are you running @rbjtech?

 

Hi @kwilcox - WebOS v 4.1.0-561101 (goldilocks-glacier)



#472 pastorn OFFLINE  

pastorn

    Member

  • Members
  • 27 posts
  • Local time: 02:47 AM

Posted 29 March 2019 - 06:43 AM

I got an answer from Luke on the Samsung Forum. I am posting his reply here (and mine) since it's LG related. I hope nobody minds..

 

We were previously rendering SRT subtitles using our own custom rendering, and it might have accidentally supported this, however in the latest release we switched back to having the LG video player render them.

 

So now it's a question of whether it supports this or not, and it looks like it probably does not. And no, we can't switch back to the custom rendering because that has it's own problems, it is really only a last resort when the built-in LG rendering doesn't work. And it turns out the custom rendering is only needed for WebOS 1.X and 2.X.

 

Thank you so much for explaining this; that makes sense if you have switched from your own rendering to LG official. I can not argue against your decision since it is not my app and i am not a developer. I can only stress that it is an unfortunate consequence if this means it is impossible to reduce the brightness of the subs, now and forever. :-(   The visual aspect of subtitles can really have a big impact on the experience of a movie, and getting blinded by a single line of white subtitles in a dark scene has become a menace with the introduction of HDR movies and big TV screens. It litterally lights up the room (!). This was easily avoided in the previous version of your outstanding Emby app using color coded SRT files.

 

If you look at competing software such as Kodi for example, there are a lot of different subtitle options to improve the viewing experience. I can not agree to the idea that an app installed on a device should have to be limited by the shortcomings of the original device; if anything, an app should try and overcome the limitations of the device to offer additional features and improved experiences.

 

The DLNA player on my LG TV has the options to select four different subtitle colors. I believe they are white, red, blue and green (pretty useless options). So the official LG subtitle rendering engine CAN show other colors than white and I would be surprised if this was hardcoded in the rendering engine (?). More likely, it is a limitation of the DLNA player, and the color can probably be freely chosen if only one figures out how the DLNA player specifies the color to the rendering engine. Could this be a way forward? If so, an option could perhaps be introduced in the Emby app instead? It would have to be one color for SDR and another one for HDR since the requirements are different.

 

I would happily participate in some kind of beta testing if you want? I Think there is a guide to be found on how to put an LG TV in "developer mode", which makes it possible to install apps from other sources than the app store. Just let me know if I can be of assistance in any way. :)



#473 pastorn OFFLINE  

pastorn

    Member

  • Members
  • 27 posts
  • Local time: 02:47 AM

Posted 29 March 2019 - 06:47 AM

@rbjtech: Thank you for trying and replicate the behaviour I experienced when forcing direct play! At least now I know I'm not crazy. ;) 



#474 KevinSartori OFFLINE  

KevinSartori

    Member

  • Members
  • 14 posts
  • Local time: 06:47 PM

Posted 29 March 2019 - 10:05 AM

FWIW, the XPlay app for LG (using Plex) has different color options.  At one point, the creator of the app added a "Silver" color subtitle option to resolve this exact HDR issue.  With XPlay, the subs are also being rendered by LG, so this should be possible as a feature add in Emby.

 

Is there a formal "feature request" process?



#475 rbjtech OFFLINE  

rbjtech

    Advanced Member

  • Members
  • 464 posts
  • Local time: 12:47 AM
  • LocationLondon, UK

Posted 29 March 2019 - 12:57 PM

I got an answer from Luke on the Samsung Forum. I am posting his reply here (and mine) since it's LG related. I hope nobody minds..

 

 

Thank you so much for explaining this; that makes sense if you have switched from your own rendering to LG official. I can not argue against your decision since it is not my app and i am not a developer. I can only stress that it is an unfortunate consequence if this means it is impossible to reduce the brightness of the subs, now and forever. :-(   The visual aspect of subtitles can really have a big impact on the experience of a movie, and getting blinded by a single line of white subtitles in a dark scene has become a menace with the introduction of HDR movies and big TV screens. It litterally lights up the room (!). This was easily avoided in the previous version of your outstanding Emby app using color coded SRT files.

 

If you look at competing software such as Kodi for example, there are a lot of different subtitle options to improve the viewing experience. I can not agree to the idea that an app installed on a device should have to be limited by the shortcomings of the original device; if anything, an app should try and overcome the limitations of the device to offer additional features and improved experiences.

 

The DLNA player on my LG TV has the options to select four different subtitle colors. I believe they are white, red, blue and green (pretty useless options). So the official LG subtitle rendering engine CAN show other colors than white and I would be surprised if this was hardcoded in the rendering engine (?). More likely, it is a limitation of the DLNA player, and the color can probably be freely chosen if only one figures out how the DLNA player specifies the color to the rendering engine. Could this be a way forward? If so, an option could perhaps be introduced in the Emby app instead? It would have to be one color for SDR and another one for HDR since the requirements are different.

 

I would happily participate in some kind of beta testing if you want? I Think there is a guide to be found on how to put an LG TV in "developer mode", which makes it possible to install apps from other sources than the app store. Just let me know if I can be of assistance in any way. :)

 

The other thing I noticed when testing, during the Emby information 'overlay transparency' the bright HDR subs were also heavily dimmed.  So while far from ideal, Emby obviously has 'control' over the screen - so maybe something could be done here to just dim the portions of the screen that uses the subtitles.  I'm going to see if .SRT 'co-ordinates' work - and if so, Emby will know exactly where to dim (and for how long).



#476 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 140425 posts
  • Local time: 07:47 PM

Posted 29 March 2019 - 01:58 PM

 

Also just read your point about the sub colour - and whilst I can't confirm that colour used to work on the old version (as I never used it) - it does not work on my TV either - but italics and underline do ..

 

1
00:03:25,247 --> 00:03:27,124
normal:Look who we have here. Works fine
 
2
00:03:32,296 --> 00:03:33,923
<b>bold:You have our money?</b>      May work, but as it's so bright anyway (HDR) I'm not sure it's any more bold than a normal sub  ..  ;)
 
3
00:03:38,469 --> 00:03:39,470
<i>italic:Search him.</i>   Works fine
 
4
00:03:41,060 --> 00:03:43,395
<u>underline:Not if I shoot you.</u> Works fine
 
5
00:03:45,998 --> 00:03:50,458
<font color="#808080">colour:Coaxium is precious.</font> Doesn't work - just retina burning white ...  :o
 
Lets hope this can be restored - as I agree with you subs are FAR too bright - I've never tested as I've never had any HDR movies using SRT subtitles .. 

 

 

I did actually just answer this yesterday but i can't find the topic, it must not have been in the LG section. But previously we were rendering the subtitles with our own code and that's why it worked, but that's also the reason why there were other subtitle problems such as alignment and things of that nature. 

 

For WebOS 3+ we have switched to just having the LG player render the subtitles as we've discovered that our workaround is only needed for WebOS 1&2. So if you're not seeing the font style then it means LG does not support it.



#477 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 140425 posts
  • Local time: 07:47 PM

Posted 29 March 2019 - 01:59 PM

FWIW, the XPlay app for LG (using Plex) has different color options.  At one point, the creator of the app added a "Silver" color subtitle option to resolve this exact HDR issue.  With XPlay, the subs are also being rendered by LG, so this should be possible as a feature add in Emby.

 

Is there a formal "feature request" process?

 

There is an open feature request already related to subtitle color. I would lend your support into that topic. Thanks.



#478 rbjtech OFFLINE  

rbjtech

    Advanced Member

  • Members
  • 464 posts
  • Local time: 12:47 AM
  • LocationLondon, UK

Posted 29 March 2019 - 04:32 PM

 

For WebOS 3+ we have switched to just having the LG player render the subtitles as we've discovered that our workaround is only needed for WebOS 1&2. So if you're not seeing the font style then it means LG does not support it.

 

Playing the same video file on the internal LG player with external .SRT ignores the italic and underline while Emby plays them  .. so it's not consistent.  Anyway - I'll add my support for the colour options, as that is a real issue for HDR movies.  Thanks Luke. 

 

For those wanting to add support - the subtitle colour feature request thread is here :-

 

https://emby.media/c...e-2?hl=subtitle


Edited by rbjtech, 29 March 2019 - 04:43 PM.


#479 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 140425 posts
  • Local time: 07:47 PM

Posted 29 March 2019 - 04:36 PM

What do you mean internal LG player? How did you do that?



#480 rbjtech OFFLINE  

rbjtech

    Advanced Member

  • Members
  • 464 posts
  • Local time: 12:47 AM
  • LocationLondon, UK

Posted 29 March 2019 - 04:41 PM

What do you mean internal LG player? How did you do that?

 

Same file as Emby would have played but copied to a USB stick and played directly in the file list browser when you navigate the USB files.







Also tagged with one or more of these keywords: LG, app, official

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users