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

From: Joel Roth <joelz@email-addr-hidden>
Date: Wed Apr 03 2013 - 12:40:00 EEST

Good of you to take the time to characterize
this. Let's see if Kai has some ideas.

rocco wrote:
> OK, so I feel I've tried every possibility that I can think of and every
> suggestion Joel has offered.
> I would like to make an assessment based on several days of working with
> this.
> When you have all objects of the same name, then regardless of what
> a(oi)-index-select that is issued, it simply ignores that request and
> chooses the object that was last created.
> I tested this by creating a new chain and attaching an input object to
> it. Then I chose the index of a different input object. It ignored the
> request and removed the last input object that was created.
> Remember, the (above) scenarios exists when all the objects have the
> same name. But when there's (either) all unique names (or) a mixture of
> same object names and unique object names, then it behaves in less
> predictable ways, sometimes removing the last created object and
> sometimes actually rearranging the chains and objects in strange ways.
> Thanks,
> Rocco

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
Ecasound-list mailing list
Received on Wed Apr 3 12:15:04 2013

This archive was generated by hypermail 2.1.8 : Wed Apr 03 2013 - 12:15:04 EEST