On 3/17/2014 3:06 AM, Ruchit Agrawal wrote: > Hello guys, > So following is a list of ideas that I have for GSOC project: > 1) Music Accompaniment feature for MuseScore > 2) Score similarity detector > 3) Speech recognizer and processor engine > 4) Fretboard/keyboard viewer
I should preface this by saying I'm not a "core developer" and have no idea what my role, if any, might be in the decision-making process. But since I'm a potential mentor, I figure my opinion is worth something at least. I definitely support #1 if it is accomplished through integration with Impro-Visor or some other similar software. Actually building sophisticated accompaniment features into MuseScore is rather out of scope, and building unsophisticated accompaniment features into MuseScore is perhaps not worth the effort. The goal for me is so I could create a score that left rhythm section parts as chord symbols and slashes (eg, a typical jazz or rock band arrangement) but when I hit "play", some automatic accompaniment was provided so I could get a better idea of how my score will really sound when played by real musicians. For #3, there is absolutely no way I can see speech recognition having anything whatsoever to do with MuseScore. To me, that's a complete non-starter. As discussed earlier, speech recognition is a completely separately project that is more OS-level. Now, the idea of having some sort of console window in MuseScore where you could enter commands as text - whether that text is generated by your fingers on a keyboard or by your favorite completely separate speech-to-text utility is completely - is moderately interesting, if a bit esoteric. I think more useful than being able to *enter commands* this way would be the ability to *ask questions* - to search the online help. Again, though, this seems decidedly like a totally separate thing to me: a general purpose online help system. I really can't see any reason why a music notation program should be trying to solve this kind of problem independently. There are enough problems left to solve that actually relate to music notation. The other two could potentially be interesting depending on where you went with them. Score similarity detection seems like an interesting research project in itself; the trick would be figuring out what the practical application would be that made it seem relevant. As I mentioned before, it seems perhaps something more useful for musescore.com than for MuseScore itself, but that is not necessarily a deal-breaker. The fretboard/keyboard viewer seems like a gimmick to me unless it actually were part of some sort of teaching facility, which starts to feel out of scope again. On the other hand, Finale has "SmartMusic", which I've never really looked at so I don't know what it does, but I guess it is somehow related and appears to be successful. For MuseScore to make real inroads into schools, some sort of associated education tools could help. But I'm pretty sure the fretboard/keyboard viewer isn't where I'd *start* if that were my goal. So I'm back to thinking of it as a minor gimmick. I tend to be focused on making MuseScore better at its primary purpose: creating scores. Things that make the playback sound better for the purpose of checking your work or generating demos are good too. Things that try to turn MuseScore into some sort of generalized practice tool seem out of scope to me, even if, again, I could see this being a future direction for companion products. Marc ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ Mscore-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer
