Skip to content
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

Nested beat/bassline editors? #4829

Closed
rafaelferreiraql opened this issue Feb 17, 2019 · 5 comments
Closed

Nested beat/bassline editors? #4829

rafaelferreiraql opened this issue Feb 17, 2019 · 5 comments

Comments

@rafaelferreiraql
Copy link

Currently, when you add a new Beat/Bassline editor inside a Beat/Bassline editor, it just creates a new Beat/Bassline inside the Song Editor. The way the interface is set up lead me to believe that it should be created inside that same Beat/Bassline editor instead of outside of it, just like the sample track and automation track buttons.

image

I personally believe nested Beat/Basslines would be great for being able to build patterns out of other, smaller, patterns. If this proposal is rejected for whatever reason, at least that misleading Add Beat/Bassline button should be removed from the Beat/Bassline editor.

@0xf0xx0
Copy link
Contributor

0xf0xx0 commented Feb 17, 2019

The button is there so you can easily add a new B/B track to the Song Editor without having to click out of the B/B Editor, especially if the B/B Editor is maximized.

@musikBear
Copy link

And those buttons should definitively not be removed!
@rafaelferreiraql - I recommend you to read the chapter about usage of Beat-editor:
https://lmms.io/wiki/index.php?title=Composing_Bass_Lines_and_Drum_Sequences#Philosophies_of_pattern_design
It seams to me that you need to understand the reasons for the design.

@zonkmachine
Copy link
Member

@rafaelferreiraql I too found it confusing but I don't know a better way and have more or less gotten used to it.

@DeRobyJ
Copy link
Contributor

DeRobyJ commented Feb 18, 2019

It's actually the same button with the same explanation that does the same thing, it's just placed in a different window...

Having a different button with a different explanation would be misleading too.

@tresf
Copy link
Member

tresf commented Mar 11, 2019

As part of a pruning effort, this enhancement request is archived into a dedicated "Better Workflow" checklist here #4877.

@tresf tresf closed this as completed Mar 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants