Mixxx

loop & cue sets

Bug #717841 reported by dead_devil_66
22
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Mixxx
Confirmed
Wishlist
Unassigned

Bug Description

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.

See original description
Revision history for this message
jus (jus) wrote :

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

Revision history for this message
dead_devil_66 (deathdevil66) wrote :

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

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

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

Changed in mixxx:
status: New → Confirmed
importance: Undecided → Wishlist
Revision history for this message
dead_devil_66 (deathdevil66) wrote :

Will do, sir. Thanks

Revision history for this message
dead_devil_66 (deathdevil66) wrote :

see if this pleases you:

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

Revision history for this message
Phillip Whelan (pwhelan) wrote :

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

Changed in mixxx:
milestone: none → 1.10.0
Revision history for this message
jus (jus) wrote :

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.

Changed in mixxx:
milestone: 1.10.0 → none
Debra Virden (teddydlv)
description: updated
Phillip Whelan (pwhelan)
description: updated
Daniel Schürmann (daschuer)
tags: added: looping
removed: loop
Daniel Schürmann (daschuer)
tags: added: sampler
Revision history for this message
Ferran Pujol (ferranpujol) wrote :

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

Owen Williams (ywwg)
Changed in mixxx:
milestone: none → 1.13.0
Revision history for this message
Be (be.ing) wrote :

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

Revision history for this message
Be (be.ing) wrote :

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

Changed in mixxx:
milestone: 2.1.0 → none
Revision history for this message
Steve (stevetheshark) wrote :

Would be fantastic to get this feature working!

Daniel Schürmann (daschuer)
tags: removed: feature sets
Revision history for this message
Swiftb0y (swiftb0y) wrote :

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

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.