Any update from YouView about a possible fix for this problem? It is extremely annoying and does imply that they don't do enough testing before releasing new software.
As an ex-test manager, I can't imagine there is a quick fix likely.
In fact, I do not believe that we have "bottomed out" the problem.
I cannot say, for certain, when it happens, such that I can predict when it is going to happen. Did anything happen overnight on 3108/0109 and 0909/1009? New channels added/deleted/changed? Software updates?
I cannot say, for certain, what actions trigger it, except the switch from BBC1 SD to BBC News HD. Has anyone come across the same behaviour with other channel changes?
I cannot say, for certain, that the configuration of Humax and TV does not cause it. My latest test would seem to point to a "handshake" problem between the two devices, and it might be either device causing the problem. Does anyone else have the same problem who is not using a T2000 and an LG32LD490?
Reading back over the thread, there are not a lot of reported instances and a few "not me"s. Does this mean that there are configurations or user behaviours that avoid the problem?
Until the probelm can be predicted and replicated consistently, the underlying cause is going to be very difficult to find and, therefore, to fix.
It's interesting that the proble was initially reported with the "old" software and has continued into NextGen
As an ex-test manager, I can't imagine there is a quick fix likely.
In fact, I do not believe that we have "bottomed out" the problem.
I cannot say, for certain, when it happens, such that I can predict when it is going to happen. Did anything happen overnight on 3108/0109 and 0909/1009? New channels added/deleted/changed? Software updates?
I cannot say, for certain, what actions trigger it, except the switch from BBC1 SD to BBC News HD. Has anyone come across the same behaviour with other channel changes?
I cannot say, for certain, that the configuration of Humax and TV does not cause it. My latest test would seem to point to a "handshake" problem between the two devices, and it might be either device causing the problem. Does anyone else have the same problem who is not using a T2000 and an LG32LD490?
Reading back over the thread, there are not a lot of reported instances and a few "not me"s. Does this mean that there are configurations or user behaviours that avoid the problem?
Until the probelm can be predicted and replicated consistently, the underlying cause is going to be very difficult to find and, therefore, to fix.
It's interesting that the proble was initially reported with the "old" software and has continued into NextGen
Ok, I'll republish any times that it happens. Regarding your point about it being config and not YouView I strongly disagree with it. We've had many years trouble free use of the YouView box until this started to happen - our config has never changed. It appears to be a change that the team has done with a low level audio interface module a while ago and this hardware abstraction level is reused in the new UI interface.
Changing from the old UI to the new UI (HTML5) would not be factor in this as you're taking about the display abstraction layer which would not be affected by it. Personally I cannot see the development team throwing out ALL code and interface layers just for the hell of it.
Hi trophytr5 & Nick. I have over the years occasionally suffered both the symptoms you mention - no sound & PSOD.
I was once plagued by psod for a period of 2 weeks solid. But heres the strange bit - it only happened if I had been watching Sky Sports for a period over 2 hours. No other channel was affected. Then after 2 weeks the behavior just suddenly stopped. There have been no occurrences since. I have no idea why but believe it to be a handshake issue. No sound on changing channels - This happens nearly everytime I change a channel, however, I have my box hooked to a Yamaha amp. It was looked into by the technical team but no cure was found. In the end we both decided is was again a handshake issue and my Yamaha and box just don't play nice together. Hitting the mute button twice always brings the sound back. Its an inconvenience I've just learned to live with. I suspect we all have slightly different issues but the underlying root-cause is at this time unknown. I know what I've said doesn't help much but I just wanted you to know your not alone.
I'm now happy with the disagree icon, because its gone.
Just to add a little to this, I have not noticed loss of sound on my YouView box, but have experienced something similar on my Samsung TV.
When tuning from a SD or HD channel to BBC News HD on 107, the TV takes several seconds to start decoding the sound.
Further investigation revealed that BBC News 107 (and a couple of other channels 108 111 and 112 which exhibit the same behaviour) have their sound encoded in AAC format.
All other HD channels I have checked are encoded using HE-AAC, and SD channels use MPEG encoding.
The TV seems to struggle for a few seconds to determine how to decode the audio on BBC News and I wonder if the YouView box similarly gets its knickers in a twist on occasions, failing to decode anything.
Anyway, just a thought.
John.
"Never tell people how to do things. Tell them what to do and they will surprise you with their ingenuity." - George S. Patton
Just to add a little to this, I have not noticed loss of sound on my YouView box, but have experienced something similar on my Samsung TV.
When tuning from a SD or HD channel to BBC News HD on 107, the TV takes several seconds to start decoding the sound.
Further investigation revealed that BBC News 107 (and a couple of other channels 108 111 and 112 which exhibit the same behaviour) have their sound encoded in AAC format.
All other HD channels I have checked are encoded using HE-AAC, and SD channels use MPEG encoding.
The TV seems to struggle for a few seconds to determine how to decode the audio on BBC News and I wonder if the YouView box similarly gets its knickers in a twist on occasions, failing to decode anything.
Anyway, just a thought.
John.
Sounds like it could be related to the problem. Makes sense.
Just an aside - I've just tried to like Johns post and got this error message -
<html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx</center> </body> </html> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page -->
The second attempt worked.
I'm now happy with the disagree icon, because its gone.
Just an aside - I've just tried to like Johns post and got this error message -
<html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx</center> </body> </html> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page -->
The second attempt worked.
I Liked it fine (in both senses of the words)
‘Have nothing in your houses that you do not know to be useful, or believe to be beautiful’ Wm Morris
As an ex-test manager, I can't imagine there is a quick fix likely.
In fact, I do not believe that we have "bottomed out" the problem.
I cannot say, for certain, when it happens, such that I can predict when it is going to happen. Did anything happen overnight on 3108/0109 and 0909/1009? New channels added/deleted/changed? Software updates?
I cannot say, for certain, what actions trigger it, except the switch from BBC1 SD to BBC News HD. Has anyone come across the same behaviour with other channel changes?
I cannot say, for certain, that the configuration of Humax and TV does not cause it. My latest test would seem to point to a "handshake" problem between the two devices, and it might be either device causing the problem. Does anyone else have the same problem who is not using a T2000 and an LG32LD490?
Reading back over the thread, there are not a lot of reported instances and a few "not me"s. Does this mean that there are configurations or user behaviours that avoid the problem?
Until the probelm can be predicted and replicated consistently, the underlying cause is going to be very difficult to find and, therefore, to fix.
It's interesting that the proble was initially reported with the "old" software and has continued into NextGen
If it didn't happen before and you haven't changed the config. and it happens now, then I agree, it is unlikely to be a configuration issue. That could be one possibility eliminated.
And if it happened before change to NextGen, then that's another one out.
We are making progress.
Did it happen on the same dates as I experianced it?
Just to add a little to this, I have not noticed loss of sound on my YouView box, but have experienced something similar on my Samsung TV.
When tuning from a SD or HD channel to BBC News HD on 107, the TV takes several seconds to start decoding the sound.
Further investigation revealed that BBC News 107 (and a couple of other channels 108 111 and 112 which exhibit the same behaviour) have their sound encoded in AAC format.
All other HD channels I have checked are encoded using HE-AAC, and SD channels use MPEG encoding.
The TV seems to struggle for a few seconds to determine how to decode the audio on BBC News and I wonder if the YouView box similarly gets its knickers in a twist on occasions, failing to decode anything.
Anyway, just a thought.
John.
Aha!!! I now recall having a similar problem. I'd change channels and have no sound, but either it would sort itself out or changing channels again would fix it. But I can't remember when and with which box (T1000, T1010 or T2000). It was probably the T1010 which subsequently had the HDMI port failure
This happened to me a couple of times in April, days after the NextGen update (retail T2110). Haven't seen it since but the cause wasn't obvious to me at the time. Thought it might have been due to the quick succession of fast forwarding, stopping and exiting a recording the second time. Pretty sure I tried the mute button trick but it was a hard reset that fixed it on both occasions. Didn't (and still don't) want to try and reproduce as wasn't convinced a reset wouldn't backfire and lose my recordings
Update - It happened this morning (15 Sept 2017). I've been keeping a note of the number of channels it has (Setting, TV Channels) in the hope that if the numbers changes AND it fails to have sound on changing from CH1 to CH107, it might gives us a clue, but no. It is 170 as it was yesterday.
No problem since 9 Sept. Tried switched off the TV again. WHen switched back on - PSOD. Tried switching off Humax. Didn't respond to remote control. Had to restart the box
This has been a feature of the BT YouVew box since long before Next Generation, I have experienced it on my home system: YouView box connected to internet running latest software, HMDI into Panasonic TV & Optical into top of the range Sony AV Amp. YouView set to output Surround when available. And on my parents BT YouView box, still running Current Gen, no internet connection, just HDMI to Samsung TV, set to output Stereo. Most often when changing channels, sometimes when playing recording, occasionally after re-wind or pause recording/live TV. Occasionally changing channels fixes it, more often switching to standby & back on, occasionally requires total power down & re-boot (power switch on back)
This has been a feature of the BT YouVew box since long before Next Generation, I have experienced it on my home system: YouView box connected to internet running latest software, HMDI into Panasonic TV & Optical into top of the range Sony AV Amp. YouView set to output Surround when available. And on my parents BT YouView box, still running Current Gen, no internet connection, just HDMI to Samsung TV, set to output Stereo. Most often when changing channels, sometimes when playing recording, occasionally after re-wind or pause recording/live TV. Occasionally changing channels fixes it, more often switching to standby & back on, occasionally requires total power down & re-boot (power switch on back)
Hi Peter. The sound issues years ago on BT Vision were traced to faulty encoders on its Multicast network and so were corrected. But I've no idea whats causing this. Mind you I am connected to some third party kit in the form of a Yamaha amp which causes loss of sound when changing channels (which is a handshake problem). Hitting the mute button twice cures it for me, but apparently not for others.
I'm now happy with the disagree icon, because its gone.
It happened again today. Slightly different this time, in that I saw two flickers (see video above) before the channel changed and I lost sound. Thought I'd try and change the channel back before I rebooted and the picture froze and I got this display Went to sttings to check signal and got this Turned the TV off and back on and this time I didn't get the PSOD and the remote was responding but still no sound. Turned Humax off and back on with remote. Still no sound Did a restart and it all came back on channel 1. Checked signal and got this so signal is OK. Changed to channel 107 and IT LOST SOUND AGAIN. That is the first time it's done it twice (that I am aware of). It may be that if I lose sound, change back to channel 1, then restart (when it will be on channel 1) and then change to 107, it might do it again. Another thing to try.
Turned on our YouView box, changing channel from 1 to 101 and it happened again. See OP for all my system information.
POWER AND STANDBY Auto standby 3, hours Standby mode. SMART Start deep sleep. 1 AM End deep sleep 5 AM
.SOFTWARE INFORMATION Last check for update. 18th September 2017 Last check for players and apps 18th September 2017 Component SW. 3.2.92 (abd44b) Manufacturer SW. 28.35.0 Platform config. 3844 ISP configuration. 9
Hard reboot by holding down power button on box fixes it as normal.
Signal strength on 1 and 101 is 100% so I don't think it's linked to that (weather is fine as well - heavy rain does affect our signal strength especially on the lower quality channels like Pick and Spike).
Turned on our YouView box, changing channel from 1 to 101 and it happened again. See OP for all my system information.
POWER AND STANDBY Auto standby 3, hours Standby mode. SMART Start deep sleep. 1 AM End deep sleep 5 AM
.SOFTWARE INFORMATION Last check for update. 18th September 2017 Last check for players and apps 18th September 2017 Component SW. 3.2.92 (abd44b) Manufacturer SW. 28.35.0 Platform config. 3844 ISP configuration. 9
Hard reboot by holding down power button on box fixes it as normal.
Signal strength on 1 and 101 is 100% so I don't think it's linked to that (weather is fine as well - heavy rain does affect our signal strength especially on the lower quality channels like Pick and Spike).
Mine was OK this morning (18th).
Does this mean that it ISN'T to do with channel or software updates. you think?
I have the same software versions as you.
p.s. Nick, how do you get the setting information as text to insert in your messages? Is it just careful typing or do you have some crafty shortcut?
Turned on our YouView box, changing channel from 1 to 101 and it happened again. See OP for all my system information.
POWER AND STANDBY Auto standby 3, hours Standby mode. SMART Start deep sleep. 1 AM End deep sleep 5 AM
.SOFTWARE INFORMATION Last check for update. 18th September 2017 Last check for players and apps 18th September 2017 Component SW. 3.2.92 (abd44b) Manufacturer SW. 28.35.0 Platform config. 3844 ISP configuration. 9
Hard reboot by holding down power button on box fixes it as normal.
Signal strength on 1 and 101 is 100% so I don't think it's linked to that (weather is fine as well - heavy rain does affect our signal strength especially on the lower quality channels like Pick and Spike).
Turned on our YouView box, changing channel from 1 to 101 and it happened again. See OP for all my system information.
POWER AND STANDBY Auto standby 3, hours Standby mode. SMART Start deep sleep. 1 AM End deep sleep 5 AM
.SOFTWARE INFORMATION Last check for update. 18th September 2017 Last check for players and apps 18th September 2017 Component SW. 3.2.92 (abd44b) Manufacturer SW. 28.35.0 Platform config. 3844 ISP configuration. 9
Hard reboot by holding down power button on box fixes it as normal.
Signal strength on 1 and 101 is 100% so I don't think it's linked to that (weather is fine as well - heavy rain does affect our signal strength especially on the lower quality channels like Pick and Spike).
I think I mighrt just set up a NotePad document as a template into which I can insert the variables. Then copy and paste into the message
Turned on our YouView box, changing channel from 1 to 101 and it happened again. See OP for all my system information.
POWER AND STANDBY Auto standby 3, hours Standby mode. SMART Start deep sleep. 1 AM End deep sleep 5 AM
.SOFTWARE INFORMATION Last check for update. 18th September 2017 Last check for players and apps 18th September 2017 Component SW. 3.2.92 (abd44b) Manufacturer SW. 28.35.0 Platform config. 3844 ISP configuration. 9
Hard reboot by holding down power button on box fixes it as normal.
Signal strength on 1 and 101 is 100% so I don't think it's linked to that (weather is fine as well - heavy rain does affect our signal strength especially on the lower quality channels like Pick and Spike).
Not sure if this is the same fault but I have something that sounds very similar.
We get no sound from any of the Freeview HD channels unless we sit there in silence for about 30 seconds and then the sound comes out and everything works OK. But if I do anything at all - even something as innocuous as pressing the youview remote control mute button on and off or changing to another HD channel - and the sound goes away again until some time passes and then it comes back. SD channels work fine.
I've changed nothing in our set-up.. this just started happening.
Setup:
HUMAX DTRT1000 / 80B07000 Component Software 3.2.92 (abd44b) Manufacturer Software 28.35.0 Platform / ISP configuration 3844 / 253 This is a retail Freeview/Youview box that has been hijacked by BT's software/branding since switching to BT Infinity a year or so ago.
HDMI output to Octava HD41ARC to Sonos Playbar (optical)
Nothing has changed in the setup over the period when the fault appeared apart from whatever software updates will have been pushed to the freeview box (or Sonos)
Not sure if this is the same fault but I have something that sounds very similar.
We get no sound from any of the Freeview HD channels unless we sit there in silence for about 30 seconds and then the sound comes out and everything works OK. But if I do anything at all - even something as innocuous as pressing the youview remote control mute button on and off or changing to another HD channel - and the sound goes away again until some time passes and then it comes back. SD channels work fine.
I've changed nothing in our set-up.. this just started happening.
Setup:
HUMAX DTRT1000 / 80B07000 Component Software 3.2.92 (abd44b) Manufacturer Software 28.35.0 Platform / ISP configuration 3844 / 253 This is a retail Freeview/Youview box that has been hijacked by BT's software/branding since switching to BT Infinity a year or so ago.
HDMI output to Octava HD41ARC to Sonos Playbar (optical)
Nothing has changed in the setup over the period when the fault appeared apart from whatever software updates will have been pushed to the freeview box (or Sonos)
Hi Richard
Your problem sounds a little different to those above, but no matter.
Whenever there is an issue like this - something that does not seem to be a universal problem with a release - I always suggest people try a couple of resets to see if one of these will make the problem go away.
Firstly, try a soft reset - while not recording, nor about to, touch the centre ring on your T1000 for just over 8 seconds, and let the box soft reboot.
See if this clears the issue. If it does, fine.
If not try a more drastic reset, albeit one that still preserves your recordings, a Maintenance Mode Option 4.
The instructions for this are referenced in the third of the Pinned postings at the top of the Community Home Page.
If this still does not resolve the issue then as a final test, temporarily disconnect the Octava/Sonos, and see if you still have the problem using the 'ordinary' sound through your TV over HDMI direct from the YouView box.
This will tell you, and us, if this is a pure YouView problem, or a YouView/Octava/Sonos interplay problem.
If it is an interplay problem, next test dropping the Octava out of the loop by running the Sonos directly off the optical out of the YouView box.
If this then gives the delay, you have identified a YouView/Sonos interplay problem, and it may be worth a chat with Sonos to see if they have further reports of this.
But if the YouView/Sonos interplay is OK, then we would seem to be looking at an interplay problem with the Octava.
So the final test (phew!) if it goes this far, is to use the Octava as a straight HDMI switch, YouView box in, TV out, and see if the delay still occurs or not.
This last test will tell us if the Octava is fundamentally the culprit, or if it is something in the way the Octava goes from HDMI in to optical out, to feed the Sonos.
You do not say which mode you run the Octava in, and I know it is supposed to switch instantly, and I see where you report this all used to work OK.
But the tests above should absolutely bottom where the issue is now.
Do let us know how you get on!
‘Have nothing in your houses that you do not know to be useful, or believe to be beautiful’ Wm Morris
Not sure if this is the same fault but I have something that sounds very similar.
We get no sound from any of the Freeview HD channels unless we sit there in silence for about 30 seconds and then the sound comes out and everything works OK. But if I do anything at all - even something as innocuous as pressing the youview remote control mute button on and off or changing to another HD channel - and the sound goes away again until some time passes and then it comes back. SD channels work fine.
I've changed nothing in our set-up.. this just started happening.
Setup:
HUMAX DTRT1000 / 80B07000 Component Software 3.2.92 (abd44b) Manufacturer Software 28.35.0 Platform / ISP configuration 3844 / 253 This is a retail Freeview/Youview box that has been hijacked by BT's software/branding since switching to BT Infinity a year or so ago.
HDMI output to Octava HD41ARC to Sonos Playbar (optical)
Nothing has changed in the setup over the period when the fault appeared apart from whatever software updates will have been pushed to the freeview box (or Sonos)
Thanks Roy. I wasn't aware there _were_ modes in Octava! If it makes any difference, I have HDMI in from Playstation 3, Apple TV, YouView, HDMI out to TV and optical out to Sonos. I may also have optical in from one of the devices (possibly the ancient PS3? I'll have to check). It automatically switches to whichever device did something last.
I was hoping this might be a known problem with a trivial fix but I suspect you're right: no option but to do the painstaking problem determination/isolation steps. I'll look again at the weekend.
One thing to stress though: this just started happening... ie something changed... and I'm pretty sure it can only have been the software in the YouView box or, less likely given its quality seems to be so much higher, the software in the Sonos device.
Not sure if this is the same fault but I have something that sounds very similar.
We get no sound from any of the Freeview HD channels unless we sit there in silence for about 30 seconds and then the sound comes out and everything works OK. But if I do anything at all - even something as innocuous as pressing the youview remote control mute button on and off or changing to another HD channel - and the sound goes away again until some time passes and then it comes back. SD channels work fine.
I've changed nothing in our set-up.. this just started happening.
Setup:
HUMAX DTRT1000 / 80B07000 Component Software 3.2.92 (abd44b) Manufacturer Software 28.35.0 Platform / ISP configuration 3844 / 253 This is a retail Freeview/Youview box that has been hijacked by BT's software/branding since switching to BT Infinity a year or so ago.
HDMI output to Octava HD41ARC to Sonos Playbar (optical)
Nothing has changed in the setup over the period when the fault appeared apart from whatever software updates will have been pushed to the freeview box (or Sonos)
Cheers Richard
Here is the helpful resource I used when researching your issue, to bring me up to speed on the Octava, which I had not heard of.
The page refers to the modes under Features, top right.
And there's pile of information there if you chase the other links, I expect.
Not sure if this is the same fault but I have something that sounds very similar.
We get no sound from any of the Freeview HD channels unless we sit there in silence for about 30 seconds and then the sound comes out and everything works OK. But if I do anything at all - even something as innocuous as pressing the youview remote control mute button on and off or changing to another HD channel - and the sound goes away again until some time passes and then it comes back. SD channels work fine.
I've changed nothing in our set-up.. this just started happening.
Setup:
HUMAX DTRT1000 / 80B07000 Component Software 3.2.92 (abd44b) Manufacturer Software 28.35.0 Platform / ISP configuration 3844 / 253 This is a retail Freeview/Youview box that has been hijacked by BT's software/branding since switching to BT Infinity a year or so ago.
HDMI output to Octava HD41ARC to Sonos Playbar (optical)
Nothing has changed in the setup over the period when the fault appeared apart from whatever software updates will have been pushed to the freeview box (or Sonos)
I don't agree Roy. I have not changed my setup since I initially bought my Humax YouView box and never saw this happening until a couple of years ago. Nothing had changed connection wise - just HDMI into TV - our sound is piped from the optical out on the TV directly into the Queries M4 soundbar.
If I get it again, very likely as the system still has not been fixed, I'll wait 60 seconds and see if the sound comes back on.
Not sure if this is the same fault but I have something that sounds very similar.
We get no sound from any of the Freeview HD channels unless we sit there in silence for about 30 seconds and then the sound comes out and everything works OK. But if I do anything at all - even something as innocuous as pressing the youview remote control mute button on and off or changing to another HD channel - and the sound goes away again until some time passes and then it comes back. SD channels work fine.
I've changed nothing in our set-up.. this just started happening.
Setup:
HUMAX DTRT1000 / 80B07000 Component Software 3.2.92 (abd44b) Manufacturer Software 28.35.0 Platform / ISP configuration 3844 / 253 This is a retail Freeview/Youview box that has been hijacked by BT's software/branding since switching to BT Infinity a year or so ago.
HDMI output to Octava HD41ARC to Sonos Playbar (optical)
Nothing has changed in the setup over the period when the fault appeared apart from whatever software updates will have been pushed to the freeview box (or Sonos)
What is it you don't agree with, Nick?
As far as I can tell, Richard has some sort of latency problem where his kit takes a while to reestablish itself after a change, in his YouView/Octava/Sonos setup; whereas you and trophytr5 have an issue where the sound goes from the YouView box with no other kit in the loop.
And doesn't come back of its own accord after a delay, like Richard's does.
Or have I got that wrong?
But I have been very careful not to prejudge the issues with Richard's setup; we will know a lot more if his YouView box, after those two resets and working directly into his TV, still exhibits this problem, if we need to go that far.
‘Have nothing in your houses that you do not know to be useful, or believe to be beautiful’ Wm Morris
Not sure if this is the same fault but I have something that sounds very similar.
We get no sound from any of the Freeview HD channels unless we sit there in silence for about 30 seconds and then the sound comes out and everything works OK. But if I do anything at all - even something as innocuous as pressing the youview remote control mute button on and off or changing to another HD channel - and the sound goes away again until some time passes and then it comes back. SD channels work fine.
I've changed nothing in our set-up.. this just started happening.
Setup:
HUMAX DTRT1000 / 80B07000 Component Software 3.2.92 (abd44b) Manufacturer Software 28.35.0 Platform / ISP configuration 3844 / 253 This is a retail Freeview/Youview box that has been hijacked by BT's software/branding since switching to BT Infinity a year or so ago.
HDMI output to Octava HD41ARC to Sonos Playbar (optical)
Nothing has changed in the setup over the period when the fault appeared apart from whatever software updates will have been pushed to the freeview box (or Sonos)
I'm wanting to try out this wait for 60 seconds fix and see if they are related. The symptom of sound fine then after overnight changing from SD to HD no sound in all cases seems related.
Not sure if this is the same fault but I have something that sounds very similar.
We get no sound from any of the Freeview HD channels unless we sit there in silence for about 30 seconds and then the sound comes out and everything works OK. But if I do anything at all - even something as innocuous as pressing the youview remote control mute button on and off or changing to another HD channel - and the sound goes away again until some time passes and then it comes back. SD channels work fine.
I've changed nothing in our set-up.. this just started happening.
Setup:
HUMAX DTRT1000 / 80B07000 Component Software 3.2.92 (abd44b) Manufacturer Software 28.35.0 Platform / ISP configuration 3844 / 253 This is a retail Freeview/Youview box that has been hijacked by BT's software/branding since switching to BT Infinity a year or so ago.
HDMI output to Octava HD41ARC to Sonos Playbar (optical)
Nothing has changed in the setup over the period when the fault appeared apart from whatever software updates will have been pushed to the freeview box (or Sonos)
I tried waiting for about 15 minutes. Went away and did something else. Sound didn't come back.
The thing that is puzzling me is that, when it happens and I switch the TV off, why does it go to PSOD and why does it stop responding to the remote? And why, if I don't switch the TV off and I try and change channel did it lose the aerial signal?
It makes me think of the situation where you leave something touching the keyboard of PC and you fill the input buffer and then you get a stack overflow which screws up the whole thing. This used to happen with early PCs and the "New Improved" ones these days seem to be able to cope
Comments
In fact, I do not believe that we have "bottomed out" the problem.
I cannot say, for certain, when it happens, such that I can predict when it is going to happen. Did anything happen overnight on 3108/0109 and 0909/1009? New channels added/deleted/changed? Software updates?
I cannot say, for certain, what actions trigger it, except the switch from BBC1 SD to BBC News HD. Has anyone come across the same behaviour with other channel changes?
I cannot say, for certain, that the configuration of Humax and TV does not cause it. My latest test would seem to point to a "handshake" problem between the two devices, and it might be either device causing the problem. Does anyone else have the same problem who is not using a T2000 and an LG32LD490?
Reading back over the thread, there are not a lot of reported instances and a few "not me"s. Does this mean that there are configurations or user behaviours that avoid the problem?
Until the probelm can be predicted and replicated consistently, the underlying cause is going to be very difficult to find and, therefore, to fix.
It's interesting that the proble was initially reported with the "old" software and has continued into NextGen
Changing from the old UI to the new UI (HTML5) would not be factor in this as you're taking about the display abstraction layer which would not be affected by it. Personally I cannot see the development team throwing out ALL code and interface layers just for the hell of it.
I have over the years occasionally suffered both the symptoms you mention - no sound & PSOD.
I was once plagued by psod for a period of 2 weeks solid. But heres the strange bit - it only happened if I had been watching Sky Sports for a period over 2 hours. No other channel was affected. Then after 2 weeks the behavior just suddenly stopped. There have been no occurrences since. I have no idea why but believe it to be a handshake issue.
No sound on changing channels - This happens nearly everytime I change a channel, however, I have my box hooked to a Yamaha amp. It was looked into by the technical team but no cure was found. In the end we both decided is was again a handshake issue and my Yamaha and box just don't play nice together. Hitting the mute button twice always brings the sound back. Its an inconvenience I've just learned to live with.
I suspect we all have slightly different issues but the underlying root-cause is at this time unknown. I know what I've said doesn't help much but I just wanted you to know your not alone.
When tuning from a SD or HD channel to BBC News HD on 107, the TV takes several seconds to start decoding the sound.
Further investigation revealed that BBC News 107 (and a couple of other channels 108 111 and 112 which exhibit the same behaviour) have their sound encoded in AAC format.
All other HD channels I have checked are encoded using HE-AAC, and SD channels use MPEG encoding.
The TV seems to struggle for a few seconds to determine how to decode the audio on BBC News and I wonder if the YouView box similarly gets its knickers in a twist on occasions, failing to decode anything.
Anyway, just a thought.
John.
<html> <head><title>502 Bad Gateway</title></head> <body bgcolor="white"> <center><h1>502 Bad Gateway</h1></center> <hr><center>nginx</center> </body> </html> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page -->
The second attempt worked.
And if it happened before change to NextGen, then that's another one out.
We are making progress.
Did it happen on the same dates as I experianced it?
https://community.bt.com/t5/YouView-Boxes/Sound-loss-after-fast-forward/td-p/1775792
No problem since 9 Sept. Tried switched off the TV again. WHen switched back on - PSOD. Tried switching off Humax. Didn't respond to remote control. Had to restart the box
It happened again today. Slightly different this time, in that I saw two flickers (see video above) before the channel changed and I lost sound. Thought I'd try and change the channel back before I rebooted and the picture froze and I got this display
Went to sttings to check signal and got this
Turned the TV off and back on and this time I didn't get the PSOD and the remote was responding but still no sound.
Turned Humax off and back on with remote. Still no sound
Did a restart and it all came back on channel 1. Checked signal and got this
so signal is OK.
Changed to channel 107 and IT LOST SOUND AGAIN. That is the first time it's done it twice (that I am aware of). It may be that if I lose sound, change back to channel 1, then restart (when it will be on channel 1) and then change to 107, it might do it again. Another thing to try.
POWER AND STANDBY
Auto standby 3, hours
Standby mode. SMART
Start deep sleep. 1 AM
End deep sleep 5 AM
.SOFTWARE INFORMATION
Last check for update. 18th September 2017
Last check for players and apps 18th September 2017
Component SW. 3.2.92 (abd44b)
Manufacturer SW. 28.35.0
Platform config. 3844
ISP configuration. 9
Hard reboot by holding down power button on box fixes it as normal.
Signal strength on 1 and 101 is 100% so I don't think it's linked to that (weather is fine as well - heavy rain does affect our signal strength especially on the lower quality channels like Pick and Spike).
Does this mean that it ISN'T to do with channel or software updates. you think?
I have the same software versions as you.
p.s. Nick, how do you get the setting information as text to insert in your messages? Is it just careful typing or do you have some crafty shortcut?
We get no sound from any of the Freeview HD channels unless we sit there in silence for about 30 seconds and then the sound comes out and everything works OK. But if I do anything at all - even something as innocuous as pressing the youview remote control mute button on and off or changing to another HD channel - and the sound goes away again until some time passes and then it comes back. SD channels work fine.
I've changed nothing in our set-up.. this just started happening.
Setup:
HUMAX DTRT1000 / 80B07000
Component Software 3.2.92 (abd44b)
Manufacturer Software 28.35.0
Platform / ISP configuration 3844 / 253
This is a retail Freeview/Youview box that has been hijacked by BT's software/branding since switching to BT Infinity a year or so ago.
HDMI output to Octava HD41ARC to Sonos Playbar (optical)
Nothing has changed in the setup over the period when the fault appeared apart from whatever software updates will have been pushed to the freeview box (or Sonos)
Your problem sounds a little different to those above, but no matter.
Whenever there is an issue like this - something that does not seem to be a universal problem with a release - I always suggest people try a couple of resets to see if one of these will make the problem go away.
Firstly, try a soft reset - while not recording, nor about to, touch the centre ring on your T1000 for just over 8 seconds, and let the box soft reboot.
See if this clears the issue. If it does, fine.
If not try a more drastic reset, albeit one that still preserves your recordings, a Maintenance Mode Option 4.
The instructions for this are referenced in the third of the Pinned postings at the top of the Community Home Page.
If this still does not resolve the issue then as a final test, temporarily disconnect the Octava/Sonos, and see if you still have the problem using the 'ordinary' sound through your TV over HDMI direct from the YouView box.
This will tell you, and us, if this is a pure YouView problem, or a YouView/Octava/Sonos interplay problem.
If it is an interplay problem, next test dropping the Octava out of the loop by running the Sonos directly off the optical out of the YouView box.
If this then gives the delay, you have identified a YouView/Sonos interplay problem, and it may be worth a chat with Sonos to see if they have further reports of this.
But if the YouView/Sonos interplay is OK, then we would seem to be looking at an interplay problem with the Octava.
So the final test (phew!) if it goes this far, is to use the Octava as a straight HDMI switch, YouView box in, TV out, and see if the delay still occurs or not.
This last test will tell us if the Octava is fundamentally the culprit, or if it is something in the way the Octava goes from HDMI in to optical out, to feed the Sonos.
You do not say which mode you run the Octava in, and I know it is supposed to switch instantly, and I see where you report this all used to work OK.
But the tests above should absolutely bottom where the issue is now.
Do let us know how you get on!
I was hoping this might be a known problem with a trivial fix but I suspect you're right: no option but to do the painstaking problem determination/isolation steps. I'll look again at the weekend.
One thing to stress though: this just started happening... ie something changed... and I'm pretty sure it can only have been the software in the YouView box or, less likely given its quality seems to be so much higher, the software in the Sonos device.
Thanks for the detailed response.
Here is the helpful resource I used when researching your issue, to bring me up to speed on the Octava, which I had not heard of.
The page refers to the modes under Features, top right.
And there's pile of information there if you chase the other links, I expect.
https://www.octavainc.com/HDMI%20swit...
If I get it again, very likely as the system still has not been fixed, I'll wait 60 seconds and see if the sound comes back on.
As far as I can tell, Richard has some sort of latency problem where his kit takes a while to reestablish itself after a change, in his YouView/Octava/Sonos setup; whereas you and trophytr5 have an issue where the sound goes from the YouView box with no other kit in the loop.
And doesn't come back of its own accord after a delay, like Richard's does.
Or have I got that wrong?
But I have been very careful not to prejudge the issues with Richard's setup; we will know a lot more if his YouView box, after those two resets and working directly into his TV, still exhibits this problem, if we need to go that far.
It makes me think of the situation where you leave something touching the keyboard of PC and you fill the input buffer and then you get a stack overflow which screws up the whole thing. This used to happen with early PCs and the "New Improved" ones these days seem to be able to cope