edited Wire patch now has all parameters set to their defaults
Posted: Tue Feb 03, 2026 06:38
I had a wire effect patch that I used in many clips in my composition. I saved the patch with a new name, and added a parameter. After I tried it in Arena I liked it, so in Wire I opened the new patch, copied the entire network, then opened the original effect, deleted all the nodes, and pasted the updated network.
Then in my composition, every instance of the effect had its parameters set to their defaults. My composition was ruined. Major freak out.
I tried a few things like opening a saved copy of the original patch and saving it to its original name, or copying its node network and pasting it into the original patch. No joy.
Then, I opened the Arena composition .avc file in a text editor and noted that every instance of my effect had the same UUID value for "uniqueTypeId". In the Wire patch there is an element with a UUID value called "identifier". I replaced the value in the patch with the UUID from the Arena composition.
Now, when I load my composition, all instances of my effect are restored to their saved values. Whew!
So, having Wire change the identifier of the patch after deleting and replacing all its nodes was unexpected and seems to be a BUG. Is this a known problem?
Hit "like" if you agree (I don't think that's a thing though)
Then in my composition, every instance of the effect had its parameters set to their defaults. My composition was ruined. Major freak out.
I tried a few things like opening a saved copy of the original patch and saving it to its original name, or copying its node network and pasting it into the original patch. No joy.
Then, I opened the Arena composition .avc file in a text editor and noted that every instance of my effect had the same UUID value for "uniqueTypeId". In the Wire patch there is an element with a UUID value called "identifier". I replaced the value in the patch with the UUID from the Arena composition.
Now, when I load my composition, all instances of my effect are restored to their saved values. Whew!
So, having Wire change the identifier of the patch after deleting and replacing all its nodes was unexpected and seems to be a BUG. Is this a known problem?
Hit "like" if you agree (I don't think that's a thing though)