interceptintercept
Hello! Currently, swap_decks, move_deck, clone_deck, and clone_from_deck reset stems, but I think it would make sense if the current stem state carried over. For example, if I have a song on deck 1 with only acapella and I move it to another deck, I would expect it to remain acapella.
Thank you!
Thank you!
Mensajes Mon 04 Nov 24 @ 4:04 am
locoDog
I could argue against for swap, I like having the difference, I could have eq & fx one way on one deck then one button can switch to a different set of eq & fx that have been set up with no lead preparation. Then cut between the 2.
Clone with stems I can go along with... sort of, I think both clone as is and a new 'duplicate_everything' both have merit.
Move was made for a particular bit of hardware that I don't have, so I'm not really versed on why it is like it is, but definitionally move feels like it should be a indistinguishable change [so 100% the same, fx stems, etc]
Clone with stems I can go along with... sort of, I think both clone as is and a new 'duplicate_everything' both have merit.
Move was made for a particular bit of hardware that I don't have, so I'm not really versed on why it is like it is, but definitionally move feels like it should be a indistinguishable change [so 100% the same, fx stems, etc]
Mensajes Mon 04 Nov 24 @ 5:01 am
DJ VinylTouch
So I think this has been brought up a few times already (I discovered this was an issue when using deck move on the S11) but they have already chosen to keep this current behavior it seems (and choosing None for resetStemsOnLoad doesn't have any effect). It would be nice if that behavior could at least be reflected in the selection of None for the resetStemsOnLoad functionality, since clone from deck is a type of load to a new deck.
Mensajes Thu 07 Nov 24 @ 12:05 pm
interceptintercept
I'm actually using an S11 now, which is how I noticed!
Mensajes Fri 08 Nov 24 @ 1:14 am