-
-
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
Add Fader Start feature that allows to start a track from its last cue-point by moving the corresponding line-fader up or the crossfader to the side of the deck #5587
Comments
Commented by: pwhelan This sound to me like another feature that is very specific to a certain A much better idea would be to design a way for scripts to do program wide To make it even easier on people, on Window and Mac OS X we could make part |
Commented by: marczis Hello, "Add Fader Start feature that allows to start a track from its last cue-point by moving the corresponding line-fader up or the crossfader to the side of the deck" I think that it should start from the actual position not from the last cue-point. What do you think ? |
Commented by: daschuer Yes, a start from the current position is what the user might expect. How will you issue N-Decks? Just stopping a deck by Crossfader sound weird, for a manual mixing use case. It might make sense in combination with https://bugs.launchpad.net/mixxx/+bug/1187258 What are the use cases we have? |
Commented by: marczis I'm okay with re-cue the track you leave with the cross-fader. Both thing will open up some new ways of mixxxing for me :) |
Commented by: DJChloe This is not a good Idea. Some controllers like the Reloop Beatpad have the Fader Start logic implemented : opening the level fader of the controller, sends a play button event to the software when you activate the faderstart with SHIFT+Load button. More over, it's not so difficult to emulate it in javascript. |
Commented by: DJChloe I am working about the Numrk Mixtrack (pro) 3 mapping, and I have implemented the faderstart in javascript without any problem. May be we could explain how to implement faderstart in the Mixxx scripting tutorial. |
Commented by: daschuer It would be great, if we could add such features an things like spin down break and spin up start to the mixxx C++ domain. This will allow to access it via skin, an offers the same experience throughout all mappings. @CHLOé: what would be the ideal control interface for this. So that we can enable rlthis feature for skins as well? |
Commented by: ywwg We do have some controller actions in c++: https://github.com/mixxxdj/mixxx/blob/master/src/controllers/controllerengine.cpp |
Commented by: DJChloe The ideal control is not complicated : From the code perspective, Faderstart is just one feature added : line fader to zero, stop playing /line fader increasing, start playing if the track was stopped. |
Commented by: daschuer Cool, I have just read in the DDJ-T1 manual and it looks like a nice feature. So if one has fun to adopt this bug, here some possibles steps.
|
Commented by: daschuer By the way: On a for deck setup it makes sense to start only cued tracks. |
Commented by: DJChloe I put here my parts of script mapping implementing the faderstart "emulation", it can help, it is a bit modified in order to make it "algorithm" like :
|
Reported by: Pegasus-RPG
Date: 2010-10-16T21:44:12Z
Status: Confirmed
Importance: Wishlist
Launchpad Issue: lp661917
Tags: autodj, cue, easy, hackathon
We should add a fader start feature to each deck's volume faders as well as the cross-fader and make it toggleable on each deck individually. (Fader-start is where the deck will start playing when the volume fader is moved up from 0 and will cue when moved to 0. Same on the cross-fader.) But default it to off so we don't surprise anyone.
The SCS.1m script currently does this (and it takes affect for any other controllers connected to the same virtual decks) but it should be program-wide instead of in script.
The text was updated successfully, but these errors were encountered: