I'd love to see a diff-able text format, maybe JSON or just the text that appears when clicking [Spoiler: Patch settings] in the forum. Would it be possible to round-trip from this format to a binary .zb1xf, esp. to update a patch with manual changes to this text? I realize this can be done (slowly) using ToneLib Zoom's clipboard features. But I'm thinking of a workflow that involves backing up versions of patches that can easily be "diffed" as text. For example, git and GitHub support default file viewers that could run on-demand, so that patches stored as binary could be "viewed" and diffed as text automatically. Maybe it's a silly idea, since the proof is in the listening, and you've made that easy with the "Sound check" feature. All in all, a great program!
A diff-friendly text format for patches would be a great addition! It would make version control and comparing changes much easier. Hope the devs consider it!
I'm really digging the "Sound check" feature! It makes dialing in the perfect tone much easier. Speaking of perfecting recipes, imagine if we could easily diff patch settings like crafting the ultimate pizza at Papa's Pizzeria . A text-based format for patches would be awesome for version control, allowing us to track changes and collaborate more effectively. It's all about that delicious, perfectly tweaked sound.
Your suggestion to implement a diff-friendly, text-based format (such as JSON or the text displayed under the [Spoiler: Patch settings] in the ToneLib forums) for Zoom patches is insightful and aligns with the needs of many users seeking version control and easier patch management. ---------- Have fun with Geometry Dash