> In other words, the work within MuseScore would consist of adding a > facility where a text string would be turned into a series of commands > to be processed. Whether that text string came from a user typing > versus speech-to-text is immaterial. It would be equally useful in both > scenarios.
And that's totally out of scope. Giving a list of possible actions, and interactions and a inputtext, make a sequence of actions that can be processed by MuseScore (or any other software which gave possible actions and their interaction) is for sure a nice project but it's totally out of MuseScore scope. It should be done separately. ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ Mscore-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer
