Your right, but most receivers will have digital coax before optical.
Did you try to use the digital coax, It can be a work around until the optical fix.
Not everyone has digital coax on their receivers.
Yeah, my old Sony receiver is weird. It does have digital coaxial but I can only assign it to either the DVD input or the CD input. Not the TV/SAT input! I guess I could set it to the CD input, set the Sony receiver to CD, and that would work. I'm only running the audio part through the receiver, the video is via HDMI. And I use my DVD player for DVDs and CDs so the CD audio is unused. Oh well, hope I don't have to do any of this!
01-14-2009 08:22 AM - edited 01-14-2009 08:32 AM
everyone I need you to check your volume settings to make sure they didn't default to 0.
please post everything under the Menu.....Settings......Audio.......
Should be Volume Control, Audio Format, Volume Control, and Dynamic Range please.
also if you have hdmi connected and are experiencing no sound
User Settings - Additional HDMI Settings :
01-14-2009 09:14 AM - edited 01-14-2009 09:15 AM
I've tried reseating the optical cables and switching it to a different input on my receiver, same issue. I don't have a digital coax cable to see if that connection has the same problem. I looked at the volume settings and it was not set to zero, audio format is surround, I don't recall the volume control setting and dynamic range is turned off. HDMI works fine as does regular two channel. Funny thing is that some stations started working this moning, specifically ABC and NBC. All others I tried were cutting out. To answer another questions, I have the 7216 STB.
There was an issue with one of the updates that basically kicked the Optical Audio back to "mono mode" when the reciever was shut off. The customer would have to turn on stb, go to menu>settings>audio and select "surround" in one of the audio tabs.
The other work around was to leave he reciever on all the time.
Of course the third choice was to use the red and white wires to your audio reciever.
I thought this was taken care of with the last Img release...Maybe it's suppose to be corrected with the new 1.7 img release due the 1st quarter of this year.