Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

loop & cue sets #5768

Open
mixxxbot opened this issue Aug 22, 2022 · 11 comments
Open

loop & cue sets #5768

mixxxbot opened this issue Aug 22, 2022 · 11 comments

Comments

@mixxxbot
Copy link
Collaborator

Reported by: deathdevil66
Date: 2011-02-12T18:57:53Z
Status: Confirmed
Importance: Wishlist
Launchpad Issue: lp717841
Tags: cue, looping, sampler


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.

@mixxxbot
Copy link
Collaborator Author

Commented by: esbrandt
Date: 2011-02-12T21:48:37Z


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

@mixxxbot
Copy link
Collaborator Author

Commented by: deathdevil66
Date: 2011-02-24T04:20:57Z


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

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2011-02-24T04:40:51Z


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

@mixxxbot
Copy link
Collaborator Author

Commented by: deathdevil66
Date: 2011-02-24T13:18:53Z


Will do, sir. Thanks

@mixxxbot
Copy link
Collaborator Author

Commented by: deathdevil66
Date: 2011-02-28T02:14:18Z


see if this pleases you:

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

@mixxxbot
Copy link
Collaborator Author

Commented by: pwhelan
Date: 2011-05-12T10:20:56Z


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

@mixxxbot
Copy link
Collaborator Author

Commented by: esbrandt
Date: 2011-08-19T13:39:38Z


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.

@mixxxbot
Copy link
Collaborator Author

Commented by: ferranpujolcamins
Date: 2014-09-09T08:44:13Z


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

@mixxxbot
Copy link
Collaborator Author

Commented by: Be-ing
Date: 2015-07-20T15:54:00Z


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

@mixxxbot
Copy link
Collaborator Author

Commented by: Be-ing
Date: 2017-11-11T14:35:22Z


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

@mixxxbot
Copy link
Collaborator Author

Commented by: stevetheshark
Date: 2018-01-18T19:44:35Z


Would be fantastic to get this feature working!

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant