Radium

For the assertion reporter, what seems to have happened is that two mouse-press events where sent in a row, without a mouse-release event in between. This should not happen. Do you remember how you opened the plugin GUI? Did you double-click the module, or right-click and then "Open GUI" f...

With rendering I mean something like bounce, yes. E.g. mark 4 lines and these 4 lines are bounced to a sample. Like it is working in Renoise. Yeah, you can do that by selecting "export sound file(s)" in the file menu. But it's not available in the demo version: export.png Regarding sample...

Oh, and yes, I got the crash report. That was a hard crash I haven't seen before. Unfortunately there wasn't enough information in the report to fix it.

Thanks, it seems to be more stable compared to last time I tried it. But I still got 3 crashes already after playing with it for some minutes. I'm missing the possibility to render a track or a part of the track to audio and to preview the samples while the track is playing. I have a quite large sa...

Yes, lots of things have happened since last time. Please give it try now.

Biggest change for this release is that JUCE has been upgraded from 7.0.3 to 7.0.11. JUCE is used to host AU, LV2, VST, and VST3 plugins, so this upgrade might improve plugin hosting. In addition, all the binary releases of 7.3.84 except MacOs/ARM had a bug causing instruments to automatically switc...

MacOS m1/m2/m3 has been supported a few months now. Seems to work very well, and actually much better than x86. Smooth scrolling in the editor is less smooth than on other platforms since OpenGL now must run on the main thread on newer macs (at least it looks that way), but it's actually not that ba...

This release contains quite a few changes and improvements. The biggest change this time is that the "locked instrument" concept has been removed. Please let me know if this changes your workflow. It is still possible to put back "locked instrument", but I would rather not. Yust1...

oh wait, it looks like faust's c++ backend is separate from llvm and interpreter. is it? sorry if i'm being dumb Yes, that's right. :-) The built-in faust plugins in Radium are compiled into c++, they don't use llvm or the interpreter. (sorry for late reply, I didn't get an email notification. Seem...

It might not be that hard. If you look at the tapiir plugin, for instance, it uses one .dsp file: audio/faust-examples/tapiir.dsp Then I would run "git grep faust_tapiir", and use this information as a template for what you have to do: Makefile.Qt:OBJ_FAUST=$(T)zita_rev.o $(T)stk_flute.o $...