bogaudio / bogaudiomodules Goto Github PK

/dist/fundamental should probably be /dist/BogaudioModules

Hi Matt,
i have a personal dark theme 80% Gray that i use for your modules.
Several members approached me for this svg mod.
I can not share this with them since that is not the right thing to do.
If you like it and are interested you could include it with your modules as an alternative to your light theme.
Let me know.
Take care!

8-1 1-8 switches, addr seq crashs rack, Win10 pc

Would love to see an option to switch your sample and hold module to track and hold.

well, the title says it all...

Fedora 23 Linux
Rack 0.5.x

The module is looking for DGATE.svg, the case matters on Linux. :)
And thank you very much for your excellent modules !

All the new stuff is so great! one more reguest ;-) It would be great to be able to see below -48db. Don't know how useful that is is VCV land, but I'm used to seeing down to -96. Maybe some range controls for amplitude like the new control over frequency range?

Hi

Any chance of implementing a Uni/Bi switch (0-10/-5+5) on the LFOs?

Thanks.

BogaudioModules-0.5.0-01-win.zip

I have an external controller encoder mapped to the CV jack beneath the Dry/Wet mix knob on the CVD, but the encoder does not seem to change the dry/wet mix. I can see voltage is being applied because the jack lights up. Maybe this is not the intended purpose of this jack?

Module - Sums. With the new update I can't seem to _disableOutputLimit. I can't find an option to do that in a menu or on the panel. I would like to be able to sum more than 12...

Hello there!
First of all thank you for these great modules! Especially for the FM-OP, which is just wonderful!
The sequencers are also really nice, but I was wondering if you might want to add a shift function to the sequencers.
What I mean is a control next to the step length that shifts the starting point of the sequence (offsets the sequence), and then it would also be nice to be able to automate sequence length, offset and toggle between forwards and backwards with a gate. With these functions I would consider them perfect.

Hi, Matt,

Have you considered adding a peak indicator to you beautiful VU meter?

Hi, I have found that the CV inputs for the PAN function do nothing if the PAN knob is centred. CV input will only effect audio if the PAN knob is either hard left or hard right. For version 0.6.13 of both.

Regards.

Just a note to say that the BogAudio collection is really impressive. Most modules offer more than just the basic functionality, such as built-in VCAs, variable responses, and the visual colour cues for amplitude on faders. I use your modules a lot, and would gladly make a donation. :)

I realize this -might- be intentional, since it's a VCAttenuator rather than strictly speaking an amplifier...

But, nevertheless, many other things that only attenuate (like the VCA-1 from Fundamental, and many other VCAs) also behave that way, and all of those are in that tag.

As such, I expected the 3hp VCA to have that tag, so I have made an issue in case it's unintentional.

Any instance of LLFO (whether New, Initialized, Duplicated, or Cables Removed) will not switch wave shape unless Output is patched.

Not sure if bug or feature.

I just want to say great job on the development of your modules. I use them a lot in my projects. now that you have developed a VCA module, it is a long awaited complement to your DADSR(H) module that I wanted.

I am still trying to figure out the DADSR(H) module in whole, but it sounds nice. I will be waiting for a compressor/limiter in mono/stereo.

Great Job,

Thanks

Fedora 23 Linux

g++ -fPIC -I../../include -I../../dep/include -MMD -g -O3 -march=nocona -ffast-math -fno-finite-math-only -Wall -Wextra -Wno-unused-parameter -DARCH_LIN -Isrc -Isrc/dsp -Wsuggest-override -std=c++11 -c -o build/src/dsp/oscillator.cpp.o src/dsp/oscillator.cpp
In file included from src/dsp/oscillator.cpp:3:0:
src/dsp/oscillator.hpp:199:79: error: ‘NULL’ was not declared in this scope
void setPartial(int i, float frequencyRatio, float amplitude, float* phase = NULL);
^
../../compile.mk:53: recipe for target 'build/src/dsp/oscillator.cpp.o' failed

Solved by adding #include to src/dsp/oscillator.hpp

Hi Matt, I find your modules some of the best out there for what I'm trying to do with Rack. In particular, they're very very functional, with an impressively low appetite for CPU.

I noticed an issue with MIX8 the other day, and just had a chance to verify it today: it seems like the level inputs on Ch 5-8 do not respond to CV to change the volume output.

Thanks! and I appreciate all your amazing work!

Would it be possible to:

• allow longer FFT windows?
• allow selection of windowing functions?
• make the UI stretchable, like full scope?
• allow zooming in to areas of interest?

