Posted
Hi,
I have used 'Complete Chords' (successfully) to import files for a Harmony Library.
Now though, I see a crash that seems to be related to having used 'Complete Chords' in the past.
Here is a picture of the console before the crash, which took place immediately after a fresh start of Synfire followed by dragging in a single MIDI file to a Library window for static pitch import.
Those "Failed to match" messages are related to 'Complete Chords' , yes?
I have sent the crash report also.
I note that this all happens without me accessing during this session the UI dialog where 'Complete Chords' checked or not. Hence, it seems something is "left over" in a way that is causing an issue.
BTW, it looks like quite a bit of processing goes on prior to detecting that the user wants to 'Import All Tracks As Static Pitches (Fast)'. Just a thought, but would it make sense to ask immediately after a MIDI file is dropped on a Library window if 'Import All Tracks As Static Pitches (Fast)' is the goal, and if so, to skip all the other processing and go right to doing exactly and only that?
So., 21.01.2024 - 17:02 Permalink
That preprocessing before the dialog shows up is necessary to calculate what's on tack (number of voices, complexity, etc). Static import requires part of this information. It still has to estimate Harmony.
Yes, the crash is because of very large chords that can't be matched. Must be an edge case. Without the file it's difficult to fix.
So., 21.01.2024 - 18:08 Permalink
You need to disable "Complete Chords" unless the file really contains only sustained chords in root position, rather than overlapping notes and other sequences.
We'll put in a safeguard to protect against that.
Look in your Catalog and do View >> Show Temporary Items, you will be surprised what a mess this can cause.