I just downloaded this and tried it out. Does it not compile at all on windows? The interface is so clean and fast I really want to start using it. It really seems like a great way to try out ideas quickly but still end up with native executable. There isn't even an install to go through which I actually really like.
We're actually waiting for a few gremlins in Clang/LLVM's Windows support to get straightened out before it can successfully compile on Windows. Fingers crossed we should be able to release a working version in the next couple of weeks..
(Author here) There's a set of problems that tend to go together when you're doing audio tech development: We have to build apps/plugins that run on many platforms and plugin APIs (so managing many different compiler projects for the same codebase is really helpful). We always tend to have complicated and custom GUIs (hence all the GUI framework stuff). And there's a whole set of other commonly needed library code th…
A workflow I think would be extremely useful would be to take serialized data, live program some sort of data transformation, then visualize the result (and maybe the initial data too) Then for anything that is an arbitrary data transformation it could be done live and in isolation.
Yeah, that's the kind of thing it can do. We've got demos of live-coding audio algorithms, for example, which is the same kind of process.
This has been partly done several times with Lua (one by myself). One problem is that JUCE is not a C framework, it relies heavily on C++ features (notably, using it means deriving lots of parent classes and interfaces). This makes language bindings a bit more tedious, especially if you want your binding to keep up with JUCE's non-stop development. So it would take a really strong incentive for someone to create and…
The smart way to generate bindings nowadays would probably be to use Clang to get an AST and auto-generate the wrapper code. But TBH I've never quite seen the point of binding scripts to C++ classes in general.. C++ is already a great way to write that code, why have a messy layer in the middle! The place where I'd have thought it makes sense is for custom APIs, e.g. in Tracktion we let the users write javascript to…
i kinda figured the gui stuff would be impractical, but what i was more interested in was a low friction way to play with midi / audio buffers. i haven't worked with c / c++ since college (too busy paying the bills in a managed shop), but i guess this is as good an excuse as any to get back into it. the fact it comes with its own ide / tooling is nice because learning an entirely new workflow / tool-chain is a barrier in itself.