Re: ai-index-select, ai-remove and ao-index-select, ao-remove not working properly

rocco wrote:
> Quick assessment of the situation, then my complete session...
> 
> It seems that when there are multiple input objects of the same name or 
> multiple output objects of the same name, 'ai-index-select', 'ai-remove' 
> and 'ao-index-select', 'ao-remove' removes the wrong object.
> 
> It does (not) seem to have this confusion when the input objects have 
> different names or the output objects have different names.
> 
> Also, it seems (possibly) that in certain situations, it seems to think 
> it removed the object from a different chain instead of the chain that 
> it actually removed it from.

Hi Rocco,

One part of your problem is that you should
disconnect your chain setup before modifying
the inputs/outputs.

By just removing the one input, you have an invalid chain
setup. That causes weird complaints when Ecasound tries to
reconnect it, (I seem to recall Ecasound performs poorly at
providing meaningful information from a broken setup.)

So I would try this:

cs-disconnect
(modify chains)
cs-is-valid # should return 1
cs-connect

Hope this helps.

Joel


-- 
Joel Roth

------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
Ecasound-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ecasound-list