Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About Hunter_S

  • Rank
  • Location Cincinnati, OH, United States
  1. On devices that have simple web browsers, I like to do speed tests using fast.com. It's a very simple browser-based test that is operated by Netflix. https://fast.com/
  2. No, Krash, I do not have that problem. DTS plays fine for me through the internal speakers. I tested this with MKV files containing DTS streams over DLNA, and verified that the TV was indeed receiving DTS sound by opening the 'info' panel during playback. (I also needed to change the sound out option to Internal Speaker, but I'll assume you did that too. 😀) Gurnaam, I was thinking the same thing about compatibility (and why not? the published WebOS 3.5 compatibility listing is pretty long), and I had high hopes. There are some fairly new video codecs supported, which is why I was so surprised that my set was having difficulty with long-standard audio codecs like AC-3/DD and AAC. Do I know what's happening? No, not for certain. To be honest, the specific issue that you are noticing seems a little bit different from mine: for you, it occurs during pause, and some sound isn't playing at all. I would be interested to hear about the specific file types you are trying to play and what the rest of your setup looks like (optical or HDMI? Receiver or Soundbar? Age of other components? etc...). On my set, I just notice poor quality audio during playback from certain AAC and DD 5.1 sources that I know are fine.
  3. I guess I had thought that my issue was limited to AAC audio, but during the past several days, I've been noticing popping \ garbled \ compressed sound from both ATSC broadcast and DLNA content with DD 5.1 over HDMI ARC. A side-by-side comparison to a PS3 made it pretty clear that the source of the issue is the TV set. So I guess I'm now noticing the same exact issue that you are, Krash. I guess the decision now is whether to return the set, live with it, or hope that this is on LG's radar and repairable with a firmware update. I also agree that any mainboard replacement isn't like to solve the issue unless there has actually been a hardware revision.
  4. How old are are your Receiver and Sound Bar? In case it helps, I had an older Pioneer receiver that was otherwise fine, but two issues appeared when it was used with the Optical out on a new 55LJ5500 (WebOS 3.5) set: 1. The TV attempts to passthrough Dolby Digital Plus (DD+) content as-is. The can cause issues for older receivers that do not explicitly support DD+. Content-wise, DD+ is served up by some broadcast stations and some streaming platforms like Netflix. On my old receiver, this caused momentary and random audio drop-outs, but I imagine this could manifest itself in different ways. The same content seemed to play fine on a receiver that supports DD+. 2. The TV transcodes AAC audio to Dolby Digital. At least on my set, WebOS does a very poor job at this. On my older receiver, the resulting audio also caused momentary audio drop-outs. On a newer receiver it doesn't drop-out, but it still sounds bad. Content-wise, most YouTube content uses AAC.
  5. It sounds like you are right that there is a configuration issue. Are you certain that ARC is enabled on both your LG and your Yamaha? On your LG, you will need to go to Settings - > Sound - > Sound Out - > Audio Out (Optical/HDMI ARC) and set SIMPLINK to On.
  6. I have a 55LJ550M (WebOS 3.5) TV, connected to an A/V Receiver via ARC. Per the online documentation, when the TV encounters AAC audio, it will transcode that audio to Dolby Digital for transmission over ARC. See: http://www.lg.com/ca_en/support/product-help/CT20098005-1437136302910-others However, the sound quality is very poor when this occurs. The sound is full of compression artifacts, and with some older A/V Receivers, this causes the sound to periodically cut-out. Some of the WebOS applications affected by this issue are YouTube (which mostly uses AAC audio), any Netflix stereo programming, and using the Music\Photo\Video app to play music or videos with AAC audio. To me, it makes the entire YouTube application unusable. Honestly, I'm surprised that WebOS doesn't just output PCM audio over ARC whenever it encounters AAC. This would make more sense, and it would require less processing power and sound much better. (I know that I can set the TV to output everything to PCM over ARC, but I do not want to lose DD 5.1 and DTS sound from other programming which works perfectly). Is this behavior a known WebOS 3.5 issue? I know that my unit is a one of the cheaper LG sets--it is possible that this particular set is just too under-powered to function as designed?

  • Create New...