Update Beosound Theatre 3.2.1
36 replies
I will do that. ?
Quick q - for the setup where you are experiencing this, do you have other speakers attached?
Watching live TV has the decreased volume. Other speakers are attached (Beolab 28) but I don't use them watching live tv. Only when watching movies.
thanks - actually I'm experiencing the same low volume issue on both my Theatre setups - one has 50s/17s attached, one is standalone.
You could use one of the MyButtons for Live TV and set the startup volume somewhat higher there.
Sure that does not solve ‘the problem’….if there is any - but it makes things less annoying.
MM
Sure that does not solve ‘the problem’….if there is any - but it makes things less annoying.
MM
Location: Flensborg————Danmark
??
You could use one of the MyButtons for Live TV and set the startup volume somewhat higher there. Sure that does not solve ‘the problem’….if there is any – but it makes things less annoying. MMI don't think it does? Sandyb's problem is the sound format. Some channels on Live TV broadcast different lower grade formats......PCM2.0 to 5.1. this is where the bug" lies. On the UK Freeview service, you can literally CH+/CH- and go 5.1, 2.0, 5.1, 2.0........... "Higher grade" subscription services (Netflix, Disney, Amazon) can do 5.1, DD+ or Atmos. These subscription services tend to have a more consistent playback sound/volume (less format changes) and not the problem from Sandyb's perspective and not where the PCM2.0 bug resided. What I do find...is that specifically with Netflix, it tends to play quite a bit louder than others - and that can be solved by Mybuttons on source change. The "bug" needs to be fixed by B&O PDQ. What I don't understand however is that reading across multiple forums is some people like myself have not experienced the volume dip bug as SandyB does in 3.2.1, or the switch to standby or a good deal of other bugs? I do not recall the last time I noticed the PCM2.0 problem for many months (not just SW3.2.1 update). Whereas this particular instance seems to have swapped one bug for another, from reading, SandyBs Theatre's seem to be very buggy, whereas mine seem not to have (they have had issues - but nothing like SandyBs issues). I have a hypothesis that this issue is a lot deeper than we know and a reason why B&O can never seem to fix the issues in Mozart. Old bugs never get written-out, or come back or new bugs replace old ones. I think the problem is the additive nature of Mozart and when peripheral equipment is added (speakers, Beolink, other Mozart devices or Set top boxes of any flavour or HDMI devices), specific code comes (configured) in and unintended consequences result. Add this speaker and this HDMI device...no issues. Add something else...or different speakers or a Set top box or an AppleTV combination...and issues appear?
Indeed, and who knows really.
Remember it was Geoff/Flatpanels review that highlighted the original PCM 2.0 issue with True Image. As mentioned before, this was very noticeable on my standalone Theatre, not noticeable on my Theatre/50s/17 room. So I can see why not everyone experienced it, but it was an issue.
Elsewhere, as seen in the 3.2.1 release notes, there was a separate issue "Fixed an issue where bass was lacking in 2.0 setup, when playing Dolby Digital 5.1 content"
For those who largely / just watch Netflix Atmos stuff, or Discs with Dolby True HD - there is no issue, and indeed I have no issue with this content.
But with live Tv, as programmes switch from PCM / Dolby Dig 2.0 to Dolby Dig 5.1 and back again, the volume drops away / rises by a big amount, requiring a 10-15 volume adjustment.
CK (over on Discord) passed on a msg he had from Geoff - that the new SW has changed the time alignment of the left/centre/right channels, and there should be some sound changes, although what type of setup he was referring to is unclear.
Anyway, I'll pick it up with CK this week.
And bear in mind, Marc above is having the same issue.
Remember it was Geoff/Flatpanels review that highlighted the original PCM 2.0 issue with True Image. As mentioned before, this was very noticeable on my standalone Theatre, not noticeable on my Theatre/50s/17 room. So I can see why not everyone experienced it, but it was an issue.
Elsewhere, as seen in the 3.2.1 release notes, there was a separate issue "Fixed an issue where bass was lacking in 2.0 setup, when playing Dolby Digital 5.1 content"
For those who largely / just watch Netflix Atmos stuff, or Discs with Dolby True HD - there is no issue, and indeed I have no issue with this content.
But with live Tv, as programmes switch from PCM / Dolby Dig 2.0 to Dolby Dig 5.1 and back again, the volume drops away / rises by a big amount, requiring a 10-15 volume adjustment.
CK (over on Discord) passed on a msg he had from Geoff - that the new SW has changed the time alignment of the left/centre/right channels, and there should be some sound changes, although what type of setup he was referring to is unclear.
Anyway, I'll pick it up with CK this week.
And bear in mind, Marc above is having the same issue.
After updating Beosound theatre to software 3.2.1 there is a buzzing noise coming from the rear speakers, has anybody else experienced similar issues?
Set-up is Beolab 5 front, Beolab 9 rears, and 2 pairs of Beolab 3’s as front and rear height channels, all connected via powerlink cables.
Set-up is Beolab 5 front, Beolab 9 rears, and 2 pairs of Beolab 3’s as front and rear height channels, all connected via powerlink cables.
Same here... with BL6000 rears and BL5 front. BL5 are fine, rears have the noise.
My B&O Icons:
Please Log In to Reply
You must be logged in as a BeoWorld member to post replies to forum threads.
or
Join BeoWorld
Register to access the forums, reference material, and exclusive member benefits — including our monthly prize draw.
Become a Member