I personally use a map where the value is a Property object that has an "update" virtual method see on github (measurement on my local machine, so not general, seemed to indicate that calling a virtual method was faster than a bind). Does it make my REs slow and unusable? Certainly not. Is is slowe...

rcbuse wrote: ↑

26 Jun 2021

I have a huge switch statement. But, its auto generated. I've automated out a bunch of the tedious stuff. I parse the motherboard.lua file with some python and generate the switch. I also auto generate the texts.lua from the motherboard.

Hm, maybe that's the way to go. Thanks!

I think the most performance -efficient way is by using plain C and avoiding function calls for each diff. A single function processing all the diffs in a loop containing a big switch statement. Oh sure, I forgot about that! I am trying to avoid a switch statement, though, to increase reusability o...

Hi guys! I am currently refactoring a lot of my code and am wondering what the best way for handling property diffs would be. At the moment I am using std::map and std::bind which someone suggested on the dev forum a long time ago, if I recall correctly. Is there a way to do this more efficiently or...

Hi guys! If this belongs in a different subforum feel free to move the post. Recently I got lucky and got a used Madiface XT on Ebay for very cheap which replaces my Octa-Capture. However, I am having trouble recording with the dedicated ASIO driver. The interface has two metric tonnes of MADI input...

Ottostrom wrote: ↑

23 Feb 2021

I think I just found a bug in the DEQ.

The fix is now live! Hopefully it works as intended now.

I think I just found a bug in the DEQ. If you switch to "Split Stereo" as your stereo mode it will completely mangle your sound if you include any amount of Lookahead. Thought my computer was about to die or something when I heard it lol. As a sidenote while I'm in this thread I wanna add that this...

selig wrote: ↑

19 Feb 2021

I just create the panel graphics at the 5x pixel resolution thus can type values directly from the objects on the layout into the .lua file.

This is definitely a great technique! I guess I just go through too many stages of graphics changes where it starts to become a hassle.

Here is a little python script I wrote that helps me out. It evaluates and collapses down any calculations inside device_2d.lua I run it as follows: python collapseCalcs.py GUI2D/device_2D.lua Which allows me to write things like: ButtonTool0 = { offset = {575+5*30, 200-10*5}, { path="SeedSwitch", ...

Thanks for your input, Brian!
I actually think that my current approach might be faster for me because I can re-position the widgets and get instant feedback in GIMP without having to rebuild anything or having to re-open Recon. But I'll have to try your method!

I am beginning to find it frustrating positioning the graphics in GIMP and then manually copying the coordinates into the device_2D.lua file. How do you handle this process? Are there any faster alternatives?

For owners of the Forgotten Compressor: There has been a mini update which fixed a small bug that I've run into a couple of times. I hope this helps!

Hello there! Nice and useful little device, especially with the steep filter slopes. I stumbled upon a small issue with the silence detection. When using the lowpass filter with a low cutoff and the inputs go completely silent, the outputs go silent at the same time as well, which results in a smal...

Happy to help out my fellow Reasoners! Hope you all like it
Maximum oversampling is closer to x16, even! Although it isn't regular oversampling and not directly comparable.

Omega Trimmer is also free during Black Friday if anyone's interested.

stuk71 wrote: ↑

24 Oct 2020

I am on Catalina and willing to help out.

Great. Please PM me your Reason username so I can give you a beta license.

Hi guys, I'm working on a very small project but sadly there seems to be an issue that I cannot recreate. I'd need a few people to quickly check if the RE outputs any sound (will take 5 minutes or so with downloading and everything). Both Mac and Windows is appreciated but Mac the bug is more likely...

I dived in the forgotten waveshaper, it has so much options. I read in the (very well written) manual you are thinking of how to implement the cv input. I was thinking a matrix would be awesome for this. The user could assign the cv input to the desired parameter on the device without the routing i...

Looks like some kind of syntax error. If you don't figure it out yourself, can you post the device_2D.lua file?

Ottostrom wrote: ↑

18 Jul 2020

Can confirm that it is behaving like normal again

Great to hear, thanks for reporting back!

v1.3 is available now and should work properly!

I've used them a bunch and I think they are fine. I'm sure they are well-optimized and use lookup-tables. There could be optimized versions for special cases (if one needs the optimization). Like a split radix FFT for lengths 4n or for zero-padding / zero-insertion (there has been a post on reddit.c...

A really inconvenient bug has slipped through where you can't really use the filter section. Unfortunately, I am currently on holiday but will fix it ASAP when I get back.

For the time being, I would advise against updating to v1.2. Sorry!

Quick info: Version 1.2 is now available for free which introduces Polyphony and a new "Release ASAP" mode.

That said, such examples could be potentially useful for other reasons, so maybe that's a good case for a more general open-source RE example gallery, where re-cmake just happens to be the common build system they all use, but maintenance is shared by others? That was my thought. The examples are n...

Amazing, thanks! I'll have to look into this.
When you say "fully wired" I assume audio inputs/outputs and not much else, right? I would be willing to throw in my FX template which features much more functionality that new devs might not think they needed.