I wouldn't mind it. As long as it was opt-in. It should be accompanied with a readme that asks me to enable it, and why/what they are going to do with the data, etc.What does the Pyra community make of the recent Audacity telemetry issue? I only really have Purism’s article and TLG’s video as points of reference but, given all the testing Pyra s/w is going under, I did wonder what perspective the Pyra community has on it?
The data going to Google (and when my session starts+ends) actually feels like giving google a better looksie on why I'm suddenly using their google.com to search for samples or searching for songs on youtube.com (because I'm recording things). So I'm negative about them using the easy-to-add google analytics (it's so easy to add).
Knowing Musescore, it also means that a paid version will be in the make. And that to make that paid version more attractive, they probably will remove that filter everybody* uses (or hopefully, create a better one, and entice people to upgrade while discouraging the opensource community to duplicate the paid filters)
Filters clearly depend on what you are doing:
Recording guitar and voice? noise reduction, reverb, eq
Creating mixtapes? Crossfader, normalize
Creating your own karaoke song? Voice removal (easier than manual split stereotrack, invert one channel and join them back)
Digitizing your tapes/LP's? Clickremoval and Repair
Finding reverse masked messages in songs? Reverse
Playing around? Pitch shift and what not
I guess that it will also show how people are using it. Ofc, I still use version 2.3.2 from 2018 (the Bleeding-edge version for Debian )
I also expect Debian to never present me with a version that wants telemetry.