features: implement some deckadance features

Bug #897968 reported by Ilkka Tuohela
This bug report is a duplicate of:  Bug #703585: feature request: "slip mode". Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Invalid
Wishlist
Unassigned

Bug Description

Deckadance has a couple of useful features which you might want to consider adding to mixxx.

- start mark: this is like a normal hotcue, except when set, the song is loaded in future from the point given, and you can't go beyond this point in beginning of track (seek 0.0 point). When set, you never need to seek empty space from track start again, or look for the 'here starts the beat after 40 seconds of useless noise' point. You could always set a hotcue, this would be like fifth specialized hotcue with the 'load this with track' exception.

- leap: this is a variation of beatgrid loops, where the software keeps track of underlying audio: when you release the leap, the song continues from where it would have been if loop did not occur. Very useful if you want to for example repeat something three times and easily go back to beat without losing sync

Maybe some others, but these were my main thoughts when testing mixxx :)

Also, it would be nice to be able to store the time signature of song (4/4 by default) and show a 'bar start' marker in waveform matching this. Not really critical though.

Revision history for this message
Sean M. Pappalardo (pegasus-renegadetech) wrote :

Please file these as separate bugs. Bug #703585 covers the "leap" function you mention, so please vote for that.

Changed in mixxx:
importance: Undecided → Wishlist
Revision history for this message
Sean M. Pappalardo (pegasus-renegadetech) wrote :

Also, the main CUE point should behave like you describe (where Mixxx loads the song at that point) but we do allow seeking before it for various reasons (scratch cue-ing for one)

Revision history for this message
Ilkka Tuohela (hile) wrote :

OK I'm happy with main cue behavior (sorry did not notice it) and since the other issue here is dup, invalidating the bug.

Changed in mixxx:
status: New → Invalid
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Sean isn't trying to discourage you, Ilkka :) We'll just sort your bugs into the right categories and de-dupe them and it makes it easier on us if you file 1 bug for 1 feature request instead of describing multiple things in 1 report. Please keep them coming! It's very useful to have your feedback.

Revision history for this message
Ilkka Tuohela (hile) wrote :

Hah yeah. I was really just happy with his answers and filled my part of making sure there are no hanging bugs which are not really relevant after all.

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/6152

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.

Other bug subscribers

Remote bug watches

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