Cantabile sends audio to wrong output if another instance is running

[bburtin]

I have an Echo Indigo audio card that has 8 virtual audio outs. I have two instances of Cantabile. The first one uses audio out 1 & 2. The second one uses 3 & 4. I set up the two instances separately. When I then loaded instance 1 followed by instance 2, instance 2 started sending audio to outputs 5 & 6 instead of 3 & 4. I looked in the driver list and saw that audio outs 1 & 2 are no longer displayed, probably because they're now in use by the first instance of Cantabile.

I think I can work around this by making sure that I always load both instances, in the same order, but it would be great to get this bug fixed so I wouldn't have to.

Thanks,

Boris

[bradr]

Hi Boris,

Any chance this could be an audio driver issue? Perhaps the audio driver reports different settings when another instance is in use. Does this happen with other hosts, or just Cantabile?

Brad

[bburtin]

That's probably the case, since the second instance of Cantabile isn't listing outputs 1 & 2. Let me test some other audio apps and see how they behave. Would it make more sense for you to reference outputs by name instead of by index?

[TiUser]

Maybe what you describe is similar to when I change the used audio ports in Asio4All which gave me odd effects in cantabile too... It's true that one does not do this very often, but when it's very confusing.

Saving an index is usually no good idea for lists with content that can change for external reasons... so I also vote for a different way of saving the audio port assignment setup.