libossia VS score

You can check out the code here: https://github.com/ossia/libossia/tree/master/src/ossia/audio ; feel free to use, it's LGPL

Here's an example: https://github.com/ossia/libossia/blob/master/examples/Editor/curve.cpp

> 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

For https://ossia.io I have developed multiple audio backends:

How are you building your code ? Here's my iteration time when working on the main codebase I'm on, https://github.com/ossia/score which is very template-heavy, uses boost, C++20 and a metric ton of header-only libraries: first on some semi-heavy file and then on a simple one https://streamable.com/hfkbzg

A lot of those are tied to a specific environment / runtime API, and if you want to use the same algorithm in another environment (in my case, the one I am developing: https://ossia.io) , you have to basically rewrite the whole thing as the framework permeates every part of the code, or import the whole environment and pay the performance price for converting from your run-time types against their run-time types, integrate their UI library (embedding a plug-in UI made with, say, NanoVG, in a Qt QGraphicsScene is not exactly a fun thing to do).