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

Arpeggios, sort mode, and release #340

Closed
eagles051387 opened this issue Feb 19, 2014 · 8 comments
Closed

Arpeggios, sort mode, and release #340

eagles051387 opened this issue Feb 19, 2014 · 8 comments

Comments

@eagles051387
Copy link

Hello, I'm on LMMS 0.4.14-rc1, and there is a problem with arpeggios.
This existed for a while, but I just did a bit more debugging. When the release of the instrument overlaps with the next note in sequence, a note will either a) fail to play, or b) play two notes together when the instrument is set to "sort" mode.

@diizy
Copy link
Contributor

diizy commented Feb 19, 2014

I can confirm this is still an issue. In sort mode, some notes get skipped - haven't seen the "two notes together" thing happening though.

@repsej
Copy link

repsej commented May 23, 2015

This is still an issue (1.1.3 win64) - and I think it has gotten worse recently.

I've made a very simple example that shows it.

image

There are just two half notes in the piano roll and the arpeggio time setting is also set to half a note.

Playing this yields a lot of overlapping notes and strange clicking noise.

Worth noticing:

  • Changing the tempo of the song changes the bug behaviour.
  • Changing gate, range, sorting mode dosn't affect the bug.
  • The bug only comes after the first looping (also it disappears from time to time in some strange pattern)

@repsej
Copy link

repsej commented May 23, 2015

A short video with some of the arpeggio problems.

https://youtu.be/tDRmTxxEYSA

@musikBear
Copy link

interesting! and tchanging the BMP, other weird things happens
when we get below 50 the 'double-note' is replaced by silence. The playhead moves over the note, but there is no sound.
I think that might be the case also at higher bmp, but there its not possible to discriminate the silence ?
fi:
at 60 bmp. arp: 2 octaves. TimeSync : ½-note
beat1 sound
beat2 silence
beat3 sound
beat4 silence
or..
1+ 2- 3+ 4-
second run is different:
1* 2- 3- 4+
where " * " is double note
3..8 as 2.
9.
1* 2- 3* 4+
That is reproduceable, and could(?) give insight in the off-sequence

@musikBear
Copy link

How does current Master do in this respect?
Should this actually be marked at least Bug or isent it in fact Critical ?

@Umcaruje
Copy link
Member

!? This bug isn't critical, neither its even milestoned, so it isn't such a high priority.

@musikBear
Copy link

@Umcaruje #2589 was marked critical, this is same thing, but its fine that its now marked 'bug'. :+1
Sort-mode may also be ok in current Master, because #2589 is closed.
Could you do a test of sort-mode on Master?

@zonkmachine zonkmachine mentioned this issue Oct 6, 2017
2 tasks
@zonkmachine
Copy link
Member

Closing as a duplicate of #2606
The later issue goes into more depth.

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

6 participants