Erich Keil

Been digging around through BEAP and am running into the problem that my knob tweaks and sequencer fiddles don't seem to store with the patch. I'm using nothing but BEAP modules 'out of the box' and if I set notes in the sequencer or fiddle knobs on my oscillators, most or all of them reset after I save, quit, and relaunch the patch. According to the model curriculum I followed online those settings should save with the patch. My forum digging has lead me to look for an object called bp.Presets.maxpat but I can't find that anywhere in my Max 7.0.6 install. What appears to be Max 6 documentation refers to the 'Beap Master' menu where I can find said presets object, but master doesn't show up as a category in my beap modules quick menu or in the 'paste from' contextual menu. The only preset object I can find is the stock (non-beap) "preset" object which requires connections I can't seem to make function with Beap modules....Is there something I'm missing here? The new snapshot functionality doesn't seem to apply to Beap modules anywhere I can figure. Any help would be much appreciated. Thanks!

Hi All,
Been digging around through BEAP and am running into the problem that my knob tweaks and sequencer fiddles don't seem to store with the patch. I'm using nothing but BEAP modules 'out of the box' and if I set notes in the sequencer or fiddle knobs on my oscillators, most or all of them reset after I save, quit, and relaunch the patch. According to the model curriculum I followed online those settings should save with the patch. My forum digging has lead me to look for an object called bp.Presets.maxpat but I can't find that anywhere in my Max 7.0.6 install. What appears to be Max 6 documentation refers to the 'Beap Master' menu where I can find said presets object, but master doesn't show up as a category in my beap modules quick menu or in the 'paste from' contextual menu. The only preset object I can find is the stock (non-beap) "preset" object which requires connections I can't seem to make function with Beap modules....Is there something I'm missing here? The new snapshot functionality doesn't seem to apply to Beap modules anywhere I can figure. Any help would be much appreciated. Thanks!

beap-snapshotssaved-states-not-saving

I was having the same problem. You need to enable the 'autosave snapshot' feature in the patcher inspector.

At first my patcher inspector didn't seem to give me the option, but after quickly popping a normal vst plug-in from the menu on the left into the patch and then deleting it again, I was able to find and turn on the 'autosave snapshot'. Now the BEAP states save as they should.

I was having the same problem. You need to enable the 'autosave snapshot' feature in the patcher inspector.
At first my patcher inspector didn't seem to give me the option, but after quickly popping a normal vst plug-in from the menu on the left into the patch and then deleting it again, I was able to find and turn on the 'autosave snapshot'. Now the BEAP states save as they should.

I don't where the problem lies, or maybe it was pre-7.1 (but snapshot appeared with 7.1 didn't they ?) I can bring and save BEAP modules state using snapshot without doing anything special, and the 'autosave snapshot' isn't activated... That is on a mpb OSX 10.8.5 Max 7.1.

BEAP Snapshots/Saved States not saving