Top Groups

Discussions

Back button issue (bug), inconsistent, only top part of screen shown

After using the in app back button I see only the top part of the screen of "Songbook".
I have this issue on my S2 TAB in portrait mode. Once I turn my screen to landscape and back again, I have full screen again.

If I use the TAB back button, I am thrown back to "Your collections" after it flashes past the "Songbook" screen. In this case I have full screen.

If I start in landscape mode, the action of in app and TAB back button remains different, however in app now maintains full screen.

(Unfortunately I first posted at the wrong forum https://musescore.org/en/node/289477]

Dashboard issues

1. The text box appears, but the send button doesn't. This is especially annoYing whenever I type something really long and then the send button isn't there. Can this be fixed?
2. Possibly show private messages on the dashboard?
3. Maybe show all comments on dashboard. Sometimes it picks and chooses comments which sort of bugs me a bit
Thanks

You Tube, Chrome, and MuseScore

In response to a bug report of mine yesterday about what seems to have been a temporary problem, DanielR (his name doesn't at-sign complete) informed me that Chrome and/or YouTube (both Google products) have implemented a policy change that refuses to embed YouTube videos, which is the present MuseScore technology for coupling score playbacks to sounds produced by other means (e.g., advanced DAW's, Virtual Pipe Organs).  If that's, as Cronkite used to say "the way it is" forever, this is a massive setback.  Not so much for contributors to this site like myself, but for visitors directed to it who will have no idea what's going on when a carefully-produced score refuses to play. I have verified that a YT score which works in FF just hangs in Chrome.

If the report is accurate
, two courses of action present themselves. First, the site page scripting should detect this, and not offer the player bar, but instead, substitute a box saying "You-Tube backed score cannot be played on Google Chrome. Please use a different browser."

Secondly, the policy of prohibiting the MP3 upload connection of arbitrary, non-MS-produced sound to score playback needs reassessment in light of this development.  "Scores with good sound can't be played on Chrome" is a horrific state of affairs.  Is that true for Google Android as well?

This seems to be Google saying "You can't use YT content this way, at least as long as we have anything to say about it", and i wonder when the other shoe will drop and you won't be able to embed YT content at all, in any browser. If the report is accurate, YouTube is no longer a viable solution to pairing MuseScore with more capable performance engines.