-
-
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 controls to manipulate the bpm via skin/midi controller #9133
Comments
Commented by: esbrandt Could you elaborate a bit more what you are requesting here? Some skins e.g. Tango and Deere do have controls to edit a beatgrid, and all skins have the ability to Change the BPM by right-clicking a track in the library, or by editing the BPM tab in the track properties editor. Beatgrid editing controls are also available in the MIDI controller wizard, under the BPM menu. |
Commented by: index82 I checked the midi controller wizard now but didn't find the requested controls. Mixxx has
Mixxx hasn't
My idea is to speed up the workflow for preparing tracks/beatgrids. And it makes realy fun to work with. |
Commented by: mxmilkiib MIDI control for fixing incorrect BPM detection would be incredibly welcome. The default skin now doesn't have these options in the main UI body, one has to go back into the media library to use a submenu, which is a bit of a workflow nightmare. The pads on many controllers now would be perfect for binding such to. |
Commented by: ronso0 FYI You can also double-click on artist/title fileds in the decks to open the Track Properties window. Besides the track metadata, it has a second tab 'BPM' with all BPM options where you can also tap the BPM or enter a value manually. |
This is a kind of a no-brainer: |
This would be very handy/essential for keyboard+mouse free library management. What is the actual status of what is in the 40a7de1 commit? Before I go yak shaving on implementing this. Is it purely an example with just one of the fractional BPM Adjustments? I guess some mindful copying+pasting and rewordings could fulfil this? |
So, given the actions are already defined in wtrackmenu.cpp, is it sensible to reproduce the = in that commit? Should there be some DRY here? Should that function remain in the wtrackmenu file even though it would be used elsewhere? If redefining is best, would that require a different w_ name to avoid a collisions, or is the scope different enough? |
40a7de1 is just a POC, I don't intend to continue that. In order to extend that example for more scales, this
would simply use a lambda
(and drop Does that make sense? |
IMHO we don't need to care about the actions in WTrackMenu, redundancy is not an issue in that case. |
Why are there 5 connect() parameters in the original example and only 4 in the lambda example? |
The fifth parameter is the Qt::ConnectionType. If it's omitted it defaults to Qt::AutoConnection. Nothing to worry about for a POC. |
I suggest to open a draft PR where we can discuss code much easier than with screenshots ; ) |
I shall, once I've been able to try build 2.5 :) |
Finally, right. How is the scope meant to get
|
Actually you don't need to build it yourself, just commit, push and CI will build for you. Should be sufficient to spot errors and discuss code. |
Some |
Reported by: index82
Date: 2018-02-13T17:35:16Z
Status: Confirmed
Importance: Wishlist
Launchpad Issue: lp1749252
Tags: bpm, skin, usability
like e.g. beats_adjust_faster, beats_adjust_slower ...
Options:
The text was updated successfully, but these errors were encountered: