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

Tab FUNC / New arpeggio : several issues #3342

Closed
musikBear opened this issue Feb 10, 2017 · 4 comments · Fixed by #3867
Closed

Tab FUNC / New arpeggio : several issues #3342

musikBear opened this issue Feb 10, 2017 · 4 comments · Fixed by #3867

Comments

@musikBear
Copy link

musikBear commented Feb 10, 2017

OS : winXP sp3
LMMS 1.1.90-RC2.8

Issue description:
Arpeggio is mixed up, and has several errors

Recreate :
New project
insert a c-maj chord with 2 bar length notes
FUNC-TAB/ ARP
Set:

  • GATE 10%
  • TIME synch to ½ note
  • Rest default

play
FREE works as SYNC should work
-All 3 notes in the chord is played simultaneous
Mark all notes and move them ½ bar fwd
play
There are now one extra hit ½ a bar from the end of the notes
If you move them 1 bar, There are now one extra hit as the playhead starts second cycle at 0

change to SORT
play
One of the notes will not play arpeggio, but plays one long note, then 2 notes play shortly, then 1 note

Change to SYNC
play
first a short all-notes artefact occur. Then one note play a long note, then all notes play simultaneous

Could it bee that a wrong commit has been used for RC?


Do anyone want a file?

@zonkmachine
Copy link
Member

I don't think there is a drastic difference from 1.1.3 .

There are now one extra hit as the playhead starts second cycle at 0

Thanks! I knew there was an extra hit in there somewhere but I thought it was the master note sounding with the arpeggio note. It's an extra trailing note that comes back as a ghost note when looping.

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

zonkmachine commented Oct 5, 2017

There are now one extra hit as the playhead starts second cycle at 0

I think I nailed this one at least but the arpeggio sync problems are a bit tricky.

@musikBear
Copy link
Author

I think I nailed this one at least

Good job! Over time i think it would make sense to re-furbish arpeggio. Options like in Oatmeal and Synth, where different delays on selected notes are possible, would open for amazing new sound.

but the arpeggio sync problems are a bit tricky.

Believe the arp has been bugged from day one, has always only had success with the sorted setting

zonkmachine added a commit to zonkmachine/lmms that referenced this issue Oct 10, 2017
When in sort mode and playing over multiple base notes, in the
beginning of the notes there is a chance that the notes will play
together as an ordinary chord instead of arpeggiate.
This is a regression from 6650dd3.

Fixes LMMS#3342
zonkmachine added a commit that referenced this issue Oct 10, 2017
When in sort mode and playing over multiple base notes, in the
beginning of the notes there is a chance that the notes will play
together as an ordinary chord instead of arpeggiate.
This is a regression from 6650dd3.

Fixes #3342
@zonkmachine
Copy link
Member

Fixed in #3858 #3867

sdasda7777 pushed a commit to sdasda7777/lmms that referenced this issue Jun 28, 2022
When in sort mode and playing over multiple base notes, in the
beginning of the notes there is a chance that the notes will play
together as an ordinary chord instead of arpeggiate.
This is a regression from 6650dd3.

Fixes LMMS#3342
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

Successfully merging a pull request may close this issue.

2 participants