I believe so yes.Bandaide wrote: Mon Aug 24, 2020 9:15 pm Can one of you Cypher 2 gurus remind me how to delay the LFO, Juno style.
I have to use a ramp, don't I?
FXpansion releases Cypher2
-
- Banned
- 7624 posts since 13 Nov, 2015 from Norway
EnergyXT3 - LMMS - FL Studio | Roland SH201 - Waldorf Rocket | SoundCloud - Bandcamp
-
- KVRist
- 71 posts since 21 May, 2015
I'm going to answer my own question:
Using the TransMod system to scale modulators (pg 47)
Using the Ramp to delay and 'fade in' an LFO
1. Deactivate the Sync and Loop buttons on the Ramp section if they are activated.
2. For Ramp 1, increase the Delay parameter to around 500ms and increase the Rise parameter to
around 1 second. 3. Select the LFO+ source in the upper part of a TransMod slot
4. Select Ramp+ as a Scale function in the lower part of the same TransMod slot
5. Now set a TransMod modulation depth within this slot on a parameter such as the Filter Cutoff or
Oscillator Wave control in order to hear the effect.
Using the TransMod system to scale modulators (pg 47)
Using the Ramp to delay and 'fade in' an LFO
1. Deactivate the Sync and Loop buttons on the Ramp section if they are activated.
2. For Ramp 1, increase the Delay parameter to around 500ms and increase the Rise parameter to
around 1 second. 3. Select the LFO+ source in the upper part of a TransMod slot
4. Select Ramp+ as a Scale function in the lower part of the same TransMod slot
5. Now set a TransMod modulation depth within this slot on a parameter such as the Filter Cutoff or
Oscillator Wave control in order to hear the effect.
-
- KVRAF
- 4751 posts since 22 Nov, 2012
it's not currently fixed, and they haven't said anything directly that i know of. but, the developer has come on and stated that it is still being developed and supported, and i'm pretty sure he is trying to fix it if he can, it's just creating some issues because it's taking a while probably. i'm thinking it will be fixed before they stop supporting it. it might be a huge install tho.
-
- KVRer
- 28 posts since 26 Oct, 2017
I've pinged Roli a couple of times recently about this and there's just no response now. Before the standard response would be along the lines of "this is complex and will take a long time". The bug was first raised with them over a year ago. If anyone hears from Roli or the FXpansion team on this it'd be great to know what they are saying about it. I wouldn't be surprised if we see some sort of "new" synth from Roli with he same functionality (and mod matrix) as Cypher and Strobe that we would have to pay to upgrade to (or a new named synth completly), if they are still working on it I suspect they would be looking to recuperate the cost in some way.Dasheesh wrote: Tue Sep 22, 2020 5:10 pmit's not currently fixed, and they haven't said anything directly that i know of. but, the developer has come on and stated that it is still being developed and supported, and i'm pretty sure he is trying to fix it if he can, it's just creating some issues because it's taking a while probably. i'm thinking it will be fixed before they stop supporting it. it might be a huge install tho.
(small rant) I'm pretty pissed off with Roli on this, I can't think of another software industry where a HUGE bug can be acknowledged and yet they continue to sell the product without fixing it, software bugs are a fact of life, yes, but this feel like they are turning their back on it, I think we've been totally ripped off.
-
- KVRAF
- 24405 posts since 7 Jan, 2009 from Croatia
Well first they would have to agree on if it's a bug, or if they made it like that intentionally, then they could say it's "by design", no case then.
-
Echoes in the Attic Echoes in the Attic https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=180417
- KVRAF
- 12002 posts since 12 May, 2008
They acknowledged the bug a long time ago. By email (to me and probably many others) and even in this thread a while back I believe.EvilDragon wrote: Sun Sep 27, 2020 10:51 pm Well first they would have to agree on if it's a bug, or if they made it like that intentionally, then they could say it's "by design", no case then.
I'm no lawyer but I don't see a court case here, that's a little extreme.
I don't know if the roli and fxpansion guys work on the same projects but maybe the devs are focused on the roli dashboard and lumi software. Otherwise I don't know what's going on. Equator hasn't seen updates in ages and neither has cypher.
-
- KVRist
- 307 posts since 23 Apr, 2009
I am a lawyer in my country, so I know. they are selling defective product. its like selling car with breaks not working or wheels not turning to the left for example. they must stop selling it until its working properly.Echoes in the Attic wrote: Sun Sep 27, 2020 11:13 pmThey acknowledged the bug a long time ago. By email (to me and probably many others) and even in this thread a while back I believe.EvilDragon wrote: Sun Sep 27, 2020 10:51 pm Well first they would have to agree on if it's a bug, or if they made it like that intentionally, then they could say it's "by design", no case then.
I'm no lawyer but I don't see a court case here, that's a little extreme.
I don't know if the roli and fxpansion guys work on the same projects but maybe the devs are focused on the roli dashboard and lumi software. Otherwise I don't know what's going on. Equator hasn't seen updates in ages and neither has cypher.
-
- KVRAF
- 4751 posts since 22 Nov, 2012
i just wanted to mention that if you are buying in to this or other fxpansion products save yourself some frustration and UNPACK THE INSTALLERS FROM THE WEBSITE. they do not auto unpack and installs errors. unpack the installers and you will find an installer. use that. that will give you the latest.
-
- KVRist
- 168 posts since 20 Jun, 2003
Question, which may be a feature request:
Is there any way to get more than one Analogue Drift modulator, so each of the 3 oscillators get completely unique values?
It seems that the Analogue Drift modulator only has one unique value per voice, so this means if you try to modify each of the 3 oscillators independently with it they all end up with the same value, so they aren't detuned from each other. I think typically on a real analog synth each of the oscillators has a unique drift, and they will drift in and out of tune from each other. Other software synths I've used behave this way, with each oscillator having their own unique drift value.
The only way I've found to do this in Cypher2 is to use the Analog Drift modifier for one oscillator, and use LFOs for each of the other two oscillators (set to Rmp-Wht). The problem with this is that it uses all of the LFOs so it leaves you with no LFOs to use in the rest of your patch!
Any way to do it without using up the LFOs, or should I make this a feature request for more Analog Drift modifiers?
If you look at software like Diva (where you have variance knobs for cutoff, envelopes, etc.) or hardware like the new Sequential Prophet 10 (where you have a "Vintage" knob to control the slop of the pitch and envelopes, etc), then you'll see why having multiple drift modifiers would be helpful for more closely emulating a real analog synth.
Here you can hear Dave Smith talking about how the "vintage" knob affects multiple parameters in the new Prophet 10 (he talks about it around 5 minutes in where I've started the video):
Would be great if we could do this in Cypher2, so that not only do each of the oscillators have slowly changing random values (not static random values), but also have drift for each of the LFOs, envelops, etc.
Thanks!
Jacob
Is there any way to get more than one Analogue Drift modulator, so each of the 3 oscillators get completely unique values?
It seems that the Analogue Drift modulator only has one unique value per voice, so this means if you try to modify each of the 3 oscillators independently with it they all end up with the same value, so they aren't detuned from each other. I think typically on a real analog synth each of the oscillators has a unique drift, and they will drift in and out of tune from each other. Other software synths I've used behave this way, with each oscillator having their own unique drift value.
The only way I've found to do this in Cypher2 is to use the Analog Drift modifier for one oscillator, and use LFOs for each of the other two oscillators (set to Rmp-Wht). The problem with this is that it uses all of the LFOs so it leaves you with no LFOs to use in the rest of your patch!
Any way to do it without using up the LFOs, or should I make this a feature request for more Analog Drift modifiers?
If you look at software like Diva (where you have variance knobs for cutoff, envelopes, etc.) or hardware like the new Sequential Prophet 10 (where you have a "Vintage" knob to control the slop of the pitch and envelopes, etc), then you'll see why having multiple drift modifiers would be helpful for more closely emulating a real analog synth.
Here you can hear Dave Smith talking about how the "vintage" knob affects multiple parameters in the new Prophet 10 (he talks about it around 5 minutes in where I've started the video):
Would be great if we could do this in Cypher2, so that not only do each of the oscillators have slowly changing random values (not static random values), but also have drift for each of the LFOs, envelops, etc.
Thanks!
Jacob
Uniphonic - Sounds for Synths || My music: Gravity Evasion ||
-
- KVRian
- 821 posts since 11 Aug, 2018 from UE
Hi Jacob,
It should be possible if you use the drift modulator for one osc, the drift mult by random for another osc...or you could multiply the drift by any other numbers or random source or use the math module.
Best wishes
YY
It should be possible if you use the drift modulator for one osc, the drift mult by random for another osc...or you could multiply the drift by any other numbers or random source or use the math module.
Best wishes
YY
Best
YY
YY
-
- KVRist
- 168 posts since 20 Jun, 2003
Thanks, YY! Those are some good ideas! Those seem a bit different though, in the fact that they're all relative to the one drift value, which I think wouldn't have the same results as completely unique modulators would.
One other thing which I did find can be a good modulator source for this is pink noise, which seems to be similar to the drift modulator. Maybe I could use some of your ideas combined with this...
I do still wish that Cypher had multiple unique drift modulators, but these are some good workarounds for now.
Thanks!
Jacob
One other thing which I did find can be a good modulator source for this is pink noise, which seems to be similar to the drift modulator. Maybe I could use some of your ideas combined with this...
I do still wish that Cypher had multiple unique drift modulators, but these are some good workarounds for now.
Thanks!
Jacob
Uniphonic - Sounds for Synths || My music: Gravity Evasion ||
-
- KVRist
- 168 posts since 20 Jun, 2003
An issue I just noticed with Cypher2: the Oscillator "beat" detune knob looks as if it is mislabeled as the "Fine" tune?
It says the word "Fine" next to the knob, but when you hover the mouse over it, it says for instance "Osc1Beat". I was tuning this knob thinking it was the fine tune knob, but then I noticed I was getting odd results where the lower notes would be more out of tune than the higher notes. Then I realized it seems this is because it's not really a fine tune knob, it's a beat tune knob, and should probably be labeled as "beat" instead?
I think this mislabeling could lead to a lot of people thinking the synth doesn't sound good because the tuning sounds strange if you try to use this knob as a fine tune knob. I was adjusting and modulating this knob and getting strange unexpected results, until I noticed it is mislabeled. I thought others should know too, so I thought I'd post here. Maybe something FXpansion should fix?
It says the word "Fine" next to the knob, but when you hover the mouse over it, it says for instance "Osc1Beat". I was tuning this knob thinking it was the fine tune knob, but then I noticed I was getting odd results where the lower notes would be more out of tune than the higher notes. Then I realized it seems this is because it's not really a fine tune knob, it's a beat tune knob, and should probably be labeled as "beat" instead?
I think this mislabeling could lead to a lot of people thinking the synth doesn't sound good because the tuning sounds strange if you try to use this knob as a fine tune knob. I was adjusting and modulating this knob and getting strange unexpected results, until I noticed it is mislabeled. I thought others should know too, so I thought I'd post here. Maybe something FXpansion should fix?
Uniphonic - Sounds for Synths || My music: Gravity Evasion ||