Specific instrument won't play in playback for four beats
When I playback the song I've attached to this post, the last four beats of my halo synthesizer part don't play. I've tried everything I can to fix this but nothing has worked. Does anyone know a fix for this?
| Attachment | Size |
|---|---|
| NYC 2083.mscz | 18.88 KB |
Comments
They do sound, when playing from the beginning of the long tied sequence (starting measure 36)
In reply to They do sound, when playing… by Jojo-Schmitz
Not for me.
In reply to They do sound, when playing… by Jojo-Schmitz
And not for me. See below.
There is a mistake in your score and maybe in Musescore too.
Look at bar 38. There is no note in the halo synthesizer staff. Bars 37 and 39 are tied. This probably messes up Musescore so that the last bar is not played.
If you insert a note in bar 38 and tie it to those in 37 and 39, it will play correctly to the end.
In reply to There is a mistake in your… by HildeK
It's not really the last bar not being played; it's more that the tied note total duration is just 4 beats shorter than where the end is notated because of that.
In reply to It's not really the last bar… by jeetee
Yes, it is 4 measures shorter because there are 4 beats missing in measure 38.
![NYC 2083.png]( "NYC 2083.png")
![NYC 2083-1.png]( "NYC 2083-1.png")
I presume it is a bug, because it should not tie over a rest or other note(s). Musescore then messes up the beat count.
Compare:
In reply to Yes, it is 4 beats shorter… by HildeK
This seems more like operator error than a bug. MuseScore can't play the impossible.
In reply to Yes, it is 4 beats shorter… by HildeK
MuseScore allows you to tie discontiguous notes if you ask it to - it's important for things like arpeggios tied to held chords in piano and guitar music. It's up to the user not to use this feature when they don't intend to.
In reply to MuseScore allows you to tie… by Marc Sabatella
Why then does the organ play this way? Or must this tieing over several notes be activated somewhere separately?
![Ties.png]( "Ties.png")
In reply to Why does this organ play… by HildeK
Addendum:
![Ties_1_.png]( "Ties_1_.png")
Wouldn't it have to be written that way then?
In reply to Addendum: Wouldn't it have… by HildeK
If that's what you want to hear, then indeed, that's the way to write it - except, you are missing a beat in the first measure, I think you removed a quarter rest that would be needed in order for that rhythm to make sense.
In reply to If that's what you want to… by Marc Sabatella
> I think you removed a quarter rest that would be needed in order for that rhythm to make sense.
Yes, you are right, sorry.
[Edit] I replaced the screen shot.
In reply to Why does this organ play… by HildeK
I'm not sure what you're asking here. The above notation is kind of nonsensical, but again, if you ask MuseScore to create it, then it will happily oblige. It won't sound meaningful because it isn't meaningful here. Again, the feature is meant more for arpeggiate-and-hold and other special-purpose notations.
In reply to I'm not sure what you're… by Marc Sabatella
See the original problem of the thread opener, that was the starting point.
Then I wondered why it was possible to put a tie over the one empty bar.
And yes, it does not sound sensical, so in his case he missed four beats.
I don't have much experience with music theory, so I don't know anything about this "arpeggiate-and-hold".
In reply to See the original problem of… by HildeK
It's not a concept from music theory, just a basic keyboard technique thing - the idea of putting your fingers down on the keys one at a time and holding them. Notated like this:
No rests involved here of course, but this is an example of why MuseScore needs to support ties between non-adjacent notes in general.
In reply to It's not a concept from… by Marc Sabatella
Ah, thanks for the explanation!
This does not happen with me, because I play the horn :-) (beginner).
In reply to There is a mistake in your… by HildeK
This worked. Thanks!