Befaco modules development blog

steve · December 2, 2021, 3:17pm

Noise Plethora looks really interesting.

The fact you are using a Bastl Kompas in the demo is potentially even more interesting!

Where on earth did that come from? - are you porting some Bastl modules to VCV? That would be awesome if so.

fractalgee · December 2, 2021, 3:20pm

I am with @steve , Bastl in VCV? Want!

hemmer · December 2, 2021, 3:39pm

Good eye, I am indeed porting some Bastl modules to VCV! Well just this one to start…

hemmer · December 2, 2021, 3:40pm

I’d be interested if any Mac users can manage to locally build and run (meaning it’s a GH autobuild issue) or something more fundamental. Coincidentally I have a Mac mini en route, but that only gets here next week…

steve · December 2, 2021, 3:42pm

I’m on Mac and can try building in about an hour.

That’s excellent news!

Nik · December 2, 2021, 3:54pm

I didn’t spot that. A friend picked up Kompas recently and has been really enjoying it. I look forward to giving it a try! Thanks again.

CiDE · December 2, 2021, 5:37pm

Excellent! Beautiful! Always was questioning myself on this module but now that I’m trying it out I fell in love with it! I’ve uploaded my first patch with this on my Bandcamp:

https://cide-shii.bandcamp.com/track/persephone-telephone-audacity-blinds-mix

In short, everything but the kick/snare is the Noise Plethora in all its glory (except the bottom section).

I’ll later do a better take and mix it and stuff. Just wanted to show my newfound love for this thing.

pgatt · December 2, 2021, 10:44pm

Did you want GitHub - hemmer/Befaco: VCV Rack plugin based on Befaco Eurorack modules branch v2-noise-plethora pulled and tested on Mac? If so this is the error I received. Built fine but would not install into Rack

[0.431 warn src/plugin.cpp:206 loadPlugin] Could not load plugin /Users/paulgatt/Documents/Rack2/plugins/Befaco: Failed to load library /Users/paulgatt/Documents/Rack2/plugins/Befaco/plugin.dylib: dlopen(/Users/pg/Documents/Rack2/plugins/Befaco/plugin.dylib, 6): Symbol not found: __ZTI19NoisePlethoraPlugin
  Referenced from: /Users/pg/Documents/Rack2/plugins/Befaco/plugin.dylib
  Expected in: flat namespace
 in /Users/pg/Documents/Rack2/plugins/Befaco/plugin.dylib

steve · December 2, 2021, 10:49pm

Might be worth messaging @modular80 as I believe some changes were made to Rack at the last minute regarding this symbol thing reported in the error log. Bidoo modules were compiling but not loading in the browser on Mac with a similar error and it was something that needed to be changed in Rack itself.

cschol · December 2, 2021, 11:40pm

Compiles fine with the rack-plugin-toolchain for all platforms.

But there is a runtime-error when trying to load the plugin (here on Linux): undefined symbol: _ZTI19NoisePlethoraPlugin

This looks like a code issue rather than a build system issue.

hemmer · December 3, 2021, 8:02am

One thing that is slightly non-standard is that some of the source files are in subdirectories (makefile should pick up cpp files though):

...
NoisePlethora.cpp
noise-plethora/
    plugins/
        P_Atari.hpp
        ...
    teensy/
        effect_multiply.hpp
        ...

Also there are some functions that had to be namespaced, don’t know if that’s an issue? One of these is called random() so maybe the Mac build is a flattened namespace that leads to collisions? Definitely out of my depth here though, never done any Mac dev!

Finally, there are a few teensy units that ended up being made header only, maybe having separate cpp/hpp will help.

cschol · December 3, 2021, 12:59pm

The missing symbol is happening on Linux.

What platform are you developing on?

pgatt · December 3, 2021, 1:11pm

And Mac

hemmer · December 3, 2021, 1:30pm

Good point, I forgot it was linux also, I’m developing on windows. I’ll try out a few things after work.

pgatt · December 3, 2021, 1:33pm

Let us know if you want testers.

hemmer · December 3, 2021, 7:03pm

@pgatt confirmed that the most recent fixes didnt help.

__ZTI19NoisePlethoraPlugin demangled is _typeinfo for NoisePlethoraPlugin

I can’t see anything too unusual about the class? The module code holds two std::shared_ptrs to this, does it perhaps need forward declared?

github.com

hemmer/Befaco/blob/v2-noise-plethora/src/NoisePlethora.cpp#L149

    
      
          	};
          
          
	enum ProgramKnobMode {
          		PROGRAM_MODE,
          		BANK_MODE
          	};
          	ProgramKnobMode programKnobMode = PROGRAM_MODE;
          
          
	// section A/B
          	bool bypassFilters = false;
          	std::shared_ptr<NoisePlethoraPlugin> algorithm[2];
          	// filters for A/B
          	StateVariableFilter2ndOrder svfFilter[2];
          	ProgramSelector programSelector;
          	float lastCV[2] = {};
          	// UI / UX for A/B
          	std::string textDisplayA = " ", textDisplayB = " ";
          	bool isDisplayActiveA = false, isDisplayActiveB = false;
          	bool programButtonHeld = false;
          	bool programButtonDragged = false;
          	dsp::BooleanTrigger programHoldTrigger;

Xenakios · December 3, 2021, 7:09pm

My suspicion is that it might have indeed something to do with the makefile, after all. However, since the build for Windows works anyway, it’s bit of a mystery.

hemmer · December 3, 2021, 7:11pm

There are some extra system includes for NoisePlethoraPlugin, just it case that triggers anything (extra flags needed?)…

github.com

hemmer/Befaco/blob/v2-noise-plethora/src/noise-plethora/plugins/NoisePlethoraPlugin.hpp#L4

    
      
          #pragma once
          
          
#include <rack.hpp>
          #include <memory>
          #include <string> // string might not be allowed
          #include <functional>
          #include <map>
          
          
#include "../teensy/TeensyAudioReplacements.hpp"
          
          

          
class NoisePlethoraPlugin {
          
          
public:

Xenakios · December 3, 2021, 7:19pm

“memory” is a standard C++11 header/library that should work fine when building Rack plugins. (Of course, that is not 100% certain.)

edit : Anyway now that I have suspicion about what might be going on, I should probably check it out on my Mac system.

edit2 : Nevermind, it wasn’t as simple as what I was suspecting.

pgatt · December 3, 2021, 7:24pm

I don’t think it’s simply that you include memory as I just did a search and heaps of plugins include it. I came across 373 include results from a fairly naive search.