exactly… and thats the trap I (personally!) need to be careful not to fall into.
Ive numerous module/controllers/synths etc that are open source and/or have apis that I develop for.
so at any particular time, I have to decide which Im currently ‘experimenting’ with, and which Im ‘just’ using for music making, otherwise Ive just I dont get any music making done.
from a dev side, Ive also been bitten, by developing against ‘dev versions’ of APIs, and having to rewrite code. so it just makes sense for me to wait for release versions before I focus on them for ‘experimentation’ esp. as Ive numerous other things I can play with until then.
so yeah, when 2.0 is released, then I will be excited to look at it, as 2.0 offers a lot of new api features Ive wanted - thats why I want it to move on from dev stage to release 
1 Like
Just tried out the beta and working modules shared on Dan’s recent post today and ran almost flawlessly.
Can’t wait for the final version.
Do the “unfiltered audio” plugins work on 2.0? I’ve really gotten into them and wouldn’t want to give them up.
sadly they have not been ported to 2.0 yet
Hello all! Super excited for the 2.0 release and have considered loading the dev build to explore the new modules ported over.
I gig with the Meta Module as my main voice in my modular setup so stability is very important to me. Is the latest 2.x dev release stable enough to gig with or should I switch back to my 1.x before I go to my gigs? I won’t have access to my laptop at my gigs, but I assume I can have both firmwares on the module and just switch back and forth from the settings menu on the module itself?
yes, you can switch back n’ forth without a laptop.
though patches/modules will not be compatible
so your best bet is, have 2 sdcards, one with stable, one with dev.
a release candidate has just been put out, so its a good time to ‘give it a go’.
but really depends on:
how much time you have to prepare?
… even if its was a new stable release, you’d want to throughly test before using live - there may be some oddities etc.
do you need new features? if not, no reason to rush.
if you have a bit of time… then you can give it a go, test it with your set, and build up confidence. all the time keeping your ‘backup’ ready to fallback to.
the time to be careful, is when you start changing your patches around etc on 2.0, in a way that you wont be able to go back to your older version - as you’ll probably not want to expend the effort to maintain both.
… but hopefully, at that stage you’ll already have confidence enough in 2.0.
1 Like
That’s a great idea! I hadn’t considered two sd cards. LOL!
That will give me confidence to fall back during a gig in case something happens. I do have other gear to cover me while I recover if needed.
I don’t NEED the new features, but I WANT them. 
My next gig is in two weeks so I should have time to explore and build patches on 2.x.
Thanks!
1 Like
just to be clear… when you switch cards you will need to flash the firmware.
it doesn’t run the firmware off the sdcard, but it can be there ‘ready to go’.
I’d personally not want to do this at a gig… as presumably, you’ll have practiced alot with ‘new setup’ to be confident in what you use.
rather, this approach means over the next couple of weeks, you have a fallback in case you find 2.0 has some issues.
note: also bare in mind, its not just the firmware your changing, but also new versions of modules etc… so theres a few ‘moving parts’ to be careful of.
1 Like
Thanks for letting me know. Will hopefully get comfortable with the 2.x dev build over the next couple of weeks before my next gig.
1 Like