tcucinotta

you should have noticed by this time, that the project has also been made available as pre-compiled for both Linux and Windows; please, check the published releases at:https://github.com/tomcucinotta/MuseScore/releasesthanks, T.

please, post technical questions on the github tracker for the project at:https://github.com/tomcucinotta/MuseScore/issuesThanks.

Great that you've got it working, thanks for sharing :-)!Regarding the colors of the two hands, can you please open an issue in the github tracker and drop the question there ?https://github.com/tomcucinotta/MuseScore/issuesThanks, Tommaso.

I forgot: it would be very cool to see a picture of your hardware set-up :-)! feel free to share it.

hi there, happy to hear this comes useful to you! there's certainly a way to make these configurations persistent, and there's a number of other TODOs that deserve attention -- just I couldn't find the time to dig into these, as of yet! any contribution to the code would be very welcome of course :-)! however, stay tuned (the reference pointer is the LinkedIn page where I have the full tutorial on how to set the PianoTutor up), and hopefully some improvement to the code will come soon :-)!

in case you lost motivation and couldn't compile it, now there's a shortcut: binary installation for Linux as well as Windows :-)!https://github.com/tomcucinotta/MuseScore/releases

Now the modified MuseScore software is available as a binary release, for Ubuntu/Debian Linux as well as Windows:https://github.com/tomcucinotta/MuseScore/releases

Hi there,great to hear about your motivations, that's a perfect match with the reasons I shared the project ;-) !My Ubuntu version used to be 17.04, but now I'm using 17.10 without problems. Your problems with Q_NAMESPACE let me think of possible issues with the Qt development files set-up (perhaps you're missing some libqt*-dev packages?).On Ubuntu, these commands would normally pull all the needed dependencies:sudo apt-get build-dep musescoresudo apt-get build-dep musescore-commonLet me know if you run into further problems, I'm happy to help. For MuseScore-specifics, you might find quicker support on their own mailing list though!

Hi, your best friend is the MuseScore support pagehttps://musescore.org/en/supportand particularly the forum:https://musescore.org/en/forumas well as (dev) mailing list:http://dev-list.musescore.org/Please, let me know if you sort this out, thanks!

I see you found a nice hack to work around the problem of a bulky laptop on the piano ;-)... indeed the ideal one would be a 2-in-1 / 360 / convertible laptop (which I don't have either)

thanks!

The need for going more compact is understandable, although I'm seeing this best suited for a 360-degrees/convertible (possibly ultra-tiny) laptop, that can easily be placed on the piano bookstand.Anyway, I guess you're trying to:1) compile MuseScore on raspberrypi2) get rid of the Arduino .ino code, along with any trace of serial communication with it inside MuseScore3) replace the Arduino light driving logic with some NeoPixel libraries available directly for raspberrypi ?Perhaps if you could post your changes and/or make logs, I could try to help, otherwise I can't say much...

hi again, I made a few tuning attempts to chase the furthermost LEDs. I'd be curious to know what kind of LED stripe you have, but from the pic yours seems a set-up very similar to mine: standard piano/88-keys keyboard, 144 LEDs, mounted in 72+72, with some extra-space in between the two 72 halves. It turns out that, just adding to the code a little compensation for the extra space between the two 72-LED segments, the 2.0 scale factor that is currently used in the code (you see 144 on the dialog, but it becomes 144/72 = 2.0 internally) works just perfectly :-)!

cool, guess you won entitlement to click the "I made it!" button ;-)!about the offset for far away keys, you can compensate that by tweaking the "144" LEDs/meter scale factor within the tutor dialog: you can try slightly larger or smaller values; among my TODO, there's to enhance the wizard so that it asks additional one or two key presses, so that it can auto-adjust the scaling... in case you have further ideas, or get it to work in other ways, just let me know.

weird, perhaps a different version of the NeoPixel library ? I'm using this:version=1.1.2... and in this version including Adafruit_NeoPixel.h doesn't seem to have anything to do with Adafruit_CircuitPlayground/*, anyway, let me know how it goes, thanks...

forgot: please, ensure you switched to the piano-tutor branch after clone:git checkout piano-tutor

thanks! looking forward for your comments after the "I made it!" phase :-)!