-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Comments
Commented by: rryan 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. |
Commented by: smstewart91 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. |
Commented by: daschuer Mixxx has currently 5 hot cues. I terms of a Auto DJ Cue 0 is the "start to fade in" point. |
Commented by: wagnerflo 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.
|
Commented by: daschuer Thank you for your comments. |
Commented by: searcher68 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!
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.
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. |
Commented by: naught101 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. |
Commented by: stevetheshark This would be a great feature to add! |
Commented by: nicholas-chammas 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. |
Commented by: tezzy 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? |
Issue closed with status Fix Released. |
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
The text was updated successfully, but these errors were encountered: