Ableton Forum

Well i don't get those differences.
What stops you from patching BEAP live ?
What stops you from making a polyphonic BEAP patch ?
ok for the als.

Well the interface seems to be the main difference. He's obviously put a lot of work into making it user friendly for people who aren't Max savvy, whereas BEAP still feels like Max patching.

I'm interested to see how it's compared to the forthcoming "Integrated Modular System" from Bitwig.

"All 54 devices found in Bitwig Studio were designed using a modular device creation environment which is integrated in the application. Unlike other software, this feature is at the heart of the code running Bitwig Studio. In the next major release, anyone with Bitwig Studio will have access to the integrated Modular System, enabling the modification of existing devices, or the creation and design of entirely new ones."

I wouldn't compare the two. The Bitwig modular system sounds a lot more like Max For Live itself rather than a bunch of high level modules, which is what this and BEAP are.

wow the BEAP in max7 looks real nice. anyone know when M4L will be using max7?

Most likely when Live 10 is released, if history is any indicator.

Of course you can use Max 7 as the editor now if you have a full Max 7 license.

Oh but, duh, somehow I failed to mention that BEAP has been available long before 7. It's just become an official part of the Max package with 7.

Get it here for use in Max 6/M4L:

https://github.com/stretta/BEAP

So if you already own Reaktor, is this still relevant? Or is it just an alternative route?

Well it's built in M4L so that differentiates it from Reaktor from the get-go in that the possibilities for hackability are much greater and the potential for interaction between the OSCiLLOT modules and the Live API don't exist at all with Reaktor.

I read in the text that there are three devices included in the pack. Ok, what are they?

I haven't looked but I know one functions as an instrument and another as an audio effect. Stands to reason that the third would be a MIDI effect, which would conform to Live's own device scheme.

Those are just the larger devices though. The modules are code (likely bpatchers) that exist within the devices and are selectable via menus. There's a list of all the modules on the Max For Cats website.

chmurok wrote:It would be great if someone, who has already bought it (OSCiLLOT) made an YT video / review .

Yeah, would be great to see more.

stringtapper wrote:Well it's built in M4L so that differentiates it from Reaktor from the get-go in that the possibilities for hackability are much greater and the potential for interaction between the OSCiLLOT modules and the Live API don't exist at all with Reaktor.

This is an important point and I hope max for cats sells a bundle. I won't buy it on principle as I've just bought max 7 and I quite like the idea of making my own modular modules so I may have a look at the sdk down the road.

Are you talking of BEAP in MAX7 ? Cause it doesn't feel like max patching at all...

chapelier fou wrote:Are you talking of BEAP in MAX7 ? Cause it doesn't feel like max patching at all...

I'm talking about BEAP period. I've been using it since Max 6, before it was a part of the official Max content.

What I mean is that with Beap you're still working in an unlocked Max patch to work with it. I don't know exactly what Christian is doing with OSCiLLOT but it doesn't seem like its floating window works like a normal Max patch. But I will have to get it in order to see for sure.