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

piano-roll: piano buttons not working when playing a pattern #21

Closed
eagles051387 opened this issue Jan 15, 2014 · 4 comments
Closed

piano-roll: piano buttons not working when playing a pattern #21

eagles051387 opened this issue Jan 15, 2014 · 4 comments
Labels

Comments

@eagles051387
Copy link

If you play a pattern within the piano roll, clicking any of the pianos button won't play a sound. However, if you hold down the mouse button and move over several (or even one is enough) buttons, the sound is played as expected. If you don't play a pattern, the sound is played in both previously named situations and therefore the piano roll is working as expected in this case.

@tobydox
Copy link
Member

tobydox commented Jan 16, 2014

I remember that we once implemented this intentionally because of possible side effects with the same notes being played/stopped. I don't know how it would work without these extra checks. For testing purposes try to comment out

https://github.com/LMMS/lmms/blob/stable-0.4/src/gui/piano_roll.cpp#L1795
https://github.com/LMMS/lmms/blob/stable-0.4/src/gui/piano_roll.cpp#L1848

and check whether everything works and there are no new problems.

@diizy
Copy link
Contributor

diizy commented Feb 19, 2014

Well I did this and seems to be fine, when same notes are played they just sound twice as loud. I think we can put this in. If it causes problems we can remove the comments again.

diizy added a commit to diizy/lmms that referenced this issue Feb 19, 2014
@pgiblock
Copy link
Contributor

I think we need to be careful about this one. I say avoid it for 1.0 unless we have a good way to burn it in.

@diizy
Copy link
Contributor

diizy commented Feb 20, 2014

On 02/20/2014 04:50 AM, Paul Giblock wrote:

I think we need to be careful about this one. I say avoid it for 1.0
unless we have a good way to burn it in.

Well I think it'd be good to commit it in now so we can test it more
easily, and if it causes problems we can just revert it. I only
commented out the lines so it'd be easy to revert.

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

4 participants