Dorico 8va4/13/2023 ![]() There is also another bug here already reported above, namely in the chord layer again the ties into the following bars are again missing.Īlso, the first melody note of the second bar is too short. (Whether or not this can actually be performed by the relevant instrument should not be of a concern to Synfire, I feel.) I would like to see that the notation export retains exactly what is contained in the Synfire figures, i.e., the full 4 chord tones should be sustained for their full duration, and the simultaneous melody should happen in a *separate voice*, partly using the same pitches. On the other hand, the "stolen" chord tones are then too short. ![]() ![]() In the second bar, the melody "steals" even more chord tones. The melody starts too early and takes over two of the first chord tones. Synfire instead partially merges these two layers. One 1/8-beat later the melody should enter, and the melody should be purely monophonic. The first bar should (after the rest) start with a four-note chord, and this chord should then be sustained. I actually tried to somewhat separate the pitch range of the simultaneous figures, but on purposes I did this only partially, there is still some overlap, and seemingly this pitch overlap is what causes Synfire to struggle. In the resulting notation, Synfire fails to separate the two layers. There are simultaneously sustained chords here and a melody. The next example involves figures layered in the same track and export staff. This will save me a lot of time and make a quick fix more likely. Also tonally, something that exposes current bugs. Something with a reasonable amount of triplets and quintuplets, 16th, 32th, syncopes (please only music that humans can actually play). In order to do tests, I need a few short example arrangements that you care about. So if you are really disciplined and have a clean notation-friendly composition from the start, you can skip this altogether. The plan is to separate the pre-processing from the export. These quantization and filtering options are bloating the settings and make them difficult to understand and optimize. The issue with current export is that Synfire attempts to quantize a human-like (or randomly generated) performance into something that lends itself to readable notation, before doing the actual export. We have quite a lot feedback on this topic in several threads, so I wanted to focus this here. The next update will bring a few improvements, albeit more needs to be done.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |