Forums
1.) Switch DCA on, set Volume knob (the leftmost knob) to 0, switch DCA off: sound is still silent according to Volume knob although the knob is greyed out. To my understanding volume should be at 100% when DCA is off.
But I recommend not to change the behaviour for backward compatibility with existing sessions. It might break a mix. Maybe the Volume knob should not be greyed out when switching DCA off to show that is still in effect.
2.) Switch DCA on, set Volume knob to 100. With DCA off the sound is brighter, probably distorted, than with DCA on. Please see attached screencast.
File attachments
re. Two oddities...
I think the said oddities resolve to one single concept:
DCA Volume
this is probably a misnomer, as in other synth UIs or descriptions it is equivalent to the amount (volume?) of the signal that will feed the DCA EG (Envelope Generator) stage; it is not and not to be confused with to the final OUT Volume, which stands as the ultimate volume fader (or knob) to each synth engine (that precedes the Effects block).
however, on a second and deeper glance, there are tree (3) parameters that altogether contribute to the actual final mix: MIDI CC#10, DCA Volume and OUT Volume: the problem might be that DCA Volume is always in effect, no matter the respective DCA EG block is on or off, and that's in fact the real trouble.
Yes. it's wrong, a "dead bug" if you may call it that way, but nothing really serious or is it?
is anything missing there? please tell me.
thanks
distortion?
What about the difference in sound between "DCA on" and "DCA off" (LED on and off) when Volume = 100%? How can that be? Isn't that a bug?
re.distortion?
when DCA Volume is set to 100% or whatever, it applies regardless to the DCA block being switched On or Off--that's the whole point.
the bug is in details :)
also, this affects both drumkv1 and samplv1 (not the others that cannot have their DCAs turned off anyway :)).
re2. dirtor
It's not distortion, it's brighter because that's how the original sample sounds. Confirm that.
In drumkV1, the envelope engine is very cautious, which means some high frequencies are lost... but in return, you never hear a clipping artifact on the attack from cutting the waveform at the offset. I think that's the important thing.
re3. dirtor
well, that might be exactly what is supposed to work anyway: when you turn off the DCA block then you're actually playing the original sample envelope, whatever it is and not damping it with the DCA EG ADSR or am I missing something?
anyway, latest [develop] branch might have this issue abated, on drumkv1 and samplv1, ofc.
cheers
Standalone drumkv1: it's brighter than the original
Distortion:
With DCA off the attached kick_01.wav sample has an initial click that the original sample doesn't have when played in Audacity
*** I noticed that the LV2 plugin doesn't show this behaviour, only the standalone version ***
Volume:
It works now as expected (standalone and lv2): full volume when DCA is off, regardless of the DCA Volume. In principle that's correct but it will mess up all existing projects with drumkv1 where DCA is off but volume is not at 100%. So I don't think it's a good idea. I'd leave it as is.
re. it's brighter than the original
I've been experimenting with the new presets... and now the sound is much richer. You can really hear that extra brightness of the original sample.
In comparison, drumkv1 classic sounds a bit lo-fi.
So I think this would be a significant improvement.
The solution might be to include a "Classic" parameter in "DCA" that would be activated if the parameter doesn't exist in the element's XML. This would make it backward compatible.
What do you think?
re. it's brighter than the original
I think first we should make sure that we experience the same issue. First I thought that the standalone version behaves differently than the lv2 plugin. That's not true. I made a mistake. So we can use the lv2 version.
Please see the attached session. The same sample is in drumkv1 and on an audio track. Both sounds equal. A bit dull, but that is how the sample is.
But when you switch off DCA then it gets an initial, artificial click as if there is some distortion.
Can you confirm that?
re2. it's brighter than the original
If you disable or neutralize all the parameters that can modify the waveform (like send 100, attack 0, level 100, decay 100) and eliminate the limiter effect (which Rui already indicated is a fake limiter, actually a saturator), and you equalize the track volumes... They sound the same, I think.
And I also think that when I tried this new version of drumkv1 and samplv1, the sound seemed richer and brighter to me, simply because I had that expectation, and also because my ear was rested.
So I think this improvement won't have any consequences for older projects, and my previous suggestion is pointless...
re3. it's brighter than the original
On my machines a click is added, please see and hear the attached video with audio.
re4. it's brighter than the original
It took me a while to understand you... sorry.
Activate the offset parameter and the distorted clip disappears.
If you work in Qtractor at the same frequency as the sample (441000), it also disappears.
My hypothesis is that when converting, the offsets can change, and "offset" is responsible for correcting them.
(In fact, with the offset activated, if you increase it by two milliseconds, the distortion clip reappears.)
re5. it's brighter than the original
You're right. The sample is in 44100 Hz but my audio system runs with 48000.
The click vanishes when I activate the offset parameter, even if the offset is 0.
Thank you.
Speaking of volume...
Is essential that in the effects section, right after Dynamic (Compress and Limiter), there should be a master gain control, volume control, amp control, or whatever you want to call it.
Another one? SamplV1 and PadthV1 don't need it because they can be controlled with the existing master volume. However, DrumkV1 and SynthV1 (since they have two synths in one) do... They don't have a master instrument volume control.
This complicates things considerably when you want to combine several instances on a track to create combo instruments.
re. Speaking of volume...
no. you do control the effects section by means of the "OUT Effects" knob (think of it as a wet control, formerly named "FX Send" on the late century or whatever); in this vein, "OUT Volume" is therefore considered the dry output signal control.
isn't that enough?
Yes and no?.. umm no
In DrumKv1, it would be sufficient if it affected all instruments equally (it's an instrument of instruments), not each instrument separately.
But that solution isn't backward compatible.
Something similar happens in SynthV1... You already have the instrument configured, but there are two synths in one. So you adjust the volume in one and... Damn!... I messed it up because it doesn't affect both synths.
This has also made creating the instrument collection very difficult, especially when it comes to reviewing it to ensure all the presets have equivalent volumes... Since there's no way to adjust the volumes of the two synths integrated into the single SynthkV1 and maintain the exact same ratio without using a calculator... Of course, I did it by ear.
So, either we add another gain control to the plugin's final output... or we delegate it to the current control, which will then become global and therefore not backward compatible.
Or you can leave it as is, of course... but this implies many significant shortcomings (already mentioned) for certain workflows such as creating presets, samples, or simply being able to combine several instances in a single track.
Solution: Global Parameters Link
Conclusion
It would be better to be able to select multiple "elements" in de list. If I make a change, it would apply to the selected ones.
If I import a wav it is imported in all of them... I have needed something like this for a long time.
However, it would be a lot of work...
Multiple selection function:
1 When selecting several elements, it is checked which parameter values are shared (identical values between elements).
2 Those parameter that are not shared are marked with a custom-property (a state) "not-shared-value". They should show default parameter values and a grayed out graphical style.
3 When modifying any parameter value, it is applied to all elements, which automatically loses the "no-shared-value" status, since now it shares identical values in those edited parameters.
---- Process that has led me to the conclusion ---
This would solve the problem and be compatible with older versions since it's just a UI feature. If enabled, the change is applied simultaneously to all instruments (DrumkV1) or synths (SynthV1). It doesn't affect the audio or the logic.
In the image, I only placed it for the OUT function, but instead, it could go right before the footer and affect all parameters.
That would be really useful.
EDITED!!!
It's better as a button at the top. If it's activated, it appears highlighted, because if it's activated by mistake it can cause problems...
Likewise, all keys with WAV files appear in the selected state.
The most appropriate name would be "Global edit".
EDITED 2!!!
On second thought, it would be better to be able to select multiple WAV files/keys. If I make a change, it would apply to the selected ones.
If I import a wav it is imported in all of them... I have needed something like this for a long time.
As for SynthV1... I'm still not sure.
Forget all the previous chaos
It would be useful, compatible, and implementable...
Add a checkbox to the DrumkV1 and SynthV1 options:
"Unified OUT Volume editing".
With this checked, when I edit a volume, the change applies to all instruments (elements in DrumkV1, synthesizers in SynthV1).
Add new comment