In addition, I’m not sure to understand the difference beetwen the two Filter inputs. The one on the left has no attenuator. The one on the right has one. But the result on the scope doesn’t match…
Alain
In addition, I’m not sure to understand the difference beetwen the two Filter inputs. The one on the left has no attenuator. The one on the right has one. But the result on the scope doesn’t match…
Alain
Beautiful sounding modules! Thank you!
The PWM range seems to be too low on the oscillators - it seems 10V only moves the pusewidth by 10% or something like that.
Linear FM is also a bit low, might be same on hardware, though, don’t know.
@bubbleandsquawk I checked the Q107 and the behavior of the filter is correct.The controlled input has higher gain.
@Schabbes There is a bug in the PWM control. I’ll fix it in the next release. The linear FM is correct. The hardware does not have a very strong linear FM.
Cool, thanks Leo. I guess sometimes analog modules are just quirky like that
nice
@modlfo - The Q128 Switch and Q962 Sequential Switch are bidirectional in hardware, but are understandably unidirectional in VCV. That limits those modules to 50% or less of their functionality in VCV.
It would be great if the missing functionality could be restored.
One simple solution is to have two versions of the module for each. The downside to this is you probably would want to change the faceplate somehow to differentiate them visually, and that takes away from the aesthetics. Another downside is the Q128 top and bottom sections in hardware can flow in opposite directions. So it would require three modules to truly get all the functionality.
The other possibility that I really like is to provide context menu options to configure the direction of each of the Common ports in the Switch, and the output ports in the Sequential Switch. The Common ports could be configured differently, so full functionality would be there.
Of course this 2nd option would be a bit trickier from a coding standpoint, but it certainly could be done. If there are already cables patched into any of the “input” or “output” ports, then either the context menu configuration options would have to be disabled, or else the existing cables would have to be automatically removed if the configuration changes.
With the Sequential Switch “output” ports configured as input, I suppose the effective input would be a unity mix of the two ports.
What do you think?
When developing the module we considered some of those alternatives. But none of those seemed to us “clean” and simple. The ideal would be if Rack provided input/output jacks that change the direction based on what’s connected. I will contact Andrew and ask if he can think of a better solution and if he thinks it worths implementing it.
We decided to stick to the default behavior. I guess that there are other modules in Rack to achieve the complementary behavior for now.
There are other DotCom modules (that I did not port) that use jacks as I/O. That’s one of the advantages of acausal systems like hardware.
Hello @modlfo,
About LFO++. several knobs (eg Sus time, Decay, Speed…) seem to have an exponential behavior just before the end of their possible value. Is it “normal”?
Alain
Yes. All those have exponential behavior.
In the “Gate Math” page, the link to the manual goes to the MIDI module page.
Alain
I love the new State Variable Filter. It’s an acid monster.
that’s already been mentioned by jomas in post #22
Thank you thank you! I’ve started using these and they are wonderful
Good evening,
I have the sequencer providing CV as VOCT to the VCO. Via the Quantizer bank, in Scale mode, it’s impossible (for me) to get the E4. Same test directly (with no Quantizer), that works.
All the modules in Synthetizer.com of course.
Strange. I will be able in case of to publish the patch tomorrow morning (France).
Alain.
I don’t see the problem, maybe different settings. Are you in minor scale, that would miss E? Your patch will help to work it out
Thank you. Works! I think I misunderstood the documentation. Actually, how does the module guess the root note of a chord, or the root note of a scale, to define for instance chords of a minor or major scale? Alain
Interesting. That is indeed a hard (impossible?) problem, in general. For comparison my Visualizer module does that. Probably differently than this module. I’d be happy to talk about that over on my thread, if you are interested.
I didn’t know this collection, and typically this module. Really interesting to explain things. Thank you! Alain
oops - I had the wrong link in there. I’ll send you a message in the right place.