wdl-ol
JUCE
wdl-ol | JUCE | |
---|---|---|
1 | 105 | |
933 | 6,148 | |
- | 2.1% | |
0.0 | 9.5 | |
over 2 years ago | 12 days ago | |
C | C++ | |
- | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wdl-ol
-
Clap: Née
quite some time ago, i used to write audio plugins. i'd started by using WDL-OL[1], but quickly ended up re-writing most of the front-end code to use Direct2D/Cocoa + OpenGL, as i began to run into limitations with the rendering capabilities. in time, i ended up rewriting most of the framework in order to take advantage of VST3 and AAX's more.. separated APIs.
Steinberg did some really good work with the design of VST3, and it's frustrating that it never really took off. it's the only plugin API that can actually guarantee sample-accuracy. the initial design required UI and processor separation.
it turns out that latter point seems to unstick many developers. contrasted with AAX (which i'm also keen on), AAX allows for even more modular architectures (which you'd need to operate around, if you wanted to use their DSP hardware), however, AVID - perhaps learning from VST3's mistakes - made "singleton" architectures allowable straight away.
a subsequent release of VST3 allowed for singleton architectures, given that so many people seemed to be put off with the (imo slightly) increased complexity, but it was too late. at least until recently, people are still writing VST2 plugins, and VST3 support across DAWs is not as extensive as VST2's.
[1] - https://github.com/olilarkin/wdl-ol
JUCE
-
3rd Edition of Programming: Principles and Practice Using C++ by Stroustrup
Personally, I started by writing externals for Pure Data, then started to contribute to the care. Later I took the same path for SuperCollider.
The more typical path, I guess, would be to start with simple audio plugins. Have a look at JUCE (https://juce.com/)!
Realtime audio programming has some rather strict requirements that you don't have in most other software. Check out this classic article: http://www.rossbencina.com/code/real-time-audio-programming-...
-
Anyone know anyone that creates plugins?
Check out https://juce.com in the meantime
-
Modern C++ Programming Course
You can definitely start putting C++ into your embedded projects, and get familiar with things in an environment in which you're already operating. A lot of great C++ code can be found with motivated use of, for example, the platformio tooling, such that you can see for yourself some existing C++ In Embedded scenarios.
In general, also, I have found that it is wise to learn C++ socially - i.e. participate in Open Source projects, as you learn/study/contribute/assist other C++ developers, on a semi-regular basis.
I've learned a lot about what I would call "decent C++ code" (i.e. shipping to tens of thousands, if not hundreds of thousands of customers) from such projects. I would suggest finding an open source C++ project, aligned with your interests, and study the codebase - as well as the repo history (i.e. gource) - to get a productive, relatively effortless (if the interests align) boost into the subject.
(My particular favourite project is the JUCE Audio library: https://juce.com/ .. one of many hundreds of great projects out there from which one can also glean modern C++ practices..)
- Ardour 8.0 released
-
What programming languages do you recommend starting with regarding audio visual programming/audio software development?
Respect for the others here who recommend C but I think they’re possibly masochists. If anything JUCE, which uses C++ is in my opinion far more approachable.
-
How have you used coding in your setup?
Here's a link to their website: https://juce.com/
- xcode or visual studio?
-
Anyone here have experience writing VST audio plugins in C++, or 'wrapping'/converting a VST to an AU plug-in?
It seems like most audio plug-ins are built in C++ inside an audio coding program called JUCE, so maybe if I could open up the exisiting code inside that and then output it as an AU instead of a VST that could work.
-
Common Audio Production
C++ has https://juce.com/, I think.
-
Apple Logic Pro Ruleface
Open source rule https://juce.com/
What are some alternatives?
dlfcn-win32 - Official dlfcn-win32 repo
Qt - Qt Base (Core, Gui, Widgets, Network, ...)
Manhunt.PluginMH - Free camera, first person mode and more!
iPlug2 - C++ Audio Plug-in Framework for desktop, mobile and web
awesome-musicdsp - A curated list of my favourite music DSP and audio programming resources
OpenFrameworks - openFrameworks is a community-developed cross platform toolkit for creative coding in C++.
LuaScript - Notepad++ plugin for Lua scripting capabilities
imgui - Dear ImGui: Bloat-free Graphical User interface for C++ with minimal dependencies
audiogridder - DSP servers using general purpose computers and networks
Cinder - Cinder is a community-developed, free and open source library for professional-quality creative coding in C++.
Boost - Super-project for modularized Boost