v1.3.2
Updated ZynAddSubFX from 3.0.6-determinism0 to 3.0.6-determinism1 to fix nondeterministic behaviour of ZynAddSubFX at runtime. See the changes between these two ZynAddSubFX versions here: white-axe/zynaddsubfx@3.0.6-determinism0...3.0.6-determinism1.
Specifically, this fixes nondeterministic results when exporting an Ardour project containing a ZynAddSubFX instance that uses LFO in ADsynth or PADsynth with "sync" enabled, since that option causes the LFO phase to be calculated based on global time instead of time since the note started playing. The problem was that the global time for the LFO was being calculated based on the time since the synthesizer was initialized. It's now the time since the first note was played.
Full Changelog: v1.3.1...v1.3.2
Image digest (skopeo inspect oci-archive:container-image-determination.tar | jq -er '.Digest'
):
sha256:0ef8d6806617765b05fbb0099232423bdfe2257bf0b6ff349adfe06b5c5fc41a
Image ID (skopeo inspect --raw oci-archive:container-image-determination.tar | jq -er '.config.digest'
):
sha256:2ad4518f640d590de0771e3dce358d4e15e12354dd692610833d4e3236d8afb8
SHA-256 hash of container-image-determination.tar:
sha256:ba4e3db736cee38e2c1cfac99600d0c889f4d0a5bb0d50a3cdb332867ed2e6da
SHA-256 hash of closure-determination.tar.zst:
sha256:3588665bf1470edd3b911e042d97b54e7e879cd40407dd937cf5a3e365ebed26