Rotary works peachy here in every patch I make as it is part of my default effects in my template. That is never crashing here, nor have I had any crash in 2.1.1 on MacOS 12.4. M1 Mini.
PLEASE, Ignore any specific plugin or modules discussed in my thread. At various times several modules seemed implicated in the crash but that seemed to just be due to the crash being more likely to occur the more modules there were in the patch.
That seems similar to what is happening here in this thread, perhaps.
Note, I edited my first post in my linked thread to clarify that this bug seems to be in Rack rather than in any specific plugin or module. But, this all still unresolved, so there is no solution closing out that topic, yet.
DaveVenom
June 10, 2022, 8:12pm
19
For anyone interested - I posted the following PAD2 enhancement requests on github, in case you want to express interest (or lack thereof) in the ideas:
opened 07:23PM - 10 Jun 22 UTC
I am loving the sounds and design of PAD2, and it is spawning lots of ideas:
… The Generate button that randomly creates partial amplitude profiles is begging for a trigger CV input to go with it.
And it would be great if there was an option for slew (knob and CV input) during profile transitions, expressed as seconds to morph from one profile to the next.
I think there should be 3 polyphonic CV inputs to cover the 48 partial amplitudes. There should be an option (control or context menu) to control whether the input voltages are sampled continuously, or by trigger. To keep things simple, you could ignore all partial inputs if the first input (2-17) is empty. If the first input is patched, then any missing channel(s) would default to 0.
I think less important, but still potentially useful would be 3 polyphonic outputs for the instantaneous partial values (reflecting any slew or morph state)
I envision the following rules for how the various inputs would interact:
If 1st partial input is empty, then:
- 2nd and 3rd partial inputs are ignored
- generate button (and new trigger input) randomly assign partial values following current method
- time to morph from old profile to new is set by slew
If 1st partial input is not empty, then:
- any unpatched partial channels default to 0
- method control is ignored
- If input mode is sample:
- generate button/trigger samples inputs to assign partial values
- time to morph from old profile to new is set by slew
- If input mode is continuous:
- partial values continuously updated by input values
- generate button/input and slew knob/input are ignored
opened 07:47PM - 10 Jun 22 UTC
The fundamental frequency definitely has a significant impact on the resultant s… ound. I generally find that as long as the value is <= the actual V/Oct pitch, then I perceive wavering pitch over time that is pleasing to my ears. As the V/Oct rises in pitch relative to the fundamental, I hear more and more "shimmer"
If the fundamental is > then V/Oct pitch, then I typically perceive stepped pitch variation over time that is jarring to my ears. Not sure if there is anything you can do about that. I am curious - Are you using the upsampling/downsampling tip from the algorithm creator? It might be interesting to try with and without, in case you haven't already.
Given that the fundamental has such a strong impact, it would be good if it had a CV input.
Beyond that, I think it might be nice if you could specify the fundamental frequency as a ratio of the incoming V/Oct. You could have a mode select (control or context menu) to control which option is used. If frequency mode, then the knob would offset the incoming V/Oct. If ratio mode, then the knob would attenuate/amplify the incoming V/Oct.
Now the big question - should the fundamental CV input be mono or polyphonic?
If computationally feasible, then allowing poly would be good, where each each channel gets its own wave table based on its own fundamental value.
If not feasible, then mono input is the obvious choice.
You could forgo a separate CV input for the fundamental, and simply use the existing V/Oct input. But I think a dedicated fundamental input gives the most flexibility.
opened 08:05PM - 10 Jun 22 UTC
PAD2 is great for discovering interesting sounds.
An expander could be used t… o store the current partial profile, as well as bandwidth, scale, etc. based on the press of a button (and maybe CV trigger input?)
The expander could have N slots, each with its own button for setting/recalling a given profile.
And there can be CV control to select any one of the slots on demand. And it can honor the slew that I suggested in another enhancement request. There can be a number of modes as to how the CV selects the each profile.
Basically I am talking about the functionality of Stoermelder's TRANSIT module, but dedicated to PAD and PAD2. TRANSIT has a large number of interesting selection modes.
The beauty of such an expander would be you could discover/dial in and store the sounds you want with PAD2, and then transfer the expander to PAD for a more compact combination that no longer needs the sound discovery UI of PAD2.
One thing I have not thought through is what the behavior of the PAD2 controls should be if they are modified after the expander specifies a given profile.
I see two different use cases for the expander
- To create compact static "instruments" using customized PAD sounds. By static I mean that the partial profile and other parameters would likely not change once set up.
- To sequence constantly evolving PAD sounds
One other idea is to have a mechanism to write out a given profile to an external file that can then be shared and loaded by others. There could be some interesting preset files distributed with the module(s)
1 Like
docB
June 24, 2022, 5:32pm
20
Mainly there are now some features for morphing between PAD sounds. See also:
Changes over pre1:
PAD2:
Uses bigger wave tables for higher sample rates
Has inputs for controlling the partials
The partial sliders start now with one - the fundamental (breaking change) which was set to 1.0 before
new module µPad2 : small version of PAD2 which is fully controlled by inputs (see manual)
PAD:
has now an amp knob for the first partial, was 1.0 before.
has now a menu for setting a fade time for morphing between changes
presets are now applied directly
has now a trigger input for regenerating the wavetable if parameters are externally changed (e.g.) via µMap
has a new method for generating saw and pulse wavetables
(see also manual)
Faders
has now 100 voltage addressable slots
has now a knob for setting a glide time to morph between slots
has 3 additional knob values
has a special function for fetching values from PAD2 to feed them into µPad2
(see also manual)
7 Likes
ablaut
June 25, 2022, 2:00am
21
and people can grab these and make a patch still in time for the current vcp challenge !
1 Like
docB
June 25, 2022, 6:24am
22
yes, its still a pre release but i think there will no breaking changes anymore so it will stay compatible in the patches.
FiroLFO
June 25, 2022, 10:21am
23
Those Pad2 demos sound so gorgeous…
1 Like
Amazing collection of modules doc, really need to dive into these. Well done and thanks!
1 Like
docB
July 9, 2022, 8:04am
25
Thanks all for testing/commenting.
dbRackModules 2.1.0 is now in the library.
6 Likes
FiroLFO
July 9, 2022, 4:42pm
26
It still excludes the latest ACC modification , doesn’t it?
docB
July 9, 2022, 4:52pm
27
sure, because ACC is dbRackSequencer. There i have to write manuals first, as there are some new modules.
FiroLFO
July 9, 2022, 5:03pm
28
Ah, right…
1 Like
Yesssssss new docB modules! So hyped!
Do you take ideas/suggestions for new modules?
docB
October 16, 2022, 6:34am
31
Release dbRackModules 2.1.3 is now in the Library
New modules:
PHSR2 An advanced Phasor for phase distortion with FM.
CSOSC A cosine oscillator with skew and clip controls.
BWF An FFT based brickwall filter.
EVA A tiny fast ADSR with integrated VCA, also designed for use as part of an FM operator.
Ratio Applies a ratio to an incoming V/O signal, designed for use as part of an FM operator.
Fixes/Enhancements:
RSC occasional freeze on windows now gone
PLC Hover Keys ^R and ^I now working
Faders right click now correct
MVerb Fixed noise if wet = 0; Fixed Mesh_Freq_Mod amount – is now V/Oct if Amt = 1
PHSR has now FM
PhO has now a knob for setting a phase offset (e.g. 0.25 = 90° = cosine)
21 Likes
Can’t wait to check it out!
1 Like
Glad to have PHSR2 and Ratio. I find a lot of this collection really useful in fact!
1 Like
Squinky
October 18, 2022, 5:13am
34
what’s the latency on BWF?
docB
October 18, 2022, 5:16am
36
depends on the fft length (1024,2048,4096 - config in menu)
1 Like
I’m already dizzy because of the amount of modules you released.