170 points by bennett_dev 3 days ago | 93 comments | View on ycombinator
jrickert 2 days ago |
iainctduncan 2 days ago |
The live object model is MUCH nicer to use in a lisp, as basically you do everything by making dynamic lists to represent what you want to access! There are examples in the Scheme for Max help file.
(Also, Scheme for Max can run in the scheduler thread, unlike JS in Max. Though of course calls to the Live API are deferred to the lower priority thread anyway)
bbgm 2 days ago |
This is just what I've been looking for. I never warmed to Max for Live for mods. But the extensions SDK I can get behind.
arikrahman 2 days ago |
abstractbill 2 days ago |
peteforde 2 days ago |
Far too much of Ableton's secret sauce is hidden away behind Max for Live and top-tier pricing only features. This is a great step in the right direction.
macscam 2 days ago |
krrishd 2 days ago |
nedt 2 days ago |
Biggest issue with having something so easy to work with is the huge amount of extensions we will be getting, which makes it harder to find the jewels.
Also wondering if we will get extensions for Abelton Move as well. There are already a couple of hacks that are adding functions that are running as a sidecar. This could give them an official API.
barcoder 2 days ago |
Time to see what's possible with the new SDK.
Lucasoato 2 days ago |
Try slowing the PSX opening sound by 5x to 10x, you won't regret it.
undefined 2 days ago |
moralestapia 2 days ago |
I applied for a job with them and proposed this exact thing about 8 years ago (got auto-rejected, I would've been very happy to work on it).
But I'm glad to see they finally did it.
honkycat 2 days ago |
It would be TRIVIAL in any other language, but noooo, I have to write a fucking max patch and deal with their trash visual syntax and runtime.
processing 2 days ago |
analogpixel 2 days ago |
My initial take on its strengths/weaknesses:
- Strong: Using the TS/JS ecosystem to render UI and tools
- Medium: Creating custom application windows in a web view. Window management features are pretty limited currently (can’t resize or render a native “close” button on the window chrome)
- Strong: Creating custom control panels for integrating with external services (like pushing and pulling audio clips or midi to/from an external service)
- Weak: Anything real-time, that’s still the domain of Max4Live or other control APIs, so don’t expect playback automation
- Medium: Tinkering with the Ableton project, clips, tracks, etc. API surface is still incomplete. Like I can read warp markers but not create them, for example. And I can’t access the global time signature settings.
The extensions are pretty aggressively sandboxed, and I appreciate that security consciousness in this season of the js ecosystem. It’s a hassle though if you want to save or load files outside of your little sandbox folder.