Replies: 7 comments 13 replies
-
Yes, a lot of operations can be applied to a selection instead of current beat. It's my intention to backport from 2.0beta these features, but for sure it will take some time (currently working on other features) |
Beta Was this translation helpful? Give feedback.
-
Implementation of selection-wide actions is in progress, please be patient this is time-consuming. These features in 2.0beta fork broke the compatibility with Android version, so it's not only back-porting but adaptation is required (see #62). @Sy256: regarding increment/decrement semitone actions, you're right it could conflict with "play beat when note is transposed" feature implemented recently. However, I do not think a checkbox is needed. Globally, as a design rule: avoid requesting users to set config parameters, better find an implementation which fits all cases. Especially if parameter (checkbox) is "hidden" somewhere in a dialog most users won't even be aware of.
|
Beta Was this translation helpful? Give feedback.
-
This is going to take time: I'm intentionally slowing down this activity. The strategy of 2.0beta fork was simple for selection-wide actions: loop over all selected notes and apply action. But in some cases it doesn't make sense.
It's even worse with "shift up/down" action: applying the same strategy can lead to deleting notes (e.g. shift down So I will rework this, with the strategy to apply action either to all selected notes, or to none of them. "Semitone down" action applied to a basic Em chord shall do nothing. |
Beta Was this translation helpful? Give feedback.
-
Note, bug present for all effects in 2.0beta: when clicking on an effect in toolbar when a bunch of notes is selected, it toggles the effect on all notes. It should either set or unset the effect everywhere. |
Beta Was this translation helpful? Give feedback.
-
Yeah I have experienced that bug in 2.0 beta, but personally I can live with it and avoid it usually, would it be possible to port over that behavior and just refine it in further versions if needed? For my purposes I just use the range select effects mostly for string switching and making a bunch of things palm muted, and secondary, velocity changes. Usually I have it set it a way to avoid those bugs but if it misses a couple notes I can just go set those manually. Also been away a few days but trying the latest version (7-27) now, I was on 7-21 before it seems. Thanks |
Beta Was this translation helpful? Give feedback.
-
Apply all effects to selection: merged (#89)
and many combinations of the different tests mentioned above. |
Beta Was this translation helpful? Give feedback.
-
Just a suggestion: close this discussion now it's implemented? |
Beta Was this translation helpful? Give feedback.
-
This is how older 2.0 branch worked, in this video you can see the difference when I try to adjust the duration of a group of notes, but after I made the video I also found that other things like palm muting, triplets, transposing, staccato are only applying to the last selected note. Is it possible to change that to how the other one is working?
See here and ignore my messy desktop lol. First I show the older 2.0, and then I switch to the remote computer I had this tuxguitar.
https://youtu.be/NzJ4g9bvfo8
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions