been playing around with the Rack SDK for several weeks now and am working on my first module. Right now it has a Stereo Chorus, yet another expander based mixer and a little A/B swittcher.
I am developing under Linux and can also test under Windows, but do not have access to a Mac. Therefor it would be really nice if someone could get the repository and try to build and run it on a Mac.
The files are here:
It also has a CMakeLists,txt, which I am using to develop and debug with CLion (Linux and Windows). But for the official builds there is the classic Makefile to build dep, dist and install. I made minor modifications to the sample Makefile to support a folder structure for the sources, works under Linux.
Also if anyone else would like to test it, this would would be very welcome. I am really new to all of this, so any pointers are appreciated.
There’s some warnings, though: (These are not all of them, just a few samples)
src/common/Faders.cpp:23:2: warning: suggest braces around initialization of subobject [-Wmissing-braces]
23 | 0.0, -144.0,
| ^~~~~~~~~~~~~~
| { }
src/ChainMixer/ChainMixerModule.h:103:7: warning: private field 'm_bDisabled' is not used [-Wunused-private-field]
103 | bool m_bDisabled = false; // happens if motule Aux/Master modules or too many channel modules were found
| ^
src/ChainMixer/ChainMixerChannel.h:91:2: warning: class 'GPaudioFader' was previously declared as a struct; this is valid, but may result in linker errors under the Microsoft C++ ABI [-Wmismatched-tags]
91 | class GPaudioFader* m_pFader = nullptr;
| ^
Also, a bug report: connecting Stereo Chorus’ output to something without having ever connected anything to the inputs causes a crash. (It doesn’t crash if you’ve connected something to either input at any point)
The Github repository is updated. The crash and the warnings you posted should be eliminated. Also performance is optimized if fewer StereoChorus voices are used.
If you find the time again, would it be possible to direct the output of the toolchain to a text file and post that, then I could work on all Mac warnings. I would install the toolchain myself, but I read that you need a Mac with XCode to setup the toolchain under Linux.