First of all, I absolutely love your modules, they are my favourite ones in VCV.

I would like to make a feature request: I think it would be really great to have a multiplexer (also known as mux) and a demultiplexer (demux) as part of your modules. A multiplexer takes N different inputs and routes just one of them to its single output according to a selector value. Basically:

A demultiplexer is the opposite, it takes a single input and routes it to a single one of its N outputs:

One way of implementing the selector is to divide a range (say 10V) into 8 steps and use these as ranges for the selection. This is how it is implemented in a language such as Pure Data:

These can be very handy when creating complex patches that require the same signal to be sent to different modules at different times, as well as for selecting an input signal in a more complex way than a simple sequencer allows for.

Would you please consider if feasible for you, to create a 3hp 1 channel mix/vca fader module,
the direct out is starting to come indispensable within an existing signal path.
And as the current mixer modules are cramped / not offering space anymore for "post fader direct out", such a tiny module would come in handy.

I saw in the docs that the S&H module normals to internal white noise if nothing is in the input, but I'm not getting anything in my scope until I hook up a noise source to the input. I'm on 0.6.2b. Would love to use this awesome tiny module for all my S&H needs!

Switch, Reftone, DGate and a few other utilities are not showing up in VCV Rack. Running OSX 10.9.5

It's difficult working on plugins without your analyzer available.

Attempting to open 'miscrush.vcv' from https://patchstorage.com/miscrush-vcv/ on a osx 10.10.5 machine causes Rack to crash with:

'random_device failed to open /dev/urandom: Too many open files'

The crash reporter logs point to the Bogaudio Noise plugin hitting the error:

Application Specific Information:
abort() called
terminating with uncaught exception of type std::__1::system_error: random_device failed to open /dev/urandom: Too many open files

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib              0x00007fff92524286 __pthread_kill + 10
1   libsystem_c.dylib                   0x00007fff910a29a3 abort + 129
2   libc++abi.dylib                     0x00007fff954322d1 abort_message + 257
3   libc++abi.dylib                     0x00007fff9545a9b9 default_terminate_handler() + 243
4   libobjc.A.dylib                     0x00007fff85a447eb _objc_terminate() + 124
5   libc++abi.dylib                     0x00007fff954580a1 std::__terminate(void (*)()) + 8
6   libc++abi.dylib                     0x00007fff95457b38 __cxa_throw + 121
7   libc++.1.dylib                      0x00007fff941aeb25 std::__1::__throw_system_error(int, char const*) + 77
8   libc++.1.dylib                      0x00007fff941a559b std::__1::random_device::random_device(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) + 99
9   plugin.dylib                        0x0000000108c411bf bogaudio::dsp::NoiseGenerator::NoiseGenerator() + 95
10  plugin.dylib                        0x0000000108c41386 bogaudio::dsp::BasePinkNoiseGenerator<bogaudio::dsp::WhiteNoiseGenerator>::BasePinkNoiseGenerator() + 86
11  plugin.dylib                        0x0000000108c41a2d bogaudio::dsp::BasePinkNoiseGenerator<bogaudio::dsp::PinkNoiseGenerator>::BasePinkNoiseGenerator() + 205
12  plugin.dylib                        0x0000000108c40951 Noise::Noise() + 129
13  plugin.dylib                        0x0000000108c401ea NoiseWidget::NoiseWidget() + 266
14  plugin.dylib                        0x0000000108c3602f rack::Model* rack::createModel<NoiseWidget, rack::ModelTag, rack::ModelTag>(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, rack::ModelTag, rack::ModelTag)::TModel::createModuleWidget() + 31
15  com.vcvrack.rack                    0x0000000107e5580a rack::RackWidget::fromJson(json_t*) + 1194
16  com.vcvrack.rack                    0x0000000107e5471f rack::RackWidget::loadPatch(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >) + 191
17  com.vcvrack.rack                    0x0000000107e43603 main + 579
18  com.vcvrack.rack                    0x0000000107e254b4 start + 52

The system has the default file limits (256).

Running the 'File activity' profile with Xcode Instruments shows Rack calling open() on '/dev/urandom' 200+ times around the time the Noise plugin resources are being loaded (the 'Bogaudio/res/Noise.svg' is for example). Rack fails when trying to open('/dev/urandom') after hitting the 256 fd limit.

The 'miscrush.vcv' patch looks to be using 4 instances of the Noise plugin, amongst a lot of other plugins.

