MuseStrings stop playing after 1071 bars/pg 95/36 min

• Dec 19, 2022 - 19:22

Trying to upload old score to v4 mostly worked. Solo strings that use MuseStrings stop playing after 1071 bars or page 95 or 36 minutes, which ever is relevant. Clicking on the note plays correctly but play button goes silent on all intruments (violin, viola and violoncello) except contrabass plays OK to the end. It is the only one not found in MuseStrings so the problem could be there?
I checked this by changing a violin back to MS Basic (or whatever it was called) and then it continues to play normally. So the problem IS in MuseStrings.

Other maybe known problems:
- playing method like pizz. in voice 2 does not play correctly (if voice 1 is arco, voice 2 plays arco too)
- glissandos (portamento) do not sound correctly - sometimes just omitted. May be related to the tuned shape that seems to be missing in new version?
Positive notes about pizzicato, col legno and sul pont. in violins at least.


Comments

The main problem moved a bar ahead when I changed one fermata to shorter value. So the problem seems to be with time, not bars, pages or number of notes. Increasing buffer size did nothing.

In reply to by jounip

Update for pizzicato: reattaching pizz. from text menu for voice 2 sounds at least OK but text appears as voice 1 control on the bar indicator. Something mixed there.

Another problem with MuseStrings: there is some noise at start of playback regardless where you start the playback. Different chords and trills for each instrument. This may be an old problem but I don´t see any complaints recently. No problems with MS Basic.

In reply to by jounip

OK, I managed to remove the noise from the start when I deleted all notes after bar 1071 at 36 minutes. These two were related problems and some table will leak over after certain time to start of play. At least the start sounds OK now. Any other problem does not seem to be correcting with this. Seems simple to fix when tried with long enough entry.

For the main problem I attach the full score for help to fix the problem - if it is what I suspect or not. Be warned about the start of playback - it does not sound pretty. All output ends after bar 1073 with MuseString instruments. When MuseStrigs are switched to MS Basic or the rest of music after bar 1073 are cleared the problem goes away. As I mentioned above this limit seems to be in time, not related in bars or notes.
Hope this helps because I have not seen this problem reported.

Attachment Size
Kameleontti_m7_5.mscz 626.5 KB

In reply to by jounip

I did a test of re-installing all. Result was no change to main problem. Others have same problem but can not be reproduced on all computers. I attach here first page test mp4 where the noise at start can be heard. I press play, then stop and play again. The noise appears again.

The latest versions are:
MS 4.0.0.2234772
Muse Strings: 0.4.4
sampler: 0.3.3.18
QT: 3.15.2
Computer INTEL i7 4-core 16G RAM 2.80GHz, Win 11 home 64.bit 22H2.

Attachment Size
alku.zip 1.86 MB

In reply to by jounip

Couple new tests:
1) I can save and load the file with MS4 but the problem is the same after it.
2) I can remove the middle movement (around 8 minutes) and the problems at start dissapear and the end plays ´normally´. So it does not matter where you remove material. (If I remove only notes from the middle the problem is still present. If removing at the end you only need to remove the notes.)
That proves that problem is not in the score but the system. If there was an index that is running 30 times per second and instead of long it was integer... Would do something interesting at 36 minutes.

I just installed MS 4.0.1 but it did not correct this problem. There was some mentions that this would be fixed in next MS update with MuseSounds update (another thread issue #340504). But the MuseString version did not chage so it could not be fixed (it was mentioned both would need to be updated). Is there any way to check what is expected of new versions or what was corrected on new versions?

I am happy to say this problem has gone with MS4.1. But not so happy that no other problem seems to be affected that I have been concerned about.
This of course is related what scores are in question. My piano score seems to be more sensitive and variable in expression - up to overly bass resonance on some keys. But I happen to like variance like that.
But strings are still (maybe even more than before) overly tuned to one kind of sensual, over-expressive attitude. It is fine for some pleasure seeking music but is applied in too many places. The algorith may lear in time but now it is lost in slower places where solemn interpretion is needed.
There seems to be an illusion that all music can be treated with same attitude no matter the notation. At least there should be a possibility of neclecting the espressivo given for almost every phrase.
For strings the second biggest problem is poor portamento. This has been reported last year with examples. This may be a problem of the MuseString library but I don´t really care. It keeps me using MuseScore for anything. I felt beeing too negative when I estimated that it might take until summer that these problems would be fixed not until summer. But now I feel optimistic to think they would be fixed before next christmas.

Do you still have an unanswered question? Please log in first to post your question.