Comment 6 for bug 1438746

I've thought about some kind of remix decks counterpart several times last year. Remix decks are nothing more than 4 mini decks (with its individual filter and volume controls) that are routed to the same standard mixer channel. We support n-decks each with its full mixer channel, so we have actually already overcome that. Even if we provide a GUI with 32 decks with few controls for space reasons, users could still map their controllers to use the full mixer controls for each Mixxx deck.

The other two main features of remix decks are:
1) The 4 mini-decks are hold together under a "meta deck". Tracks or samples can individually be loaded to each mini deck. But besides that, a special library entity that is nothing more than a group of tracks can be loaded to the "meta deck". That automatically loads the corresponding sample to each mini deck.

2) Each mini deck is an ableton-like collection of slots, instead of a single deck. There can be up to 16 samples loaded to the same mini-deck that can be alternatively triggered.

Possible solutions:
1) Support for NI Stems or other multi channel file format seems like the way to go to store related tracks together in the library easily. However, we are missing this "meta deck", or the way to group 4 decks together so they can be loaded with related content at once.

2) We don't really need this ableton-like slots if we have a solid work-flow of cue-points with this multi channel files.

Additional "secondary" remix decks features:
The 4 mini decks in a remix deck are always in sync. Also, if the meta deck is scratched, all its mini decks are scratched accordingly. The same happens with transport and looping controls.