Okay, I'm not trying to be redundant, but I don't think you completely follow the issue. In your reply, you said "...this TV does not understand the encoding..." but if you follow the two cases below, I think you'll see that the TV DOES understand the encoding, at least in one case.
Case 1. I copy a video clip, let's call it "clip.mkv" from the My Videos folder on my Win7-PC, to a USB thumb drive and plug the drive into the LG TV's "USB-1" port. I then navigate on the tv screen to select the USB input and I see a "video folder." When I click on the "video folder" on the TV screen, I see the video called "clip.mkv." When I click on "clip.mkv", the movie plays on the tv screen-- video and audio-- no problem... beginning to end. So, to state the obvious, the TV is able to decode and play the clip in the mkv bucket.
Case 2. I access the "My Videos" folder on my Win7-PC by selecting the corresponding "Win7-PC input" on the LG TV. There, I see a listing of all the video clips in the My Vidoes folder, including AVI, WMV, MPG, MP4, etc., but I DO NOT see in the listing is the video titled "clip.mkv". (Remember, this is the identical file to the one on the USB thumb drive.) And believe me when I say, "clip.mkv" is most certainly in the My Videos folder on the computer.
So here's my confusion-- Why can the TV "see" and "play" the clip in the MKV bucket when it's on a USB thumb drive plugged into it, but can't even "see" the clip in the MKV bucket when it's on the computer? Obviously, something is getting lost between the computer and the TV (over the hard-wired Ethernet connection). The only thing I can figure is that the TV handles the USB input differently from how it handles the network connection.
I know how to re-encode clips, and I can certainly do this, even though it's generally time-consuming (esp. for very large files). However, this is such an intriguing situation that I'd simply like to find an explanation.
I'm not the kind to beat a dead horse, but I'd really like to know if anyone else has had a similar experience, and has hopefully solved the problem. Thanks again for listening.
Was this reply helpful? (1) (0)