Nice, didn’t see that before. Thanks!
Anyone know if their are any sale’s coming up for fors???
I want everything they got but i don’t see any bundles so figured Maybe could be a sale soon?
Hi! Has anyone tried using Opal with max 9.0.5? Is it just me or does the randomization not work properly, meaning it doesn’t place any triggers in any of the channels?
Yes, I see the same thing. In fact pushing randomise for Gem removed the one trig I had added to audition the sound, so there was nothing at all.
In fact, I now can’t add any trigs to Gem after trying randomise.
Aargh! wrote an email already, no answer yet… hope it’s an easy fix — I love Opal randomization
Yep, similar issue here - the max window is filling up with “no dictionary named step_n, cannot access values” whenever I try to edit a step. Doesn’t appear to be relevant just to randomisation, it happens from the start whenever I open an instance whether or not I’ve randomised?
Max 9 is not currently supported– it’s still in beta with regards to running it in Live.
I’ve tracked down why the issue happens but I’m not sure if this is an issue on my end or if it’s a regression in Max 9.0.5. This was working fine up until 9.0.4 as far as I can tell.
Unfortunately the release notes doesn’t mention the Dict object, so I’m not sure what changed or why this new issue occurs. Regardless will look into it and make sure this all works for the official release of Ableton Live 12.2 which introduces Max 9 as the bundled Max for Live version.
9 Likes
That would be a great oppurtunity to roll out that Opal scale/quantiser feature 
2 Likes
Thanks for the reply! Hopefully it will come soon, I have some devices that only work on Max 9 and one that specifically works on 9.0.5 only (Dillon Bastan’s Pathways)… I think I’ll have to jump between versions for the next few months haha
And yes scale/quantizer will be very welcome 
Gotcha! Yeah sorry for the annoyance– I try my best to make our devices fully compatible with the bundled version of Max down to Live 10, so this is why I haven’t prioritized making it Max 9 compatible yet since it’s still in a beta phase. Right now it’s unclear whether these issues stem from something on my end or if it’s a bug in Max.
3 Likes
Yes it is absolutely understandable! I shouldn’t have jumped so impulsively into Max 9’s boat (I’m always too hungry for news and I pay the consequences). I hope you can easily discover the bug before the official release of Live 12.2. Have a nice evening!
I guess anyone having issues can always download Max 8 and use it instead of the bundled version.
If you run 12.1.10 (i.e. the release version of Live) it still uses Max 8 as its bundled version so Opal runs as normal. Can parallel install with the beta.
FYI have been talking to Cycling74 about these issues and it will be fixed in 9.0.6. 
15 Likes
I just fed Opal’s Max console logs and the release notes for Max 9.0.5 to ChatGPT and tracked down the issue.
Max 9.0.5 release notes mention:
dict: setparse parses arrays and strings correctly
Searching for setparse found the line
setparse(XYZ, "")
in multiple JS files. The change to setparse in 9.0.5 made the parsing stricter, so setparse no longer accepts empty string. Replacing the empty string in setparse,
setparse(XYZ, "{}")
with an empty Dict object “{}” in all JS files fixed the problem, the sequencer in Opal works again!
5 Likes
Haha, I’m surprised ChatGPT knows anything about Max, let alone this insight. Used to be terrible at it.
But yeah, that’s the gist of it– but in any case 9.0.6 will be backwards compatible so an update to Opal will not be necessary. (The strictness was introduced because setparse had some issues that were addressed, which effectively “broke” Opal)
3 Likes
New beta today :
- Updated Max 9.0.6 to d455507:
- dict.deserialize: fixed no output on invalid data regression
- JS Dict.setparse(): fixed empty string as empty object regressions
- live.push: attributes/attrui fixes when used outside of Live
- MFL: disable global zoom
- pattrstorage: fixed crash after purge when restoring slots
- pattrstorage: fixed saving vst~ settings when store is called
- thispoly~: mute resets busy (fixes adsr~ usage)
- v8: fixed Live observer issues after new v8 instance
4 Likes
Hey, does anyone else experience the issue with Opal Ctl not saving locks / settings / anything when saving and closing a project?
Is that a known issue? I read in this thread that currently there are some max4live related issues, could that be a reason and if so, is there a fix coming in the foreseeable future?
It’s a shame cause recently I built some cool randomizer synths with Opal Ctl, it’s pretty powerful. But in the current state you have to bounce if you wanna keep the sequence.
Another unrelated question, does Opal not randomize pitch ? When hitting the random button I noticed that a #C just changes the octave, becoming a #c-3 or something, but it doesn’t change to a different note. Am I overseeing something?
Greetings , Markus
Did you email us about this? Sorry I’ve been a bit slow, we had this Intonal festival in Malmö all of last week where Felisha and other friends were playing so that took up a lot of time – and then we got hit with some sort of cold after, haha…
In any case, will look into this today. I’ll email you back to troubleshoot/pin down the issue.
FWIW doesn’t seem to happen on my end, and haven’t gotten other emails about it so could be a Max version/setup issue but will try to figure out what could be going on.
3 Likes