Hi Drew769,
Thanks for the post. It is hard to tell, where the issue with downmix might be. Could you please share more details how the VanityPRO is configured and what firmware version it is running? Also, can you confirm the player is configured to output full 5.1 or 7.1 channels and you get correct number of channels shown in the home screen on the VanityPRO? I have just checked the mixing ratios with the latest firmware and it all seems to be fine as per description in the user manual. I would also suggest to use some channel ID test tracks to help you identify if you are getting the correct mix and how the downmix output sounds. You can find some multichannel ID files here: [url=https://www2.iis.fraunhofer.de/AAC/multichannel.html]https://www2.iis.fraunhofer.de/AAC/multichannel.html[/url]
Please try and let us know.
Regards,
Pavel
VanityPRO FAQ
Re: VanityPRO FAQ
Pavel,
I have some blu ray audio discs that have two channel DTS-MA layers. When I selected the bitstream output from my Oppo I got no sound. If I used the Oppo to output LPCM I did. Since the VP couldn't decode DTS-MA it all made sense.
I just updated my VP to the latest FW and, just for fun, I sent a DTS-MA signal via bitstream to my VP. Now I'm getting a 24/192 or 24/96 signal, depending on the source, and it plays fine.
I'm happy, but perplexed!
I have some blu ray audio discs that have two channel DTS-MA layers. When I selected the bitstream output from my Oppo I got no sound. If I used the Oppo to output LPCM I did. Since the VP couldn't decode DTS-MA it all made sense.
I just updated my VP to the latest FW and, just for fun, I sent a DTS-MA signal via bitstream to my VP. Now I'm getting a 24/192 or 24/96 signal, depending on the source, and it plays fine.
I'm happy, but perplexed!
Re: VanityPRO FAQ
Hi egradyh,
Thanks for your observation! This is actually a correct behavior, because in the latest firmware there are more options to configure the local EDID capabilities. By default, the bitstream capability on the Vanity[sup]PRO[/sup] side is switched off, only PCM and DSD is supported. This is why the player sends PCM regardless of the setting. There are scenarios where you might want to pass a bitstream through so you can enable bitstream support in the menu of the Vanity[sup]PRO[/sup].
Regards,
Pavel
Thanks for your observation! This is actually a correct behavior, because in the latest firmware there are more options to configure the local EDID capabilities. By default, the bitstream capability on the Vanity[sup]PRO[/sup] side is switched off, only PCM and DSD is supported. This is why the player sends PCM regardless of the setting. There are scenarios where you might want to pass a bitstream through so you can enable bitstream support in the menu of the Vanity[sup]PRO[/sup].
Regards,
Pavel
Re: VanityPRO FAQ
Pavel,
I'm a bit perplexed by your answer. Are you saying the VP is now telling the player to transmit LPCM even though the player is set to output bitstream?
egradyh
I'm a bit perplexed by your answer. Are you saying the VP is now telling the player to transmit LPCM even though the player is set to output bitstream?
egradyh
Re: VanityPRO FAQ
Correct! It is not the source, it is the sink what dictates what the capabilities are and what the source should send down the line. It is a standard handshaking mechanism to ensure the user will always get sound, in other words the source will send the format which the sink can handle.
If you set your player to bit stream, it means the player will send bitstream only if the sink supports it. There is no point sending what the sink cannot handle/decode.
In the early versions, the VanityPRO had all capabilities enabled by default, including all compressed formats. The idea was that the user would control the capabilities on the source side, but it turned out not to be very practical. Now the user can control the capabilities on the VanityPRO independently, which should result in better compatibility.
Hope it is more clear now.
Regards,
Pavel
If you set your player to bit stream, it means the player will send bitstream only if the sink supports it. There is no point sending what the sink cannot handle/decode.
In the early versions, the VanityPRO had all capabilities enabled by default, including all compressed formats. The idea was that the user would control the capabilities on the source side, but it turned out not to be very practical. Now the user can control the capabilities on the VanityPRO independently, which should result in better compatibility.
Hope it is more clear now.
Regards,
Pavel
Re: VanityPRO FAQ
Hello,
Does the Dop v1.1 (on XLR output) of the vanity have the 0x05/0xFA and 0x06/0xF9 markers?
Thank you.
Does the Dop v1.1 (on XLR output) of the vanity have the 0x05/0xFA and 0x06/0xF9 markers?
Thank you.
Re: VanityPRO FAQ
Hello Fred-ql,
The DoP markers used in the VanityPRO are 0x05/0xFA. Could you please point me where the other set of markers is mentioned?
Thanks.
Pavel
The DoP markers used in the VanityPRO are 0x05/0xFA. Could you please point me where the other set of markers is mentioned?
Thanks.
Pavel
Re: VanityPRO FAQ
Hello
It is the designer of HQplayer who provides the values '0x05/0xFA and 0x06/0xF9'
https://signalyst.com/consumer/
It is the designer of HQplayer who provides the values '0x05/0xFA and 0x06/0xF9'
https://signalyst.com/consumer/