[vcanadell]

All Prime is ok, but I have found a big problem: I have connected 7.1 (in my case, only 5.1) analog audio to a 7.1 or 5.1 input analog of a good receiver (denonavc1xv) because it have not hdmi. DTS MA or Dolby True DH decoded by Dune sounds perfect. Problem: if you start first the receiver and AFTER you start the Dune HD prime 3.0, then the receiver is BROKEN, after a big sound from speakers. If you start DUNE BEFORE the receiver all is OK. Dune broke my receiver, and I tried with other old Yamaha and "near" break
also. I am reparing my receiver, but I feel it is very dangerous, because you can "forget" start before the dune and after the receiver, and then broke it.
I think DUNE must do somethink, there are a lot of people that are usig "old" but very good and very expensive a/v receivers trough 7.1 analog and can broken them.

[kaanic]

Sorry for your loss...

The reported problem is already known:
B-OTH-002 - Loud noise on audio 7.1 analog outputs when unit is turned on/off (not healthly for the speakers)

[bsoima]

How could the receiver broke from this ?
I encountered the same situation a couple of time with my Denon AVR-1909.
Could it be that this is the cause for the hissing/noise problems I'm having ? (see other thread).
Also, will/can this be fixed with a firmware update ?

[DaneelSE]

Originally Posted by vcanadell I think DUNE must do somethink, there are a lot of people that are usig "old" but very good and very expensive a/v receivers trough 7.1 analog and can broken them.

This is a very serious issue.
My main motivation for buying the BD Prime was that it would enable all new audio formats without buying a receiver. If I cannot use the analog outputs without risk of damaging pre-amplifier, power-amplifier and or speakers I will NOT use it.

Having the BD Prime powered on at all times is NOT an option !

[bitethebytes]

Hi,

there is allways the discourse about analog 7.1 & 5.1 audio craches receivers or speakers.
Does this bug also apply on analog 2.0 output?

Thx
Frank

[bitethebytes]

Ähm, is the answer right in front of me and i am not seeing it?
Does this bug apply to ALL (7.1, 5.1, 2.0) analog output variants?
Is this bug still existant in newer 3.0 models?

Anyone?