hello! I've been using this for some time in my set so was devastated when the update to Max 9 stopped it working! has anyone yet updated it for the new system? My set totally crashed after the auto update a few weeks ago and I had to revert the version. Before diving in to editing, if anyone else has already fixed it, please let me know! Got the following from Ableton:
Based on what you’ve described, the issue is most likely related to the recent update to Max 9. This update introduced changes that can affect how certain Max for Live devices function, especially those with specific scripting or parameter routing.
It seems that the bcresonators device may need to be updated by its developer in order to be fully compatible with the new version.
Reverting to a previous Max version, as you've done, is a practical workaround for now. To avoid this happening again, keeping automatic updates disabled in both Live and Max is a good precaution.
In response to your questions:
Fixing the issue with M4L scripting
Without access to the internals of the device, it's difficult to offer a concrete fix. If you’re comfortable editing the patch, it may be worth checking how it interacts with Live’s API. For example, whether it's relying on object IDs or paths that might behave differently in Max 9. Sharing this information with the device developer might also help move things forward.
About a MIDI-controllable version of Resonators
We appreciate your feedback. Independent MIDI control over each resonator voice is something we've seen interest in from other users as well. While we can’t make any promises, future versions of Live may offer more flexibility in this area.
Alternatively, you could revert max to the latest Max 8.6.5 version and use this an editor in Live:
Please note though that this might bring risks with newer Max devices that were developed for Max 9. So the best approach would be to get the resonator device updated by their devs.
Let us know if anything else comes up, or if you'd like help rolling back or freezing your current Max version more permanently.
This website uses cookies.
Clicking “Accept” means you consent to your data being processed and you’ll let us use cookies and other technologies to process your personal information to personalize and enhance your experience.
Click “Close” to deny consent and continue with technically required cookies that are essential for the website to function.
Based on what you’ve described, the issue is most likely related to the recent update to Max 9. This update introduced changes that can affect how certain Max for Live devices function, especially those with specific scripting or parameter routing.
It seems that the bcresonators device may need to be updated by its developer in order to be fully compatible with the new version.
Reverting to a previous Max version, as you've done, is a practical workaround for now. To avoid this happening again, keeping automatic updates disabled in both Live and Max is a good precaution.
In response to your questions:
Fixing the issue with M4L scripting
Without access to the internals of the device, it's difficult to offer a concrete fix. If you’re comfortable editing the patch, it may be worth checking how it interacts with Live’s API. For example, whether it's relying on object IDs or paths that might behave differently in Max 9. Sharing this information with the device developer might also help move things forward.
About a MIDI-controllable version of Resonators
We appreciate your feedback. Independent MIDI control over each resonator voice is something we've seen interest in from other users as well. While we can’t make any promises, future versions of Live may offer more flexibility in this area.
Alternatively, you could revert max to the latest Max 8.6.5 version and use this an editor in Live:
https://downloads.cdn.cycling74.com/max8/Max865_241008.dmg
Here is how to set this:
Using a separate Max for Live installation
Please note though that this might bring risks with newer Max devices that were developed for Max 9. So the best approach would be to get the resonator device updated by their devs.
Let us know if anything else comes up, or if you'd like help rolling back or freezing your current Max version more permanently.
All the best,
Marcus