teapodo.com
- Teapodo now supports adding audio effects to tracks by mounting VST3 (Windows and macOS) and AudioUnit (macOS) plugins.
- Teapodo for Windows now has an installer.
* Smooth and fast.
* 160MB disk space, and 100MB RAM on startup isn't lightweight in my book, though.
* The plugin selection window is unwieldy. I tested it on an (audio-wise) clean macOS system, and the list of Apple plugins was already almost impossible to navigate. On my personal laptop, I've got hundreds of plugins more. A search/filter function would be most welcome.
* I wouldn't call it an audio editor, as I don't seem to be able to edit the actual wave. Or are you still planning to add that? I don't have a good alternative description handy, though. DAW, perhaps?
* Vertical zoom would be nice too.
* There seems to be always one tracked armed. That's going to cause accidental overwrites, which won't be noticed until it's too late. I see it's easy to remove recordings, but people in a hurry won't notice until after bouncing.
* Joining/grouping clips is needed.
Excellent work.
- Glad it felt smooth and fast to you, that's exactly what we are striving for. - For the plugin list issue, yes, we also noticed that before release, we are planning to add plugin search/filter in the next iteration. - On wave editing (and potentially spectrum analysis), we had some ideas around this, but we aren't able to fully commit to these yet (we are a very small team). I see your point and I think we will think more carefully about how we present the main selling point of Teapodo in the future (same goes for the "lightweight" part). - Vertical zoom and grouping clips: these also came up when using it internally, so we will also look into these soon.
Again, really appreciate your feedback!
I have a friend who enjoys online multi-player games, but she often faces quite a bit of unfriendly remarks when she speaks (CS:GO, I believe it's been an ongoing problem in the community). I'm thinking perhaps an audio program that can alter her voice from female to male would let her game in peace - would anyone on HN have any suggestions/recommendations?
Yes, we will eventually try to make it a sustainable business.
We don't have a concrete licensing plan yet, but we are hoping to keep all released functionalities free to use so that existing users won't be interrupted.
It's not open source yet, but it's certainly a possible option.
And would you mind sharing your reasoning behind deciding for Qt?
As for graphics performance, I think the heavy lifting is done by Qt6, as it took advantages of modern GPU rendering APIs on each platforms (e.g. Metal on macOS and DirectX 11 on Windows).
What we did to keep the UI responsive is more of following the best practices when possible, things like: * Use QML binding when we can (e.g. serving data from C++/Rust via Qt View Models), this so that frequent data changes will be batched to UI redraws only when needed * Use C++/Rust as much as possible for calculating data needed in the UI rendering (e.g. the waveform's data) * Avoid fractional pixel position/sizes during animation (e.g. by rounding the values), so that UI redraws are quantized to changes on visible pixels
We decided to use Qt because we previously worked in a few successful commercial audio projects with it (for our previous employers), and felt quite positive with those - so mostly just to work with what we already know, as the audio side of the project also requires a fair amount of attention, and we are a very small team.
We have an upcoming article about the technical details of the project [1], perhaps that will be interesting to you, if so stay tuned :)
[1]: and here is a sneak peek https://twitter.com/teapodo_audio/status/1559695230693101568...
Plugin host in Teapodo is done in two main modules: - The Teapodo audio engine provided "plugin slots" for the application to mount plugin instances to (in a thread safe way), which is written in Rust - The plugin format parsers to understand each plugin formats (e.g. VST3, AU) and create plugin instances from, which is written in C++ and is just a thin wrapper around JUCE
We did think about building our own plugin format parsers from scratch, but since we are really small (only 2 devs) we ended up using an existing solution for now. Maybe we will come around and do it at some point (I certainly hope we could!).
As for releasing the source code, that's definitely a possible option. We've seen some interest in the implementation of the project, and we will start by writing about it soon, so stay tuned!
Tempo adjustments and beat analysis do sound like interesting ways to expand Teapodo's capabilities! We will certainly consider those. Cheers!