Yeah, they can help get more complex results with fewer operators. If you have Reaktor, look for an ensemble called SY66; it's a 6 operator FM synth that lets you use several different DSP waveforms or imported samples for each operator. Galbanum's Architecture waveforms work nice with it.c_voltage wrote:Hm different waveforms (additionally to sinus) in fm osc would be really good.
UVI Falcon - v4 = 2026 released - rumors, ads, praise, kindergarden, auto-sampling and off-topic inside!
-
- KVRian
- 1209 posts since 11 Jan, 2006 from Pittsburgh
-
- KVRAF
- 2487 posts since 28 Mar, 2005
Currently you cannot set it explicitly.the3ug3reeder wrote: in the Multi Envelope, is it possible to have more than one point in the release stage?
However if you load back the default envelope and add step after the last one, then they will be after the release step and hence part of the release segment.
-
- KVRAF
- 24415 posts since 7 Jan, 2009 from Croatia
Hm, I have no problems in setting more loops in the release stage here...
-
- KVRAF
- 2487 posts since 28 Mar, 2005
-
- KVRAF
- 1925 posts since 23 Sep, 2005
Hi otristan,otristan wrote:@Muziksculp what is your PC setup ?
My PC : OS is Windows 8.1 / DAW : Cubase Pro 8.5.15
I emailed your support (UVI-Support), about this issue in more detail, but have not received a reply yet.
Thanks,
Muziksculp
-
- KVRist
- 109 posts since 28 May, 2013 from MUC
Thanks Oliver, this works. For some reason i didn't try adding points AFTER the last point beforeotristan wrote:Currently you cannot set it explicitly.the3ug3reeder wrote: in the Multi Envelope, is it possible to have more than one point in the release stage?
However if you load back the default envelope and add step after the last one, then they will be after the release step and hence part of the release segment.
-
- KVRist
- 109 posts since 28 May, 2013 from MUC
in the Slice Oscillator...
are there any modulation sources that can be used to modulate the starting slice?
i've tried quite a few of them, and they all seem to cause the dial to react, but actual starting slice only modulates between slice 0 and slice 1.
i thought it might be necessary to add a mapper but that doesn't seem to work either... then i thought it might be necessary to set the mapper to uninterpolated integer output. that also doesn't work.
assigning a host automation id does work as expected.
is this a bug?
are there any modulation sources that can be used to modulate the starting slice?
i've tried quite a few of them, and they all seem to cause the dial to react, but actual starting slice only modulates between slice 0 and slice 1.
i thought it might be necessary to add a mapper but that doesn't seem to work either... then i thought it might be necessary to set the mapper to uninterpolated integer output. that also doesn't work.
assigning a host automation id does work as expected.
is this a bug?
-
- KVRAF
- 2487 posts since 28 Mar, 2005
Never tried to modulate that.
Might be easier to map it and then add some random note triggering no ?
Might be easier to map it and then add some random note triggering no ?
-
- KVRist
- 109 posts since 28 May, 2013 from MUC
actually, what i'm trying to achieve is a kind of round robin effect using the slice oscillator.
since it's possible to connect the start position to a modulation source, i think this should work.
especially since it does work when connected to an automation curve...
since it's possible to connect the start position to a modulation source, i think this should work.
especially since it does work when connected to an automation curve...
-
- KVRAF
- 2487 posts since 28 Mar, 2005
@the3ug3reeder I suspect it doesn't work either using automation curve. This is an engine limitation regarding parameter with no static range as this one is related to the number of markers. I will disable the modulation.
-
- KVRist
- 109 posts since 28 May, 2013 from MUC
thanks for your reply Oliver,
i tested host automation again, and it seems at first to work as expected though it is 'funky'... for example, (in reaper) setting the start value to '0' will write a maximum value in the automation curve, and the in between values seem to be written as negative integers though the start dial in the slice oscillator seems to react properly to the recorded automation.
it would be a shame to simply disable the modulation feature. if it worked properly, i could definetly find many uses for it.
one possible implementation might be to modulate the start position via a Mapper that is set to integer output... in this case you could manually set the range of the mapper to equal the number of slices in your sample.
i tested host automation again, and it seems at first to work as expected though it is 'funky'... for example, (in reaper) setting the start value to '0' will write a maximum value in the automation curve, and the in between values seem to be written as negative integers though the start dial in the slice oscillator seems to react properly to the recorded automation.
it would be a shame to simply disable the modulation feature. if it worked properly, i could definetly find many uses for it.
one possible implementation might be to modulate the start position via a Mapper that is set to integer output... in this case you could manually set the range of the mapper to equal the number of slices in your sample.
-
- KVRist
- 302 posts since 1 Feb, 2014
I have idea for automation / modulation range control - that means (for example) if I have cut off on 60% and I want modulate it with ADSR from maximum to 60% I must find ratio value for ADSR where is maximum, because when is modulation ratio on 1, the decay from cut off is some short time on maximum and then go to 60% (Sustain level is on zero). I must set value 1 down to lower value and find when is modulation on maximum. (In different explanation - if I add ADSR modulation to cutoff with 60%, and ratio in modulation is 1, it is like from 160% to 60% and not from 100% to 60%) My idea is add new button (where are Inverted and Modulation mapper buttons), which change maximum ratio to maximum value for modulation, that means it will modulate from 100% to 60% and not from 160% to 60%. This setting make this, if I change value on cutoff filter, ADSR modulation will be still from 100% (if ratio will be on 1) or 80% (if ratio will be on 0.8 ).
I hope you understand what I want say
.
I hope you understand what I want say
.-
Sampleconstruct Sampleconstruct https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=191286 - KVRAF
- Topic Starter
- 16752 posts since 12 Oct, 2008 from Here and there
-
- KVRist
- 109 posts since 28 May, 2013 from MUC
in the Analog ADSR, i think the time values displayed under Attack Decay and Release are very wrong.
1. set attack to 100 micro seconds, decay to 350 milliseconds, sustain to 0%
2. hit a key and simultaneously start your stopwatch.
3. wait 'till the sound gets so quiet that you can't hear it, and hit stop on your stopwatch.
my stopwatch says 6.8 seconds.
1. set attack to 100 micro seconds, decay to 350 milliseconds, sustain to 0%
2. hit a key and simultaneously start your stopwatch.
3. wait 'till the sound gets so quiet that you can't hear it, and hit stop on your stopwatch.
my stopwatch says 6.8 seconds.
-
- KVRAF
- 24415 posts since 7 Jan, 2009 from Croatia
That makes perfect sense for an analog envelope - you see, on analog envelopes it was all about discharging capacitors, and their decay curve is exponential and asymptotic, which means that theye never fully reach the final expected value. Hence you cannot perfectly measure the length of a decay stage, you can only use some speculative measurements like "time needed to reach 60% of amplitude". Or 90%. And so on.
Not sure if that classifies as a bug. Go by your ears, not eyes. Or, if you want a precise envelope, use DAHDSR.
Not sure if that classifies as a bug. Go by your ears, not eyes. Or, if you want a precise envelope, use DAHDSR.