Patternflow v3.10.0
A heavy pattern comes on every time now. That is the one to reflash for.
Firmware core
- A pattern no longer gets refused while the memory it needed is free. If a
big pattern sometimes just didn't appear — dark panel, no error, a different
one each reboot — this was it. - Pushing a frame to the panel is about 14% cheaper. Origin goes from 72.5
to 78.2 fps. - Thumbnail work and installing or deleting a pattern left the render loop. An
upload that held the panel still for two seconds now holds it for about fifty
milliseconds. - Wi-Fi gets a moment to recover on the network it was using before it starts
cycling through your saved ones.POST /api/wifi/reconnectreconnects without
a reboot.
Audio · MIDI
Network MIDI runs as its own service, with queues that no longer wait on a heavy
pattern's next frame. Incoming automation is no longer echoed back out as
controller messages.
For pattern authors
api->alloc() is a zeroed allocation again, as the ABI has always documented —
it had briefly stopped clearing what it handed out. If your pattern looked wrong
on its first frames recently, this was probably why. The ABI is unchanged; your
existing .pfm files keep working.
Editions
Audio v0.6.0, Performance v0.2.5 and Clock v0.1.3 are all re-cut on this core.
Reflashing keeps your patterns, your Wi-Fi and your settings.