Handbook 3 Chapter frontpage
I've been editing "Sound and playback" for days, only just find out each chapter has an individual page:
* contains a outdated list of links to subpages, which is a slice off the main TOC.
* hidden from TOC a link to a very useful page : How to restore sound if playback stops working
Why double handling? Wouldn't it also limit readers' freedom to scroll and wander around other chapters? eg cannot find Text in Notation Would it be better to move things to the main TOC, and point towrads it?
Comments
One is for the online manual only, the others are for the PDF version.
The latter doesn't get generated anymore, unfortunately, it used to get generated once every night.
In reply to One is for the online manual… by Jojo-Schmitz
Thank you for your explanation, and many thanks for your hard work touching up pages esp. the URL nodes conversion it is tedious.
In reply to Thank you for your… by msfp
.
In reply to Thank you for your… by msfp
See also https://musescore.org/en/print/book/export/html/278625, which is the full PDF version but as one big html page, not using that main page https://musescore.org/en/handbook
In reply to See also https://musescore… by Jojo-Schmitz
I see, thanks for the info. I didn't know about the pdf.
See #328598: PDF handbook generation stopped working
Anyway, with MuseScore 4 being just around the corner, further work on the MuseScore 3 handbook is not really needed
In reply to Anyway, with MuseScore 4… by Jojo-Schmitz
Unfortunately to run v4 I need a machine upgrade. I'm skeptical how many users are able to experience the beautiful new Sounds on their laptop/pad .
In reply to Unfortunately to run v4 I… by msfp
plus pages I edited so far do not have proper full v4 version written yet, I edit v3 pages with v4 in mind, hoping they could provide some reference for future v4 writers to copy and paste
In reply to Unfortunately to run v4 I… by msfp
It should run just fine on pretty much any computer sold in the past 5-10 years or so - longer for Windows and Linux than for macOS I guess. But probably 99% of users have machines that can run it. At most a $20 hard drive upgrade might be needed to install Muse Sounds.
In reply to It should run just fine on… by Marc Sabatella
I should have phrase it properly. Yes it runs on the (quite old) intel i5 v8 CPU and even low level Soc CPU. It's just a minute thing similar to the milliseconds latency issue of any MIDI keyboard: occasional lagging in UI, eg easing on sliding open of submenus; wait for menu population; and the delayed start and then 'stuttering' of playback. As much as I want to have all the fixes and great improvements on engraving and UI, let alone the new Sounds, it's become not enjoyable to use anymore at this stage , awaiting post beta optimization. Some app use terms 'Basic system requirement' and 'Recommended requirement' I've seen playback messed up happen on your Musescore Cafe channel I think you understand.
I am all for progress and devs: I have nothing but admiration for musicians contributing to free and open source, if your marketing strategy says 99% then I will go set myself back and match my CPU - I've had enough with fFinale monopoly and all those years of dev stagnation.
In reply to I should have phrase it… by msfp
Muse Hub: Win10 May 2020, but that's mostly the fault of the other MS: microsoft: upgrade need 20GB free space that's not possible. Makes you think what's really inside a OS, we sent astronauts in spaceships with floppy disks.
![musehubwin10support.png]( "musehubwin10support.png")
In reply to I should have phrase it… by msfp
If you are still experiencing these issues in recent builds, best to report them on GitHub as requested in the beta announcement. The developers have fixed tons of issues reported there over the past few months, but they can't fix what isn't reported.
For the record, I have not encountered anything like you describe, especially since the big performance boost changes were merged a week or two ago. BTW, my Café sessions are live streams, and the live streaming software is quite taxing of system resources, which can make MuseScore playback stutter. But MuseScore 4 is not affected more than 3 - actually rather less, since the performance changes went into effect (I haven't played any scores demonstrating this yet, but I will soon enough).
In reply to If you are still… by Marc Sabatella
Thanks for the great new, I didn't know about the performance boost, haven't used since beta announcement.
In reply to Thanks for the great new, I… by msfp
Multithreading was the big one that made a huge difference on all platforms, plus there was some sort of Windows-specific thing that eliminates (or greatly reduces) the need to go to preferences and increase the buffer size.