I'm going to be the broken record on this particular topic but there IS a work-around for the DTS bomb. Don't bitstream DTS MA and the issue goes away. Decoding in the player will sound no different than in the receiver.
I am NOT defending Marantz's CS or their firmware policy. I'm only re-stating that if you have a player that can decode the HD codecs the DTS bomb issue disappears.
Marantz, Onkyo, Integra and Yamaha didn't know about this problem and it got by ALL of their R+D departments. To me, the problem lies with TI not getting it right in the first place.
Finally, with all of the different stories coming from Marantz CS, why are we so quick to believe the nastiest of them all and then get all worked up over it? Maramp was told it was a nasty soldering job and arkasi55 was told the DTS bomb was a simple software fix. Which one is true? Even if it's the soldering job, if you choose to send it in then you're without it for a week or two and it comes back fixed. Is it really worth getting so angry about? Again, this issue got by 4 major R+D departments. I have a real hard time blaming Marantz for this problem with the TI chip.
I am NOT defending Marantz's CS or their firmware policy. I'm only re-stating that if you have a player that can decode the HD codecs the DTS bomb issue disappears.
Marantz, Onkyo, Integra and Yamaha didn't know about this problem and it got by ALL of their R+D departments. To me, the problem lies with TI not getting it right in the first place.
Finally, with all of the different stories coming from Marantz CS, why are we so quick to believe the nastiest of them all and then get all worked up over it? Maramp was told it was a nasty soldering job and arkasi55 was told the DTS bomb was a simple software fix. Which one is true? Even if it's the soldering job, if you choose to send it in then you're without it for a week or two and it comes back fixed. Is it really worth getting so angry about? Again, this issue got by 4 major R+D departments. I have a real hard time blaming Marantz for this problem with the TI chip.














.


.