Hi, Maxim. As you suggested, I decided to subscribe MuseScore's developer mailing list, to ask a few question and give some more suggestions, regarding our previous conversation through comments on your blog.
First, let me say that your latest achievements (possible Alsa MIDI support, MIDI channels combination for instrument changes, and addition of MIDI Actions for all instruments) are great for MuseScore's future. As you said yourself: "MIDI Actions have a great potential and implementing it can lead to big changes in MuseScore. Maybe it will even have an automation tracks for the midi parameters: volume, pan, chorus...". I completely agree with your approach, and since we're talking about it, why not open the way for future implementation of automation tracks for any MIDI parameter (CCs, aftertouch, Pitch Bend, etc.)? Another thing, will these MIDI Actions include Note On/Note Off events, so they can act as MIDI keyswitch triggers? If so, this may be a killer feature for using a keyswitched sample library, directly! Maybe even with customized instruments.xml files for the library, everything could be automated, no, what do you think? Another possible use for such "hidden" Note On/Note Off messaging could be the possibility of allowing the playback of cluster chords with proper notation (not yet available in MuseScore) and those ornaments more complex present in the "Articulations & Ornaments" pallete, that aren't played back in current version. This new MIDI implementation might also bring back another thing that has been forgotten for sometime now. A few years ago, there was a DAW project, OOMidi, whose developers had the idea in their develpoment roadmap to integrate/interface their software (as main DAW application) directly with MuseScore (as main scoring application). But that project seams to have died (unfortunately, otherwise it may have become the best Linux DAW), and the integration idea was lost. Maybe now, with all this MIDI development, it may be possible to rethink it, and contact other DAW development teams to consider the same scenario, no? What do you think? That would solve many issues, regarding future playback/mixing development, which could be treated "in the shadows" by the DAW application, as "playback/mixing host", having a direct MIDI "pipeline" straight from MuseScore. Thus, future focus could be kept once again in pure notation development, but now with advanced MIDI possibilities. Now, for something more down to Earth, on your posts in the blog you mentioned that you changed MuseScore's file format to adapt it for the new features. The other day, I tried to open a test file I made with MuseScore 2.0, a nightly build prior to your changes, and it crashed a more recent nightly build. But when I opened another file (a self-made orchestral template) not containing any notes/notation, other then the staves with instruments names, all went fine. Do you think there is a connection? I also have some other possible "bugs" that I'd like to address, regarding MuseScore plugins (the ones I downloaded from MuseScore's site don't load in version 2.0, because they're ".js" and not ".qml") and custom time signatures not appearing in sidebar pallete. Where should I talk about these, should I post here, or on the Forum? As my final comment for now, have you or any other developer seen carefully this other MuseScore related project, from Emile Ellberger: http://blog.zhdk.ch/ssmn/, that has custom made palletes for MuseScore 2.0, for sound spatialization? For me, this seems like a modern composer's "heaven on earth"!! The only draw back is the fact that it is only for MacOSX. Could any developer consider asking them to share their research project with MuseScore's main release version, so that all Mscore users could benefit from this wonderful tool, maybe in a future 3.x version, or so? This could send MuseScore skyrocket in usage possibilities, that no other softwares (free or paid) have and would really show the power of open-source software development, when people unite their ideas and share their knowledge! Best regards -- View this message in context: http://dev-list.musescore.org/Improving-JACK-MIDI-Out-tp7578792p7578889.html Sent from the MuseScore Developer mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Mscore-developer mailing list Mscore-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mscore-developer
