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.

Sign up for GitHub

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

Jump to bottom

[MU4 Issue] Muse Sounds: Arpeggio also affects the next chord #14941

Closed
LuisLiszt opened this issue Dec 5, 2022 · 5 comments
Closed

[MU4 Issue] Muse Sounds: Arpeggio also affects the next chord #14941

LuisLiszt opened this issue Dec 5, 2022 · 5 comments
Assignees
@davidwhearn
Labels
muse sounds P1 Priority: High
Projects
Muse Sounds

Comments

@LuisLiszt
Copy link

Describe the bug
See video. An arpeggio also plays the next chord as an arpeggio, even if it's not the same measure.

To Reproduce
Steps to reproduce the behavior:

  1. Place multiple chords.
  2. Place arppegio.
  3. Play

Expected behavior
Arpeggio should only play the assigned chord, not the next one.

Screenshots

2022-12-05.10-36-23.mp4

Platform information

  • OS: Windows 11
@krtschil
Copy link

krtschil commented Dec 5, 2022 •
edited
Loading

Seems to be correlated with Muse Sounds. If set to MS Basic the Arpeggio is played correctly (both RC and Nightly expose the same behaviour).

@LuisLiszt
Copy link
Author

@krtschil Yes, I can confirm that! Thanks for adding the information

@cbjeukendrup cbjeukendrup changed the title [MU4 Issue] Arpeggio also affects the next chord [MU4 Issue] Muse Sounds: Arpeggio also affects the next chord Dec 5, 2022
@cbjeukendrup cbjeukendrup added this to To do in Muse Sounds via automation Dec 5, 2022
@Tantacrul Tantacrul added the P1 Priority: High label Dec 6, 2022
@Tantacrul Tantacrul added this to Not for RC. For actual Release. in [MU4.0 RELEASE] via automation Dec 6, 2022
@Tantacrul Tantacrul moved this from Triage to High Priority in [MU4.0 RELEASE] Dec 7, 2022
@LuisLiszt
Copy link
Author

Issue still persists and is stuck in MU4.0 Release which isnt worked on anymore...

@cbjeukendrup
Copy link
Contributor

Issue still persists and is stuck in MU4.0 Release which isnt worked on anymore...

Don't worry, it's also in the Muse Sounds project, which is where the Muse Sounds developers look.

@zacjansheski
Copy link
Contributor

Combining this with #16917

@zacjansheski zacjansheski closed this as not planned Won't fix, can't repro, duplicate, stale Jul 24, 2023
@oktophonie oktophonie removed this from High Priority in [MU4.0 RELEASE] Jul 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@davidwhearn davidwhearn

Labels
muse sounds P1 Priority: High
Projects
No open projects
Muse Sounds
  
To do
Milestone
No milestone
Development

No branches or pull requests
6 participants
@davidwhearn @krtschil @Tantacrul @cbjeukendrup @LuisLiszt @zacjansheski