Let's start by saying yours are some of my favorite modules.
I have a question about the two new Walk modules. Is it possible to sync those to a clock?

All I am going to say is that they sound like smooth buttermilk!!!!

Thanks for this amazing collection of modules! They're quite useful, use minimal rack space, and I especially love the clean "look-and-feel" of them all!

I must not understand the Stack module because I can't get it to do much. I presumed an oscillator input on the V/OCT input would be copied to the THRU, and re-pitched on the OUT, per the settings of the OCT and SEMI controls. What I hear is a nearly imperceptible difference between the two outputs, regardless of the OCT and SEMI control positions, QZ button, and CV input positions/connections. A little snooping with a Scope seems to showsthe input gets rectified a bit...

Thanks again for these modules, and any help you can give lifting the fog from my eyes (ears?)!

hi,
could you please add this functionality:

Right click on mixer channels mute button for SOLO channel,
with visual confirmation of this action ie: change mute button color.

Thanks.

First I want to thank you for your great modules, I use them in every project I do in VCV.
my question:
Would it be possible that you add a dark mode to the interface of your fantastic modules? (Like the Geodesics e.g.)
I did a dark version for the mixers, which I use only on my private pc,
and I like this very much. (see the attached picture)

I also know there are some visually impaired users, which have problems with the light versions.
These would benefit from the dark GUIs.

I understand, that changing the GUI is a lot of work, but I think if you post a request in the VCV forum for some help,
there will be some folks that would support you ;-)

I can send you the svg's, if you want them.

Looks like the latest update to 0.6.12 forgot to include the res_b (dark panel) folder, so stuck with only light panels until fixed... Not as nice on the eyes (MacOS X, Rack 0.6.2c)

I tried shifting the root of the patter from a sequencer using stack like you can see on the image. But notes above D#4 and below A3 are being shifted one semitone lower, meaning that if I want to send a CV to change from A3 to G3, I have to press F#3, instead of G3, and so on. Am I using STACK wrong or is it a bug?

I love your modules!

CMP's A>B output is acting like an A [Less than or equal to] B, and going high when the EQUAL output is active.

bogbug.vcv.txt

Rack standard is that LFOs should be 0V=2 Hz / 120 BPM, or a touch off C_-3.

"Normal" mode = 16.35 Hz (C₀)
"Slow" mode = 1.02 Hz (C_-4)

Is there any chance you could add a toggle in the context menu for Slow = 2 Hz? It'd be nice to have your LFOs behave as expected when swapping for another, especially given their mechaSquirrel (mS) efficiency!

I wanted to challenge myself and create a "default" rack with all Bogaudio modules as a platform to build on and realized you have no filters. Are there plans to "round out" your module collection by adding the commonly needed modules? Also would like to see a brand logo blank plate I can show off when I do a Youtube video using one or more of your modules. I have some design ideas for the graphics and operation if you are interested. (Have a few module ideas but I'm a designer, not a programmer.) Wouldn't mind donating some time if needed.

Hello! I have an unexpected behavior of SLEW module. It jumps to target value at some threshold as seen on the next screenshot:

My system: Ubuntu 18.04
My sample rate: 44100 Hz
Rack version: 0.6.2c

P.S.: Thank you for a nice collection of modules :)

Hi there,

when using this module with core midi-cc attached to the mute triggers, it reacts instantly when muting, but when un-muting it takes nearly a second to un-mute.

hope i am saying this right?
i am triggering from a beatstep-pro. tried both options for the buttons on the beatstep (toggle/gate), both have same behaviour, on release of the button it takes nearly a second for the MUTE8 to un-mute.

Bogaudio Modules just updated through the plugin manager in VCV, and now it crashes when adding an ADDR-SEQ

Steps to reproduce:

• Create blank patch
• Add ADDR-SEQ

Identifier:            com.vcvrack.rack
Version:               0.6.2c (???)
Code Type:             X86-64 (Native)
Exception Type:        EXC_ARITHMETIC (SIGFPE)
Exception Codes:       EXC_I386_DIV (divide by zero)
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Floating point exception: 8
Termination Reason:    Namespace SIGNAL, Code 0x8
Terminating Process:   exc handler [45325]

