-
-
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 hotcue #1 to track load point options #12740
Comments
Using hot cue 1 as load cue seems to be a good idea. At least we will not have mapping issues. The main issue is the transition. If you have a library with many track, many will not have a hot cue 1 at a load position. So I think it needs a track by track decision. How about setting an option in the deck preferences that newly set hot cue 1, become a load cue? |
I'd expect that option to be simple: choose 'Hotcue #1' and make sure tracks have that set. |
Just my 2 cents, I'm only relaying the request from the forums. |
The user is coming form Serato. How do they handle that? Do we have to respect something in the Serato Metadata? |
@Holzhaus Reading trough our Serato cue code it looks like we do not import a load cue. Does Serato have that? |
It has a temp cue, but it's not saved in the metadata as far as I know. This is in line with the documentation on "Temporary Cues":
https://support.serato.com/hc/en-us/articles/233435527-Temporary-Cue |
Feature Description
I remember this has been requested before, and now again on the forums https://mixxx.discourse.group/t/newbie-to-mixxx-help-please/28933
Should be easy to implement.
The text was updated successfully, but these errors were encountered: