CANNOT DOWNLOAD WOODWINDS from MuseHub

• Nov 11, 2024 - 00:56

I cannot download woodwinds after upgrading to 4.4.3.
Unknown Error; could not complete download. happened 3 times.
Anyone know what to do?

Comments

• Nov 11, 2024 - 13:54

I don't have Musehub installed, but quick search I found you're not alone with this problem. I recommend posting to, or tracking one of these threads:

https://support.musehub.com/hc/en-gb/community/posts/22689388922141-Iss…

https://support.musehub.com/hc/en-gb/community/posts/21220116260125-Una…

Looks like Musehub support is done from a menu item within the MuseHub application. Alternatively, I found this link:

https://support.musehub.com/hc/en-gb/requests/new

I don't know if this workaround is a good one (or if he got past the failure just by retrying) -- something to monitor if someone posts a reliable solution.

https://www.reddit.com/r/Musescore/comments/1erodvk/unknown_error_could…

Reply

• Nov 12, 2024 - 11:26

A further attempt to d/l woodwinds resulted in the musestrings getting corrupted, somehow. They suddenly start playing col legno at will, ignoring text to pizz or arco. I suspect all files are infected. I cannot work this way.
Maybe I should delete MuseHub and download new? Go back to 4.4.2? Never sure. I hate clicking on things...that's what caused this.

Reply

• Nov 12, 2024 - 17:07

Sorry I can't help you fully as I only do Linux (we don't have a full Musehub). You have three things to keep up-to-date. Musescore app, Musehub app, and MuseSounds data. Mix of incompatible versions of these three may get you into trouble. I would first try updating Musehub (I think a minor bug fix is just being released, if not already -- see Discord).

On Linux version, where I see the icon menu of all the MuseSounds instrument classes, holding down [ALT] key turns the download "checkmark" buttons into a "trash can", allowing uninstall of individual instrument group. Perhaps try uninstalling Strings and Winds, then re-download.

Reply

• Nov 12, 2024 - 20:41

Thanks. I saw.
It seems the string problem was separate from the woodwinds. I have no woodwinds to uninstall. MuseHub showed a notification of an update about "fixes" so I clicked on it, though I am clueless as to what fixes. (This was after strings fix)
I tried yesterday to find what version of Hub I have, on the site and on my PC file. Nope.

I suppose I could try to download winds again while fixin supper. But Einstein warns about the futility of expecting different results...but he was wrong about quantum randomness...maybe

Reply

• Nov 13, 2024 - 03:13

Re the update about "fixes":

According to what I've seen in recent (past ~24-48 hours) posts, MuseHub released a version yesterday (11/11) that caused a problem for playing strings. All strings sounded as pizz. (?) MuseHub released still a newer version today (11/12) that supposedly fixed yesterday's problem. I don't use MuseHub Strings at all, so did not experience this; only repeating what other forum threads have reported. If you're interested, look at posts in the past ~24-48 hours with a subject line complaining about "pizzicato" on strings.

Sorry for duplicating, if this is something you had already found out.

Einstein's opinion on quantum randomness was exactly that: an opinion. He had no data to back his opinion. He knew so and stated this explicitly. On the futility of expecting different results, he had LOTS of data: so does everyone living :-D

Reply

• Nov 13, 2024 - 15:46

I did receive the string fix, but appreciate your response. I am now concerned solely on the woodwind downloads...will they fix that soon, I wonder.

I know it was an "opinion". He felt "God did not role dice", but then there's the question of who or what is God, which I do not want to get into here!
Even when he felt he goofed (cosmological constant) he ended up smelling like roses.

btw - a third try to d/l woodwinds resulted in same results. Now I think of Shroedinger's cat: maybe the woodwinds are "here" at the same time they are "not here". ;-)

Thanks!

Reply

• Nov 16, 2024 - 20:23

Last try was the same. Someone suggested I "switch folders". not sure what it means, but I did notice a file in my download folder.
Muse_Hub(4)EdV_WHpE.exe. a PART file. 41,000KB.

Could this be it, I wonder. If so, why did the download fail? Why didn't the others (strings, etc) end up here?
I cannot open (with default Applications\firefox.exe)
Do you have a suggestion? Or wait for a fix?

Reply

• Nov 16, 2024 - 21:57

Linux users get less-featured "Muse Sounds Manager" instead of "MuseHub" . On that, we have "Clear application cache" and "View application logs" buttons. If you have something like that in MuseHub, try them.

I recommend posting your MuseHub "log" file on MuseScore Discord "Support" channel along with short description of your problem -- there seems to be at least one dev for MuseHub there.

Unfortunately this (musescore.com) forum is likely not the best place for MuseHub support.

Reply

• Nov 18, 2024 - 14:35

  1. Seems a member responded to your help call - "force download the woodwinds". People interpret your non-response as problem solved, but didn't come back with a "thank you." You can still reply to this, like: "I'm not a computer expert, would you please explain step-by-step on how to 'force download the woodwinds' on MuseHub?" I posted how to do that with Linux above, but unable to help with Windows Musehub.

  2. Observation: for Musehub deep-dive Dominic is the dev/expert.

  3. Upper case not recommended - rather than yelling, perhaps intro with "Please help, my project has been stuck with this problem for over 2 weeks."

  4. Help those that help you, by posting your Windows, Musescore, and Musehub versions in your message. If you don't know how to find the Musehub version, that would be the first question to ask on Discord "how do I find version number of MuseHub." Perhaps, your recent Musehub upgrade failed without your knowledge, this may reveal it.

Reply

• Dec 1, 2024 - 14:55

FYI - I was able to finally get my woodwinds back - I downloaded in the early morning thinking it might be a low traffic time. I immediately noticed my speed increased and it worked.
I cannot be sure if it was a fix or the MS team did something, but I thought this might be useful to know.

Reply

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