Xhun Audio LittleOne : version 4.x Released
-
- KVRAF
- 3980 posts since 20 Feb, 2004
'Nother bug:
Same setup as before; saving a project reverts patch settings to whatever preset patch you had loaded as a basis for your modifications.
Same setup as before; saving a project reverts patch settings to whatever preset patch you had loaded as a basis for your modifications.
A well-behaved signature.
- KVRian
- Topic Starter
- 1154 posts since 17 Feb, 2010
All the "presets issues" seem to be related to Cubase only...JerGoertz wrote:'Nother bug:
Same setup as before; saving a project reverts patch settings to whatever preset patch you had loaded as a basis for your modifications.
In Cubase 6.5 it affects both VST2 and VST3, in Cubase 8/9 it affects VST3 only (VST2 works fine). It includes the "preset jump" (pressing the arrow once, it goes 2 presets forward). Other hosts all seem to work fine... I'll check it! Maybe a "rounding issue".
- KVRian
- Topic Starter
- 1154 posts since 17 Feb, 2010
Hi,JerGoertz wrote:'Nother bug:
Same setup as before; saving a project reverts patch settings to whatever preset patch you had loaded as a basis for your modifications.
you previously mentioned :
>>when reloading a project, the patch loaded seems to be off by one position
then you said that :
>>saving a project reverts patch settings to whatever preset patch you had loaded as a basis for your modifications.
Both things happen to you or only one of them?
It seems that all other hosts at first initialize all the parameter of a plugin, then assign the project values to them (correct).
Cubase instead, at first assigns values to parameters, then initalize them. This could lead to your issue...
-
- KVRAF
- 3980 posts since 20 Feb, 2004
Both happen, although I'm not sure whether in the same project if that's what you mean. I've only had one other plugin with similar issues in Cubase, so there must be a workaround...
A well-behaved signature.
- KVRian
- 1266 posts since 30 Apr, 2004 from Louisville, KY
Many thanks.xhunaudio wrote:Hi simmo75 and bftucker,
ok no problem, I can both set the interrupting signal to 60 seconds and lower the amplitude of the signal. My apologies, maybe I didn't spend so much time playing the demo version and maybe after a long time it could result too much unpleasant to listen. Available in the next update!
바보
- KVRian
- Topic Starter
- 1154 posts since 17 Feb, 2010
Ok, an update:JerGoertz wrote:Both happen, although I'm not sure whether in the same project if that's what you mean. I've only had one other plugin with similar issues in Cubase, so there must be a workaround...
the presets arrow issue seems to be related exclusively to Cubase Host. Earlier versions (Cubase 6) have this issue with VST and VST3, latest versions (Cubase 8/9) with VST3 only.
Please let me know if it happens also in other environments/hosts or if it works fine.
I'll fix that in next updates, also if disabling the arrows will be the only way (selecting presets through the menu will be always possible).
I'll do my best !
- KVRAF
- 40229 posts since 11 Aug, 2008 from clown world
Ableton Live 9 Suite 32bit, 64bit Windows 7. I thought I was having problems with the Preset Arrows but just put it down to the high CPU of some of the Presets. Maybe you can take a look there as well.
Anyone who can make you believe absurdities can make you commit atrocities.
- KVRian
- Topic Starter
- 1154 posts since 17 Feb, 2010
CPU hit on older systems is something unavoidable... This thing will mitigate itself, let's hope Intel Corporation will finally find new materials...Aloysius wrote:Ableton Live 9 Suite 32bit, 64bit Windows 7. I thought I was having problems with the Preset Arrows but just put it down to the high CPU of some of the Presets. Maybe you can take a look there as well.
By the way what kind of issues did you have with presets? Loadind/saving a project? Or when using the arrows to advance one preset (and it advances 2 presets)?
-
- KVRian
- 925 posts since 14 Dec, 2014
Live 9 x64 on Win 10 x64, similar problemAloysius wrote:Ableton Live 9 Suite 32bit, 64bit Windows 7. I thought I was having problems with the Preset Arrows
Seems the presets arrows treat the "mouse buttom up" as a second "click".
- KVRian
- Topic Starter
- 1154 posts since 17 Feb, 2010
Indeed... all the issues project save, project load, +2 presets forward are related to the presets arrows.pottering wrote:Live 9 x64 on Win 10 x64, similar problemAloysius wrote:Ableton Live 9 Suite 32bit, 64bit Windows 7. I thought I was having problems with the Preset Arrows
Seems the presets arrows treat the "mouse buttom up" as a second "click".
My apologies, I'll fix that in the next update soon ! Anyway, in the meantime I wish you will appreciate the DSP side
-
- KVRAF
- 3980 posts since 20 Feb, 2004
The DSP side is fantastic, no complaints here. However, the problems I mentioned render LOv3 unusable for me. Really looking forward to having those fixed.
A well-behaved signature.
-
- KVRist
- 33 posts since 24 Feb, 2013
Is it just me, or does the LFO not seem to work most of the time (at least in the demo)?
In some of the presets it works (and changing it will change the sound) but on others (including the init like patch the synth starts on) it does not seem to have any effect on the sound (and I have made sure that the LFO amount is above 0).
In some of the presets it works (and changing it will change the sound) but on others (including the init like patch the synth starts on) it does not seem to have any effect on the sound (and I have made sure that the LFO amount is above 0).
-
- KVRAF
- 4504 posts since 25 Mar, 2016 from Seattle
I noticed that too, but it seems random so wasn't sure if it was user error. Also, when I change presets with the arrows it skips over the next preset. Sound is lush though.Devastator wrote:Is it just me, or does the LFO not seem to work most of the time (at least in the demo)?
In some of the presets it works (and changing it will change the sound) but on others (including the init like patch the synth starts on) it does not seem to have any effect on the sound (and I have made sure that the LFO amount is above 0).
-
- KVRian
- 925 posts since 14 Dec, 2014
Seems the LFO is tied to the modwheel, so you gotta rise the modulation with the modwheel to get the LFO's effect.
Also: it always starts with the arp/FX view here, so weird the first time.
Also: it always starts with the arp/FX view here, so weird the first time.