Android production workflow suggestions

• Apr 13, 2019 - 18:21

Fellow phone lovers--

I've made so much progress breaking free of the desktop in other life areas that it's chronically frustrating to still need the desktop for music production.

Musescore's progress over the last five years has been astounding. On the desktop. 🙂

I understand a bit about the hardware architecture problems. Sigh.

Here's what my current workflow looks like, curious if anyone has ideas about how to Androidize it.

• Start in Musescore on Windows. Deliverables: musicxml, midi, occasionally PDF. Tried lilypond on Android, but I struggle to work that way and lilypond doesn't play well with musicxml (conversion to lilypond introduces rhythmic errors, and Frescobaldi (on Windows 💻) chokes too often on the return trip to musicxml).

• Convert midi to wav with sforzando on Windows. Easy, simple tool that doesn't make me think.

• Head back to Android to finish mixing with Sox.

Not an emergency, it's just amazing that nobody else seems to mind still depending on the desktop (after 12 years of iPhones). Have you ever gone for a long hike and found music inspiration from nature? I am not lugging a laptop that whole way. 🙂


It's encouraging that Musescore 2 works on Lxqt on UserLAnd on Android. Note entry is tedious because the keyboard is broken in some apps (Xkeyboard/TightVNC issue). No sound or synthesizer, but sound export works with the built in soundfont.

(Not quite ready to uninstall Chrome Remote Desktop yet.)

In reply to by andrewjosephpf…

A full MS2 on Android would be great – worth paying for. It would be so nice to simply switch between Android and Windows with the same score by saving it to the cloud.

Chrome Remote Desktop is very good but you do need to have your desktop PC left on, which is not always convenient.

I currently use the Notepad feature in the Guitar Pro Android app if I don't have desktop access. MS can open guitar pro files so transfer to MS is easy.

In reply to by yonah_ag

Thanks for the tip. I don't use guitar or tablature myself, but lots of people would find that helpful.

The world is going mobile, but it's taking forever (it's not just Musescore).

It's a hardware architecture problem (though Qt is supposed to reach Android too--maybe just Android on desktop chips?).

It's a user interface problem. Mobile first design scales up better than traditional design scales down (but it takes a serious, resource-intensive disruption to redesign from the ground up).

It's a culture problem. Like lawyers, government workers, and journalists, musicians are fixated on paper. That's why it's going to take forever (maybe mnx can help) for a composer's deliverable to change from an A4 paper sheet (or, more backward yet, US letter size) to a responsive webpage. It's hard to ask Musescore to make such a big shift when people are still using Microsoft Word (!) and then printing it out (!?!).

First, we can learn music by reading the old PDFs off a tablet, then perform from memory as even Western musicians have already been doing for 200 years. 🙂 🌲🌳

In reply to by yonah_ag

I'd love to hear about how that goes. If a Windows device could run Android apps with enough phone functionality (sensors, calls, camera &c) and Windows desktop apps that would be intriguing. (The Windows Store still feels underdeveloped to me. ) Meanwhile, I guess Chrome Remote Desktop is what we have. 🙂

Mike, that's terrific that more musicians are going digital. A tablet with one of those pedals to control scrolling, that could save a lot of headache. This virtuoso violinist has enough to worry about without having to coordinate with a page-turner:

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