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

[Feature Request] Have the black and grey squares in Song-Editor change based on the signature #7281

Open
1 task done
bratpeki opened this issue May 26, 2024 · 3 comments

Comments

@bratpeki
Copy link
Member

Enhancement Summary

Basically, the black and grey squares are always showing in 4/4 time, independent of the time signature used. Changing it would allow for easier tracking of the time signature.

Implementation Details / Mockup

The implementation should be similar to how the 4/4 time coloring schema is done. If N/D is the time signature, the color should change after N*D beats, and one bar should be N beats long.

This poses a question of how automating the signature would effect the Song-Editor UI. Regarding that, I'm open to suggestions.

Please search the issue tracker for existing feature requests before submitting your own.

  • I have searched all existing issues and confirmed that this is not a duplicate.
@bratpeki
Copy link
Member Author

I realized my request is quite confusing, and am discussing it with Jernemies. I'll get back to this when I have more idea of what exactly I am asking for.

@michaelgregorius
Copy link
Contributor

I guess what you are requesting can best be described with the following image:

7281-5 4-beat

Here I have set the time signature to 5/4 and have added a note clip that contains five quarter notes. The grid in the background still shows four lines per beat instead of the expected five lines. This results in offsets between the notes and the grid.

Lack of tempo map

I think what you are asking for might also be hard to implement. If I understand correctly LMMS has no concept of a tempo map which would be needed to correctly paint the beat lines and measures.

@LMMS/developers, do I understand correctly that changes to tempo and measures are implemented with automation patterns?

If that's the case then the following attached project shows some problems with that approach:
7281 - Change measures via automation.zip

It's a project that starts with 5/4 in the first measure and then switches to 4/4. After the switch the first pattern is drawn incorrectly (which might in part be what this issue is describing. Another problem is that the view of the song editor is changing in a sudden fashion.

@RoxasKH
Copy link
Contributor

RoxasKH commented May 27, 2024

I guess what you are requesting can best be described with the following image:

Here I have set the time signature to 5/4 and have added a note clip that contains five quarter notes. The grid in the background still shows four lines per beat instead of the expected five lines. This results in offsets between the notes and the grid.

Lack of tempo map

I think what you are asking for might also be hard to implement. If I understand correctly LMMS has no concept of a tempo map which would be needed to correctly paint the beat lines and measures.

@LMMS/developers, do I understand correctly that changes to tempo and measures are implemented with automation patterns?

If that's the case then the following attached project shows some problems with that approach: 7281 - Change measures via automation.zip

It's a project that starts with 5/4 in the first measure and then switches to 4/4. After the switch the first pattern is drawn incorrectly (which might in part be what this issue is describing. Another problem is that the view of the song editor is changing in a sudden fashion.

If it can help, pianoroll actually already update itself in a similar manner according to that info (while song editor only updates the playbar numbers). I dunno how it's implemented, but i'm guessing the same behaviour can be kind of followed.

Sudden view changes are something inevitable with automations imo, so as long as tempo changes are done that way i don't think there's a nice way around it.

2024-05-27.21-54-36.mp4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants