-
-
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
Better Workflow #4877
Comments
I think this #4554 is very, very related to this topic. Especially for lmms users with external controllers like me. Because for now lmms workflow with external controllers isn't as good as it should be. |
@qnebra that sounds like a legitimate bug. |
@qnebra you sent me a PM on Discord and I want to be more clear. Your bug affects workflow (all bugs do), but it's not a "nice to have" feature, it's a legitimate bug and should be tracked as such. Quoting the bug you've linked:
I want to keep the legitimate bugs open in our tracker so that they're easier for developers to find, assign and work on. The features above are related to items -- in most cases -- completely missing from LMMS and are better left in a |
@craslaw sure! |
@craslaw Maybe you should wait until #5524 is merged, as it changes the logic and method that changes the cursor during |
@tresf can you update the list. i feel that a lot more of it has been fixed. |
Please don't do this unless you have specific issues in mind to be added or checked off. |
i mean just to update the check marks. it feels like he didn't update it for a long time and around 80% of the issues seem to be closed. |
For our meta-issues the open/closed status of a child-issue does not determine whether or not the issue is resolved. Closing issues when we consolidate them lets us keep the open issue list a little more manageable. If you would go look at some of the recently consolidated issues you'd see this in action, they're marked as closed but not resolved. This means the list is far from 80% complete and there are no updates to be made unless you can name a specific issue and the merged PR or commit that resolves said issue. |
Sorry, if you look at the edit log, this issue is now maintained by Spekular and others. As instructed, any specifics that need updating, let us know. This bug tracker is huge and maintaining it is a lot of work, so the more specific the better. |
Hasn't this been done |
This comment was marked as outdated.
This comment was marked as outdated.
Tool to glue selected notes together. Selected notes that are adjacent to each other or overlapping are transformed into one note stretching over the combined notes on/off times. Key command: <Shift> + G Partially fixes: LMMS#746 which is part of LMMS#4877 Co-authored-by: Hyunjin Song <[email protected]> Co-authored-by: IanCaio <[email protected]> Co-authored-by: Spekular <[email protected]> Co-authored-by: Kevin Zander <[email protected]> Co-authored-by: Oskar Wallgren <[email protected]>
We have forgotten to add Blues-scale to the scale-selector. |
The scale/chord selector is not god but those scales are there. Chord/Scale is selected from the number of notes. This means short scales like blues and pentatonic scales show up as chords and if you would add a very large chord in there it would show up as a scale. I believe this is mentioned elsewhere in the issue tracker. |
I'm not talking about a workaround but merely trying to point out the reason some chords/scales aren't showing up in the right selector. Here is the code that choose between scale/chord depending on number of notes/size. lmms/include/InstrumentFunctions.h Lines 93 to 96 in 2baa23e
It's better to take this discussion to Discord if you're still not satisfied. Also, @Veratil knows more about this. |
I've taken the liberty of adding #6930 and #6931 under the Song Editor and Piano Roll headings respectively. They may need to be scoped down if there are disagreements over how much state to save, but saving more than we do now is hopefully uncontroversial enough that these issues won't need to be removed from the list. |
I'm creating a meta issue for better UI/UX workflow. This list should be updated frequently because it's the source of many of our new bug reports. If a new bug report arrives that seems workflow related AND won't be closed by a quick patch it can be marked as a duplicate and placed here.
Since workflow is so important to users -- something they can directly relate with -- this can also help serve as a futuremap if the developer team is to start milestoning certain enhancements (something we don't do a great job of currently)
Lastly, it can serve as a birds-eye-view (so to speak) of what our users really want. ❤️
💥 = Bug
🚀 = Good first issue for new developers
See also:
Tracks
Song Editor/Beat+Bassline Editor
>>
as default playhead behavior Better transport/playback/playhead behavior #3740|<<
versus "pause" default behavior Better transport/playback/playhead behavior #3740 [Milestone: 1.3]Piano Roll Editor
Automation Editor
Instruments
Internal
meta
) [Milestone: 1.3]External
Mixer and Effects
dB
indicators Signal meters dB indication #1213 dB Meters on FX Mixer/Effects #4458Files and Folders
Misc/Overall
The text was updated successfully, but these errors were encountered: