3.0 Mac Stuttering in MS3
Been working on a score with 3 pan flutes. Couple of hours, playing all sections of it. The I said, "well, I want the bottom one to be a bassoon!" And so I changed it. The bassoon immediately stuttered the first time any measure was played, and was fine thereafter. If that's not a "smocking gun", as our President spelled it today, I don't know what is (i.e., soundfont wave-tables that will be used ought (optionally?) be touched first).
Comments
Well, I seem to have fixed the stuttering problem! I brought a brand-new Mac with much more RAM and a faster processor! That was easy!
In reply to Well, I seem to have fixed… by [DELETED] 1831606
@BSG
Similar for me...
I used to have severe stuttering problems on my old laptop with MuseScore 2.x, and that was with only five separate staves for S A T B voices and organ.
My current laptop has a better spec (Windows 10, i7 processor @ 2.4GHz, 16 Gb RAM). And since then I can routinely play works for a full symphony orchestra. Works fine for MS 2.3.2 and MS 3.0.2.
In reply to @BSG Similar for me... I… by DanielR
REALLY!?!? While I'm delighted with this new machine and the boons it brings, this is a "severe limitation" as not everyone can afford "state-of-the-art" hardware. And this is the first I've heard that it's not (cue Elmer Fudd) Mac-sp, spec-, sp, sp-specific. But Marc and others should take note when the next person is plagued in this way. This is a 2.6gGHz i7 in 16Gb.
In reply to REALLY!?!? While I'm… by [DELETED] 1831606
For the record, I have never thought it was Mac-specific, it's always been pretty apparent to me it's was just a question of limited resources (RAM and/or CPU cycles). But perhaps something about macOS does require higher specs to get decent playback. I've had problems on Windows with 2GB or 4GB RAM, but not with 8GB, for example.
In reply to For the record, I have never… by Marc Sabatella
Excuse me, but you've never confessed that before, insisting that I must have had rogue processes interacting in an odd way. It is also curious how it did not start happening until it did, without changes to your playback engine. We did try an older soundfont, but that didn't do it, if you recall. And there is this odd "workaround" of pre-playing the passage so affected. But it was even affecting notes as they were typed in. The old mac was 8gb.
In reply to Excuse me, but you've never… by [DELETED] 1831606
"Rogue processes" is not a term I recall having used, but sure, suggesting there may be other processes on your system competing for resources is just another way of saying that you don't have enough resources. Two sides of the same coin. The problem has always very obviously been, MuseScore not having enough resources available, due to the combination of the total amount of resources on the system and the other processes competing for them. That's why the problem exists sometimes and not others - in any resource-limited system, you'll run into problems depending on what else is going on. Sorry if somehow this wasn't as clear as it could have been.
In reply to "Rogue processes" is not a… by Marc Sabatella
OK.
Hey, my new computer has said, "So you didn't like our stuttering, eh...?". Twice in its first three days I was editing in MS3 and all of a sudden notes play dozens of times too fast, like a mag tape at high speed, and jump around. Thinking I've hit an MS bug, I went to Firefox, and then ITunes -- and guess what -- all audio on the machine was corrupted in that way. Reboot fixed it (very fast on new machine), but I am scared that this might be a hardware defect in the new machine, let alone a bug in MS that corrupts the OS. I can't find anything like "Mac timer problem" etc on the web.
OS: macOS 10.14, Arch.: x86_64, MuseScore version (64-bit): 3.0.2.20666, revision: 8ca4d2c