Originally Posted by jazzrock
What? After all this time waiting for this X release, and no exciting banter?! I'm rather surprised!!
Originally Posted by The Bogg
Exactly - after all the kvetching about how long it was taking I expected 5 pages of opinions by now.
OK, so I've downloaded it and installed it now - congrats to Datasat for finally getting it released - I've only done a brief test on a couple of scenes, and it sounds great. I won't get more time to test more thoroughly until next week.
Unfortunately because to the cross-mixing bug, I couldn't directly compare Neural:X to DSU on the fly - which is critically what I want to do to hear how they compare - I need to set output to LPCM in the player and attempt that, and didn't have time.
The main thing that is missing from the update is the ability to allow the user to select their choice of upmixer, irrespective of layout.
Originally Posted by deyre
1. You can't "switch to DTS:X". You can select the Neural:X upmixer. However, if your disc is Atmos, then it is rendered to the available speakers and there is nothing to upmix , so Neural:X is inactive.
3: If you are playing a DTS:X disc, then again, it is rendered to the available speakers so there is nothing to upmix, so Neural:X is not active.
4. Yes. A DSP code limitation. It may or may not be coincidental that Neural:X upmix of 2-chan AC3 is tested for DTS:X certification.
5. You need an Auto mode. (DSU or Noodle:X as appropriate)
To echo Stephen's sentiments, many thanks for taking the time to post - I know we can be an ugly and unforgiving crowd sometimes, but we'd love to see you more in this thread.
So, the big question then, is can you shed any light on the inability to cross mix between DTS and Dolby - and when this is likely to be fixed. Most mainstream AVR's, although they started out with this issue, appear to have now been fixed by firmware to allow Neural:X or DSU to be user selected to upmix either DTS MA or Dolby True HD streams.
Industry insiders such as Sanjay have already confirmed in this thread that it is not a restriction imposed by either Dolby or DTS, so we can only assume its a bug in the code or an issue with implementation?
Therefore could you confirm that a) you have it scheduled as an issue that needs to be addressed, and b) what sort of timescale we might be looking at for it to be fixed?