Noctuary 2.0.2
Journeys play what they load. During a journey the volume knob did nothing, no near event came,
a texture preset showed no grains, and most knobs seemed to have no function. One cause lay under
all four, and two more sat beside it.
Morph held the instrument at Init. The Journey row sits in the Morph section, and a closed
section shows only its switch, so the way to a journey was to switch Morph on. With Morph on, every
parameter is played from snapshots A and B rather than from the knobs, and both snapshots began at
the defaults. The volume, the near layer's level, the source type, every knob: all held at Init,
whatever was turned and whatever the journey loaded.
- A snapshot nobody has chosen now holds nothing and plays as the knobs stand. Switching Morph on
before choosing A or B changes nothing you hear, and choosing only B runs from what is playing now
to B. The box says "as played" instead of an Init that was never one. - The snapshots stay with the instrument across a preset change and a journey step. They used to
live in one of the two engines a crossfade moves between, and were gone after the first step. - A saved state remembers whether a slot was chosen. Older states wrote both slots every time, so
the session recall brought the trap back on every start; for those, a slot named Init counts as
not chosen. - The Morph section no longer closes. The Journey row is always there.
The map blend was the same kind of hold and is handled the same way: starting a journey switches
Morph, the route and the map blend off, so the journey's presets are what plays.
The volume knob now reaches both presets during a fade. While one preset fades into the next,
the leaving one keeps every setting it had, and the knob reached only the arriving one. A journey
fades for up to a minute and a half after a head start of up to eight seconds, so at every step the
knob did nothing at first and half of what it should afterwards. It now moves both, by the amount it
is turned, so the leaving preset's own level does not jump when the fade begins.
Near events still take their time: the first comes after roughly three quarters of a minute, and the
rest follow the near preset's Every, which for some packs is several minutes.
Every fix was first reproduced by a check that failed against the code before it, in the plugin
itself and on the path a journey takes. Nothing else changed: the presets and the sample library
are those of 2.0.0.