Quote:
Originally Posted by randycw 
The Delta Audio card has 8 RCA outputs. So source 1 uses 1,2 outputs Source 2 uses 3,4 and so on. I moved working source 1s outputs (audio card 1,2 outputs) to another CAV input (in the case mentioned in the post that was Zone 2). So moving the audio cards 1,2 outputs around the other zones demonstrated that the CAV amplification was working properly.

The Delta Audio card has 8 RCA outputs. So source 1 uses 1,2 outputs Source 2 uses 3,4 and so on. I moved working source 1s outputs (audio card 1,2 outputs) to another CAV input (in the case mentioned in the post that was Zone 2). So moving the audio cards 1,2 outputs around the other zones demonstrated that the CAV amplification was working properly.
See, this is where I can't quite tell what it is you did. From what I read you took to outputs from 1&2 and put them into a different CAV port. Fine, but then you assumed the CAV amplification was working based on that? How so? Moving to a new set of CAV input ports (a russound 'source') you only confirmed that the audio coming from 1&2 was working, not that the previous source within the CAV was working. Get why it's confusing?
I asked about USB because of device port rippling effects. Some USB devices are notorious for disrupting the 'ordering' windows uses to set up audio devices. I'm wondering if something added (or removed) might have disrupted that 'behind the scenes' stuff used by Windows.
And you say it's all working now? By deleting and then recreating "the same" configurations? Yeah, that sort of thing definitely makes me wonder about how Windows, and then MC, were handling the devices behind the scenes.
I've found it to be hit-and-miss to fiddle with any device ordering in Windows and MC. Or to expect any driver or updates to not disrupt them. As in, a new driver for the motherboard audio (even though it might not even be used in MC) might cause enough of a disruption of ports to let MC get confused about them.










