Posted
For a longer time I assumed this error in Synfire Pro to exist. Today I was able to safely reproduce it.
For triggering this bug, one may do the following:
- Open Synfire Pro
- Insert a library phrase in the default instrument of the default container
- Synfire indicates the presence of vector data, e.g. inherited sustain pedal events
- Inspection shows that a certain pattern of pedal action has been inherited from "somewhere" (Stammcontainer)
- after overwriting the data with a single zero, Synfire indicates that this container now has its own empty sustain pedal data
- create a sub-container and examine its sustain pedal vector
- it's again inherited from the Stammcontainer (root container?) and contains pedal action
I captured the bug in the video linked below:
Sun, 2011-02-06 - 19:51 Permalink
Hm. In the situation you describe, the sustain vector you are seeing is not inherited. It is generated by the interpretation's auto pedal feature, i.e. it depends on the figure. Turn off that feature, if you want a manual sustain parameter for that instrument.
Tue, 2011-02-08 - 05:32 Permalink
Seems this is not a bug but a feature. Sorry for pointing out this as an error by mistake.
I knew there was some option for having Synfire generate pedal events on its own but I did not suspect it to be in the preset dialog of the interpretation vector inspector. Now I know what to do when suddenly there are clusters of overlapping dissonant notes. :oops: