by PastorTheDoctor » Fri Jul 14, 2017 2:30 pm
UPDATE:
I think I found out what the bug is!
In the VST case, patches changed with no particular reason.
In the AU case, as I told you before, I had many tracks receiving the MIDI messages from the same audio channel. During the live set, my tracks receive some control from ClyphX’s clips, as I told you before.
The Legend’s tracks with the same name and the same channel, after a while of practicing my live set, and so changing parameters here and there in Ableton Live, resulted to have completely changed.
Is the fact that they had the same name a coincidence? Maybe, but they also were assigned at the same channel. So, I assume it is an issue related to MIDI Input messagging (and to MIDI Input Channel).
And when they change name, they usually go at the first preset in the same Legend’s bank, which is a User Bank I created for this live gigs.
In the end, it also happens that when I change patch in a Legend instance which receives input from MIDI ch. 5 (for example), all the other Legend instances in the project receiving from MIDI ch. 5 will randomly change their patches.
n this case, the patch doesn’t always turn to the first in the bank list, but it still turns to a patch contained in the same User Bank I talked about above.
The two elements to consider, in my opinion, are:
MIDI input
The Legend’s internal [user?] banks
EDIT: though I changed all the MIDI channels to all The Legend tracks of the project, it still keeps changing.
So, I think that finally this is a Legend's issue.
I think I'll temporarily solve the problem by creating a single user bank with a single user patch inside each bank, for each Legend instance.
I'll tell you if it works.
EDIT 2: nothing, though I have created a bank for every single patch, now my Legend instances even shift between the global bunch of patches (not only in the bank the correct patch resides). So, it's just a Legend's issue: when there are multiple instances of The Legend open, it happens that they shift the patches.
I'll try with another AU to see if the problem persists.