BEAP issues - Parameters and Settings are not saved in BEAP objects
So i encountered a problem with BEAP; some of the patches lose their parameters (gigaverb, compressor and classroom filter) after saving and reopening.
That's so annoying because i'm using them for a sounddesign of very particular noises (steam bursts and pressure sounds) and redialing the knobs each time i open my project is just one hell of a mess. Is that a known issue with BEAP ? I'm using max 7.0.6 on mac and 7.0.1 on a 64bit PC.
Resolved: I had to check the "Embed Patcher in Parent" option in the inspector to make it work.
EDIT: Did not work for every BEAP object. The problem is still there! HELP!
Did you check if all the objects in the Beap modules are pattr exposed ?
Did you check if all the parameters in the Beap modules are pattr exposed ?
Hi Alex, maybe you've already found a solution...
I had the same problem, and I found that the object vizzie/preset/starter works for Beap objects.
Hope it can be useful
Simón
Hi Simón,
Thanks for posting that, seems to work so far
Best
Mark
Sorry, hold that, I can't say for sure, patch that I tried it in now won't sync with my sequencer.
Ugh. Just had my heart broken by improperly saved BEAP patch using Max for Live. Would have thought that saving from the file menu in the Max for Live editor would result in a Max patch that opens up in the same state it was saved and closed. Nope. All sequencers switched back to default patterns and switched back from trigger to transport, LFO and OSC frequencies returned to defaults. So many things returned to default values that it would be impossible to recreate my monstrosity in all its original glory. This problem only affects Max for Live as far as I can tell, not Max standalone.
I can reproduce this consistently. I can save a patch (in the Max for Live editor) containing only the BEAP oscillator with its frequency offset changed, and even save a snapshot (or not). When I close and reopen, frequency offset is returned to default, and snapshot is gone. Doesn't seem to matter if I save locked or unlocked, frozen or unfrozen, presentation or not. As I said, this only happens when using the Max for Live editor. When using Max standalone, it saves properly, and will even open properly if loaded later from within the Max for Live editor.
Man, I had such a lovely patch going on. Was looking forward to showing my wife when she got home, and my students next week in class.
I could really love these BEAP modules in Max for Live if I could get them to save properly. I've had this same problem for the entire 1.5 years I've been using BEAP in Max for Live, every version between then and the current version, on both Mac and Windows machines. I continue to teach with it, but I suffer. Unfortunately, the school does not have Max standalone licenses, but only Ableton Live Suite licenses (which include Max for Live).
Ah, well, seems my issue boils down to RTFM. Cycling '74 support kindly explained to me that in the Live context, the saved state of a device is controlled by the Live set - saving an amxd device does not contain the saved state of parameters and will resort to default setting in BEAP unless I've saved the device as part of the Live set or made a preset for it. It was suggested that my workflow should be first to save the Live set, then open a new patcher and save that, add BEAP modules and edit their settings, save the device, close it and save the Live set, and that I can also save the state by making a preset of the device. I haven't had a chance to try any of this yet, but it makes sense that my problem was due to pilot error rather than a bug, which if real, would have long ago resulted in many people screaming bloody murder long before I got around to it. ;-)
,