chupo_cro

Better subtitle handling/options (saving Code Page&transparent background)

5 posts in this topic

I have LB650V webOS TV and it is very annoying having to reselect the (Latin 2) subtitle encoding (Code Page) every time when playing the movie. Absolutely no excuse not to save the last used choice for the subtitle Code Page so I hope it will be implemented in the future firmware updates.

 

And one more thing about the subtitles: the options to turn on the transparent background and/or the character outlines has to be done - to improve the readability.

Share this post


Link to post
Share on other sites


Hello, chupo_cro. Update your TV firmware and Code Page will be saved, and every next playing it will be like last time.

 

Best regards,

Milan

1 person likes this

Share this post


Link to post
Share on other sites

Hello, chupo_cro. Update your TV firmware and Code Page will be saved, and every next playing it will be like last time.

 

Best regards,

Milan

 

So the Code Page choice saving has already been solved? Nice to hear :-) I have disabled automatic SW updates because I wanted to first read the changelog and wait to see the user reports but couldn't find any changelogs :-/ So I am still using firmware 03.23.13 shipped with the TV. I can see the latest firmware is 4.30.16 - can you confirm this FW didn't introduce some new bugs? For example, with 03.23.13 web browser often suddenly just restarts.

 

Do you maybe know if SW update can mess up some settings (e.g. calibration settings)?

 

Thank you for your reply

Share this post


Link to post
Share on other sites

Update your TV firmware and Code Page will be saved, and every next playing it will be like last time.

 

You were right - after updating the firmware to 04.30.16 the Code Page option remembers the (last used) state. I've also noticed new icon design, sooner disappearing notifications after inserting/removing the USB stick, more info in the About menu (MAC addresses), faster responding menus/options and faster previewing contents of the removable drives.

 

Unfortunately web browser still sometimes restarts when browsing the pages. However, it now restarts with 'Out of memory' error code (before there wasn't any error reports).

 

I hope the transparent subtitle background and subtitle outline options will be implemented in the near future.

 

And there is one more thing about the subtitle handling - I believe it's so important it deserves a separate thread so I am going to open a new topic...

Share this post


Link to post
Share on other sites

I would like to point that all my video files have "apost;" text everywhere in between , would like to get rid of that in future updates firmware.

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Similar Content

    • By rmz
      Hi,
       
      I bought a 47 inch 650V TV a week ago and I noticed that this SmarTV has a huge potential but still lacks very basic features. So I hope that I don't regret buying this TV if a update don't gives us some really great improvements.
       
      * First of all, WebOS it's slow. It really needs a huge performance improvement. Im not a BETA tester. If the system it's not ready, they should have hold it for a while and hire some inside beta testers.
       
      * Youtube app doesn't play videos in HD. Compared to my AppleTV, the difference it's huge. This is a 1080p SmartTV and there's not a single option on Youtube to play everything in 1080p or at least, 720p.
       
      * Audio Output only gives us a option to select one instead of a multiple sound output. Sometimes I use a Digital Out Surround Systems, and in my old LG TV, I could use the TV Speakers and this digital audio at the same time and only mute the TV. It's the fastest way to use both. In this new smartv, I have go to the audio settings to choose the audio output everytime. For a slow system, it's a really painful solution.
       
      * This TV has Bluetooth built in, and there's not a single option to pair a Keyboard, Mouse or a Audio Device. It's locked to LGs proprietary Bluetooth devices. It's inaceptable since Bluetooth technology is standard and to use a Bluetooth Keyboard/Mouse/A2DP sound I have to get a pack that cames with a USB Bluetooth dongle. So all my BT keyboards and mouses that doesn't have that USB dongle can't be used.
       
      * I own a LG G2 Smartphone and I cannot simple use the LG SmartShare. It's slow and crashes all the time, so sharing my videos and photos to TV it's simple mission impossible. The same goes for Wi-fi Direct. It simply doesn't work. And the same goes for the LG TV Remote App. It's very slow when we try to use the "mouse pointer".
       
      * It's not possible to resize .srt subtitles and tags like <i> and <b> are not recognized by the TV. So not only I can't have Italic and Bold text, but those tags are also added to the subtitles like normal text...
       
      And I notice this with just one week of usage, so obviously there's a lot more things to improve but this features are simple to use on my AppleTV and my LG can't handle them very well. I bought this TV and paid the extra money to get a good SmarTV compared to the 5700 model, with the intention to get rid off the Apple TV... but at this moment I just can't...
    • By chupo_cro
      Many subtitle files use the italic and bold tags to distinguish the translation of written text, character's thoughts, movie title, loud voice, ... However webOS doesn't support parsing of these tags and it just shows them on the screen as:
      <i>This text is italic.</i> <b>This text is bold.</b> The workaround is to Find/Replace all occurrences of <i>, </i>, <b> and </b> with 'nothing' but, of course, that removes the subtitle formatting :-/
       
      I hope the <i> and <b> tag parsing wil be implemented in the future firmware releases. In the meantime at least ignoring of these tags would be fine - so everything inside '<' and '>' would be ignored (including the brackets, of course).