More > JRiver Media Center 23 for Windows
JRiver outputting 2.0 channel stereo as if it were 5.1 multichannel
wer:
--- Quote ---I have the current Denon/Marantz ...
--- End quote ---
I know about Marantz/Denon processors. That's why I'm currently using the Yamaha CX-A5000. :)
--- Quote from: MazingerZ on September 20, 2020, 08:49:55 am ---In my 6 zone example, it would obviously be impossible to set up a rule to let the JRiver decide which audio device to use ( the receiver or the USB DAC ) -- only I can decide that (manually).
--- End quote ---
Correct, because you duplicated your rule for 4.0/5.0 non-classical. You are specifically sending it to zone 4, but you are saying it should go to zone 6 because zone 6 = "Non-Classical, regardless of number of channels".
This makes it impossible for the computer to "decide" between zone 4 and 6, except by precedence: first match controls (as I said before). However, this sort of conflict in definition is not really the problem it might at first appear to be, because...
--- Quote ---I don't mind selecting the audio device manually.
--- End quote ---
Good, because many people use ZoneSwitch in this way to automatically route traffic through different configurations of a manually selected device. In other words, the user selects the output device manually, and the computer selects which configuration (zone) of that device should be used based on rules. This matches your use case.
This functionality works because when you configure ZoneSwitch, it implicitly creates associations between different zones when those zones are mentioned in corresponding ZoneSwitch rules, using the "Play in this zone" and "Stop Playback in these zones" settings.
Here's a simple English-language example of ZoneSwitch rules to help you understand:
Rule 1: Play Classical in Zone "Unprocessed Sound". Stop Playback in Zone "Processed Sound".
Rule 2: Play Non-Classical in Zone "Processed Sound". Stop Playback in Zone "Unprocessed Sound"
These rules create an association between the "Unprocessed Sound" and "Processed Sound" zones, because both rules mention both zones in a mutually-exclusive way. Rule 1 and Rule 2 are a "Rule Set" because they talk about all zones in the association, and only zones in the association.
Now imagine a second set of rules:
Rule 3: Play Classical in Zone "Dac1". Stop Playback in Zone "Dac2".
Rule 4: Play Non-Classical in Zone "Dac2". Stop Playback in Zone "Dac1"
In this second rule-set, an association is created between the Dac1 and Dac2 zones. Now you have two rule-sets.
Zones from Rule-set 1 are not mentioned in Rule-set 2, nor vice versa. This is what keeps them as separate Rule Sets. Note: there is no place in the interface where you explicitly "name" rule-sets. It's implicit, not explicit. To help keep it straight, you should add a common rule-set name to the start of your "Display Name" for each rule you create.
The trick is "How do you know which rule-set is active? If it's simply precedence, Rule-Set 2 would NEVER engage."
The answer is: When you have multiple rule-sets, created through segregated mutually exclusive associations, the controlling rule-set is derived from the zone that is active when playback begins.
Thus, if you manually select the Dac2 zone, and then start playback, only rules from the rule-set that contains the Dac2 zone will be enforced. During playback, MC will freely switch between zones mentioned in that rule-set, as the rules dictate. Stop playback, and at that point, either Dac1 or Dac2 will be active. Restart Playback, and that rule-set will still be controlling.
But stop playback, manually select the "Processed Sound" zone, and then start playback, and what happens? The "Processed Sound" zone is in Rule-Set 1. So now Rule-Set 1 will be the set of rules that is enforced.
This is the way ZoneSwitch works.
Also, as I mentioned previously, the sort of thing you want can also be achieved by combining ZoneSwitch with automatic DSP Presets. I personally don't like the way auto DSP Presets are implemented, but you might like it because it would let you reduce the number of Zones you create (in your scenario, 2 zones would be required for each physical output device).
The information I've given you should be enough for you to figure the rest of the way for yourself. Good luck...
Hopefully a mod or the OP will modify the title of this thread to include "ZoneSwitch" since that will be helpful to others who are searching for a better understanding on this topic.
MazingerZ:
Wow, thanks for the info.
I don't think I saw this kind of info in the wiki or ZoneSwitch threads.
wer:
Glad to help.
The feature is very powerful, but is poorly documented, and it works in a non-intuitive way, so I'm not surprised you didn't find enough to help you. There is some helpful info out there, but it would require a more thorough search of the forums for threads like this one. The Wiki doesn't have much.
One other thing to keep in mind: If you create a rule that does not specify any zones to stop, it will not be part of any rule-set (because it is not making any mutually exclusive association). Any rule that is not part of a rule set will ALWAYS be evaluated. I don't think that's documented. Precedence controls for all rules that are evaluated. So unless you really know what you're doing, it's important to ensure that all of your rule-sets are tightly defined, or you may achieve results that greatly confuse you. So be careful, grasshopper. :)
petranta:
I think this HDMI limitation which has been addressed here can't be completely true. When I play the same multichannel (5 channels) album from my MC 23.0.104 through DLNA I get 2 channels in my AVR over HDMI 1.4 but when I play exactly the same album from USB memory stick connected to my DLNA player Sony ubp-x800m2 I get 5 channels to my Yamaha AVR over the same HDMI connection ? But again when I play 5.1 album from MC DLNA I get it correctly to my Yamaha over HDMI. MC DLNA server setting are 24bit PCM and 192kHz and "source number of channels" in DSP settings.
Navigation
[0] Message Index
[*] Previous page
Go to full version