-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
request: global transpose in semitones #375
Comments
IMO the main challenge with this will be coming up with a sufficiently effective way of judging which tracks are drum tracks. EG, is some Sf2 in the B&B being used as a drumkit or as a string backing? I can't think of any way to have LMMS figure this out, which means the user would have to specify which tracks were drum tracks. |
You are right! -the same goes for FX ..Perhaps a checkbox on the song-editor items, could be a solution to that. Meaning that only tracks user-marked for transposing (eg tracks with real notes) would be included in the process. ..unrelated -I maked the subsection 'Enhancements' before i posted this, but it ends up in 'Bug-Issues', and with no "Enhancement" label -What did i do wrong |
But the Master Pitch is the same as transpose whole project? |
@Stian except it doesn't account for drums and will screw them up. Also, it On Thu, Feb 27, 2014 at 4:07 PM, Stian Jørgensrud
Johnny |
There is no feasible way for lmms to guess which tracks are meant as "drums" and which aren't. For example, a soundfont can just as easily be a drumkit or a regular instrument. We could add a checkbox option to instrument tracks such as "ignore master pitch", accessible from the trackops menu. |
This transposition idea could move forward now, the checkbox exists in master. |
Since #1593 was merged, I'm closing this issue as fixed. If you believe this was closed in error, feel free to reopen the issue. |
I would like to sugest a menu item -could logically be in 'Edit'
Feature: 'Transpose project'
The user should be able to select number of semitones + up/dn
The result would be that the complete project would be in a new key/ scale.
The text was updated successfully, but these errors were encountered: