loop & cue sets

[dead_devil_66]

Imagine that, for one song, you have several possible edits and mashups, with other tracks. So, in order to know which stored cue and loop belongs to which mashup or edit, it would be EXTREMELY valuable, to have a way to create cue and loop sets, each one with a name or/and other kind of identifier. This way, i wouldnt be mind when deciding which cue or loop belongs to an edit/mashup...

For example, consider the xml tree of the nml file of traktor library. Now, just group the cue's and loop's:

<group name="">
   <comment>...</comment>
   <cue>...</cue>
   <cue>...</cue>
   <loop>...</loop>
</group>

Another thing: custom cue & loop colors and icons.

Thanks.

[jus (jus)]

FYI the Colors and icons for (Hot)cues & Loop points/overlays in the main waveform are customisable.
See the skin.xml file for the "Deere" skin as example.
http://mixxx.org/wiki/doku.php/creating_skins#waveform

[dead_devil_66 (deathdevil66)]

but can i choose, during runtime, what overlay i want?

[RJ Skerry-Ryan (rryan)]

dead_devil_66 ,

I like your idea, and I think it is very forward thinking. I definitely think your use-case will fall under 'advanced' here. My big question is that Mixxx has, in general, two audiences:

a) beginner DJs who need a fair amount of hand-holding and instruction

and

b) advanced DJs who are tinkerers, programmers, and in general DIY'ers

Part of the difficulty is to walk the line and satisfy both crowds. Would you be willing to throw together some mockups that you think would work well for your use case so that we can understand it better? I like using Balsamiq (balsamiq.com) for mockups, I think they offer a free trial. I'm just trying to understand your proposal as best as I can so I can take it into account. I think there's definitely a solution that can serve a dual purpose, the trick will be to create the right UI for it.

Thanks,
RJ

[dead_devil_66 (deathdevil66)]

Will do, sir. Thanks

[dead_devil_66 (deathdevil66)]

see if this pleases you:

http://i53.tinypic.com/s2r98g.png

[Phillip Whelan (pwhelan)]

This looks like something that might become doable soon with the new skin features in 1.10.

[jus (jus)]

I start to like the idea of cue/loop sets.
But i can not see how the the new skinning features in 1.10 alone could make this feature request gonna happen without further work on the cue/loop codebase.

[Ferran Pujol (ferranpujol)]

First stored loops as cue points should be implemented. I filed a bug: https://bugs.launchpad.net/mixxx/+bug/1367159

[Be (be.ing)]

I'm not sure XML is the best solution for this. Why not store them sets directly in the SQLite database and allow importing and exporting databases? See https://blueprints.launchpad.net/mixxx/+spec/portable-library

[Be (be.ing)]

There has been no progress on this lately, so I am removing the 2.1.0 milestone.

[Steve (stevetheshark)]

Would be fantastic to get this feature working!

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/5768