I’ve been waiting on 2.0 to come out of beta, however it sounds like there are a lot of new features and reasons to go to 2.0.
Is now a good time to jump on it or wait a bit longer?
Thanks
Yes, there is a lot there and stable.
It’s been great for me. I’ve ported a ton of new VCV plugins on there so lots to play with 
It also uses less CPU overall as there are some optimizations for larger patches
1 Like
I have been using it since I bought the module. I don’t know why anyone would want to be on 1.6 these days given all of the improvements, ported modules, and increased stability.
Don’t all airwindows plugins not work in the dev version?
They seem to be working fine for me
That’s good i was on a post 5 days ago where it wasn’t lol.
i think most of them work? galactic was still a bit buggy for me (no audio passing through it until i hit the ‘initialize’ button on it). although i haven’t tried it recently though. i’ve been substituting 2x 4ms freeverbs (with slightly different size/damp settings) for galatcit, which uses less cpu overall since they share the 2 cores, but also it still sounds pretty darn great imo.
1 Like
Thanks for the advice everyone.
Is there a way to sort the mm 2.0 plugins in vcv rack yet?
The early 1.0 plugins had a thing you could do that would allow showing only the mm plugins in vcv rack, that I have grown attached to.
Is there a target date for 2.0 out of beta?
I guess I might as well jump in, I’ve been waiting and mm has been idle…
Thanks again
1 Like
I dont think dev builds should be the recommended install for users.
if you get to that stage, then essentially the dev/beta has been ‘defacto’ released, but just with caveats of instability, thats not a good place to be.
as a dev, Ive personally held off on working on the MM, as I wanted a stable 2.0 release and sdk. because as a ‘dev’ branch, you really have no idea when it will be released… and as we have seen, its been a long road for the MM.
but its a tough call for @danngreen , they wanted to make large changes, and so the 1.x → 2.x is a bit of a migration, and its best to only do that once for both users and (3rd party) devs alike.
anyways, looks like we are reaching the end of the road, as I think dann did mention the dev release of 2.0 was a kind of release candidate, so hopefully we are not that far off now.
very exciting
1 Like
I don’t really think it is that big a deal for most users. 2.0-dev is at the release candidate stage, and the more people who are using it and torture testing it will make for a more stable final release. The number of new features and the greatly expanded array of modules make it worth it. It is easy enough to try it and see if it works for your use case. If it doesn’t, you can switch back to 1.6 in a few minutes.
Check out this post: I made a website to find MM modules in particular categories
I think they do now. The issue with them needing to be reset turned out to be that the default position of output level slider was 0. But that’s fixed now.
No hard date, just when the big bugs are all fixed.
There’s one remaining “big” bug, and I’m on that one. Still are issues with various plugins (which might be bugs in the firmware or the porting process) but as long as it’s not a problem in the core of the MM, then I’m ok with releasing v2.0 before those are fixed.
The main thing with v2.0 is that development is rapid. So you might see a bug, and then in the next version it’s fixed but you have to re-download new versions of all the plugins because the old versions are not compatible anymore. But, we’re getting pretty stable, so it’s close…
3 Likes
Thanks for replies, I’m going to try it shortly.
this sounds perfect…
as a dev Im generally happy with using dev/beta software and firmware.
but I avoid in my music setup, as when I go to make music I want to focus on that, its all to easy to fall into a trap of constantly updating things if you use betas etc… and that can take you out of the flow of actually making music.
(frankly, its bad enough, even using release software only ;))
so yeah, Im keen that 2.0 dev is released even if it has some known issues, or some plugins still need further updates.
hopefully after 2.0 the changes can be more incremental, so that the stable version can receive updates more readily.
I know that this worked with 1.0 modules to add them as favorites to VCV rack, which made making patches in VCV rack very easy. I have msg the maker of that asking about 2.0 beta modules.
The scripts are not version aware, but I have been using the beta for a few months now and I have not run into issues other than some of the very newly ported modules (that have only been ported to the new version of the SDK) not showing up as favorites.
Have you tried v2.x-dev yet?
yes, I have… but as above, went back as I didn’t want to be updating firmware/modules and patches and testing during my ‘music making’ time.
I already have my own firmwares (for numerous other modules) etc that Im testing/debugging, and find it very easy to get sidetracked doing this when Ive planned to be making music.
at the end of the day, I have to remind myself fairly regularly, I primarily bought my music gear (including MM) to make music, not as a tech/dev hobby
1 Like
I have been using 2.0 since I bought the module. The updates are not that big a deal and the dev software has been completely functional for the most part with very few showstoppers. I make most of my music these days in VCV rack, anyway. My MM rack is more of a learning and experimentation tool.