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

can not set beginning of looping points in 1.3.0 appImage #7516

Open
1 task done
asmrtfm opened this issue Sep 24, 2024 · 4 comments
Open
1 task done

can not set beginning of looping points in 1.3.0 appImage #7516

asmrtfm opened this issue Sep 24, 2024 · 4 comments
Labels

Comments

@asmrtfm
Copy link

asmrtfm commented Sep 24, 2024

System Information

Ubuntu 22.04

LMMS Version(s)

1.3.0-alpha

Most Recent Working Version

No response

Bug Summary

middle click no longer works to set the beginning of the looping points.

it was working in the "stable" version in the ubuntu apt repo.
I switched to the 1.3.0 appImage because the overall it is a huge quality of life improvement.
Noticed this issue and no way to configure the keybinds myself so...

Expected Behaviour

middle clicking at top of piano roll and song editor, when looping mode is on, marks the beginning of the highlighted section to be looped.

Steps To Reproduce

run the appimage, try to do it, see it not work

Logs

Click to expand
  

Screenshots / Minimum Reproducible Project

No response

Please search the issue tracker for existing bug reports before submitting your own.

  • I have searched all existing issues and confirmed that this is not a duplicate.
@asmrtfm asmrtfm added the bug label Sep 24, 2024
@musikBear
Copy link

True! May just say it: Positioning looppoints is not dub-optimal, it is flawed/ broken.
Both left and right looppoint reacts to right mouse click
Positioning-control depends of distance from mouse-pointer to looppoint, and that is nerve-wracking.
Best trick is to click a bit to the left of left looppoint, and a bit to right for right looppoint, then you get the grip you intend, and non of the looppoits wll 'overtake' the other -It is a mess!

@Rossmaxx
Copy link
Contributor

This is fixed in master. Use nightly to see but not now, there's another regression which is in the process of being fixed.

@asmrtfm
Copy link
Author

asmrtfm commented Sep 30, 2024

True! May just say it: Positioning looppoints is not dub-optimal, it is flawed/ broken. Both left and right looppoint reacts to right mouse click Positioning-control depends of distance from mouse-pointer to looppoint, and that is nerve-wracking. Best trick is to click a bit to the left of left looppoint, and a bit to right for right looppoint, then you get the grip you intend, and non of the looppoits wll 'overtake' the other -It is a mess!

That is not how mine behaves.
I just simply cannot set the starting point.

@musikBear
Copy link

That is not how mine behaves.

And 'mine' is??
OS?
Version?

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

No branches or pull requests

3 participants