Thread 13 Crashed:
0   plugin.dylib                  	0x00000001060f4754 bogaudio::AddrSeq::step() + 260
1   com.vcvrack.rack              	0x0000000105aad2ed rack::engineRun() + 653
2   com.vcvrack.rack              	0x0000000105aacd7d void* std::__1::__thread_proxy<std::__1::tuple<void (*)()> >(void*) + 93
3   libsystem_pthread.dylib       	0x00007fff73e3b2eb _pthread_body + 126
4   libsystem_pthread.dylib       	0x00007fff73e3e249 _pthread_start + 66
5   libsystem_pthread.dylib       	0x00007fff73e3a40d thread_start + 13

Bogaudio Modules version 0.6.15
plugin.dylib shasum 781727938a334c99e04c51072c330850aa1f23e8

Hi,
thanks for the wonderful modules.

Would be nice if the mixers had a small link button between each pair of the fader channels, that would link both faders to move at same time and value.

Also if the mutes had cv control and a mute on the master output with cv control as well.

thanks for your time.

BogaudioModules.Mac.0.5.0.zip

Love these amazing modules! Folk asking for a Mac build on the FB group so I'm uploading a build here.

Win10/Rack 0.6.0 Release/ Bogaudio 0.6.6

At default initialized settings (changing only partials), Additator Outputs the following (as per Fundamental>Scope): 1: 30Vpp; 10: 18Vpp, 20 (default): ~15Vpp; 40: ~12.8Vpp 60: 11.6Vpp 100: 10.2-10.5Vpp

Even normalizing the output to half these numbers would be more reasonable.

Hi, thanks for some great modules! I have a question about the FM operator. The main frequency knob is described as a knob calibrated for setting the frequency as a ratio of the frequency dictated by the V/OCT input. Furthermore the readme states that you can set the relative frequency of each operator via ratios.

However, the default value of the frequency knob is 0, which is in itself a bit confusing if we are using the knob to set ratios. Should the default value not be 1?

For example, if the input of the V/OCT is 100hz then this means (if I understand the functioning of the module correctly) that 100hz translates to a value of 1 in the denominator and numerators of the ratio, and by setting the knob to a value of 5, we set a ratio of 5/1, and therefore set the frequency to 500hz in this case. Setting the knob to a value of 0.5 sets a ratio of 50hz, and so on. A ratio of 0/1 does not seem to make sense in this case.

If I am correct in this, then I also think that the ticks of the dial of the frequency knob need to be adapted. There are currently 4 ticks in between the option 0 and the option 5, and presumably these stand for values of 1, 2, 3 and 4. However, if the current 0 option is actually 1, then having four ticks does not make sense (there should be 3 evenly spaced ticks in between the default setting and the setting of 5).

EDIT: Another reason why the default option of 0 is confusing is that according to the labels the range of the knob currently goes from 0.1 to 0.5 (increasing the value), then from 0.5 to 0 (decreasing the value), and then from 0 to 10 (increasing the value), while in reality turning the knob left decreases the frequency and turning the knob left increases the frequency of the oscillator.

According to VCVRack/library#173 (comment), your plugins are compiled with the wrong version. I imagine this is because you're not running make clean before building the release? Regardless, I've removed the "downloads" list from your manifest. Please try to correct this in all future releases.

I don't know if its part of the design but the limiter modules seems to distort when the threshold is lowered to -6 and below during my test. My audio signal is reading -14db on the VU-BGA module. The Pressor module comp/limiter doesn't seem to have that issue on my system.

Hi, I was just fooling around with harmonics from various VCOs and observing via the two analyzers. I noticed that the fundamental frequencies displayed at the top of each trace was slightly out. For example injecting a A4 440Hz signal always displays as 444Hz. I added a Calf Analyzer via an audio output and got a better result. See pic.

It's not a fatal thing but wonder if there is a calibration issue in the two analyzers.

Regards.

Linux Fedora 23
Rack 0.5.x

g++ -fPIC -I../../include -I../../dep/include -MMD -g -O3 -march=nocona -ffast-math -fno-finite-math-only -Wall -Wextra -Wno-unused-parameter -DARCH_LIN -Isrc/dsp -Wsuggest-override -std=c++11 -c -o build/src/Reftone.cpp.o src/Reftone.cpp
src/Reftone.cpp: In member function ‘virtual void ReftoneDisplay::draw(NVGcontext*)’:
src/Reftone.cpp:162:22: error: ‘strlen’ was not declared in this scope
if (strlen(frequency) < 5) {
^
../../compile.mk:53: recipe for target 'build/src/Reftone.cpp.o' failed
make: *** [build/src/Reftone.cpp.o] Error 1

Solved by adding cstring to Reftone.cpp includes