Ok, fine, thanks!
Hope you can manage to group visually the various controls even more effectively
- Mario
QDelay - new free Dual-Delay
-
- KVRAF
- 3154 posts since 10 Jan, 2005
Hope you can manage to group visually the various controls even more effectively
- Mario
-
- KVRist
- Topic Starter
- 171 posts since 17 Sep, 2023
Hey its a known issue, unfortunately I can't replicate it as well otherwise would have fixed by now. Another crash I had is when toggling the pan mono/collapse (two circles button next to pan knobs). Both issues are difficult to replicate and I cannot get them with the debugger turned on, also cannot find anything obvious wrong with the code.Vortifex wrote: Fri Jan 09, 2026 2:41 pm I've had some crashes when I turn the reverse mode on or off but I can't replicate it reliably.
If you find a way to get this bug more often please let me know.
-
- KVRist
- Topic Starter
- 171 posts since 17 Sep, 2023
Ah yes forgot that one, will see if its doable.mabian wrote: Fri Jan 09, 2026 2:42 pm Ok, fine, thanks!
Hope you can manage to group visually the various controls even more effectively
- Mario
-
- KVRAF
- 4225 posts since 1 Sep, 2016
Yeah it's a weird one. I made it crash just by selecting reverse on the init preset in a blank project without any audio playing. I'll keep investigating.tilr8 wrote: Fri Jan 09, 2026 2:45 pm Hey its a known issue, unfortunately I can't replicate it as well otherwise would have fixed by now. Another crash I had is when toggling the pan mono/collapse (two circles button next to pan knobs). Both issues are difficult to replicate and I cannot get them with the debugger turned on, also cannot find anything obvious wrong with the code.
If you find a way to get this bug more often please let me know.
-
- KVRist
- Topic Starter
- 171 posts since 17 Sep, 2023
Just published a potential fix to this problem, user named @evilcream noticed these crashes sometimes happen when closing and opening the UI, sure enough some params were not being unregistered on UI close.Vortifex wrote: Fri Jan 09, 2026 3:10 pm Yeah it's a weird one. I made it crash just by selecting reverse on the init preset in a blank project without any audio playing. I'll keep investigating.
With some luck is fixed, let me know if it still happens in 1.0.6 or later.
-
- KVRAF
- 7027 posts since 28 Apr, 2004 from france
Hello
I noticed that v108 is out, with some bit reduction added : thank you for that!
Two suggestions, if you don't mind :
- I find a bit strange that the samplerate and bitreduction is labelled in percentages. How would you do to set the delay quantization to 12bit, then? Wouldn't it make more sense to be able to dial in "accurate" units (like "8bit", "12bit", or 13500Hz)?
- If you're willing to add more FX to the delay lines, did you consider a phaser? It's an effect I use quite often on wet delays
I noticed that v108 is out, with some bit reduction added : thank you for that!
Two suggestions, if you don't mind :
- I find a bit strange that the samplerate and bitreduction is labelled in percentages. How would you do to set the delay quantization to 12bit, then? Wouldn't it make more sense to be able to dial in "accurate" units (like "8bit", "12bit", or 13500Hz)?
- If you're willing to add more FX to the delay lines, did you consider a phaser? It's an effect I use quite often on wet delays
-
- KVRist
- Topic Starter
- 171 posts since 17 Sep, 2023
Hi, I should add more FXs as I need yes, I never used phaser on delay, maybe I'm missing something.
About the percentages, yes they are not great I admit, problem is with other scales I would have to invert the sliders to be proper, somehow JUCE sets values to zero on presets that do not contain the values, meaning the scale is full bitcrushing if I use inverted values when switching existing presets, the alternative is to add inversion to the slider itself, but its a bit of code. I can also use the current 0...1 values and only update the labels to be bits and srate instead of percentage but would be confusing when automating from the DAW as the values would not match and be inverted.
Sorry, long answer short, as it is its not great but gets the job done. I'll keep that in mind in any case, third option seems the most likely I think.
About the percentages, yes they are not great I admit, problem is with other scales I would have to invert the sliders to be proper, somehow JUCE sets values to zero on presets that do not contain the values, meaning the scale is full bitcrushing if I use inverted values when switching existing presets, the alternative is to add inversion to the slider itself, but its a bit of code. I can also use the current 0...1 values and only update the labels to be bits and srate instead of percentage but would be confusing when automating from the DAW as the values would not match and be inverted.
Sorry, long answer short, as it is its not great but gets the job done. I'll keep that in mind in any case, third option seems the most likely I think.
-
- KVRAF
- 3154 posts since 10 Jan, 2005
About the scale of the parameters... well, who cares?
Just tweak until it sounds good, what's the added value in knowing you are at 12.5 bits or 1233 Hz of sample rate? Just asking...
- Mario
Just tweak until it sounds good, what's the added value in knowing you are at 12.5 bits or 1233 Hz of sample rate? Just asking...
- Mario
-
- KVRAF
- 7027 posts since 28 Apr, 2004 from france
Ahahmabian wrote: Sat Jan 31, 2026 2:28 pm About the scale of the parameters... well, who cares?
Just tweak until it sounds good, what's the added value in knowing you are at 12.5 bits or 1233 Hz of sample rate? Just asking...
- Mario
For me, it's quite important if I try to recreate the sound of a specific delay unit.
It's not a matter of "if it sounds good then it's good", it's a matter of getting somewhere and conforming to a model.
I have a couple a early digital hardware racks, and I know their quantization specifications. If I want to get close to their sound with Qdelay, typing "12" for the bitrate will put me in the ballpark in less than a second. But turning a knob telling "27%" doesn't give me any kind of useful information.
It's exactly the same thing as trying to recreate a preset on Uhe Repro5 if you're lucky enough to have a Prophet 5 at home (or some preset sheets and want to recreate a specific sound).
Also, for instance : I don't know any filter plugin where the cutoff value is expressed as a percentage, because it just doesn't make sense. They are all labelled in Hertz, because that's what make sense, and what's useful (beyond the "if it sounds good it's good" paradigm).
To me, it's the same thing with bitrate and samplerate. Bitrate should be expressed in bits
-
- KVRAF
- 7027 posts since 28 Apr, 2004 from france
Thank you, Tilr8tilr8 wrote: Sat Jan 31, 2026 4:28 pm Makes sense, may take a couple of days or weeks as I am currently not programming at all but I think I'll add these values/labels.
-
- KVRAF
- 7027 posts since 28 Apr, 2004 from france
(and in the meantime, I might suggest you to try using a phaser on the delay path while playing music )
)-
- KVRAF
- 7027 posts since 28 Apr, 2004 from france
I like some presets from ReplikaXT using the phaser.
ReplikaXT is quite old, but features some very good presets.
Phaser in the delay path is used quite a lot in old school dub (on drums, chords, pretty much anything), also techno dub.
It can give a great sense of space and movement, and somehow "un-mask" the wet signal from the original signal. I use phaser on delay a lot more than chorus, for instance. It doesn't need to feature a lot of phasing stages (unless you cant an obvious coloration, like with a Mu-Tron), but a simple 2 stages phasing is rather transparent while being very effective.
ReplikaXT is quite old, but features some very good presets.
Phaser in the delay path is used quite a lot in old school dub (on drums, chords, pretty much anything), also techno dub.
It can give a great sense of space and movement, and somehow "un-mask" the wet signal from the original signal. I use phaser on delay a lot more than chorus, for instance. It doesn't need to feature a lot of phasing stages (unless you cant an obvious coloration, like with a Mu-Tron), but a simple 2 stages phasing is rather transparent while being very effective.
-
- KVRAF
- 3154 posts since 10 Jan, 2005
Funny enough, I think one of the plugins that had filter cutoff in numbers instead of hertz was u-he, Zebra2 IIRC...sinkmusic wrote: Sat Jan 31, 2026 4:24 pmAhahmabian wrote: Sat Jan 31, 2026 2:28 pm About the scale of the parameters... well, who cares?
Just tweak until it sounds good, what's the added value in knowing you are at 12.5 bits or 1233 Hz of sample rate? Just asking...
- Mario
For me, it's quite important if I try to recreate the sound of a specific delay unit.
It's not a matter of "if it sounds good then it's good", it's a matter of getting somewhere and conforming to a model.
I have a couple a early digital hardware racks, and I know their quantization specifications. If I want to get close to their sound with Qdelay, typing "12" for the bitrate will put me in the ballpark in less than a second. But turning a knob telling "27%" doesn't give me any kind of useful information.
It's exactly the same thing as trying to recreate a preset on Uhe Repro5 if you're lucky enough to have a Prophet 5 at home (or some preset sheets and want to recreate a specific sound).
Also, for instance : I don't know any filter plugin where the cutoff value is expressed as a percentage, because it just doesn't make sense. They are all labelled in Hertz, because that's what make sense, and what's useful (beyond the "if it sounds good it's good" paradigm).
To me, it's the same thing with bitrate and samplerate. Bitrate should be expressed in bits
- Mario