Originally Posted by moss312
1) I have over the air running directly to the 6168. The 6168 is outputting via optical cable to a Yamaha 5760 = no lag, audio does not echo when using speakers on both the tv and the 5760.
2) 3) 4) Outputting at 1080i on both Directv Samsung Sir-160 and Samsung HD850 I hear an echo between the tv's speakers and the 5760's speakers. Setting delay between 80ms and 120ms on the 5760 (I keep delay at 100ms it sounds just right) gets rid of the echo. The 100ms delay also gets rid of the visual lip synch I notice using the HD850 with HDMI and audio sent to the 5760 with optical cable (I have not tried it with component cables).
In summary same amount of delay needed by the 5760 (100ms) between the HD850 and Sir-160 outputting video to the 6168 at 1080i, and sending audio directly from the HD850 and Sir-160 to the 5760. Anything sent to the 6168 using the 6168's speaker doesn't have a lip synch issue unless it's from the source ie Discover HD on Directv (not the 6168's fault). If you send sound from the 6168 back to the 5760 no delay is needed. However the only DD5.1 you will get is from air or cable using the 6168's built in tuner. The HDMI input only appears to accept 2.0 audio.
From item #1 above it sounds like when both the video and audio signal come into the 6168 in synch, whatecer video processing the 6168 does it ends up outputting the video and audio at the same time. You would expect this.
From item #2 above it looks like when a STB (Sir-160) is used to sned video to the 6168 and audio to the AVR, that the sound comes out of the AVR first. Because delaying it fixes the echo. In this case it also looks like the 6168 is correctly processing the audio and video input and synching them correctly for the video processing delay. The problem is that when the separate audio signal goes from the STB to the AVR, it gets output immediately, and time is not allowed for the video processing that the 6168 is doing on the signal.
I don't think that you can fault the 6168 for that, especially since it handles incoming video and audio correctly internally. It's only when the audio takes a path not through the 6168 that there is a problem.
It's almost like now that TV's are doing "so much" processing of the incoming video, that a system needs to be devised whereby the external AVR can somehow be "told" by the TV how long to delay the sound for. Back when no video processing was done by TV's this was a complete non-issue. In my case, and probably most others, my STB feeds the video to my TV and the audio to the AVR which drives the speakers. My TV is never used for outputting audio.
I don't envy you Clorox, trying to debug the situation by getting information from multiple sources, some of which may not have the technical knowledge to make sure what they are reporting in necessarily correct or not, no offense intended. Probably the best way to accurately test this is by setting the TV up in a lab, and using multiple sources, into the various TV inputs, and generate a comprehensive report. Even beyond the level of testing done by your typical A/V magazines.
I would think that Samsung would have done this level of testing and has the results. If nothing else, I would think they might want to provide a warning in the users manual that routing audio through an external path might require an AVR capable of putting delays in. They certainly know how long the video processing takes, but I don't know if that is in the manual or not. And it certainly could vary by source depending on the incoming data format.
I'm not an owner but have been following the thread to see how the computer input is working. I'm thinking of getting the Sony 50A10 for use primarily as a computer monitor as I have no HD feed.
Having spent a lot of time debugging hardware issues this entire discussion seems more like being at work than enjoying a new TV