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

Would like Cue in / Cue out markers that are honured by Autodj #5651

Closed
mixxxbot opened this issue Aug 22, 2022 · 12 comments
Closed

Would like Cue in / Cue out markers that are honured by Autodj #5651

mixxxbot opened this issue Aug 22, 2022 · 12 comments

Comments

@mixxxbot
Copy link
Collaborator

Reported by: theresajayne
Date: 2010-11-10T13:44:28Z
Status: Fix Released
Importance: Wishlist
Launchpad Issue: lp673515
Tags: autodj, cue


The ability to set cue in and cue out points that AutoDJ uses for the crossfade option to allow the DJ to strip unwanted silence or music from tracks

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2010-11-12T15:36:31Z


Good one. Support for in and out cues is already in the data model for cues, the feature that uses it just isn't written yet.

@mixxxbot
Copy link
Collaborator Author

Commented by: smstewart91
Date: 2012-06-01T22:50:23Z


Where would be the best place to fade based on the cue points? For example, should the fade start before the cue out, and complete right on the cue out, or start fading on the cue out? Same for cue in, should the fade start or finish at the cue in marker? Because it seems that a reasonable argument could be made for each configuration.

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2012-06-02T12:11:26Z


Mixxx has currently 5 hot cues.
(Hot-)Cue 0, controlled by the Cue and play button near the play button. This is the place where the deck seeks to if the track was just loaded. Then there are 4 additional Hotcues to mark special position within the song, to use them like a drum kit or a in deck sampler.

I terms of a Auto DJ Cue 0 is the "start to fade in" point.
For me, it is most natural to have an additional position where the Auto DJ starts to fade (the user presses "fade now") marked as "start to fade out point"

@mixxxbot
Copy link
Collaborator Author

Commented by: wagnerflo
Date: 2013-08-05T16:01:07Z


I also would really like to see song/fade start and end cues implemented!

In addition I'd like to have an option for silence between songs. Currently this is half-possible when setting a negative fade-duration. But only because in that case AutoDJ decides to ignore the hot-cue completely and plays the deck from a point N seconds before the start of the track.

Something like this would be my wish: Play track starting from cue-in; stop playback at cue-out; wait for N seconds; start playback of next track at cue-in.

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2013-08-05T18:07:09Z


Thank you for your comments.
I am currently working on migration of Scott's advanced Auto Dj branch. Once this is finished, we can implement your idea.

@mixxxbot
Copy link
Collaborator Author

Commented by: searcher68
Date: 2013-12-19T20:43:50Z


Status = Wishlist, BUT, honestly I can't believe that a DJ tool this robust does not already include end points.

Imagine a track that happens to have 20 sec. of dead air at the end. Or, perhaps I'd like to fade out on a breakdown, etc., instead of only at the end of the song. Really, this functionality is key to Auto DJ usefulness.

As to functionality, I agree with you daschuer. The end point should be Start to fade out point, just as the existing Cue is the Start to fade in point. Knowing what you've got your fade-time set to and having the end-point set, you are then good to go!

I would LOVE to help beta test the advanced Auto DJ branch. plmk...
<email address hidden>

My performance style is to have an Auto DJ type of function playing through my playlist for most of my sets, but then override it with manual mixing most of the time. That way I can pay attention to patrons' requests or whatever else comes up to disturb me while mixing without dropping the beat.

Thanks!!!  ;)

P.S. - Awesome piece of software overall. I'm very impressed and am looking to roll out this new tool in my live shows sometime in the next couple of weeks.

@mixxxbot
Copy link
Collaborator Author

Commented by: naught101
Date: 2015-11-18T05:37:27Z


FWIW: an "end fade out" cue point per track would be more useful than a "start fade out" cuepoint: for example, if you have your fades set to 6s, and set a "start fade out" cuepoint at 6s before the track ends, and then later you change your fades to 12s, then you're going to get silence half way through your fade. If the fade startpoint is calculated as "end fade out" cuepoint minus fade time, then it's going to always work, regardless of the fade time.

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2017-04-25T03:23:18Z


#1242

@mixxxbot
Copy link
Collaborator Author

Commented by: stevetheshark
Date: 2018-01-18T19:46:31Z


This would be a great feature to add!

@mixxxbot
Copy link
Collaborator Author

Commented by: nicholas-chammas
Date: 2019-02-04T05:50:53Z


I'm interested in this feature too, but not necessarily for Auto DJ. I just want to be able to set an end cue point that gets saved to Mixxx's database and which causes Mixxx to simply stop playing the current song at the configured end cue point, rather than at the end of the song.

@mixxxbot
Copy link
Collaborator Author

Commented by: tezzy
Date: 2019-03-11T08:35:17Z


I agree with Nicholas in post #⁠10. It would keep things simple.

Mixxx should use a configured end cue point in exactly the same way the start cue point is used.

Can keyboard shortcuts be added for end cue points?

@mixxxbot
Copy link
Collaborator Author

Issue closed with status Fix Released.

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
@mixxxbot mixxxbot added this to the 2.3.0 milestone 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