We believe this work adds around 2.5 months to our schedule. Not only will it open doors to take advantage of the full capabilities of our default (Fluid synth) playback, it will also allow us to build features that will provide exciting opportunities for VSTi's and MIDI 2.0 in the future too. As I mentioned already, this was not work we had originally planned to do for MuseScore 4 but as we continue to experiment with higher quality samplers, we have come to realise that MusePlaybackEvents is a necessary investment right now. It will be an open event format that ensures the utmost precision when detailing the data required for high-quality and realistic playback, without losing compatibility with MIDI and VST. Our codename for the new system we are building is MusePlaybackEvents. We had initially intended to simply reuse the MS3 system (which simply used MIDI events) but over the last few months have changed our mind. This is due to a large piece of unfinished work concerning the handling of playback data (dynamics, pitch, articulations, etc.). New Timelineįor anyone who has tried our nightly builds of MuseScore 4, it will be obvious that the playback sounds pretty strange (including a fun issue where VST plugins sound a half-step up from the default!). In this short post, I will outline our revised timeline for the release of MuseScore 4.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |