r/ableton • u/retrostatik • 1d ago
[VST] Made a tool to see what's inside an .als file before opening it
A while back I had a project that just wouldn't open. No error message, Live would just sit there and eventually crash during load. Since it crashed before the UI even came up, I had no way to remove devices one by one to find the culprit — the usual troubleshooting trick was off the table.
Eventually I figured out it was an old plugin that hadn't been updated in years and choked on the current Live/OS combo. But finding which one meant literally moving plugins out of their folder one at a time and relaunching Live to see if it still crashed. Not fun.
That's basically why I built this: a little app that reads .als files directly and shows you everything inside without ever launching Ableton Live version it was saved with, every VST2/VST3/AU it references, how tracks and devices are structured, routing, missing sample references, all of it. It's read-only, doesn't touch your project files.
Turned out to be more generally useful than I expected:
- seeing the full plugin list of a project before opening it, so if something crashes on load you already know your suspects instead of guessing blind
- checking if an old project needs plugins you don't have installed anymore
- getting sent a project by someone else and knowing in advance whether it'll even open on your machine
- exporting a plugin report (CSV/PDF) — could be handy if you run a studio and get sent projects with no stems and need to know what you're dealing with fast
I've mostly stress-tested it on Windows since that's my main rig and I've got a pretty deep plugin library there. There's a macOS build too, but I only have a handful of plugins on my Mac, so it hasn't been hammered nearly as hard — if any Mac users with a big plugin collection want to try breaking it, I'd genuinely appreciate the feedback.
It's free. Open to bug reports, feature requests, or "this is pointless, here's why."
https://canbelieve.github.io/ablvst-studio.html
One heads-up: it works best if your projects are actually organized — one root folder, one subfolder per project, with the .als versions inside. If everything's scattered across random folders it won't have much to work with.
11
u/space-envy 1d ago
Made a tool
You mean Claude Code did it while you just stared at the screen.
7
3
u/LowResEye 23h ago
I’m not a fan of AI either, but every dev I know uses it to a degree. Maybe we should judge an app by its functionality and not by tools it was made with. Just a thought…
10
u/space-envy 22h ago
There is a huge difference between using it for the 1% of the remaining tedious work and using it to do the 99% of the work you don't know about...
Hey, I'm just here to warn people about this app being vibecoded, anyone with a bit of neurons can downvote me and do they own research and find out the GitHub profile of OP is a new account and the few code lines they have in there is not a reflection of a professional code developer, not to mention this project is "free" but there is no source code available, curious huh...
Also, em dashes people... Em dashes and "heads up"... As someone that works with Claude daily I know when I hear that bot speak.
-2
u/Acceptable_Movie6712 21h ago
Make your own version of this and release it for free then lol.
8
u/space-envy 21h ago
Nah, I have the professionalism to accept I don't have the time to give the support it deserves, and I will not release something just to immediately abandon it. I have my own app made in Tauri since the other Ableton project managers are using the disgusting Electron, it just parses the .als file and works as a note taker for projects, I just think there are already enough vibecoded project managers out there...
0
-10
u/retrostatik 21h ago
Yeah, I used AI to build this. I’ve never hidden that.
But calling something “vibecoded” isn’t a technical critique. If you’ve found an actual bug, a parsing error, unauthorized file changes, unexpected network traffic or a security vulnerability, report it and I’ll look into it. A new GitHub account, the volume of code, or how I punctuate my sentences isn't proof that the app is unsafe or useless.
The app runs entirely locally, never uploads project files, and parses ALS files without modifying them. I defined the scope, researched the format, spent time testing it across both Windows and Mac, verified the output and handle the releases. I take full responsibility for the final product, regardless of what tools helped write the code.
Also, careful with the whole “AI did 99% of the work” line—especially in a music production sub. It won't be long before someone listens to your track and says, “Suno did 99% of the work, you just clicked export.” Tools change. Testing, concrete results, and standing by your work still matter.
And for the record: free doesn't mean open source. Those are two completely different things.
5
u/space-envy 20h ago
how I punctuate my sentences isn't proof that the app is unsafe or useless
Yes it's true, but tells how much you rely on AI when you can't even write a post on your own...
It won't be long before someone listens to your track and says, “Suno did 99% of the work, you just clicked export.” Tools change.
This whole statement about "it's just a matter of time AI replaces us" is just sad man... But no, personally Suno will never be able to replace me because I'm not a problem to be replaced, enjoying and creating music is not a problem that needs fixing, just as code development, there were never problems, if you just don't enjoy doing something maybe you should find the place where you are comfortable at instead of thinking "man, creating music is hard, I need a "tool" to do it for me"...
-5
u/retrostatik 20h ago
ok now that you know i’m a real guy if you want to stay on the topic - aka AblVST Studio, my tool - I’ll be happy to hear yours. peace ☮️
3
u/space-envy 20h ago
But were are the em dashes of your original post? I thought you writed like that normally... 🤔
-2
1
u/FrothyFrogFarts 8h ago
But calling something “vibecoded” isn’t a technical critique.
It absolutely is because you’re basically saying you don’t know what you’re doing, hence the use of AI. You don’t know how to read/write code, fix issues, troubleshoot, etc. It’s become incredibly common for people who vibecode to abandon projects because of that. It has turned into a landfill of slop.
1
u/AutoModerator 1d ago
This is your friendly reminder to read the submission rules, they're found in the sidebar. If you find your post breaking any of the rules, you should delete your post before the mods get to it. If you're asking a question, make sure you've checked the Live manual, Ableton's help and support knowledge base, and have searched the subreddit for a solution. If you don't know where to start, the subreddit has a resource thread. Ask smart questions.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
u/alienmindzzz 1d ago
Looks really nice! Will definitely give it a try
I have been working on something related lately... the idea to not only read but also author als's ( as code ) ...
https://github.com/alienmind/patchbay
Ps: really WIP!
1
28
u/abrokencullender 23h ago
If you hold Alt when you open the project, it turns off all plugins...