greetings, i want to build a daw (digital audio workstation), but i have no idea where to even start. here are my needs and the options i’ve found:
my needs:
- load and keep things (audio, midi) in memory
- cross-platform compatibility is not a requirement
the options i’ve found:
fluttergtk/qt- raylib (with zig)
webassembly (with zig)
[rejected] flutter: the first option that came to my mind was flutter. i thought it would give me a quick start in laying down the ui, but i don’t think it has the capability to fulfill my needs (please correct me if i’m wrong)
gtk/qt (with zig): i wonder if qt provide bindings for zig
raylib (with zig): it’s cool (my choice as of now)
[rejected] webassembly (with zig): it would be an ultimate comfort to build this way ig, but is it possible to make that web app into desktop one (like tauri or something)?
id really appreciate your opinions and advice
ps: i hope i’m clear. i got a headache searching about these. i’ll update this post for more clarity later
final note
Thank you guys for all your opinions and advises. Thanks for explaining the limitations with gtk, things with qt and flutter. That kotlin compose thing was cool too. Thanks for mentioning yabridge thats gonna be helpful. It might not seem like it, but I did listen to your thoughts, and stuck with zig and raylib. Thanks a lot
You must log in or register to comment.
You can try Kotlin Compose Multiplatform.
It can target JVM (windows, Linux, Mac) and then work on iOS and Android.
Android and JVM are stable. IOS is alpha and works well. Should be beta this year.
WASM support is coming as well but is experimental.
You can do as much multiplatform as you want and do as much platform specific as you want.
Compose itself is a declarative UI framework. Your UI is code.
Edit: You do require a Windows, Linux, and Mac machine to build the executables for each desktop JVM app, as well as a Mac for an iOS app. Android you can build on any of them.
He said multi platform is not a requirement. But good low-level audio performance is.
What were you thinking?
I’ve started building a lightweight daw mostly for mixing songs together rather than any actual serious music production. Currently only supports volume and bass envelopes, and dragging tracks around. I’m planning to open source it when it’s a bit more polished. It’s written in rust and I’m using egui for the frontend.
that’s so cool! it looks good too. i might need your help in the future.
Raylib sounds great. I would avoid gtk/qt. Enlightenment library also there but might not have zig bindings.
I’ve recently used dioxus with rust to build a native app with webview. Way cheaper than electron and the like.
(Google recently laid off parts of the Flutter team)
and Raylib has a LOT of bindings (ie. not just Zig)
I want to use Raylib, but mentioning it here on the fediverse doesn’t get much of a response (I can’t see a raylib community from my instance). My choice of language probably doesn’t help, though.
My first issue is wanting vertex colors on 3D models and I am not getting this (this may be a problem with the bindings I’m using, naylib(nim-lang)). The second would be needing guidance for the 2D polygon text loader that I started.
Maybe I could make simple GUI applications with raygui, but I don’t currently really have many viable ideas on what I would want to make.
To OP: Another potential option is using Godot w/bindings. Design is pretty fast and flexible, then using signals is super easy.
I’ve tested some frameworks (specific to my language, so not really helpful to most), the one that I liked more said it was
declarative user interface framework based on GTKthough I would prefer a similar thing for Qt and there wasn’t an ability to automatically scale text size to better fill the available button size (I was testing an adventure-book reader and hoping to use unicode characters).Frameworks for single page applications (or some other browser-based tech) might be ok for simple stuff. Similarly, I’ve liked the idea of TUI frameworks (yeah, because htop) but haven’t really tried that yet.
i recommend gtk’s libadwaita. it saves alot of time. It has JS Python rust and C bindings.
Bad idea. Very bad idea, especially for more complex projects.
Well, it is a bad idea if you are building anything not intended to be exclusively a GNOME app.
It’s also a bad idea if you want to build anything that’s more complex than GNOME’s single-purpose apps that lack all kinds of features. Building something as complex as a DAW would be a nightmare with libadwaita.
Why? It is solid for me
Libadwaita has been specifically designed for simple GNOME-style applications that only have one purpose and don’t include many features. I wouldn’t recommend it for complex project like a DAW.
It is made to be simple but libadwaita apps being single purpose is not true. It is a good design choice but some apps are naturally complex such as gnome settings.
Not libadwaita, but GNOME. GNOME apps are meant to be simple, and only do one single thing.
https://developer.gnome.org/hig/principles.html
The best apps do one thing and do it well.
Resist the pull to try and make an app that suits all people in all situations. Focus on one situation, one type of experience.
You do not need to follow the gnome standards. Its good practice if you do but not required.
You don’t need to, but the entire framework has been specifically designed around this GNOME development philosophy, making it basically unusable for anything else. There are much better frameworks like Qt (C++/QML, but has bindings for almost every language), Iced (Rust), Avalonia (if you use C#) and many others
QT is a cross platform UI development framework, its goal is to look native to the platform it operates on. This video from 2014 explains its benefits over GTK.
Most GTK advocates will argue QT is developed by Trolltech and isn’t GPL licensed so could go closed source! This argument seems to ignore open source projects use the Open Source releases of QT and if Trolltech did close source then the last open source would be maintained (much like GTK).
Personally I would avoid Flutter on the grounds its a Google owned library and Google have the attention span of a toddler.
Not helping that assessment is Google let go of the Fuschia team (which Flutter was being developed for) and seems to have let go a lot of Fuschia developers.
Personally I hate web frontends as local applications. They integrate poorly on the desktop and often the JS engine has weird memory leaks
Here is an alternative Piped link(s):
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.
What are your needs which aren’t being met with flutter? – It’s really just a UI renderer and it has a C/C++/ObjectC/Java underlayer for everything else. It should link fine with existing c libraries. I have done a bit with it recently including desktop dev: https://www.producthunt.com/products/which-browser So hopefully I can answer any questions. – Hit me up on matrix
It seems that Zig is the intended language? If go where a consideration I would point you at this to consider: https://github.com/go-graphics/go-gui-projects too.
Google just killed flutter. Just so you know. They do that a lot. Be careful
No they didn’t. It literally got an update this week (3.22). Laying off part of the team (which is worrying) is not the same as actually killing it.
It depends if you’re using Gnome or KDE. If you prefer KDE, use Qt. If you prefer Gnome’s interface ideas (that looks quite different), use GTK+ with libadwaita. GTK+ has good bindings for Python, and Rust, and a new, rather Gnome-specific language, Vala.
Use GTK4
GTK+ is quite old at this point
GTK4 is what I meant to say. To me, it’s the same as GTK+, because that was the original name. Just like I spell nvidia as nVidia, because that’s how it was spelt back in the early 2000s. It sticks
I recommend using qt for the interface, for audio use jack, it is better for music production, if you want to load vst plugins into the program, you can use yabridge
I would always go with something cross platform to save you or someone else effort later. I recommend Python to save yourself effort too.
Checkout kivy.
isnt python slow?
Yes. For a DAW, I would avoid languages with garbage collection.
The most important speed to optimize is developer speed. Python is by that measure one of the fastest languages.
CPU speed is negligible
In this case we’re talking about a soft real-time application where milliseconds matter. If you use Python for this, your developer speed will suffer because you’re using most of your time to fight garbage collection pauses, among other things.
Kivy is a platform frequently used for video games. It has good hardware acceleration. It would work fine for this purpose.
Again, the CPU time differences are negligible. They’re less than milliseconds.
there seems to be qt qml bindings for Zig
qml is a language made to build UIs, and is very easy to use in my experience - you can build your logic that needs to be high-performance (file loading, audio effects, etc.) in zig, and expose it to qml so it’s available in the UI.
i’ve never used zig, but i did do a similar thing using c++ & qml, and it was great to work with, so i think you should be fine going that route
You could use libadwaita
That’s gtk.
It is actually a GTK4 theme. You can use GTK4 without libadwaita but not the other way around.
I would say a “superset of gtk” since the point of libadwaita is shipping more widgets targeting Gnome UI/UX (including its theme). That’s why they describe it like “Building blocks for modern GNOME applications”.
True, but the concept of a theme is easier to understand. You also can run libadwaita on Windows and probably other platforms
Happy Qt User here, I was able to make sense of the C++ and Go bindings for Qt really quickly and there’s a lot of good resources and examples online for Qt Templates
You can also do the dance https://youtube.com/watch?v=J2mEPQGq5dU
Here is an alternative Piped link(s):
https://piped.video/watch?v=J2mEPQGq5dU
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.
bruh what was that!
