But being a 100% honest, the updates broke all the patches I had started with PatchSeq.
Same here. They do look different. E.g. Output module is occasionally replaced by Mix6 in my previously saved selection and presets. I’m looking forward to the latest updates anyway. Hopefully there won’t be many changes…
mini modules were replaced with other minimodules, and they had extremely diff results
its mostly annoying on the fm patch I spent a lot of time with and was really too complex to unravel and begin again, its just that backwards compatibility should be preserved when possible, I know these were hot to get out in front of users, but paid modules so go thru patchers beta testing to weed out all these little issues really, right?
It’s likely due to the fact that modules and ports are referenced by index, instead of the proper way – by UUID. This is an approach that I’ve since fixed with the Groovebox Advanced, but needs to updated for the PatchSeq as well.
My sincere apologies. You might be thinking, “Voxglitch is great, but Bret’s not paying enough attention to keeping his modules properly tested and backwards compatible.” And that’s totally true, and every time I get a bug report it feels like a mini existential crisis.
So maybe for the next few days I’ll just focus on setting up more automation so I can easily run compatibility tests, unit tests, etc. So far I’ve been able to run amok with my free modules, but commercial modules carry higher expectations.
There comes a time when to advance a module, it’s best to call it done and freeze it, and make a new one with a diffrent slug. The tricky part is knowing just when you’ve reached that point.
Sorry, I’ve just been super busy. It might take a few more days for me to respond. It’s all about attention management right now. What’s on my mind right now:
An update to Centralics, which addresses some requests and deficiencies in the module
But then, I should have time to swing back to this. Groovebox Advanced isn’t pressing since it has no strict due date, and there’s a ton of work to be done on it.
A notable update that’s already been done to the PatchSeq is how the patches are stored. In the new implementation, additions to the inner-modules ports won’t break existing patches. Things might be a bit rocky for the next few releases, but I’ll do my best to smooth them out.
Now it’s getting even crazier. Today I started Rack and got updates from Voxglich. It’s always cool to get updates. But as the picture shows… What is Groovebox Advance doing in my library? I didn’t buy or order it. Then Centralics is in my library, which is nice, but I didn’t buy that either. Neither of them work either.
All of these are theoretically done. However, I have to go through and test each one next. But I wanted to let you know that these features are on the way.
Thanks. I agree 100%. I spent a great deal of time nailing that behavior for my dedicated sequencer modules, and I’ll try to pull over the logic to the newer Voxglitch Devices modules.
wtf it;a even not released yet (?)
Or im did miss something.
are theoretically done. However, I have to go through and test each one next. But I wanted to let you know that these features are on the way. 