Prima Delay unofficial Demo VST plugin for Windows ready
-
- DASH Guy
- 8159 posts since 20 Sep, 2001
Here is an unofficial Demo VST plugin for Windows:
http://www.nusofting.liqihsynth.com/zip ... indows.zip
Demo Restrictions:
The free downloadable Demo of the Prima Delay has these limitations:
1) Saving the state (presets) is disabled
2) The audio output mutes after about 20 minutes of usage, then you need to unload and reload it to enable audio output again
3) Each 35 seconds a gentle bell plays thru the audio to remind you the demo mode.
The say software can not have no bugs.
So you can win one license of Prima Delay.
A free license (Mac and Win) is available to anyone who can find a meaninfull bug in the plugin.
please check the Manual
http://www.nusofting.liqihsynth.com/zip ... 20Help.pdf
Thanks
http://www.nusofting.liqihsynth.com/zip ... indows.zip
Demo Restrictions:
The free downloadable Demo of the Prima Delay has these limitations:
1) Saving the state (presets) is disabled
2) The audio output mutes after about 20 minutes of usage, then you need to unload and reload it to enable audio output again
3) Each 35 seconds a gentle bell plays thru the audio to remind you the demo mode.
The say software can not have no bugs.
So you can win one license of Prima Delay.
A free license (Mac and Win) is available to anyone who can find a meaninfull bug in the plugin.
please check the Manual
http://www.nusofting.liqihsynth.com/zip ... 20Help.pdf
Thanks
Last edited by liqih on Mon Mar 16, 2009 8:33 am, edited 2 times in total.
-
- KVRian
- 783 posts since 6 Jan, 2006 from Premià
Well, there's something which looks to me like an obvious bug: with short base times, I sometimes get the whole chain of taps once (as expected), but other times I get the whole chain of taps several times with decreasing amplitude, as if an extra, slower delay was applied to the wet output.
I still haven't found the cause of this behaviour though, or maybe I'm missing something here and it's a simple (dumb) user error?
Steps to reproduce:
1. Load the plug, load a preset with short base time i.e. Frigo resonance
2. Feed the plug with very short audio (i.e. a short snare without decay) -> the defined chain of short taps is reproduced once
3. Now feed the plug with longer audio (i.e. a drum loop) -> the defined chain of short taps is repeated several times with decreasing amplitude (?)
4. Wait a bit (maybe to clear buffers?) and repeat step 2 -> you get the expected behaviour (chain of taps reproduced once) again
This is on a puny pentiumM laptop running energyXT 1.4 under WinXP SP2...
Otherwise the plugin looks nice and able to produce a wide variety of cool effects, good job.
*EDIT*: Reproducible in Phrazor as well.
I still haven't found the cause of this behaviour though, or maybe I'm missing something here and it's a simple (dumb) user error?
Steps to reproduce:
1. Load the plug, load a preset with short base time i.e. Frigo resonance
2. Feed the plug with very short audio (i.e. a short snare without decay) -> the defined chain of short taps is reproduced once
3. Now feed the plug with longer audio (i.e. a drum loop) -> the defined chain of short taps is repeated several times with decreasing amplitude (?)
4. Wait a bit (maybe to clear buffers?) and repeat step 2 -> you get the expected behaviour (chain of taps reproduced once) again
This is on a puny pentiumM laptop running energyXT 1.4 under WinXP SP2...
Otherwise the plugin looks nice and able to produce a wide variety of cool effects, good job.
*EDIT*: Reproducible in Phrazor as well.
The mind boggles.
-
- DASH Guy
- Topic Starter
- 8159 posts since 20 Sep, 2001
Hi,
Thanks for the quick report!
"Frigo resonance" preset has a short base time but a slow deep modulation by the LFO, the Feedback is at max negative (-100%), this should explain the beaviour,
if you turn LFO Depth to zero, you should have no variable feedback
Thanks for the quick report!
"Frigo resonance" preset has a short base time but a slow deep modulation by the LFO, the Feedback is at max negative (-100%), this should explain the beaviour,
if you turn LFO Depth to zero, you should have no variable feedback
Last edited by liqih on Thu Mar 12, 2009 5:28 pm, edited 1 time in total.
-
- KVRian
- 783 posts since 6 Jan, 2006 from Premià
Ah OK I get how it works now, thanks for clarifying... but the problem is still there at LFO Depth=0, I mean I don't get variable feedback but EITHER correct feedback OR no feedback. Particularly if I feed silence to the plug for a bit and then I feed it with short audio snippets, the feedback doesn't seem to "kick in", it's only after I feed "longer" incoming audio that the feedback starts working as expected again...liqih wrote:Hi,
Thanks for the quick report!
"Frigo resonance" preset has a short base time but a slow deep modulation by the LFO, the Feedaback is at max negative (-100%), this should explain the beaviour,
if you trun LFO Deptth to zero, you should have no variable feedback
EDIT: Also there seems to be some kind of denormal issue going on... generally cpu usage is higher with silence than with audio at the input (?), plus my machine seems to handle this preset (Fringe Resonance) just fine but if I set LFO Depth to zero after a while it maximizes cpu usage and doesn't get back to normal even if I stop feeding audio to the input: I have to reload the plugin.
The mind boggles.
-
- DASH Guy
- Topic Starter
- 8159 posts since 20 Sep, 2001
feedback in Prima Delay somehow depends on the lenght of the input, but I'll check better later what you say,
that LFO Depth to zero = max CPU sounds like a bug I left behind, I check now
that LFO Depth to zero = max CPU sounds like a bug I left behind, I check now
-
- DASH Guy
- Topic Starter
- 8159 posts since 20 Sep, 2001
confirmed bug : LFO Depth to zero = increased CPU usage...
one more denormal issue missed,
Congratz Juanjo you won your license,
one more denormal issue missed,
Congratz Juanjo you won your license,
-
- KVRian
- 783 posts since 6 Jan, 2006 from Premià
Ah, then the problem seems to be that sufficiently short bursts of audio at input don't "trigger" any feedback at all, if preceded by a long enough silence.liqih wrote:feedback in Prima Delay somehow depends on the lenght of the input, but I'll check better later what you say,
Yep it's weird, maybe not denormals though as I can't correct the issue with GVST's GNormal (which usually works). Let me know if I can provide any further info.liqih wrote:that LFO Depth to zero = max CPU sounds like a bug I left behind, I check now
EDIT: just saw your comment above, so it WAS denormals then
The mind boggles.
-
- DASH Guy
- Topic Starter
- 8159 posts since 20 Sep, 2001
not audio denormals, but on parameter
Demo updated, same link, now it should not burn CPU
http://www.nusofting.liqihsynth.com/zip ... indows.zip
Demo updated, same link, now it should not burn CPU
http://www.nusofting.liqihsynth.com/zip ... indows.zip
-
- DASH Guy
- Topic Starter
- 8159 posts since 20 Sep, 2001
Thanks ZW, the message is for Live does a check of the plugins state at each unload, now I'm gonna check that issue
-
- DASH Guy
- Topic Starter
- 8159 posts since 20 Sep, 2001
Tried in XP SP3 and Live 7, no message deleting the plugin, could it be a a Live 8 Beta issue to report to Ableton?
- KVRian
- 622 posts since 12 Mar, 2005
The error happens each time I unload the plugin in Live 8 Beta 17. In Live 7.0.14, it is not as evident, but it does happen when I delete the plugin from a track and then undo the deletion.liqih wrote:Thanks ZW, the message is for Live does a check of the plugins state at each unload, now I'm gonna check that issue
-
- DASH Guy
- Topic Starter
- 8159 posts since 20 Sep, 2001
yes I found it, so it's the Undo feature of Live over the Demo of Prima Delay to do that, as you know the Demo doesn't save presets, but the Undo to work needs to save the plugin state. So I could simply say that the Demo of Prima Delay done's not support Undo, or force the Demo to save a dummy bank file so that Live is happy to have something to reload.
The difference to Live 8 seems that now it checks in advance if the plugin can reload by Undo.
The difference to Live 8 seems that now it checks in advance if the plugin can reload by Undo.
- KVRian
- 622 posts since 12 Mar, 2005
Good catch. Not really a bug then, but a path to deeper understanding.liqih wrote:yes I found it, so it's the Undo feature of Live over the Demo of Prima Delay to do that, as you know the Demo doesn't save presets, but the Undo to work needs to save the plugin state. So I could simply say that the Demo of Prima Delay done's not support Undo, or force the Demo to save a dummy bank file so that Live is happy to have something to reload.
The difference to Live 8 seems that now it checks in advance if the plugin can reload by Undo.
