Resolume Forum

When I add a deck from another composition and there is already a deck with the same name in the current composition, then it replaces the deck of the current composition. Is this a bug or a feature? I don't like this.

This is normal. Don't use duplicate names

Although for a feature request, it might be nice to add a sequential naming scheme to prevent this in the future, so when copying Red to a comp that already has a Red deck, it would then show up as Red1, etc...

Agreed, I would prefer such a behaviour, too.

You might pop over to the request part of the forum and add a request

After some testing I would insist that this is a bug:
I renamed the deck that I want to insert from '11.Greedtrap' to 'Cover'.
When I insert this deck (doubleclick in the compositions tab), it still replaces the original '11. Greedtrap' deck!
Apparently the deck still "remembers" that it is a copy (save composition as...) and wants to replace the original deck. Please Resolume, stop that nonsense.

Actually, it's the same deck you try to load if it replaces a deck in your current composition.
Probably saved a copy of this composition, or it's an old version.

Every deck gets a unique id set on creation, this uid identifies a deck.
When you save a composition under a new name, the deck is saved with the same uid. So if you load a deck which is has the same uid, Resolume replaces the one you already have loaded.

We have ticket for this.
What you can do would be creating a new deck and copying the content of one of the decks to this new one. Then you can load the old deck, keeping your clips.

Ah, I could have thought of that... just copying the clips to another deck. Thanks for the hint!
And looking forward to that being solved with the ticket.