gsequencer VS score

It's entirely GPL - the whole source code & build scripts are available on github, someone can trivially run the steps here: https://github.com/ossia/score/blob/master/.github/workflows... to make their own build of the software

> and at the end of the day LLVM compiles 30min and uses tens of GBs of RAM on average hardware

I mean, that's the initial build.

Here's my compile-edit-run cycle in https://ossia.io which is nearing 400kloc (with a free example of performance profiling, I haven't found anything like this whenever I had to profile python)

    C/C++ Header                      2212          29523          17227         200382

2.) Learning programming can be incredibly frustrating. You should not expect the same results in a VPL that you get in a DAW. DAW's are engineered very carefully and will almost always be better pieces of software than custom code. Making cues in a VPL is one of the more difficult aspects of writing computer music in a VPL and PD has not good solution that I know of built in besides reading a text file with different instructions (which you have to program how it is interpreted of course). There are some other companion solutions such as OSC sequencers like ossia score. I have used this software a number of times and found it helpful.

> And what would the helpful error dialog even say? „A problem has occurred and the app will now shut down“? From the user’s point of view, is that really an actionable or helpful error dialog?

Yes, literally - or even continue if you are running an event-driven app where the error may have happened as part of an event handler (and thus very limited to a very specific part of the software).

To give my own experience: I develop https://ossia.io and use this catch-all method. In 7 years I've gotten numerous thanks from the users for it not crashing but being able to carry forward. Not a single time I remember this to cause some memory corruption later.

It's not limiting on c++ version though - I'm building https://ossia.io with the very latest clang-14 on CentOS for instance, and ship that as an appimage - don't hear many complaints. My SDK is available if you wanna use it 😁

Most big media author apps are written with Qt. Da Vinci Resolve is a Qt app, so are Cubase, Maya, Substance stuff... Natron... Kdenlive... Qt is part of the standard toolkit for VFX apps if I'm not mistaken also. I'm developing a DAW/media art-ish app with it: https://ossia.io and am super happy with it.

https://ossia.io welcomes you if you are interested in media art, low latency, performance and reflective APIs :)

Working on a DAW, https://ossia.io