Bug Description
After the song loops round to the beginning and replays After an amount of patterns have played; the FAD trigs in a sequence become played notes.
I’ve played about with this and it seems to be after about 6 patterns have played through although I’m not convinced this is the trigger for it.
I’ve attached another project file (obeisant stamp_150824.zip (2.4 MB)) where it happens around the second drop of what I’m playing about with, if you just load the project and play from Pattern 24/25 it doesn’t happen but playing through from the start or from a few patterns before it will start doing the FAD trigs.
Reproduction Steps
I’ve attached the project file this happens on. This bug seems project-specific as it hasn’t happened on others.
Play attached project through and FAD become notes on second or later play, this specifically happens on Track 10 of the project, monophonic VAP instrument.
Occurrence
Always for that project.
Found in
- Version: 2.0.0
- Build: 995
Attachments
obeisant stamp.zip (2.4 MB)
Additional Bug Observations
Track 7: Filter LFO note FX can have some ‘overhang’ and modify the base filter value as the song plays, leading to inconsistencies in filter frequency as the song plays.
Using step FX to modify the synth macros also doesn’t correctly reset it’s parameters once the note is complete. Using FAD/CUT/OFF to close it off didn’t seem to reset either.
You can mitigate this with further note FX for the macro on a later note in the sequence but it feels imprecise to do this as it doesn’t return to the patch settings.
I have noticed that using chord FX on some of the instruments can cause extremely high CPU usage, using the FAT synth and playing a chord results in an immediate red bar/overload with minimal other instruments running.
I don’t have examples for the last two points in the supplied project but these are probably quite easy to reproduce.