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

Inconsistent Violin 1 playback of fingered/measured tremolos #22976

Open
wizofaus opened this issue May 25, 2024 · 2 comments
Open

Inconsistent Violin 1 playback of fingered/measured tremolos #22976

wizofaus opened this issue May 25, 2024 · 2 comments
Assignees
Labels
muse sounds needs info More information is required before action can be taken

Comments

@wizofaus
Copy link
Contributor

Issue type

Muse Sounds bug

Bug description

A fingered (or even alternating-bow) measured tremolo is played back very differently depending on whether the notes are written out or tremolo bars are used.

Steps to reproduce

  1. Create a new score with solo Violin 1/MuseSounds
  2. Enter in 8 1/16th notes that alternate between G3 and F4
  3. Enter 1/4 notes G3 and F4, and add a 2-line tremolo bar between them (to indicate a measured two-note tremolo)
  4. Play it back
  5. Observe that the "written out" version sounds very different to the tremolo version (the tremolo version is what I would expect both to sound like, I'm not sure why the other version sounds the way it does).

Screenshots/Screen recordings

https://musescore.com/user/7209246/scores/17318203/s/_7-mLa
(slight variation on above instructions but gives the same idea)

MuseScore Version

4.3

Regression

I don't know

Operating system

Windows 11

Additional context

No response

@wizofaus wizofaus changed the title Violin 1 playback of fingered/measured tremolos Inconsistent Violin 1 playback of fingered/measured tremolos May 25, 2024
@bkunda
Copy link

bkunda commented May 28, 2024

My guess is that the tremolo articulation mark is triggering a different sample.
Ideally in this case though, the tremolo mark is indicating an abbreviation of the previous written-out bars, so the user would reasonably expect the playback to be the same.
@sampleeditor @matthewreadbass can you pls confirm whether this is what's happening on the sample end?

@bkunda bkunda added the needs info More information is required before action can be taken label May 28, 2024
@TobyTwo32

This comment was marked as off-topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
muse sounds needs info More information is required before action can be taken
Projects
None yet
Development

No branches or pull requests

5 participants