The Official Sequential/DSI Forum

SEQUENTIAL/DSI => Prophet => Prophet Rev2 => Topic started by: TimOliver on August 24, 2017, 10:59:14 AM

Title: Feature Requests
Post by: TimOliver on August 24, 2017, 10:59:14 AM
REV 2 is gorgeous. I'll just say that from the outset.
Having played with it a little - I've immediately noticed that the following things would be really helpful.

• With 16 voices available, it would be great to be able to have polyphonic unison. A 4 note chord could have 4 detuned and panned voices per note for example. I know I can set this patch up, but to have it easily accessible in Unison would be great.

• Again with Unison, it would be nice to be able to set it up by holding the Unison button down, à la Prophet 6. It seems more intuitive that way.

• Should the Misc Parameters button light up when it's selected ? It looks like there are LEDs inside it but I've never seen them come on. It would be nice if it could, just helps you know where you're at.

• I would love to be able to assign audio outputs per programme. I sometimes use a Vocoder live and in those cases I need to send a Mono output through my EHX V256 pedal. The automatic routing on cable insertion of Panel B to Output 3 is fine for that, but it eliminates the possibility of stereo split or stacked patches through outputs 1&2. Therefore being able to select what panel goes to what output per patch would be really helpful for me.

• When creating a sequence ... It would be nifty for the 16 dials on the auxiliary and amplifier envelope panels to convert to individual encoders for each step. It's a little fiddly and therefore counter-creative to dial through each step one by one.

• When saving a program, it would be good to see the existing name for the destination programme. At the moment I can't tell if I'm going to overwrite a patch I need.

That's it for now. Word, anyone ?

T

x
Title: Re: Feature Requests
Post by: jazzygb1 on August 24, 2017, 05:28:29 PM
Seems like a good start. :)
My Rev2 arrives tomorrow and I'll post if I find anything else.
Title: Re: Feature Requests
Post by: Sleep of Reason on August 24, 2017, 07:40:11 PM
Well I'm going to keep banging the drum for preset categories.
Title: Re: Feature Requests
Post by: Alphacode909 on August 28, 2017, 11:58:06 AM
Hi All

Just got my Rev2 so i thought i give it a go as there are a few things still that should be updated so here is my wish list , feel free to add REALISTIC Os updates only !! thanks :)

1. Sub oscillator volume is way to low (not sure if it's just my model but it's like half the volume of the DCO.)

2. Pan Split option in ''Misc menu'' to switch off alternate PAN ( from the PAN knob ) and instead by default Pan left Sound A and Pan Right Sound B by the Pan Knob. (without having to use a MOD Matrix slot)

3.Poly UNISON mode (reducing notes the more notes are played)

4.Saving Patches with EDIT A+B enabled and would recall the patch with it enabled (blinking light) Very useful !!!

5.LOCAL OFF is still absolute Useless CR*P !!! (in Both Rev2 and Pro2 i own) Please fire up a Korg , Roland or Yamaha product to see how it should behave ( It should only disconnect Keyboard )

6. Save Patches with Transpose setting that was selected.

That's all from me for now :)
Title: Re: Feature Requests
Post by: Ibsen on August 29, 2017, 05:38:04 AM
Please - add MPE support on the Rev2.
Title: Re: Feature Requests
Post by: nitromouse on August 29, 2017, 08:52:31 AM
3 and 6 will do for me too)
Title: Re: Feature Requests
Post by: Bezoblika on August 30, 2017, 05:05:00 AM
• When creating a sequence ... It would be nifty for the 16 dials on the auxiliary and amplifier envelope panels to convert to individual encoders for each step. It's a little fiddly and therefore counter-creative to dial through each step one by one.

Top idea that - it has my vote!

My addition to the list: If the current patch has been edited, there's a prompt on the screen to ask if you want to lose your edits before changing patches should the Program or Bank knobs be turned.   
Title: Re: Feature Requests
Post by: jazzygb1 on August 30, 2017, 04:22:46 PM
My addition to the list: If the current patch has been edited, there's a prompt on the screen to ask if you want to lose your edits before changing patches should the Program or Bank knobs be turned.

Yes +1 for this, it's very frustrating to spend time programming a great sound, only to have it all disappear because your finger accidentally brushes the program knob when your trying to press the write button - grrrr!
Title: Re: Feature Requests
Post by: SNAiP on September 02, 2017, 02:20:31 PM
The ARP MODE button could switch between different types of arp.
Title: Re: Feature Requests
Post by: Alphacode909 on September 04, 2017, 08:18:16 AM
Chorus delay line is to high , there is audible and very noticable delay between ths osc sounding fitrst and chorus kicking in a few mili-seconds later, should be reduced.
Title: Re: Feature Requests
Post by: gernotreininger on September 04, 2017, 10:24:58 AM
Some kind of sign in the display (maybe a point or something like this) when values are on original settings would be great.
Title: Re: Feature Requests
Post by: Propheteer on September 05, 2017, 01:05:43 PM
"• When saving a program, it would be good to see the existing name for the destination programme. At the moment I can't tell if I'm going to overwrite a patch I need."

I second this, I can only test by ear if it's one of my patches at the moment which is frustrating! Definitely needs this!

I also second poly unison mode, can make some awesome sounds with that (even on the 8 voice in 2 note unison per voice).

Arpegiator beat sync. Goes without saying. All arps should have that or they are almost useless for many things (nothing to do with playing/changing in time either it's about feel and playability)
Title: Re: Feature Requests
Post by: Robot Heart on September 05, 2017, 04:03:58 PM
Seeing the existing name for the destination program already exists! Use the Compare button to swap back and forth between your current program and the destination program. You can see (and hear) what you're about to overwrite. Read more about Compare on page 3 of the Rev2 manual, and comparing before you save on page 5.
Title: Re: Feature Requests
Post by: Propheteer on September 05, 2017, 09:12:42 PM
Seeing the existing name for the destination program already exists! Use the Compare button to swap back and forth between your current program and the destination program. You can see (and hear) what you're about to overwrite. Read more about Compare on page 3 of the Rev2 manual, and comparing before you save on page 5.

Was this updated in the latest firmware? I've not updated yet but was going to very soon, I wouldn't have asked for the feature if the above was true for me, I already use the compare button extensively to check the audio/sound of the patch or I'd not be able to 'test by ear' as I'd said. At the FW it arrived on at least, when I press compare, no matter how many times and no matter on which patch I move to overwrite, the name remains the same as the current patch/edited patch in progress.

Furthermore on that page you mention it doesn't say anything about 'seeing' the name, only about 'hearing' the patch you are about to over-write!

Quote
Comparing Before You Save
Before saving a program to a new location, it’s a good idea to listen to the
program in the target location to make sure you really want to overwrite it.
To evaluate a program before you overwrite it:
1. Get ready to save by pressing the write button. It starts flashing.
2. Press the compare button. Its LED lights up.
3. Use the bank and program knobs to navigate to the sound you want to
compare and play the keyboard to hear the sound.
4. To disable the compare function and go back to the edited sound, press
the compare button again to turn it off. (Programs can’t be written
while in compare mode.)
5. If you want to save the edited sound, the write button is still flashing
and ready to save, so navigate to a location with the bank and program
knobs and press write. The sound is saved.
6. Alternatively, if you want to cancel saving and continue editing, press
the global button. Saving is canceled.

Have already read the cover from end to end (in fact before I even bought the synth) and I try to avoid noob errors that would normally be in the manual. As said, if it's in a newer FW then cool and glad you added it already if so!
Title: Re: Feature Requests
Post by: Propheteer on September 06, 2017, 08:42:55 AM
Seeing the existing name for the destination program already exists! Use the Compare button to swap back and forth between your current program and the destination program. You can see (and hear) what you're about to overwrite. Read more about Compare on page 3 of the Rev2 manual, and comparing before you save on page 5.

As my last post above, no. I've just updated to latest FW and it still doesn't do this! Not sure why you think it does?
Title: Re: Feature Requests
Post by: dsetto on September 06, 2017, 09:24:24 AM
Early on, I tried the compare function as explained in the manual. In that one trial, I believe it functioned as the manual explained. This was with an early OS, before OS updates were released.
Title: Re: Feature Requests
Post by: Propheteer on September 06, 2017, 09:41:22 AM
Yes it does function exactly as the manual explains, i.e just sound no writing! lol
Title: Re: Feature Requests
Post by: AngelSynth on September 06, 2017, 08:03:40 PM
Well I'm going to keep banging the drum for preset categories.


If you download the demo version of the Prophet Rev2 Editor you will see that the library is categorized. It is worth downloading the demo version to see other "architectural" aspects of the digital layers.

BTW- I agree with everything said here. Also would like to have an option to use the matrix between layers A and B. A "PHASE" knob would be great. Controlling the phase of oscillators 1 and 2 (especially when synced) would boost the control of oscillators' every aspect. Phase adjustment can tune, increase amplitude, change the shape, and change how the result will respond to other modulation. (FYI-The "Shape Mod" does not adjust the wave's phase.)
Title: Re: Feature Requests
Post by: Sleep of Reason on September 07, 2017, 12:41:57 PM
Well I'm going to keep banging the drum for preset categories.


If you download the demo version of the Prophet Rev2 Editor you will see that the library is categorized.
Seeing how well it's implemented in Soundtower, there's really no excuse for why it's not a feature.
Title: Re: Feature Requests
Post by: Beatmaster on September 09, 2017, 12:42:54 AM
Hi,

this is the feature i missed instantly on day one when i started exploring my PRO-2 and its the same with the REV2.

You can modulate the frequency of a LFO but only if it is not switched to CLK SYNC.
It would be great if you could modulate ( or control via midi ) a tempo synced LFO.
Instead of changing the frequency number from 0-127 it should change the steps 8Steps 4Steps 2Steps 1.Steps etc...
This could map to a number Range. So that the 16 Step Settings that there are are mapping to a range of 8 Numbers

E.g:
32 Steps =  0-7
16 Steps =  8-15
 8 Steps = 16-23
 6 Steps = 24 - 31
 4 Steps = 32 - 39
 3 Steps = 40 - 47
 2 Steps = 48 - 55
1.5 Steps = 56 - 63
 1 Step = 64 - 71
2/3 Step = 72 - 79
1/2 Step = 80 - 87
1/3 Step = 88 - 95
1/4 Step = 96 - 103
1/6 Step = 104 - 111
1/8 Step = 112 - 119
1/16 Step = 120 - 127

There are many use cases for this. An example would be:
Create a filtered sound, assign LFO with e.g. revers saw to Filter Frequency.
LFO switched to click synced and change the "frequency aka steps" of that LFO.
You get very cool rhythmic patterns.
Title: Re: Feature Requests
Post by: jurfin on September 09, 2017, 01:57:00 PM
Absolutely loving my Rev 2. Only a few days in but it brings a smile to my face every time I turn it on. I find it inspiring and  magical. A few things I've noticed so far.

- Reduce minimum delay time on BBD delay. It would be very useful for me for the minimum time to be shorter than it is. This would open up possibilities for chorus and flange sounds with adjustable feedback, as well as all kinds of other cool stuff.
- I second the notion that an indication of what a knob was set at would be super beneficial when editing a sound. Yes, you can hit show, but I believe that only works right before you've changed the preset value. Also keeping the show button pressed while you're adjusting every parameter is really not ideal. It would be way better to be able to see what the preset value is/was whenever you're adjusting the knob. It seems like there is plenty of room on the screen to fit this info. It would be great if that could be implemented.
- I'm not sure how common this is, but the DX7IIFD I had (traded for Rev 2  ;D) gave you some very interesting options for how the pitch wheel worked. You could set whether the pitch changes were smooth or stepped. Being able to instantly snap a sound up or down an octave is a really fun and musical thing. I miss it. It also gave an option whether the pitch mod effected all notes, just high or low notes, or just ones that currently had their keys depressed. These options would be great additions to the Rev 2.
- If there's any way to give finer control over mod slot depth amounts, as in less than 1, that would be very useful for me. I know there are workarounds using another mod slot to control the thing you're modulating, but finer control would be better and leave mod slots open for other things.

I feel like I'm whining here haha. Just want to say I think this is a wonderful machine. It will be with me for years to come and I couldn't be happier with my choice to get a Rev 2. Just throwing out some ideas here.


Title: Re: Feature Requests
Post by: dsetto on September 09, 2017, 10:42:55 PM
These are neat ideas. This is not whining.
Title: Re: Feature Requests
Post by: kirby1985 on September 10, 2017, 07:23:43 AM
I'd like to see Osc Slop as a mod source. I want to try sending it to the filters or envelopes as a polyphonic controller. Other polyphonic mod sources would be great also like one of the LFOs perhaps. Something else that would be great is a random value at key on as a mod source like my An1x has. It mildly randomizes your destined parameter with each key press which can be great for adding complexity to a sound and helps keep it fresh.
Title: Re: Feature Requests
Post by: Proton on September 11, 2017, 01:42:43 AM
Hi,

this is the feature i missed instantly on day one when i started exploring my PRO-2 and its the same with the REV2.

You can modulate the frequency of a LFO but only if it is not switched to CLK SYNC.
It would be great if you could modulate ( or control via midi ) a tempo synced LFO.
Instead of changing the frequency number from 0-127 it should change the steps 8Steps 4Steps 2Steps 1.Steps etc...
This could map to a number Range. So that the 16 Step Settings that there are are mapping to a range of 8 Numbers

E.g:
32 Steps =  0-7
16 Steps =  8-15
 8 Steps = 16-23
 6 Steps = 24 - 31
 4 Steps = 32 - 39
 3 Steps = 40 - 47
 2 Steps = 48 - 55
1.5 Steps = 56 - 63
 1 Step = 64 - 71
2/3 Step = 72 - 79
1/2 Step = 80 - 87
1/3 Step = 88 - 95
1/4 Step = 96 - 103
1/6 Step = 104 - 111
1/8 Step = 112 - 119
1/16 Step = 120 - 127

There are many use cases for this. An example would be:
Create a filtered sound, assign LFO with e.g. revers saw to Filter Frequency.
LFO switched to click synced and change the "frequency aka steps" of that LFO.
You get very cool rhythmic patterns.

yes !
Title: Re: Feature Requests
Post by: jurfin on September 11, 2017, 10:27:42 AM
These are neat ideas. This is not whining.

Haha thanks! I think I felt bad because my first post after acquiring the Rev 2 was asking for more things, things it can't do, when in actuality I am already very pleased with everything it can do.
Has there been an update for the mod source/dest glitch? Where it only works the first few times you hold the button and move the control you want to select. If not, it would be cool if that could get sorted out.
Title: Re: Feature Requests
Post by: Sleep of Reason on September 11, 2017, 12:54:33 PM
It would be nice for all the inapplicable lights to shut off during midi use in local off mode and also from inactivity like when the screen goes to sleep. Plus the tempo light when it's not applicable (I.E. the arp/seq aren't running or when the clock section isn't being tinkered with.)
Title: Re: Feature Requests
Post by: Propheteer on September 12, 2017, 02:28:28 AM
I would like the flashing tempo/tap button/light to be able to be disabled in the menus, it can get a bit annoying flashing away for little reason (even when using it you don't really need to see it) esp if you have it on a desk in front of you / under your monitor. the other lights are fine, the screen goes off, the LFO flashings are great (small) and very welcome. I'm nit picking here but if it's do-able I'd like it!
Title: Re: Feature Requests
Post by: jurfin on September 18, 2017, 11:36:46 AM
Yesterday I discovered that the sustain portion of the envelopes are not available as modulation destinations. I wonder why that is...
If there's a reason for this, I'm all ears. However, if not, it would be very useful for me to be able to modulate the sustain of the envelopes! 
Title: Re: Feature Requests
Post by: sakaida on September 20, 2017, 05:45:59 PM
Flexible key assignment.
For example, split A is monophonic + split B is 15 polyphonic.
For example, Unison Polyphonics, 4 Voice Unison and 4 Polyphonics.

Effect serial connection.
Title: Re: Feature Requests
Post by: jok3r on September 22, 2017, 02:27:53 AM
+1 for two effetcs in a row if not stacked or split...
Title: Re: Feature Requests
Post by: Troy92Evans on September 25, 2017, 12:16:45 PM
My only current issue with it (I absolutely love the synth more than any I've had, and it's been a few months) seems rather large to me...I've already stated it here but am curious to see how I'm not hearing others bring it up. Unassignable sustain pedal...it's SO logical to have pads on the left side of a split and leads on the right, but I can't sustain pedal control the pads while modulating my lead? That seems pretty big to me as a live player, to the extent that it necessitates me returning to have an extra board with me at times when in a band setting.
Title: Re: Feature Requests
Post by: Nuwrel on October 01, 2017, 01:16:12 PM
Please - add MPE support on the Rev2.

I support the addition of this feature.
Title: Re: Feature Requests
Post by: philroyjenkins on October 02, 2017, 01:14:43 PM
Flexible key assignment.
For example, split A is monophonic + split B is 15 polyphonic.
For example, Unison Polyphonics, 4 Voice Unison and 4 Polyphonics.

Effect serial connection.

So much this. Can someone in the know sound in on if this is even possible with the architecture of the rev2?

As soon as I heard of bitimbral I thought to myself "ok cool, so big full chords on the left side and a single voice lead on the right."
Title: Re: Feature Requests
Post by: luk.vermeir@gmail.com on October 12, 2017, 08:28:07 AM

Yes +1 for this, it's very frustrating to spend time programming a great sound, only to have it all disappear because your finger accidentally brushes the program knob when your trying to press the write button - grrrr!

yes indeed, have lost some edited sounds this way too...
Title: Re: Feature Requests
Post by: skrohmer on October 12, 2017, 09:13:25 AM
Yes +1 for this, it's very frustrating to spend time programming a great sound, only to have it all disappear because your finger accidentally brushes the program knob when your trying to press the write button - grrrr!
+1
Title: Re: Feature Requests
Post by: Sleep of Reason on October 12, 2017, 01:33:29 PM
It would also be nice if the LFO lights would only be turned on for those that are actively modulating (& thus turned off for those that are not).
Title: Re: Feature Requests
Post by: jazzygb1 on October 12, 2017, 02:10:56 PM
It would also be nice if the LFO lights would only be turned on for those that are active (& thus turned off for those that are inactive).
I agree and would like that applied to the Prophet 12 too! :)
Title: Re: Feature Requests
Post by: LoboLives on October 13, 2017, 05:29:55 AM
Poly Sequencer transpose.

Hold the "Hold" button down, it starts flashing indicating that the sequencer can be transposed by the keys on the fly.

and then do the same for the P6/OB6 sequencers if their OS ever gets updated ;)

Also question, when I assign the pitch of one of the oscillators to the pitch bend wheel at what about should I set the modulation to be so it can be an octave up?
Title: Re: Feature Requests
Post by: skrohmer on October 14, 2017, 11:28:09 PM
It would also be nice if the LFO lights would only be turned on for those that are active (& thus turned off for those that are inactive).

Very good idea IMO!
Title: Re: Feature Requests
Post by: philroyjenkins on October 15, 2017, 08:23:08 PM
- Reduce minimum delay time on BBD delay.

In the meantime you can tempo sync it and turn your tempo all of the way up :)

For what its worth though, I love the BBD time as is. I find the MONO and STEREO Delays to be better for weird modulation stuff anyways.

BBD time is at minimum is like the perfect tempo for me most of the time when I just want a subtle little bit of echo.

Also LFO on delay time (even like a tiny amount of 1-3) is absolutely amazing.
Title: Re: Feature Requests
Post by: jazzygb1 on October 19, 2017, 07:17:26 PM
How about making the Parameter Knob do something when you're editing?

It should automatically advance to the next item in the section you are editing.

For example...
If I'm editing the VCA envelope and turn the attack knob and then use the Value Knob to accurately dial in a value, turning the Parameter Knob should then take you to the next setting for that section (i.e the VCA decay), followed by its Sustain setting, then release etc etc.

At the moment turning the parameter knob does precisely nothing!!! :(

Because they are 'notched' the Parameter & Value Knobs are far easier to dial in specific amounts and it'd be much quicker to be able to 'step through' related parameters in a section using the parameter knob than having to physically jump from the value knob to another in the VCA section itself.




Title: Re: Feature Requests
Post by: niagarasynths on October 20, 2017, 08:43:32 AM
I would like to have a knob that is assignable to Mix/Balance between the 2 layers. Volumes of the layers are already established within the layers but a knob that can adjust in real time would be super useful, like on my old CS-80. There is already the knob in the Effects section called Mix. When the Effects button is off, make it a mix layer knob.
Title: Re: Feature Requests
Post by: jazzygb1 on October 20, 2017, 09:45:22 AM
There is already the knob in the Effects section called Mix. When the Effects button is off, make it a mix layer knob.

Good idea! :)
Title: Re: Feature Requests
Post by: Sleep of Reason on October 20, 2017, 10:43:38 AM
I would like to have a knob that is assignable to Mix/Balance between the 2 layers. Volumes of the layers are already established within the layers but a knob that can adjust in real time would be super useful, like on my old CS-80. There is already the knob in the Effects section called Mix. When the Effects button is off, make it a mix layer knob.

I was just thinking about how this should be a modulation option yesterday... I would specifically like to use the modwheel for this.
Title: Re: Feature Requests
Post by: Robot Heart on October 20, 2017, 03:10:40 PM
You can already do this in the Mod Matrix by assigning the Mod Wheel to Amp Env Amt for each layer. Make one layer's Mod Amount -127 and the other layer's Mod Amount +127 and turn its Amp Env Amt to 0. Now stack the two layers and use the mod wheel to mix between them.
Title: Re: Feature Requests
Post by: niagarasynths on October 21, 2017, 08:57:27 AM
I understand that this would work, but when I play live, Aftertouch is normally used for vibrato and my Modwheel is usually reserved for affecting filter type parameters. Having a dedicated knob to make real time changes in the layer mix would be the best option.
Title: Re: Feature Requests
Post by: luk.vermeir@gmail.com on October 22, 2017, 04:48:27 AM
HOLD functionality user defined:

1. the 'DSI' way: adding notes to until full polyphony is reached
2. the 'regular' way: latch the played tones / chords until next tone / chord is played.

Thanks.
Title: Re: Feature Requests
Post by: Cabana on November 15, 2017, 02:41:23 PM
So many great ideas here to improve this already mind blowing machine. I love my Rev 2.

It'd be fun if the Clock "Divide" was a mod destination. This could get some exciting unpredictable rhythms going with the arpeggiator.

Big thumbs up to making the gated sequencers more hands-on like on the Prophet 08. Use 16 of the LPF and VCA ENV knobs for gated sequencer control.

FX: I love the sound of the HPF. What about adding a second sweet digital LPF?

Happy synthesizing!
Title: Re: Feature Requests
Post by: Chimponaut on November 15, 2017, 09:32:06 PM
Big +1 for the original parameter value being indicated somehow. The little dot that shows up in the OB-6 display would be perfect. No need to reinvent the wheel here. Keep things standard across the range of instruments.

Title: Re: Feature Requests
Post by: dsetto on November 15, 2017, 10:00:53 PM
Great ideas.

Digital bandpass filter? (The digital HPF is good.)
Title: Re: Feature Requests
Post by: Chimponaut on November 19, 2017, 09:47:33 AM
Big +1 for the original parameter value being indicated somehow. The little dot that shows up in the OB-6 display would be perfect. No need to reinvent the wheel here. Keep things standard across the range of instruments.

Just discovered the "Show" button...Because someone mentioned it earlier in this thread but didn't really explain it. I only knew it as the Misc Parameters button. Didn't even see the tiny "show" text until I studied the panel for a few minutes. For anyone else that might be wondering, pressing and holding the show/misc parameters button and then turning a knob will display the original stored parameter value for that knob without changing it. Exactly what I have been needing for the last few weeks. Damn, why isn't this in the manual? or Did I miss it?

Title: Re: Feature Requests
Post by: dsetto on November 19, 2017, 10:45:19 AM
It's a good feature. Often I get out of habit of using it. A great way to make a subtle move.
Title: Re: Feature Requests
Post by: Razmo on November 20, 2017, 02:14:45 AM
I do not know if these have been requested before... but I'd really like to see these effetcs features:

1. Ping Pong Delay.
2. String Ensemble (preferably modelled after the Eminent E310 Unique / Solina).
3. Frequency Shifter.
4. Formant Filter.
5. Pitch Shifter.

The FX section of the REV2 is some of what sets the synth apart from the older P08, so the more varied FX options, the more versatile this beast becomes. Any other FX added will greatly increase the sound design potential, so by all means, if you can DSI; put more of them FX in there!
Title: Re: Feature Requests
Post by: LoboLives on November 20, 2017, 05:01:42 AM
Sequencer Midi Out

Transpose the sequencer on the fly WITHOUT having to hold down the record button.

Please and thanks.
Title: Re: Feature Requests
Post by: joesh on November 20, 2017, 11:16:07 AM
Quite a few good suggestions - just above here #53 is a good idea.

I'd like to see several little changes, some of them just practical things. I'd like to see a button for midi settings ON/OFF. You'd set up your synth for a DAW or whatever (ex: clock/slave, local/off, etc), then just press ON to remember/activate the settings. If you want to make some changes to sounds/settings you just press midi 'OFF'.   
Title: Re: Feature Requests
Post by: LoboLives on November 20, 2017, 02:46:27 PM
Quite a few good suggestions - just above here #53 is a good idea.

I'd like to see several little changes, some of them just practical things. I'd like to see a button for midi settings ON/OFF. You'd set up your synth for a DAW or whatever (ex: clock/slave, local/off, etc), then just press ON to remember/activate the settings. If you want to make some changes to sounds/settings you just press midi 'OFF'.

I have to say one thing that the P6 and OB6 excel At is the simplicity of its interface because all the global functions like these are literally right there on the front panel.
Title: Re: Feature Requests
Post by: Razmo on December 01, 2017, 03:12:41 AM
I'm not certain if this is a mistake by DSI or what, but one thing that is constantly annoying me is that if I have a program which is a stacked program, then I want the poly sequencer to record into BOTH LAYERS at the same time... currently, you have to record the same sequence twice, once for each layer which is not only tedious and trivial, but also impossible since it's basically not possible to record them with the same velocity values.

A stacked program are meant to be used as a "single program", so it is only logical that it should play the same sequence with the same velocities.

If I press and hold the "Edit Layer B" button so that it flashes for editing both layers, then I am not able to initiate the record button at all...

Summa Summarum: I'd REALLY like to see the recording being possible when the Edit Layer B button is blinking, storing the played sequence into both layers at the same time.... please. :)
Title: Re: Feature Requests
Post by: skrohmer on December 01, 2017, 08:40:48 AM
Summa Summarum: I'd REALLY like to see the recording being possible when the Edit Layer B button is blinking, storing the played sequence into both layers at the same time.... please. :)

What about using the function "Copy Seq A to B"?
Title: Re: Feature Requests
Post by: Razmo on December 01, 2017, 08:50:26 AM
Summa Summarum: I'd REALLY like to see the recording being possible when the Edit Layer B button is blinking, storing the played sequence into both layers at the same time.... please. :)

What about using the function "Copy Seq A to B"?

It's an option yes, but I really think that it should be an automatic thing when the Layer B edit button is blinking... everything else is edited on both layers in this mode...
Title: Re: Feature Requests
Post by: philroyjenkins on December 01, 2017, 09:13:53 AM
Sequencer Midi Out

Transpose the sequencer on the fly WITHOUT having to hold down the record button.

Please and thanks.

OMG I didn't know you could hold the record button to transpose! Thank you so much. I'm using this feature now and I don't personally think I'd like it to transpose without holding something since you can play along to a sequence then transpose it only when you want to.

Then again, if you wanted to play along to it you could just make a split patch and be able to transpose sequence with one finger. There should be a choice to toggle 1 finger transpose within params somewhere.

In the meantime though, you can one finger tranpose a gated sequence its just much harder to program in notey things on the fly.

E: I just noticed the hold record to transpose works kind of strange. Its not based off the first note in your sequence, rather the sequence is sort of locked to c2 no matter what notes you played, so transposing on the fly requires a bit of thought unlike the unison chord mode which is much more intuitive. This brings me to another suggestion.

I'd love to be able to use the ARP on a chord held my unison chord mode.
Title: Re: Feature Requests
Post by: Robot Heart on December 01, 2017, 12:49:37 PM
There aren't any plans to allow recording to both sequences simultaneously. The copy function that has already been pointed out is the workaround, and there are numerous use cases where you don't want to record to both layers together.

--

As you've noticed sequencer transpose is based on middle C as a reference point, so transposition moves out from there in either direction when new keys are pressed.
Title: Re: Feature Requests
Post by: Razmo on December 01, 2017, 01:58:35 PM
There aren't any plans to allow recording to both sequences simultaneously. The copy function that has already been pointed out is the workaround, and there are numerous use cases where you don't want to record to both layers together.

--

As you've noticed sequencer transpose is based on middle C as a reference point, so transposition moves out from there in either direction when new keys are pressed.

Well... why should recording to both layers be a problem for cases where you do not want to record on both layers? ... I was talking about recording to both layers, when the Edit Layer B button was blinking only, which is the normal way of editing both layers at the same time...

But I can understand that this is not likely to happen, so I'll just move on... thanks for the answer.
Title: Re: Feature Requests
Post by: creativespiral on December 01, 2017, 04:50:04 PM
There are so many great ideas in this thread!!!   While I'm happy with my Rev2, I would gladly pay for future firmware upgrades if some of this "new feature stuff"  could be implemented.

DSI:  Would you consider investing in new feature development time, if you monetize it?   How about a v2.0 OS upgrade for $100 or even $200?    I would gladly pay for new features and functionality for my REV2, and I bet others would as well... 

My top wishes:
1. Add a second, select-able HOLD / latch type that holds just most recent simultaneous key triggers / chords
2. Development of some sort of preset categorization / grouping (pads, leads, bass, ambient drones, drum, arp seqs, etc...)
3. More options with the effects section and more effects
4. Some better indicator for original / saved settings for parameters along with current setting.
5. Tempo sync'd LFO as described by beatmaster would create some great tempo sync options.
Title: Re: Feature Requests
Post by: Robot Heart on December 01, 2017, 05:49:01 PM
That's not really our business model, so I'm going to say it's highly unlikely we'll ever charge for feature requests or firmware upgrades. Admittedly, there are always tons of great feature ideas. I've written some detailed responses regarding feature requests in some other threads so I won't go into detail again here, other than saying not everything that is suggested can make it into the instrument. I know that's not the answer you're looking for but I'm just trying to be as transparent as possible.
Title: Re: Feature Requests
Post by: creativespiral on December 01, 2017, 08:46:34 PM
Yeah, I get that its not currently your business model.. but maybe something to consider / chat about with Dave. 

I am happy with my Rev2 (and PEK and P12).  You guys make really good synths... But there does seem to be a good amount of software/firmware possibilities that could take some of your instruments to next level status.  I get that some stuff is not possible due to memory or processor restrictions, but some of it does seem possible, and just requires programmer resources.

I'm not sure if you guys follow what Fractal Audio is doing in the Guitar Modeling and FX area... but they really set a gold standard when it comes to continued development of their products.   You "buy into" their Axe-FX II hardware unit, and you can pretty much expect that every month or two the unit will be significantly improved with new effects, new amp models, new modeling techniques and advanced options.   Their founder and lead developer, Cliff Chase, is basically worshiped by the entire user base (Fractal Audio Forum), and if you look at their growth and adoption of artists, you see that they are completely changing the paradigm for guitar amp and effects sales.   I don't know their financials, so can't say that their business model is the best out there, but it sure seems like it, when you see how fervent the user base is, and how every couple weeks they have new major artists endorsing them.  (3/5 of best rock album Grammy noms are Fractal Audio endorsers)

Anyways, again, I'm a happy customer... would just love to see more software/firmware development and a philosophy of "leaving no stone unturned" in that realm...  if its possible with the hardware architecture, find a way to make time resources to develop it,... and if you need to, just monetize it... I would happily pay for continued development of new features.   
Title: Re: Feature Requests
Post by: philroyjenkins on December 02, 2017, 04:13:40 PM
Just voicing an opposing point of view as I'd very much not want to have to pay for the "DLC" pack to get updates to my synth. It would leave a pretty sour taste in my mouth and I'd probably steer clear of a company that did this.

I can understand this on a device like the H9 where it is explicitly stated when you purchase the beginner model that you will be paying for additional algorithms but this would be something entirely different.
Title: Re: Feature Requests
Post by: Martin_B on December 03, 2017, 09:37:44 AM
Very good suggestions here!
for me most important would be:
1. A louder Subosc
2. Saving patches and Comparing: Show the Name of the Compared Patch
3. Enable a second Effect, when not Stacking or Splitting
4. Tweaking the Sequencer. For example: The Korg Mini/Monologue shows a graph of Modulated Parameters. This is super handy!
5. Start a New Patch with taking all the states of the Knobs.
6. Indicate a not Used LFO by taking of its indicator LED
Title: Re: Feature Requests
Post by: Consigliere on December 03, 2017, 02:34:30 PM
So pleased so I feel almost embarrassed to ask for something...
I had a long post a while ago about getting the voices in sync with LFO. It would be nice if that could be done with a shortcut, like a "2-button-click" instead of...
-turn of layer (if split or stacked)
-press unison button while holding misc params (this is shortcut to that area in menu)
-turn unison mode to all of your available voices (8 or 16)
-turn on unison
-turn on key sync on lfo then press a note. The lfos are now synced.
-turn off key sync and turn off unison

Title: Re: Feature Requests
Post by: Robot Heart on December 04, 2017, 01:25:18 PM
Hi creativespiral-

One of the most difficult aspects of my role as a forward facing representative is that my personal views are more aligned with "no stone unturned". As a customer of plenty of gear I fully understand and sympathize with your position. But, all I can do here is convey the company practices so you guys know how things operate, and give my best guess on how likely or unlikely it is that something will happen.

Again, I won't get into it here as I've written at length on this very topic and to the exact points you bring up in multiple other areas of the forum, so I encourage you to seek those out if you'd like more detail. I am glad to hear you're a happy customer and otherwise enjoying your Rev2 as well.
Title: Re: Feature Requests
Post by: vinnyburns1@mac.com on December 04, 2017, 06:11:23 PM

I'm not sure if you guys follow what Fractal Audio is doing in the Guitar Modeling and FX area... but they really set a gold standard when it comes to continued development of their products.   You "buy into" their Axe-FX II hardware unit, and you can pretty much expect that every month or two the unit will be significantly improved with new effects, new amp models, new modeling techniques and advanced options.   Their founder and lead developer, Cliff Chase, is basically worshiped by the entire user base (Fractal Audio Forum), and if you look at their growth and adoption of artists, you see that they are completely changing the paradigm for guitar amp and effects sales.   I don't know their financials, so can't say that their business model is the best out there, but it sure seems like it, when you see how fervent the user base is, and how every couple weeks they have new major artists endorsing them.  (3/5 of best rock album Grammy noms are Fractal Audio endorsers)

I use the Axefx XL in my studio and for live, two Fractal AX8. What you fail to mention is that pretty much all these many many free upgrades change every preset you have meticulously programmed into the unit and you are expected to reprogram them again every time.
As a professional, that is not great. Both my AX8 are on an old FW as I just cannot be bothered having to update all my own live sounds every time there is an update.
I don’t think many in the synth world would find that acceptable. It’s the only brand I own/owned where this happens.
Title: Re: Feature Requests
Post by: creativespiral on December 04, 2017, 09:57:46 PM
Robot Heart - thanks for the insights... yeah, I've followed all the discussions for Evolver, P12 and Rev2 going back through the years to the early days of the old forum.   I get where you're coming from...  love all my boards!... and looking forward whatever is next!

Vinnyburns - Every now and again I see someone post a response about the "hassle of getting updates" in regards to Fractal... makes no sense though, as you're not forced to update... If you're happy with your Fractal presets as they are, don't upgrade to new firmware.   For every one person who complains like you, there are a hundred who are ecstatic to have the updates, and willing to spend a few minutes to fine tune their presets for any changes.   I think if you look at their artist list, its hard to make a case that Fractal is doing anything but the best in the industry.   Anyways, this is not a forum for Fractal, so no sense in discussing it here... but if you wanna post in their forum, and complain about the hassle to of free updates to a world class piece of hardware, be my guest...
Title: Re: Feature Requests
Post by: trashdinner on December 05, 2017, 07:39:26 AM
Very good suggestions here!
for me most important would be:
1. A louder Subosc
2. Saving patches and Comparing: Show the Name of the Compared Patch
3. Enable a second Effect, when not Stacking or Splitting
4. Tweaking the Sequencer. For example: The Korg Mini/Monologue shows a graph of Modulated Parameters. This is super handy!
5. Start a New Patch with taking all the states of the Knobs.
6. Indicate a not Used LFO by taking of its indicator LED
+1
Having a second effect when not stacking would be number one for me but I agree to all of them.
Title: Re: Feature Requests
Post by: vinnyburns1@mac.com on December 05, 2017, 01:26:03 PM

Vinnyburns - Every now and again I see someone post a response about the "hassle of getting updates" in regards to Fractal... makes no sense though, as you're not forced to update... If you're happy with your Fractal presets as they are, don't upgrade to new firmware.   For every one person who complains like you, there are a hundred who are ecstatic to have the updates, and willing to spend a few minutes to fine tune their presets for any changes.   I think if you look at their artist list, its hard to make a case that Fractal is doing anything but the best in the industry.   Anyways, this is not a forum for Fractal, so no sense in discussing it here... but if you wanna post in their forum, and complain about the hassle to of free updates to a world class piece of hardware, be my guest...

Nice passive aggressive answer. :-)
The fact that the Fractal fw updates normally contain a crucial bug fix blows your little argument out of the water.
I use their stuff professionally. I love using it live. You fit right in with the 90% fanboy posters on their forum.
Here I am using my Fractal stuff professionally.
Title: Re: Feature Requests
Post by: vinnyburns1@mac.com on December 05, 2017, 01:29:41 PM
So, would the consensus be that pretty much all the major annoyances have now been ironed out now on  the Rev2?
Is it time to eBay/sell my Pro 08?
Title: Re: Feature Requests
Post by: creativespiral on December 05, 2017, 02:52:18 PM
Vinny - you are in the super-minority with your first world problem... for every ungracious user like you, there are a hundred other Fractal users who would disagree with you.  The majority of updates don't even require changes to presets, or just a simple reset of a block or adjusting a new parameter dial.  If you can't spare a couple minutes of your precious time to adjust your custom presets when updating, then just stay on an existing firmware... some people do that and are perfectly happy, even on pre-quantum fw.   Fractal's level of dedication to improvements and the quality of updates is world class, as evidenced by their rapidly growing artist list. http://www.fractalaudio.com/artists.php .   I have never bought any product of any sorts that improves over time like theirs.  I will admit to being a "fan" of that.  Anyways, if you want to further complain about their updates, start a thread in the Fractal Forum and we can debate it over there.
Title: Re: Feature Requests
Post by: extempo on December 05, 2017, 02:55:03 PM
Let's stay on topic here. As suggested, any further discussion of Fractal Audio should occur in the "Other Gear" forum or elsewhere off site.
Title: Re: Feature Requests
Post by: Loak on December 09, 2017, 11:34:10 AM
Just received my Rev 2 - 8 Voice and I'm loving it so far. A few features I would like to see added:

1) More effects! Bitcrush,ping pong delay,ensemble. Decimate and hack from the Prophet 12.

2) Ability to use two effects if only using one layer. This would open up a huge amount of new sound creation.

3) Category search. Almost seems necessary with over a 1000 sounds and would help me a lot when searching for a certain sound.

4) The ability to transpose each layer individually. That's how my Nord Lead works and I love it.

5) If you have the full 16 voice version...layer C & D. Each layer is 4 voice. Not sure if this is even possible,but it would absolutely sell me on the 8 voice expansion card. I loved that the Tetra could do a 4 part multi,but I hated the interface. Still only 2 effects,but each layer could be routed to effect A or B, AB, BA or none.

6) The ability to route effects to more than one layer. Say I have reverb on layer A and on layer B I want to use a delay and the same reverb from layer A.  Routing A or B, AB, BA or none. Not sure if this possible either.

That's it for now. I'll post more as I dig deeper.
Title: Re: Feature Requests
Post by: Razmo on December 12, 2017, 02:03:16 AM
Not a that necessary feature maybe, but I really miss the voice LEDs on the REV2, which are present on all other polysynths from DSI... I think DSI left them out because of cost savings, but they were always handy to get a quick visual representation of what voices is being used... I know they cannot be added now, but maybe, if DSI had the time, they could implement a visual representation in the OLED display somehow... I'd like to see that.
Title: Re: Feature Requests
Post by: AlainHubert on December 12, 2017, 10:33:27 AM
Not a that necessary feature maybe, but I really miss the voice LEDs on the REV2, which are present on all other polysynths from DSI... I think DSI left them out because of cost savings, but they were always handy to get a quick visual representation of what voices is being used... I know they cannot be added now, but maybe, if DSI had the time, they could implement a visual representation in the OLED display somehow... I'd like to see that.

Me too. On my Oberheim Matrix 6, there are small dots at the bottom of the VFD display, showing which voices are being used. It could very well be implemented that way too on the OLED display of the REV2.

Title: Re: Feature Requests
Post by: Sleep of Reason on December 13, 2017, 09:59:04 AM
I'd prefer a visual representation of filter, etc. If this (https://www.youtube.com/watch?time_continue=1&v=MF8G_CFC5gs) guy can do it with a one man operation, I don't see why DSI can't implement something similar. Ofc the Korg Mini/monologue has something like this too. Although having a little number icon showing the amount of voices being used at any given time would be pretty nifty as well.

3) Category search. Almost seems necessary with over a 1000 sounds and would help me a lot when searching for a certain sound.
I've said it before and I'll say it again ... yes, yes, yes!
Title: Re: Feature Requests
Post by: Razmo on December 15, 2017, 01:22:46 AM
I'd prefer a visual representation of filter, etc. If this (https://www.youtube.com/watch?time_continue=1&v=MF8G_CFC5gs) guy can do it with a one man operation, I don't see why DSI can't implement something similar. Ofc the Korg Mini/monologue has something like this too. Although having a little number icon showing the amount of voices being used at any given time would be pretty nifty as well.

3) Category search. Almost seems necessary with over a 1000 sounds and would help me a lot when searching for a certain sound.
I've said it before and I'll say it again ... yes, yes, yes!

If it's just a graphic representation of the Filter as in that link, sure they can implement it... if you want the changing waveform display as in that video also, I think it's not possible hardware-wise because that would require sampling the output of every single voice to show it correctly, and I bet DSI did not put an ADC after every Curtis chip.

One thing they should be able to do though, is a realtime summed waveform display of what is playing, like on the KORG monologues because if you look in the modulation sources, you can see that you can use "Audio Out" as a modulation source, and the manual also state, that the whole mixed signal is sampled after the VCAs, but before the FX engine (which is logical, since that is the way the analog signal is put thru the digital FX section... this signal could be used to make a graphical realtime scope... something I'd actually suggest as a feature because such a scope is really handy when you do sound design... it makes it possible to spot even small amounts of distortion from too high levels etc. but also how the oscillators change with modulation and interact... probably not one of the most important features, but it would definitely be useful, and cool looking.
Title: Re: Feature Requests
Post by: Indigo V. on December 17, 2017, 08:35:14 AM
I miss an option to turn of the OLED screen completely so that even midi does not trigger it on.
I use my module and remote control it, so I can't see anything on the screen anyway :-)
Title: Re: Feature Requests
Post by: Indigo V. on December 17, 2017, 08:46:48 AM
I had two rev2s and noticed that both had pulswidth differences on certain settings and tones between voices. Interestingly in blocks of 4 voices.

One rev2 had voices 5-8 different to 1-4 and 9-16 and similar to 8-12. The other one had voices 13-16 different to the others. In some cases this is bothering me, most notably when playing certain bass notes with wide, static pulse widths.

This is, except the 4 voice blocks, not unique to the Rev2, other units have various discrepancies including filters (where auto calibration does not help) and loudness.

So, I would like to suggest an option so users can manually tune/offset parameters for each voice. Actually not just regarding PW but also filters including other units as well (Prophet 12, 6).
Title: Re: Feature Requests
Post by: philroyjenkins on December 17, 2017, 10:14:53 AM
I miss an option to turn of the OLED screen completely so that even midi does not trigger it on.
I use my module and remote control it, so I can't see anything on the screen anyway :-)

(https://i.imgur.com/zCMdNEN.png)
Title: Re: Feature Requests
Post by: Robot Heart on December 18, 2017, 01:57:13 PM
I split the "pulse width" talk into its own topic, located here (http://forum.davesmithinstruments.com/index.php/topic,2176.0.html).

Please keep this thread specific to feature requests.
Thanks!
Title: Re: Feature Requests
Post by: Indigo V. on December 25, 2017, 06:35:34 AM
I miss an option to turn of the OLED screen completely so that even midi does not trigger it on.
I use my module and remote control it, so I can't see anything on the screen anyway :-)

Just to explain: The reason I request this feature is to prolong the longevity of the screen. I would also like to see this for the Prophet 12. If you use the module versions of these synthesizers and remote control them via midi editors, these screens show the very same pixels for hours and hours. Even worse, it's maximum contrast, white on black.
Title: Re: Feature Requests
Post by: AlainHubert on December 25, 2017, 09:19:51 AM
I miss an option to turn of the OLED screen completely so that even midi does not trigger it on.
I use my module and remote control it, so I can't see anything on the screen anyway :-)

Just to explain: The reason I request this feature is to prolong the longevity of the screen. I would also like to see this for the Prophet 12. If you use the module versions of these synthesizers and remote control them via midi editors, these screens show the very same pixels for hours and hours. Even worse, it's maximum contrast, white on black.

Yes, that would be a good feature to add to save the screen.

[rant mode On]
And, while we're on the subject, this OLED technology is not well suited for displays on synths. And until they find a way to have the lifespan stated in decades, instead of hours, it's doomed as a display technology. Yes, it's crisp and fast, with excellent contrast. But the limited lifespan and poor performance under bright light, not to mention the higher price (for now), make it less than ideal.
I've got 30 year old synths that have VFD, or LCD, or even LED displays that are still working very well, and they don't have, nor do they need, any screen saving feature. One, my Ensoniq SQ80, shows some faint signs of burn-in on some segments on its VFD display, but it's barely noticeable after 29 years of being powered-on.
If OLED technology doesn't get better, and require the need for screen saving feature, it will take the way of the Plasma TV screens, which is OUT.

[rant mode Off]
Title: Re: Feature Requests
Post by: DavidDever on December 26, 2017, 07:47:21 PM
[rant mode On]
And, while we're on the subject, this OLED technology is not well suited for displays on synths. And until they find a way to have the lifespan stated in decades, instead of hours, it's doomed as a display technology. Yes, it's crisp and fast, with excellent contrast. But the limited lifespan and poor performance under bright light, not to mention the higher price (for now), make it less than ideal.
I've got 30 year old synths that have VFD, or LCD, or even LED displays that are still working very well, and they don't have, nor do they need, any screen saving feature. One, my Ensoniq SQ80, shows some faint signs of burn-in on some segments on its VFD display, but it's barely noticeable after 29 years of being powered-on.
If OLED technology doesn't get better, and require the need for screen saving feature, it will take the way of the Plasma TV screens, which is OUT.

[rant mode Off]

All displays die after a period of time, including (if not especially!) the Ensoniq VFD displays (such as the SQ-80). There are plenty of options for display replacement, provided that the schematics are handy, and provided that the chassis cutout is reasonably large enough. I wouldn't worry about it, to be honest.
Title: Re: Feature Requests
Post by: gernotreininger on January 10, 2018, 05:42:27 AM
When tweaking a sound a feedback in the display would be great when you reach the value where you started of. Could be a white dot or circle.  It would be much easier to go back to initial settings.
Title: Re: Feature Requests
Post by: AlainHubert on January 10, 2018, 09:30:05 AM
When tweaking a sound a feedback in the display would be great when you reach the value where you started of. Could be a white dot or circle.  It would be much easier to go back to initial settings.

Agreed. But the "Compare" button is also a way to know. But not as practical as a dot on the display.
Title: Re: Feature Requests
Post by: AndreCult on January 12, 2018, 10:05:27 AM
Poly Sequencer transpose.

Hold the "Hold" button down, it starts flashing indicating that the sequencer can be transposed by the keys on the fly.


Page 44 of the manual. 
Play sequence;  Hold record button while playing keyboard.

Request:  It would be nice to toggle this feature instead of holding the record button.

I like to program a series of rests/ties onto one note in the seqencer and then transpose live.  (for now i use my microbrute for this) :)
Title: Re: Feature Requests
Post by: dequalsrxt on January 12, 2018, 01:30:04 PM
Hi all, I just received an 8 voice desktop yesterday, really enjoying it! It was an impulse buy, but I’m totally happy with my decision. I enthusiastically agree with these feature requests:

My addition to the list: If the current patch has been edited, there's a prompt on the screen to ask if you want to lose your edits before changing patches should the Program or Bank knobs be turned.

Yes +1 for this, it's very frustrating to spend time programming a great sound, only to have it all disappear because your finger accidentally brushes the program knob when your trying to press the write button - grrrr!

I mention this first because it happened to me last night - had a killer jam going, was just at that point where I was like, I should record this, and then I brushed the program knob, lost everything. I guess I should record more liberally, save my patches more often, but…

Sequencer Midi Out

This is #1 on my wish list. I imagine it’s not very practical for the gated sequencers since they can be routed anywhere and are part of the patch. But the ability to bounce regular midi note data from the poly sequencer (and arp) would be friggin’ ace. The poly sequencer is pretty much what pushed me over the edge on this synth. I don’t play keys and sitting at a keyboard and trying to come up with something for me is just blah. I much prefer just entering data and playing with it until it sounds right.

This is basically how I want to work with the synth - enter note data on the rev2 poly sequencer, then advance through the steps like an sh101/jx3p sequencer with gates programmed from my drum machine and/or modular. It’s super easy to build complex patterns from simple parts this way - for example, program a 7 step sequence on the rev2 and advance through it with a 9 triggers in a 16 step bar on a drum machine or whatever. Once I’ve got a cool sequence and rhythm, I’d like to be able to bounce it down to an external sequence. This would open up the sequencer slot on the rev2 so I could use the gated sequencers to modulate other parameters. That would also give me the original poly sequence to edit and/or port to other synths or patches on the rev2.

I'm telling ya, sequencer midi out would be just awesome - you should totally do it.

 - - - -

So those are the big things that I'd like to lobby for. Other things off the top of my head…

It’s already been mentioned, but the ability to modulate the sustain stage on the envelopes, that’d be cool.

It’d also be cool to have a poly mode like poly 2 on the Jupiter 6. Paraphrased from the jp6 manual - ‘only the last note(s) played receive their natural release length’, so the next note(s) cuts off the previous note(s)’ release.

Also would be cool - the ability to select different divisions relative to the master tempo for each gated sequencer.

Anyways, thanks for your consideration, I should get back to the synth!
Title: Re: Feature Requests
Post by: Sleep of Reason on January 18, 2018, 07:46:38 AM
It's truly time for preset categories (and perhaps live set-list mode) now that the Korg Prologue has such features. (https://youtu.be/KlaGeJs4LSs?t=9m18s)
Title: Re: Feature Requests
Post by: extempo on January 18, 2018, 08:56:18 AM
Just to put it out there, it's never been our prerogative to shape the functionality of our instruments based on what our competitors do. As has been said elsewhere in this thread, our users come up with great feature ideas, but they are not always practical to implement, and if a particular feature doesn't fit the design ethos of the product, it's not likely to get implemented.

That said, no one should hold back with even the wildest requests--that's what this thread is for!
Title: Re: Feature Requests
Post by: AlainHubert on January 18, 2018, 10:00:03 AM
Just to put it out there, it's never been our prerogative to shape the functionality of our instruments based on what our competitors do. As has been said elsewhere in this thread, our users come up with great feature ideas, but they are not always practical to implement, and if a particular feature doesn't fit the design ethos of the product, it's not likely to get implemented.

That said, no one should hold back with even the wildest requests--that's what this thread is for!

That's a nice way to tell us to basically forget about any new feature, but to keep on dreaming even if some of them, while really useful and great suggestions, will never be implemented. Because DSI doesn't follow what other companies do ?

Well, at least they're upfront about it.
Might as well lock this thread then, or perhaps renamed it Dreamer's Utopia Corner ?  ;)  ;D
Title: Re: Feature Requests
Post by: Robot Heart on January 18, 2018, 11:38:00 AM
No, we're not saying nothing will ever get implemented. We've been extremely clear with communication, so you guys know what to expect. Would you prefer the standard practice of indefinitely offering lip service, repeatedly promising to implement everything, and delivering on nothing?

This is a feature requests thread. It does not mean features will be implemented. It also does not mean we won't implement any features suggested here. It also does not mean we don't listen to our customers.

Complaining that other companies have a feature, or that your feature isn't implemented but it should be, or why isn't your feature implemented even though it has been suggested previously will certainly not do anything other than turn this thread into an unpleasant place to interact.

We all know it's frustrating when something that you view critical to your workflow or something "glaringly obvious" (to you) hasn't been addressed. However, I will remind you it's best to take the instrument for what it is when you purchase it. Some features will get implemented over time, some will not, because of the litany of reasons cited previously.

We make extremely flexible musical instruments that are capable of creating fantastic sounds right out of the box. Can any commercial product ever manufactured be improved? Unquestionably. Does this mean nothing is useable or good until it's been revised to your personal specifications? Definitely not.

No instrument is perfect, and no instrument will have absolutely every feature and workflow you want. But everything we make is useable now. It's literally impossible to implement everything that everyone wants, and our timeline for OS updates is not frequent. Please take this into consideration and understand we aren't purposely trying to upset you. We're only being transparent so you are educated and informed.

Now, let's keep this thread on topic.
Title: Re: Feature Requests
Post by: Sleep of Reason on January 18, 2018, 11:50:59 AM
I don't believe I'm off-topic when I say that it's completely impractical to have a thousand presets and no categories. Categories are the absolute most logical (rather than subjective) seemingly feasible missing feature.

Title: Re: Feature Requests
Post by: robheit on January 18, 2018, 11:55:08 AM
+1 on he poly unison request.
Title: Re: Feature Requests
Post by: Robot Heart on January 18, 2018, 12:18:34 PM
I don't believe I'm off-topic when I say that it's completely impractical to have a thousand presets and no categories. Categories are the absolute most logical (rather than subjective) seemingly feasible missing feature.

I should have also mentioned, repeating a feature request will not make it happen any faster. Whether or not you think something is impractical or feasible has no bearing on the request, and your assumptions about ease of implementation do not automatically mean you are correct.

Speaking to your specific request, it is possible to organize your programs yourself via the onboard copy/move/save functions, a free hex editor, or one of the available software editors. Multiple solutions exist now. It simply requires you to put in the time to set things up specific to the way you like them.

*Edit: added another organization method.
Title: Re: Feature Requests
Post by: dslsynth on January 18, 2018, 02:42:40 PM
Documentation feature request: Fully document sysex format including program vector layout, CC/NRPN controllers and the location, current values and semantics of sysex format version numbers.
Title: Re: Feature Requests
Post by: Sleep of Reason on January 18, 2018, 08:20:13 PM
your assumptions about ease of implementation do not automatically mean you are correct.
Thus the "seemigly" part. Now I could go on an entire esoteric rant about how categories have been systematically crucial since Plato, but then I would admittedly be derailing the thread.

Speaking to your specific request, it is possible to organize your programs yourself via the onboard copy/move/save functions
Excuse my ignorance, I was under the impression that factory banks are not editable since that's what the manual states right off the bat, which I took for unmovable. It's much more palpable knowing that those 512 factory presets (not to be confused with my 512 user presets) can also be ordered as well. Thanks for the kind & helpful info.
Title: Re: Feature Requests
Post by: kris on January 20, 2018, 03:33:50 PM
Documentation feature request: Fully document sysex format including program vector layout, CC/NRPN controllers and the location, current values and semantics of sysex format version numbers.

Agree on that, the documentation could be better. Note that support hands out on request a document called "Prophet Rev2 Packed Parameter Data Assignments.pdf" which gives you the layout of the sysex, helped me fill the gaps I had missed.
Title: Re: Feature Requests
Post by: kris on January 20, 2018, 03:40:15 PM
Not sure if this was asked before, I couldn't find it reading through the previous posts in the feature request thread:

+ Single-shot LFO mode

Like the Access Virus, where you can set each LFO to not loop. Sort of the opposite of "loop Env3". I find the two Ramp generators of the Oberheim Matrix 1000 to be of great use, and the Rev2 could basically provide the same with the sawtooth/inverse saw and a non-looping LFO on slow speed?
Title: Re: Feature Requests
Post by: AlainHubert on January 20, 2018, 06:15:33 PM
Quote from: kris on January 20, 2018, 06:40:15 PM:

"Not sure if this was asked before, I couldn't find it reading through the previous posts in the feature request thread:

+ Single-shot LFO mode

Like the Access Virus, where you can set each LFO to not loop. Sort of the opposite of "loop Env3". I find the two Ramp generators of the Oberheim Matrix 1000 to be of great use, and the Rev2 could basically provide the same with the sawtooth/inverse saw and a non-looping LFO on slow speed?"

-------

Hi kris.

Even though what you suggest could be interesting, I'll simply quote what extempo of DSI wrote, earlier in this thread, about following in other companies footsteps:"...it's never been our prerogative to shape the functionality of our instruments based on what our competitors do."

 ;)








Title: Re: Feature Requests
Post by: LoboLives on January 20, 2018, 09:11:25 PM
I miss an option to turn of the OLED screen completely so that even midi does not trigger it on.
I use my module and remote control it, so I can't see anything on the screen anyway :-)

(https://i.imgur.com/zCMdNEN.png)

I just hate screens on analog synths all together. I appreciate the fact the REV2 menu is shallow but I’d much rather not have to use it at all. It’s weird I thought I’d be frustrated with the P6 and OB6 lack of screens but I’ve actually fallen in love with it and would rather not have them. Probably in the minority here.
Title: Re: Feature Requests
Post by: Paul Dither on January 21, 2018, 03:48:05 PM
Would it be possible to calm down a bit?—I'm not asking this to shut people down, but I can sense a growing passive aggressive tone that I believe isn't very fruitful for the future climate of this forum.

As for those rather provocative meant comments about feature requests and how some perceive the operation of other companies, I would like to point out that it doesn't make sense to measure a comparably tiny company like DSI against manufacturers like Korg for example, as they simply don't share the same resources, neither in terms of employee numbers nor—which is related to that—in terms of exclusive firmware maintenance time. There is no large division for past products and one for future developments. In a small company like DSI, most people have to take care of many different tasks simultaneously.

The latter simply means that it sometimes takes a bit of patience while you're waiting for OS updates or bug fixes. Yes, that can be frustrating at times, which has also already been acknowledged on behalf of DSI on a number of occasions. But there's certainly not an evil masterplan behind all that, like a willful strategy for letting down customers. Quite the opposite is the case: The tech support is very responsive and will usually get back to you within 24 hours. These people also make sure that in those cases where parts have to be swapped, things will be handled as straightforward as possible both in terms of repairs and shipping.

The reason why it can take a bit longer now and then is simply a company with less than 20 employees, a not inconsiderable number of instruments to take care of—most of which have a flagship status—, and finally the fact that they're still developing new products each year to keep us gear nerds happy.

On top of that it has always been a good practice—as it has been pointed out several times already—to take an instrument for what it is, not for what it may be in the unpredictable future. People have always used synths like that because no single instrument is perfect in the sense that it comes with every feature you can possibly think of. In fact, the only type of instrument that was trying to cater to that notion was the workstation. And if you actually like and use a synth for what it was originally meant to be, you'll probably also find a way around some quirks or limitations that lie in the nature of every instrument's design. Above that, a bug is a bug and should of course be fixed in the long run. Every additional feature, though, that wasn't included in an otherwise fully working synth is a bonus instead.

The latter doesn't render this thread useless, since DSI have already implemented user suggested features in the past. But not each and every desired additional feature can be expected to be implemented on a mandatory basis, especially not if it was never promised nor specifically announced in the first place.

So, let's all take a deep breath and try to engage in a more constructive conversation, not least because there are human beings that like to be treated fairly on each side.
Title: Re: Feature Requests
Post by: Sacred Synthesis on January 22, 2018, 08:06:55 AM
Just to put it out there, it's never been our prerogative to shape the functionality of our instruments based on what our competitors do.

Pardon me, but I really, really, really like this approach.  Not to be so simplistic as to presume that "different" is always and necessarily better.  Not at all.  It can be much worse than average.  But I do like the fact that DSI is not a monkey-see-monkey-do affair.  Perhaps that's one advantage of being a small business.  You can still have an individual personality. 
Title: Re: Feature Requests
Post by: AlainHubert on January 22, 2018, 10:15:13 AM
That's perfectly fine. And it's good that a company like DSI would like to do things somewhat differently. I really appreciate the fact that they didn't follow the dreaded "mini-keys" fad, started by Korg, Yamaha and Roland, and stuck with full size keyboards.

But it should also reflect the needs of its customer base, in an attempt at offering even more satisfying products. Especially when some of those needs are shared by numerous customers, many of which are professional musicians, not just occasional players like myself.

And if some of those needs happen to also be fulfilled by competitors on their products, it shouldn't preclude DSI from offering them also, if that's what musicians expect.

Like a global LFO mode, a dot on the display when passing thru previously saved parameter value with a knob (which was also added later on to the Prophet 6 and OB6 I might point out), and the ability to see the patch name when comparing before saving, and finally some sort of confirmation request to change patch when accidentally touching the "Program" knob, preventing loss of hours of tweaking...
Title: Re: Feature Requests
Post by: Sacred Synthesis on January 22, 2018, 10:22:04 AM
That's all fine.  I have no problem with your point.  I, too, want features.   As long as our "shoulds" don't turn into ugly "musts".
Title: Re: Feature Requests
Post by: vinnyburns1@mac.com on January 22, 2018, 10:33:12 AM
That's all fine.  I have no problem with your point.  I, too, want features.   As long as our "shoulds" don't turn into ugly "musts".

I agree too. Also, let’s not go too far the other way though. It’s a user forum not a staff forum is it not?
They can’t have it both ways. Sometimes it’s “if you need official support, don’t do it here, contact us direct at the company” Then on the other, it’s being treated like they are here in an official capacity and everyone has to bite their lips and keep quiet.
As for only buying synths on the spec that is published and the way it behaves on release, I totally agree but that only works if the synth works correctly on release.
Title: Re: Feature Requests
Post by: dequalsrxt on January 22, 2018, 10:57:26 AM
Got another feature request. I would like to be able to advance through the gated sequencers with a trigger/gate like you can with the poly sequencer; like the key step mode but instead of midi notes, external triggers.
Title: Re: Feature Requests
Post by: Chonkey on January 22, 2018, 07:34:42 PM
Would love to see OSC 1 and/or OSC 2 as source options in the modulation matrix!
Title: Re: Feature Requests
Post by: lcbzh29 on January 23, 2018, 05:00:25 AM

We all become addicted to the update ... any type of update (computer, tv box, mobile phone, software, video game, etc ...)

the time we are losing to always updating something.   ;) :(
Title: Re: Feature Requests
Post by: AlainHubert on January 23, 2018, 08:56:44 AM

We all become addicted to the update ... any type of update (computer, tv box, mobile phone, software, video game, etc ...)

the time we are losing to always updating something.   ;) :(

Yep. Back in the days of hardware ROMs, companies had to make sure that their products were as bug-free as possible before bringing them to market. But today, we have to compose with half baked software, and in some cases even serve as involuntary beta testers, because of the overuse of the ability to publish updates to correct poorly written code.
And that's not just DSI. All electronics companies do it. From Apple to Samsung, from Behringer to Moog. I wouldn't be surprised if one day soon we'll have to update the firmware on a bug filled toaster (software bug, that is. lol! )

The only positive point to all this, is the possibility of getting additional new features not part of the original design. IF there is enough room in memory. Most of the time, free of charge. Which is great. 

But to keep this thread on topic, I'd like to be able to change the root note of the sequencer without having to hold down the Record button (if that was already asked for, I'm sorry). BTW, if someone could perhaps compile a list of already requested features and publish them, that would be great !   
Title: Re: Feature Requests
Post by: Sacred Synthesis on January 23, 2018, 10:56:46 AM
But today, we have to compose with half baked software, and in some cases even serve as involuntary beta testers, because of the overuse of the ability to publish updates to correct poorly written code.

I posted a comment just like this years ago when I was just getting back into synthesizer.  It was quite annoying to me, since I had been raised on ARPs, Moogs, and Junos.  The answer I was given by others was that it's virtually impossible to write a perfect code.  So, if you want a complex instrument, that's the price you have to pay - corrective updates. 

I could be wrong, but I'm not aware of any company that has issued a modern instrument with a perfect code.  It seems to me that we have to take it all in stride if we're to demand so many features.
Title: Re: Feature Requests
Post by: elliottjkeen on January 23, 2018, 02:50:04 PM
Hi everyone,

This is my first post/comment on the forum ever so I apologise if this question has been asked already. I've had my Rev2 since the end of November and I've not had time to do much exploring as yet. I noticed today that the sustain for the envelopes is not assignable as a destination to modulate. If DSI updated the firmware or something would this be made possible or is this something that cannot be changed?

Cheers

Elliott
Title: Re: Feature Requests
Post by: Paul Dither on January 23, 2018, 03:10:20 PM
Hi everyone,

This is my first post/comment on the forum ever so I apologise if this question has been asked already. I've had my Rev2 since the end of November and I've not had time to do much exploring as yet. I noticed today that the sustain for the envelopes is not assignable as a destination to modulate. If DSI updated the firmware or something would this be made possible or is this something that cannot be changed?

Cheers

Elliott

The sustain stage has never been available as a modulation destination on any synth, or at least none I can currently think of. It's a level parameter, not a temporal parameter like Delay, Attack, Decay, and Release. You can implicitly modulate it by modulating the filter cutoff or the VCA level directly, depending on what level you'd like to modulate.
Title: Re: Feature Requests
Post by: MintMark on January 26, 2018, 11:27:34 AM
Hi everyone,

This is my first post/comment on the forum ever so I apologise if this question has been asked already. I've had my Rev2 since the end of November and I've not had time to do much exploring as yet. I noticed today that the sustain for the envelopes is not assignable as a destination to modulate. If DSI updated the firmware or something would this be made possible or is this something that cannot be changed?




Cheers

Elliott

The sustain stage has never been available as a modulation destination on any synth, or at least none I can currently think of. It's a level parameter, not a temporal parameter like Delay, Attack, Decay, and Release. You can implicitly modulate it by modulating the filter cutoff or the VCA level directly, depending on what level you'd like to modulate.

I guess you could modulate the corresponding envelope amount too? (LP Filter Env Amount or Amp Env Amount)

I think it would be great if the forum could let us "like" or vote or somehow indicate our support for feature suggestions. That way DSI could get a better view of the relative popularity.

Anyway, if I could vote for only one it would be a beat syncing mode for the arpeggiator. I was quite surprised when I discovered the way it currently works...

   Mark
Title: Re: Feature Requests
Post by: AaronRA on January 26, 2018, 08:10:52 PM
and finally some sort of confirmation request to change patch when accidentally touching the "Program" knob, preventing loss of hours of tweaking...

I like this idea, but it would absolutely have to be an option we can turn off. Reason being, I perform with the Rev2 live, and frequently tweak parameters during a song, and then have to make an immediate switch to another patch. If every time I try to switch to the next patch after moving the cutoff knob I have to confirm or deny the switch, it would literally make this instrument entirely useless to me. I'm sure I'm not the only one in that situation by a long shot.
Title: Re: Feature Requests
Post by: kris on January 27, 2018, 04:23:48 AM

Hi kris.

Even though what you suggest could be interesting, I'll simply quote what extempo of DSI wrote, earlier in this thread, about following in other companies footsteps:"...it's never been our prerogative to shape the functionality of our instruments based on what our competitors do."

 ;)

Hi Alain,

granted, we don't need to reinvent what's already there in other synths. I just can't wrap my head around how to do a long ramp that does not repeat with the Rev2 - maybe there is a solution I am overlooking? The Env3 can do that, but I use that often already for other things... so 4 LFOs (repeating) and just 1 additional Env (optionally repeating!) is great, why not make the 4 LFOs optionally non-repeating? You would get easy rising and falling ramps with that, and it doesn't look impossible to me given that the Env3 has the option to repeat.

But again, I'm a noob and still learning.

Cheers!
Title: Re: Feature Requests
Post by: joesh on January 31, 2018, 02:25:57 PM
I've read the several complaints/suggestions about the lack of categories for the presets, and of course the suggestion that one can indeed just copy/move/save if needs be. However, I would suggest a simpler solution which would be to produce an OS with blank U1-4 banks. This would be a simpler idea. Since the F Banks are mirrored in the U Banks, then one would just copy - in the order one wished - the various setting/sounds to the fill up your U Banks. You would probably ignore some of the F Banks sounds, leaving you with a less cluttered selection of sounds to work from. 

I hope that makes sense..... :o
Title: Re: Feature Requests
Post by: jurfin on February 01, 2018, 09:48:12 AM
I would love to see some effects added. A compressor would be really nifty, as would a spring reverb, tape delay, and overdrive. The distortion sounds great but I'd really enjoy a lighter option for dirt.
The idea of an oscilloscope is a great one! Probably not gonna happen, but that would be really awesome. Also want to add a +1 to the many requests for some kind of an indicator of a saved value in a patch. A dot on the screen, or even better, a numerical display of where the parameter is set within the preset would make a world of difference when programming/editing patches.
Title: Re: Feature Requests
Post by: Synthnoob on February 01, 2018, 02:21:10 PM
I'm new to Dave Smith Instruments but I would like if there was an Instructional DVD going over the synth in detail and a quick start guide for the Synth. My GAIA came with stuff like that and it was a big help in learning how to get into the board and start making sounds. The existing product manual I found hard to understand without really knowing the synth. I'm big on reading manuals it's the first thing I do before even playing or I like to read and play as learn the keyboard. I found youtube videos going over the synth to be extremely helpful in learning how to use it.
Title: Re: Feature Requests
Post by: Sacred Synthesis on February 01, 2018, 07:29:23 PM
That's a great idea.  Unfortunately, DSI lacks the resources to create such a DVD.  They tend to leave such things to us, to we who buy their instruments and know them like the backs of our hands.  As an example, Paul Dither has made a superb and amazingly thorough overview video of the Rev2 that may serve the same purpose as you've suggested.  It's here:

https://www.youtube.com/watch?v=kqcE1OjWtZE



Title: Re: Feature Requests
Post by: jg666 on February 02, 2018, 01:55:25 AM
That's a great idea.  Unfortunately, DSI lacks the resources to create such a DVD.  They tend to leave such things to us, to we who buy their instruments and know them like the backs of our hands.  As an example, Paul Dither has made a superb and amazingly thorough overview video of the Rev2 that may serve the same purpose as you've suggested.  It's here:

https://www.youtube.com/watch?v=kqcE1OjWtZE

Agreed. That was the first thing I suggested in the thread by Synthnoob asking for such help :)
Title: Re: Feature Requests
Post by: thelmalalala on April 22, 2018, 03:22:24 PM
I was surprised I didn't see another topic like this, but correct me if I'm wrong!

Here are some features I would like in the future-

Keeping within bi-timbrality, have a combo layer/split mode where you can have part of the keyboard stacked, and the other part just one of the layers. Would be great to have stacked pads in one hand and then a more simple sound in another hand for bass or melodies.

Another idea- have the hold button selectable on the different layers in stack mode. Right now it is in split, but not stack. Would be nice in stack mode to be able to arpeggiate on one layer with hold, but not have the other layer hold unless you specifically assign it to.
Title: Re: Feature Requests
Post by: jipumarino on April 24, 2018, 02:27:59 PM
One minor thing I'd like to get at some point is an additional MIDI sync option: sync when MIDI clock is present, use internal clock when it's not.
Title: Re: Feature Requests
Post by: thelmalalala on April 25, 2018, 07:10:14 PM
Keeping in the confines of bitimbrality- would be cool if there was a stack/split combo mode where you could stack half the keyboard and have the other half only using one of the two patches. Would be great for thick pads in one hand with a melody or bass line in the other.

also, I noticed in stack mode there is no option to "hold" only one layer, you have to do both, yet in split they are separate. Would open up a lot of possibilities.

More interesting/innovative arpeggiator modes

Now some more farfetched/obscure suggestions:
What if the different tracks on the sequencer could have different time divisions? Also what if these tracks could be triggered in succession of on another as another option besides layering. this way you could create chains of sequences or swithc between sequences. Would be cool to have midi implementation too so I could trigger track one, or track two externally.
Title: Re: Feature Requests
Post by: ferdi2k on April 27, 2018, 04:19:50 AM
+1 for a patch-based option to have a global LFO, as discussed e.g. here
https://forum.davesmithinstruments.com/index.php/topic,2127.0.html

As there is a manual workaround to achieve what is asked for, there must be a way
for doing the same using the firmware, I hope.

Title: Re: Feature Requests
Post by: Quatschmacher on April 27, 2018, 02:43:48 PM
Would it be possible for each oscillator waveshape selector switch to also serve as a mute or on/off toggle by means of a long button press? That way it would be easy to bring in or switch off an oscillator during performance without having to adjust its level in the mixer or or having to cycle through each oscillator shape. It would be cool if it could be implemented in such a way that even when muted, it were still possible to cycle through the waveshapes via short button presses; doing so would temporarily illuminate each LED as it is cycled and it would go dark again after a second or two (if still muted).
Title: Re: Feature Requests
Post by: Micimacko on April 27, 2018, 10:47:58 PM
Hi,
the local control off would be nice to turn off only the keyboard, not the front panel.

thanks
Title: Re: Feature Requests
Post by: SynthPlayer on May 02, 2018, 10:08:34 AM
Simply my feature requests:

1. Usefull hold button:
Hold all keys played together. If all keys were released keys are hold but if then new keys are pressed the old keys are released.
(look at products of other manufacturers (Yamaha, Behringer, Roland, ... ), if it is not familiar for you)

2. Unison modes with polyphonie

3. Sequencer transpose by single key touch.

4. Patch categories and browse possibility


This was good:

Speaking to your specific request, it is possible to organize your programs yourself via the onboard copy/move/save functions
Excuse my ignorance, I was under the impression that factory banks are not editable since that's what the manual states right off the bat, which I took for unmovable. It's much more palpable knowing that those 512 factory presets (not to be confused with my 512 user presets) can also be ordered as well. Thanks for the kind & helpful info.
Title: Re: Feature Requests
Post by: AlainHubert on May 02, 2018, 11:03:15 AM

1. Usefull hold button:
Hold all keys played together. If all keys were released keys are hold but if then new keys are pressed the old keys are released.
(look at products of other manufacturers (Yamaha, Behringer, Roland, ... ), if it is not familiar for you)


Let me mention what someone from DSI essentially said a while back about features found on other synths: We don't really care what other manufacturers do. If you don't like our products the way they are, it's just too bad.

So, I wouldn't hold my breath on getting new and useful features like the ones being mentioned repeatedly here.
Title: Re: Feature Requests
Post by: Sleep of Reason on May 03, 2018, 09:41:36 AM

1. Usefull hold button:
Hold all keys played together. If all keys were released keys are hold but if then new keys are pressed the old keys are released.

Agreed.

Plus I know it's tantamount to a crime around these parts to mention something like this, but a visual representation (https://youtu.be/TLa3QLEAq08?t=3m28s) of the filter/envelopes is simply what modern synths feature. If the REV2 is going to be in production for 9 more years hopefully, then it would certainly be beneficial for all parties involved (that is, product producer and consumer alike) to make it more user-friendly and streamlined in the right places.
Title: Re: Feature Requests
Post by: guyaguy on May 04, 2018, 09:49:02 PM
Ability to program the gated sequencer via the keyboard as per the poly sequencer. This was not a feature of the 08 but it was on the PolyEvolver.
Title: Re: Feature Requests
Post by: roberth909 on May 06, 2018, 11:35:29 AM
Yep, some unison modes with poly would be interesting.  (On a 16-voice) 2 unison / 8 poly, 3 unison / 5 poly, 4 unison / 4 poly would be a good start, just to see what those sound like.  It may not be very useful going further, too many sonic collisions.
Title: Re: Feature Requests
Post by: Quatschmacher on May 13, 2018, 04:42:10 AM
It’d be great to have some of the buttons also be modulation destinations, most notably the oscillator sync button and the 2/4 pole selector button.

A use of this would be to create a patch where turning up the mod wheel would both change from an un-sync’d sound to a sync’d one and simultaneously alter the amount of pitch modulation being directed to the sync’d oscillator.
Title: Re: Feature Requests
Post by: Montyrivers on May 14, 2018, 08:22:34 AM
Sorry if it's been asked already, but:

LFO One-Shot mode!

I want to be able to use my lfo's as additional envelopes.
Eg:  with key sync engaged and sawtooth shape selected it triggers only once as a decay stage.
Title: Re: Feature Requests
Post by: benbravo on May 16, 2018, 11:56:06 AM
Some features I would love to see on the rev2 next firmware updates:

- A way to see what the stored values are when changing something in a preset!
- Local control off : choosing keyboard or panel or both.
- A new modulation destination : program volume

Cheers!
Title: Re: Feature Requests
Post by: dsetto on May 17, 2018, 04:39:14 AM
LFO One-Shot mode!

I want to be able to use my lfo's as additional envelopes.
Eg:  with key sync engaged and sawtooth shape selected it triggers only once as a decay stage.
I like this. (Doesn't seem resource-intensive.)
Title: Re: Feature Requests
Post by: hageir on May 22, 2018, 05:57:54 AM
Sorry if it's been asked already, but:

LFO One-Shot mode!

I want to be able to use my lfo's as additional envelopes.
Eg:  with key sync engaged and sawtooth shape selected it triggers only once as a decay stage.

This you could achieve using the auxiliary envelope (destination: depth of LFO)
Title: Re: Feature Requests
Post by: hageir on May 22, 2018, 06:01:19 AM
A better naming/alphabet system.
The way the encoder speeds up / multiplies with a turn is very nice and quite precise. All good in my opinion.
but
I want an additional way of naming/typing.
BY FAR the best method is from Elektron, once you got it, it takes a couple of seconds to write a name for a patch:

(https://i.imgur.com/gE2lcYE.png)

—————
(Oscillator Level; untied from the Mix? -perhaps as a Modulation Destination or a Misc. Parameters setting?)
—————
Last but not least (fingers crossed; pun?)
(Cross) Modulation (Poly Mod) between oscillators 1&2, like on the Pro-One and Prophet 5, you could send Osc. B into Osc. A,
the 'closest' thing I can get to that is either by a KBD Tracked LFO at high rates* or the 'Audio Out' Modulation Source (The Ring Modulation effect is also quite nice)

Is it possible to achieve a rate/speed Multiplier for the LFOs or are they analog as well?
Title: Re: Feature Requests
Post by: Montyrivers on May 22, 2018, 09:24:49 AM
Sorry if it's been asked already, but:

LFO One-Shot mode!

I want to be able to use my lfo's as additional envelopes.
Eg:  with key sync engaged and sawtooth shape selected it triggers only once as a decay stage.

This you could achieve using the auxiliary envelope (destination: depth of LFO)

But that would require me to use up my aux envelope when I could have four one shot lfo's with their own independent rate and depth controls.
Title: Re: Feature Requests
Post by: hageir on May 22, 2018, 10:21:32 AM
Oh, before I forget:
a more detailed way of handling; importing and exporting the microtonal scales
(I would like to back up the factory scales and I want to choose the 'slots' where I drop in new ones)
Title: Re: Feature Requests
Post by: Robot Heart on May 22, 2018, 12:28:28 PM
You can download the factory alternate tuning scales from the "Download Sound Banks" page for the Rev2 (and all instruments that support alternate tunings). You can also choose which slot new tunings go into by changing the "program number" byte in the SysEx file before sending it to the synth. So, perhaps not exactly what you're asking for but you can get pretty close with the current implementation.
Title: Re: Feature Requests
Post by: guyaguy on May 24, 2018, 01:15:55 PM
Hi,

this is the feature i missed instantly on day one when i started exploring my PRO-2 and its the same with the REV2.

You can modulate the frequency of a LFO but only if it is not switched to CLK SYNC.
It would be great if you could modulate ( or control via midi ) a tempo synced LFO.
Instead of changing the frequency number from 0-127 it should change the steps 8Steps 4Steps 2Steps 1.Steps etc...
This could map to a number Range. So that the 16 Step Settings that there are are mapping to a range of 8 Numbers

E.g:
32 Steps =  0-7
16 Steps =  8-15
 8 Steps = 16-23
 6 Steps = 24 - 31
 4 Steps = 32 - 39
 3 Steps = 40 - 47
 2 Steps = 48 - 55
1.5 Steps = 56 - 63
 1 Step = 64 - 71
2/3 Step = 72 - 79
1/2 Step = 80 - 87
1/3 Step = 88 - 95
1/4 Step = 96 - 103
1/6 Step = 104 - 111
1/8 Step = 112 - 119
1/16 Step = 120 - 127

There are many use cases for this. An example would be:
Create a filtered sound, assign LFO with e.g. revers saw to Filter Frequency.
LFO switched to click synced and change the "frequency aka steps" of that LFO.
You get very cool rhythmic patterns.
Dear lord yes!
Title: Re: Feature Requests
Post by: Razmo on June 15, 2018, 01:31:32 PM
This has probably been requested before, but I guess it won't hurt to wish for it again:

An extra global LFO...

I know that the "per voice" LFO's are individual and meant for each voice, which is also what it should be like, but the REV2 has a modulateable FX engine which is essentially monophonic and works on all voices at the same time, thus it's CRUCIAL that the mod matrix can route a global LFO to those parameters, otherwise the result is complete chaos.

An example: when I route an LFO to the hipass filter cutoff, the effect I get is a modulation that seem to jump here and there because the LFO routed to it is from the currently last played voice... it's completely unuseable to be honest.

So please... if it could be added as some extras in the MISC menu, please add a global LFO and add it to the modulation sources.

You'd imagine that a global EG would also be crucial, but since it always restart when a new key is pressed, it's not needed... also, if you use the four LFO's with keysync on, it will also work, but many of the FX has parameters that would benefit from a free running global LFO.

If the four LFO's could somehow get a switch for a "global mode" that would of course also do it, but I do not know if the hardware would allow this...
Title: Re: Feature Requests
Post by: AlainHubert on June 15, 2018, 10:46:49 PM
This has probably been requested before, but I guess it won't hurt to wish for it again:

An extra global LFO...

I know that the "per voice" LFO's are individual and meant for each voice, which is also what it should be like, but the REV2 has a modulateable FX engine which is essentially monophonic and works on all voices at the same time, thus it's CRUCIAL that the mod matrix can route a global LFO to those parameters, otherwise the result is complete chaos.

An example: when I route an LFO to the hipass filter cutoff, the effect I get is a modulation that seem to jump here and there because the LFO routed to it is from the currently last played voice... it's completely unuseable to be honest.

So please... if it could be added as some extras in the MISC menu, please add a global LFO and add it to the modulation sources.

You'd imagine that a global EG would also be crucial, but since it always restart when a new key is pressed, it's not needed... also, if you use the four LFO's with keysync on, it will also work, but many of the FX has parameters that would benefit from a free running global LFO.

If the four LFO's could somehow get a switch for a "global mode" that would of course also do it, but I do not know if the hardware would allow this...

I seem to remember that DSI were pretty clear in saying that there will never be any global LFO mode on the REV2, and not to keep our hopes up, very unfortunately.
Title: Re: Feature Requests
Post by: Razmo on June 15, 2018, 11:09:52 PM
Well... I'll wish for a way to get a free running global LFO anyway... Did they have any particular reason to not making a simple single global LFO?
Title: Re: Feature Requests
Post by: guyaguy on June 16, 2018, 08:30:20 AM
Well... I'll wish for a way to get a free running global LFO anyway... Did they have any particular reason to not making a simple single global LFO?
It seems like architecture of the Rev 2 is such that it is essentially 16 monophonic synthesizers. I actually enjoy the fact that the LFO, gated seq, and 3rd looping EG run independently per voice. It's fairly unique and can create some complex rhthmic patterns just by staggering keystrokes. But I know it's not something everyone wants all the time.

One way of getting a global LFO is to use the Pedal/CV input. Obviously it requires a second device with LFO out like a Moogerfooger, Moog CP-251, a Eurorack module, etc., but it then lets you route a global LFO to any parameter in the mod matrix.
Title: Re: Feature Requests
Post by: AlainHubert on June 16, 2018, 10:46:26 AM
Well... I'll wish for a way to get a free running global LFO anyway... Did they have any particular reason to not making a simple single global LFO?
It seems like architecture of the Rev 2 is such that it is essentially 16 monophonic synthesizers. I actually enjoy the fact that the LFO, gated seq, and 3rd looping EG run independently per voice. It's fairly unique and can create some complex rhthmic patterns just by staggering keystrokes. But I know it's not something everyone wants all the time.

One way of getting a global LFO is to use the Pedal/CV input. Obviously it requires a second device with LFO out like a Moogerfooger, Moog CP-251, a Eurorack module, etc., but it then lets you route a global LFO to any parameter in the mod matrix.

Yes, fortunately we have a CV input for an external global LFO. I've found a way to temporary get an LFO to act as a global one; I momentarily set KEY SYNC to ON, and press 16 keys at once (using my forearm to press a minimum of 16 keys at a time) and then set KEY SYNC to OFF. Not an elegant way to do it, but it works...for a while. After several minutes, all 16 LFOs (on a 16 voice model) will start to slightly drift apart again (especially if the synth is very busy).

An, unfortunately, the Random waveform will generate a different value for each one of the 16 LFOs, but the changes will be in sync. Not exactly global LFO behavior.
But then again, DSI were pretty clear about that too: there won't be any firmware updates offering to get true global LFO behavior, because they're not in the habit of copying what other manufacturers do. A bit silly if you ask me, since most of the features of many of their synths DO offer the same kinds of features as other manufacturers (2 osc per voice, LPF, ADSR envelopes, MOD matrix, etc...). 
Title: Re: Feature Requests
Post by: 4dubs on June 16, 2018, 03:16:56 PM


Yes, fortunately we have a CV input for an external global LFO. I've found a way to temporary get an LFO to act as a global one; I momentarily set KEY SYNC to ON, and press 16 keys at once (using my forearm to press a minimum of 16 keys at a time) and then set KEY SYNC to OFF. Not an elegant way to do it, but it works...for a while. After several minutes, all 16 LFOs (on a 16 voice model) will start to slightly drift apart again (especially if the synth is very busy).

[/quote]

Pretty sure someone else mentioned this same approach in another thread, albeit they suggested first enabling unison mode with all 16 (or 8) voices stacked.  This allows for hitting just a single key to get everything in sync (temporarily) rather than having to use the forearm technique.  Unison can then be disabled.   
Title: Re: Feature Requests
Post by: Razmo on June 16, 2018, 03:34:37 PM
Well... I'll wish for a way to get a free running global LFO anyway... Did they have any particular reason to not making a simple single global LFO?
It seems like architecture of the Rev 2 is such that it is essentially 16 monophonic synthesizers. I actually enjoy the fact that the LFO, gated seq, and 3rd looping EG run independently per voice. It's fairly unique and can create some complex rhthmic patterns just by staggering keystrokes. But I know it's not something everyone wants all the time.

One way of getting a global LFO is to use the Pedal/CV input. Obviously it requires a second device with LFO out like a Moogerfooger, Moog CP-251, a Eurorack module, etc., but it then lets you route a global LFO to any parameter in the mod matrix.

I did not mean in any way that it should be substituted for a global LFO... the way it works is essential... I'm just talking about maybe an extra digital global LFO in the MISC section, that would get added to the mod sources and destinations ... as things are now, you can only use a free running LFO on the FX parameters, if the preset is monophonic so it always is assigned the same LFO... it will not work in polyphonic mode.

An example of what I want to do: Use the Hipass filter as a sort of frequency booster... by setting the MIX to 50/50, and cranking the resonance up to max, and then modulate the cutoff via an LFO... this can get me some nice modulations that boost frequencies up and down the frequency spectrum... but try it! ... set an LFO with a triangle, and you'll definitely not get af nice triangle sweep of the cutoff... it bounces up and down depending on what voice's LFO gets assigned to the cutoff, and it changes with each keystroke.

I just think that if DSI give us the abillity to actually modulate the two FX parameters, then at least it should be possible to modulate them via an LFO, one of the most obvious modulation sources for many of these parameters...

Using something on the CV input is not good enough for me because this is not something everyone have, and if I want to create program banks for others to use, I'd like to incorporate this kind of modulation as part of the preset.
Title: Re: Feature Requests
Post by: Frocktar on June 16, 2018, 11:40:44 PM
I must say I agree with this point completely, they’ve seriously crippled the usefulness of the FX as mod destinations.  I hope someone there is wise enough to see that this one should definitely be added, heck it should have been thought of at the start honestly.
Title: Re: Feature Requests
Post by: Razmo on June 17, 2018, 12:55:35 AM
I have to add something to my above request... for some reason, today, when I create a program routing an LFO to the cutoff of the hipassfilter FX, it seems to work... result is not bouncing around anymore... I made a few tests with the other mod sources that should work polyphonically and realized, that the "global thing" is actually taken care of regarding the modulation of FX parameters... also the LFOs.

When I about when the LFO bounced around the last time, I can remember that it shifted every 8 keypresses... so I assume that it happened as part of the edit buffer dump bug, that is currently on their bugfix list (you can read about this in my dedicated topic).

So I'll say that there is no need to implement a global LFO anyway... at least not for the FX section.

I know others would want a global LFO for the filter... and if DSI has stated that a global LFO is not going to be made for the LFO's, then maybe a request for a Lowpass and even bandpass filter in the FX section is an alternative for those who want to have a global modulateable lowpass filter... if it works with the hipass filter it should work with any filter FX.
Title: Re: Feature Requests
Post by: guyaguy on June 17, 2018, 11:39:49 AM


Pretty sure someone else mentioned this same approach in another thread, albeit they suggested first enabling unison mode with all 16 (or 8) voices stacked.  This allows for hitting just a single key to get everything in sync (temporarily) rather than having to use the forearm technique.  Unison can then be disabled.
Yep

https://forum.davesmithinstruments.com/index.php/topic,2127.msg23142.html#msg23142
https://forum.davesmithinstruments.com/index.php/topic,2027.0.html

Quote
-press unison button while holding misc params (this is shortcut to that area in menu)
-turn unison mode to all of your available voices (8 or 16)
-turn on unison
-turn on key sync on lfo then press a note. The lfos are now synced.
-turn off key sync and turn off unison
 

It gets the LFOs in sync and they will stay in sync even after saving and returning the patch and turning it off/on. Of course if you WANT the LFOs independent you have to hit Key Sync. But the LFOs seem to remember their sync state across patches. So if you had saved a patch with synced LFOs, hit Key Sync on another patch, then go back to the synced LFO patch, the LFOs will no longer be in sync.

I suppose it's smart to remember to sync them again after saving a non-synced patch if global is your default for most patches.
Title: Re: Feature Requests
Post by: guyaguy on June 17, 2018, 11:46:39 AM
I have to add something to my above request... for some reason, today, when I create a program routing an LFO to the cutoff of the hipassfilter FX, it seems to work... result is not bouncing around anymore... I made a few tests with the other mod sources that should work polyphonically and realized, that the "global thing" is actually taken care of regarding the modulation of FX parameters... also the LFOs.

When I about when the LFO bounced around the last time, I can remember that it shifted every 8 keypresses... so I assume that it happened as part of the edit buffer dump bug, that is currently on their bugfix list (you can read about this in my dedicated topic).

So I'll say that there is no need to implement a global LFO anyway... at least not for the FX section.

I know others would want a global LFO for the filter... and if DSI has stated that a global LFO is not going to be made for the LFO's, then maybe a request for a Lowpass and even bandpass filter in the FX section is an alternative for those who want to have a global modulateable lowpass filter... if it works with the hipass filter it should work with any filter FX.
Right, only one LFO is needed for an effect since effects are post-VCA, so there's no out-of-sync state when using LFOs on the effects section. However the LFO modulating the effects section can be out of sync with the others. The reason it's a phenomenon at all (I'll leave it up to you to decide whether it's a feature or an issue!) with modulating the actual synth voice is that each voice has its own LFOs for a total of 32 on the 8 voice or 64 on the 16 voice. But the workaround above works for modulating the LPF with synced LFOs.
Title: Re: Feature Requests
Post by: RonGerrist on June 23, 2018, 10:30:26 AM
I really love the REV 2 but there is one thing that is really frustrating; how easy it it to lose you changes.
What would be nice is a (like a software application on your computer would do) warning that you are going to lose you data before it actually switches to the next patch.
Title: Re: Feature Requests
Post by: roberth909 on June 29, 2018, 08:39:09 PM
I want a Layer A/B Mix setting in the Misc Params, that would default to 50, equal amounts of both, so that there is more control over the volume of Stacks and Splits, with 0 all Layer A, 99 all Layer B.

Oh, maybe you can just do that using the Amp Envelope Amount.
Title: Re: Feature Requests
Post by: RonGerrist on June 29, 2018, 11:41:49 PM
I want a Layer A/B Mix setting in the Misc Params, that would default to 50, equal amounts of both, so that there is more control over the volume of Stacks and Splits, with 0 all Layer A, 99 all Layer B.

Oh, maybe you can just do that using the Amp Envelope Amount.

You can set their individual levels already. But like you idea better.
Title: Re: Feature Requests
Post by: Djinn on June 29, 2018, 11:49:02 PM
Sorry i Havnt read the thread in full so dont know if this has already been mention but i would like to see higher filter resolution to improve the stepping
Title: Re: Feature Requests
Post by: LoboLives on June 30, 2018, 12:10:33 AM
I know that a Beat Sync feature is set to be added to the REV2, OB6 And P6 But I wonder what the ETA would be for that. I also wonder if it will be a complete and final OS update with some simple features like transposing the sequencer without holding down Record or sequencer’s root note determined by the actual note you press not the key interval. Perhaps on the OB6 and P6 the ability to turn oscillator note quantization on and off in Global settings.
Title: Re: Feature Requests
Post by: guyaguy on June 30, 2018, 09:29:30 AM
I want a Layer A/B Mix setting in the Misc Params, that would default to 50, equal amounts of both, so that there is more control over the volume of Stacks and Splits, with 0 all Layer A, 99 all Layer B.

Oh, maybe you can just do that using the Amp Envelope Amount.

You can set their individual levels already. But like you idea better.
Yep each Layer has its own Program Level under Misc Param. Good enough for me.
Title: Re: Feature Requests
Post by: Djinn on July 01, 2018, 05:47:25 AM
Imdividual osc volumes would be great for reigning in those wild volume fluctuations and horrible clipping peaks
Title: Re: Feature Requests
Post by: Robot Heart on July 02, 2018, 10:00:13 AM
Djinn-

Individual osc levels are not possible without redesigning the hardware. The IC responsible for the oscillators has osc mix only. It would either require a new IC design or to use twice as many ICs to achieve this feature, and then you'd be wasting an extra filter and VCA per voice. Not to mention using another 8 - 16 ICs would add quite a lot to the build cost for that one feature.

Regarding the filter stepping, it's implemented that way so you can tune the filter in semitones. If you want a smoother response you can turn the knob faster or assign the filter to a modulator that has much higher resolution, either an LFO or the mod wheel.
Title: Re: Feature Requests
Post by: Djinn on July 02, 2018, 10:12:42 AM
Hi robot heart
Thankyou for taking the time to explain those points so clearly.
I will definitely try the mod wheel for filter later on tonight
Thanks
Title: Re: Feature Requests
Post by: Razmo on July 02, 2018, 11:59:06 AM
This is a common thing with many synths... I bet it has to do with MIDI CCs (Modwheel in this case) being only 7 bits wide, allowing only 128 discrete steps... I know that the original MIDI specification had two CC's for many standard CCs so that you could do 14bit CC resolution, but for some reason most manufacturers obviously used only a single CC for sending out (and receiving) Modwheel data thru MIDI, sealing the "standard" as 7bit for the Modwheel using MIDI... if a keyboard would begin sending two CC's for Modwheel data to get a higher resolution, it would probably make other connected devices (via MIDI) behave strangely since the second CC might be used for other stuff in the attached device, ruining compatibility... it's just one of those signs that the MIDI specification is more than 40 years old.

It would be cool though, if manufacturers began making support for using CCs in 14bit ... it could simply be a global switch to turn on 14bit mode... the global switch could also simply let any movement of the Modwheel send out NRPNs instead which are also 14bit... that would fix the problem with the Modwheel resolution at least...
Title: Re: Feature Requests
Post by: Razmo on July 02, 2018, 12:02:41 PM
Djinn-

Individual osc levels are not possible without redesigning the hardware. The IC responsible for the oscillators has osc mix only. It would either require a new IC design or to use twice as many ICs to achieve this feature, and then you'd be wasting an extra filter and VCA per voice. Not to mention using another 8 - 16 ICs would add quite a lot to the build cost for that one feature.

Regarding the filter stepping, it's implemented that way so you can tune the filter in semitones. If you want a smoother response you can turn the knob faster or assign the filter to a modulator that has much higher resolution, either an LFO or the mod wheel.

Why would it help assigning it to the Modwheel, if you also want to record the Modwheel's movement via MIDI? ... MIDI would only truncate the higher resolution down to 7 bit, making MIDI playback step as usual...
Title: Re: Feature Requests
Post by: Robot Heart on July 02, 2018, 02:56:05 PM
The mod wheel runs through the mod matrix, which has higher resolution processing than the pot.
Title: Re: Feature Requests
Post by: Razmo on July 02, 2018, 03:32:46 PM
The mod wheel runs through the mod matrix, which has higher resolution processing than the pot.

Sure... but still, how would you automate the modwheel's and mod matrix's high resolution from a DAW, when the REV2 is only sending 7bit CCs to the DAW when moving the modwheel? ... for people using the REV2 live, it'll work fine, but anyone wanting to record the movements via MIDI will suffer the 7bit quantization... this is not only DSI instruments that does this...
Title: Re: Feature Requests
Post by: Robot Heart on July 02, 2018, 03:56:23 PM
Through the mod matrix you have control of the curve, essentially. Since you can assign larger or smaller amounts of modulation, DC offset, and/or stack mod slots it's not a one-to-one comparison when using the mod matrix to control a parameter vs the parameter's dedicated pot.
Title: Re: Feature Requests
Post by: Razmo on July 02, 2018, 04:03:54 PM
Through the mod matrix you have control of the curve, essentially. Since you can assign larger or smaller amounts of modulation, DC offset, and/or stack mod slots it's not a one-to-one comparison when using the mod matrix to control a parameter vs the parameter's dedicated pot.

Lets say that in the Modmatrix you assign Modwheel to Filter cutoff directly... when you move the modwheel, I understand that the wheel has a greater than 127 steps (higher resolution) that makes the movement smooth without steps... but the MIDi CC (CC#1) sent out of the REV2 is 7bit... when the DAW is then sending this recorded movement back to the REV2, how will the playback then have more than 128 steps? ... do you use some kind of interpolation of the incoming CC values to sort of "reconstruct" the missing resolution?
Title: Re: Feature Requests
Post by: Robot Heart on July 02, 2018, 04:39:41 PM
Correct, there are only 128 steps via MIDI CC; we don't interpolate the incoming CC values to reconstruct the missing resolution. But if you've manipulated the target parameter in the mod matrix using the ideas I previously mentioned you'd still be able to get a different result than the standard 0 - 127 values from controlling it directly.
Title: Re: Feature Requests
Post by: Razmo on July 03, 2018, 12:26:21 AM
Correct, there are only 128 steps via MIDI CC; we don't interpolate the incoming CC values to reconstruct the missing resolution. But if you've manipulated the target parameter in the mod matrix using the ideas I previously mentioned you'd still be able to get a different result than the standard 0 - 127 values from controlling it directly.

As far as I know, the MIDI specification was made with 14bit CCs in mind, but no manufacturers seem to implement it... I have only seen MOOG include the option to switch 14bit CCs on... MIDI specification has 14bit for modwheel using CCS 1 and 33... Many CCs in the first 32 range has an msb if you add the value 32 to it... It could also be done if the modwheel would send NRPNs instead...


Title: Re: Feature Requests
Post by: Djinn on July 03, 2018, 03:47:11 AM
Im not that technically minded but im pretty sure novation uses two cc s
To provide higher resolution i honestly would prefer it on the actual filter pot itself.
Just saying
Title: Re: Feature Requests
Post by: Razmo on July 03, 2018, 04:26:33 AM
Im not that technically minded but im pretty sure novation uses two cc s
To provide higher resolution i honestly would prefer it on the actual filter pot itself.
Just saying

The question is then, how big a resolution the pots have... that depend on the DAC which is probably some internal ADCs on either a microcontroller or the CPU... DSI have been using Microchip PICs earlier on, and I know that many of these are max 10bit resolution, so even if it's better than the 128 steps, 10bit "only" allow for 1024 discrete steps.

I'm not so sure though, that I'd want a greater resolution on the Cutoff knob because it's actually rather convenient that it's set in semitone steps... i use the self resonating filter for A LOT of presets, where the playability of the filter chromatically is important... it would take too long time to set the cutoff right if the resolution is bigger...

and also, the greater the resolution, the less movement it takes to change the values... you'd practically end up with a knob that might change values on it's own because the miniscule steps may change with small vibrations, where it will stand switching between two adjacent values constantly... setting precise values will become a nightmare with a 1024 resolution.

Besides, the MIDI SysEx dump is already set up for a value from 0 to 164 for the cutoff... it uses a single byte for this value, if you were to change the knobs resolution, you'd have to change the SysEx dump format as well, and make additional code to figure out which version of the dump it's receiving, otherwise it would not be backwards compatible with earlier formats.

So maybe if it is not obvious, it would require quite a few changes to create this feature... so I would not put my hopes up for it :)
Title: Re: Feature Requests
Post by: Razmo on July 03, 2018, 05:05:09 AM
I have a few feature requests that I've come up with during my latest sound design adventure:

1. Bit Reduction FX (parameter1: bit depth, parameter2: sample rate)
2. Band Pass Filter FX (parameter1: frequency, parameter2: resonance)
3. Some sort of porting of the Prophet X's longer reverbs if possible
4. Static versions of the Phaser & Flanger, where the rate parameter and integrated LFO is replaced with a static value you can modulate from the modmatrix instead.
5. A slew parameter for the LFOs.
6. Bipolar versions of the sawtooth and square LFO waveforms.
7. at least two configurable MIDI CC#s added to the modmatrix sources for external MIDI control (CC#s set in global menu).
8. Formant filter FXs

...and basically any other added FX would be welcome, as the FX section is one of the things that really sets the REV2 apart from the Prophet 8... any FX that would mangle the sound would be welcome.
Title: Re: Feature Requests
Post by: extempo on July 03, 2018, 10:28:51 AM
We don't have enough DSP horsepower remaining to add additional FX to the Prophet Rev2.
Title: Re: Feature Requests
Post by: Razmo on July 03, 2018, 12:31:47 PM
We don't have enough DSP horsepower remaining to add additional FX to the Prophet Rev2.

I thought that it was a matter of codespace... how can it be a matter of horsepower when you simply change the algorithm!? ... it's not like all FX are running at the same time ?
Title: Re: Feature Requests
Post by: Montyrivers on July 03, 2018, 08:16:39 PM
We don't have enough DSP horsepower remaining to add additional FX to the Prophet Rev2.

I thought that it was a matter of codespace... how can it be a matter of horsepower when you simply change the algorithm!? ... it's not like all FX are running at the same time ?

probably because all the existing effects are loaded into RAM or reserve a certain amount of system resources to be recalled instantly every time you power on the Rev2.  If I had to guess.
Title: Re: Feature Requests
Post by: latoxine on July 03, 2018, 11:33:50 PM
God...


I know ( I'm sure ) already asked here but...

Why no midi sequancer  transmission ?! Why ?

has someone ever had an answer for that ?
Title: Re: Feature Requests
Post by: Razmo on July 04, 2018, 01:52:05 AM
We don't have enough DSP horsepower remaining to add additional FX to the Prophet Rev2.

I thought that it was a matter of codespace... how can it be a matter of horsepower when you simply change the algorithm!? ... it's not like all FX are running at the same time ?

probably because all the existing effects are loaded into RAM or reserve a certain amount of system resources to be recalled instantly every time you power on the Rev2.  If I had to guess.

Sure... but then it's not horsepower that is the problem, but codespace/memory... but it really does not matter anyway... if they cannot put in more FX, then there is no reason to wish for them anymore.
Title: Re: Feature Requests
Post by: Razmo on July 04, 2018, 02:24:39 AM
I would really like to see the sustain pedal input as a modulation source, and a global parameter added to set the sustain input's function, just like with the expression pedal, so that I can switch other parameters on/off (0/127 CC value) in the same way as the Hold function... if the same could be done with the Sequencer input it would be even nicer.

Also, instead of dedicated slew parameters for the LFO's as I wrote further up, maybe a mod source and destination named "Slew" could be even better... where you route a mod source to the "Slew Input" destination, and then after this you route the "Slew Output" source to whatever you want... this way the slew function could be used for any source and destination. The amount sent to the "Slew input" would of course be the slew rate.

I'd like to see some way of calibrating the Pedal/CV input... My newly bought Moog EP-3 seems to switch between 0 and 1 values as the lowest value... when the pedal reach minimum value it stops at either 1 or 0... I'm not sure if this is the pedal, or if it's the REV2 doing this, but if a calibration routine could fix this, it would be very welcome... with many parameters, this 0 or 1 is not a big deal, but if routed to pitch, it makes quite a big difference.
Title: Re: Feature Requests
Post by: RonGerrist on July 06, 2018, 05:44:24 AM
I'm not sure that has been discussed already. I would like to choose how voice are distributed in split mode. I've had some synths for which you could have 2/4 and 4/2. As I have the Rev 2 8voice (will upgrade to 16 very soon) I would like to have 1 or 2 for the left and the rest for the right hand side.

I think 2/6, 4/4, 6/2 for 8 voice and 2/14, 4/12, 6/10, 8/8, 10/6, 12/4 and (you guessed it right) 14/2 for the 16 voice, is not that much to ask for.
Title: Re: Feature Requests
Post by: Razmo on July 06, 2018, 08:08:17 AM
I'm not sure that has been discussed already. I would like to choose how voice are distributed in split mode. I've had some synths for which you could have 2/4 and 4/2. As I have the Rev 2 8voice (will upgrade to 16 very soon) I would like to have 1 or 2 for the left and the rest for the right hand side.

I think 2/6, 4/4, 6/2 for 8 voice and 2/14, 4/12, 6/10, 8/8, 10/6, 12/4 and (you guessed it right) 14/2 for the 16 voice, is not that much to ask for.

If I'm right, this is not possible because of the hardware... the more I look at the REV2, it seems like you should see the synth as two independant 8-voice synths... one for each layer... when being in 16voice mode (only using layer A), I bet that layer A is automatically copied to Layer B so their sounds are exactly the same, and then an internal kind of "Polychain" method is used so that it seems like you have one synth with 16 voices.

If this is correct, then the two layers are hardwired each to their own with their own FX slot... thus it would be impossible to use any voices from one layer, on the other layer, as they are hardwired to the given layer.

If I'm not correct on this, DSI may correct me... but I'm pretty certain this is what is going on... and if I'm not mistaking, I bet this is the same for both Prophet 12 and Prophet X as well.

The reason I believe that the sound on Layer A is normally copied to Layer B on a preset using only layer A is, that the edit buffer dump bug that I've found earlier, seems to forget to copy the layer from A to B when it receives a dump that should be in 16voice mode... when this happen, the 16 voices that will cycle have the first 8 keystrokes being the right sound, but the next 8 in the cycle is whatever is stored on layer B of the dump... so if you say; dump a preset that use only layer A, and layer B just contain the "basic Preset B" sound, then the first 8 keypresses gives the intended sound, but the next 8 gives you the "Basic Preset B" sound... and so on and on and on...
Title: Re: Feature Requests
Post by: RonGerrist on July 06, 2018, 11:43:57 AM
I'm not sure that has been discussed already. I would like to choose how voice are distributed in split mode. I've had some synths for which you could have 2/4 and 4/2. As I have the Rev 2 8voice (will upgrade to 16 very soon) I would like to have 1 or 2 for the left and the rest for the right hand side.

I think 2/6, 4/4, 6/2 for 8 voice and 2/14, 4/12, 6/10, 8/8, 10/6, 12/4 and (you guessed it right) 14/2 for the 16 voice, is not that much to ask for.

If I'm right, this is not possible because of the hardware... the more I look at the REV2, it seems like you should see the synth as two independant 8-voice synths... one for each layer... when being in 16voice mode (only using layer A), I bet that layer A is automatically copied to Layer B so their sounds are exactly the same, and then an internal kind of "Polychain" method is used so that it seems like you have one synth with 16 voices.

If this is correct, then the two layers are hardwired each to their own with their own FX slot... thus it would be impossible to use any voices from one layer, on the other layer, as they are hardwired to the given layer.

If I'm not correct on this, DSI may correct me... but I'm pretty certain this is what is going on... and if I'm not mistaking, I bet this is the same for both Prophet 12 and Prophet X as well.

The reason I believe that the sound on Layer A is normally copied to Layer B on a preset using only layer A is, that the edit buffer dump bug that I've found earlier, seems to forget to copy the layer from A to B when it receives a dump that should be in 16voice mode... when this happen, the 16 voices that will cycle have the first 8 keystrokes being the right sound, but the next 8 in the cycle is whatever is stored on layer B of the dump... so if you say; dump a preset that use only layer A, and layer B just contain the "basic Preset B" sound, then the first 8 keypresses gives the intended sound, but the next 8 gives you the "Basic Preset B" sound... and so on and on and on...


That sounds like a plausible explanation. I think that is a flaw. The machine could have even more potential than the beast it already is.
Title: Re: Feature Requests
Post by: LoboLives on July 06, 2018, 04:17:13 PM
I'm not sure that has been discussed already. I would like to choose how voice are distributed in split mode. I've had some synths for which you could have 2/4 and 4/2. As I have the Rev 2 8voice (will upgrade to 16 very soon) I would like to have 1 or 2 for the left and the rest for the right hand side.

I think 2/6, 4/4, 6/2 for 8 voice and 2/14, 4/12, 6/10, 8/8, 10/6, 12/4 and (you guessed it right) 14/2 for the 16 voice, is not that much to ask for.

If I'm right, this is not possible because of the hardware... the more I look at the REV2, it seems like you should see the synth as two independant 8-voice synths... one for each layer... when being in 16voice mode (only using layer A), I bet that layer A is automatically copied to Layer B so their sounds are exactly the same, and then an internal kind of "Polychain" method is used so that it seems like you have one synth with 16 voices.

If this is correct, then the two layers are hardwired each to their own with their own FX slot... thus it would be impossible to use any voices from one layer, on the other layer, as they are hardwired to the given layer.

If I'm not correct on this, DSI may correct me... but I'm pretty certain this is what is going on... and if I'm not mistaking, I bet this is the same for both Prophet 12 and Prophet X as well.

The reason I believe that the sound on Layer A is normally copied to Layer B on a preset using only layer A is, that the edit buffer dump bug that I've found earlier, seems to forget to copy the layer from A to B when it receives a dump that should be in 16voice mode... when this happen, the 16 voices that will cycle have the first 8 keystrokes being the right sound, but the next 8 in the cycle is whatever is stored on layer B of the dump... so if you say; dump a preset that use only layer A, and layer B just contain the "basic Preset B" sound, then the first 8 keypresses gives the intended sound, but the next 8 gives you the "Basic Preset B" sound... and so on and on and on...


That sounds like a plausible explanation. I think that is a flaw. The machine could have even more potential than the beast it already is.

In Paul Dither's interview with Dave he spoke about multitimbrality...perhaps if we ever do see another synth with more than two engines we might see voice allocation.
Title: Re: Feature Requests
Post by: LoboLives on July 06, 2018, 04:19:17 PM
God...


I know ( I'm sure ) already asked here but...

Why no midi sequancer  transmission ?! Why ?

has someone ever had an answer for that ?

It's been that way for a while. Dave is a creature of habit and since it wasn't a function on the original MIDI development he just never incorporated it into his synths. I think it's true as well for the arpeggiator.

Until we see an update...external midi sequencers are the way to go for now. Be they hardware or software.
Title: Re: Feature Requests
Post by: Quatschmacher on July 06, 2018, 04:49:30 PM
God...


I know ( I'm sure ) already asked here but...

Why no midi sequancer  transmission ?! Why ?

has someone ever had an answer for that ?

Does this mean it is currently impossible to use the Rev 2’s sequencer to control a Prophet 12 (which has no sequencer)?

Is this also the case with the Pro 2’s sequencer?
Title: Re: Feature Requests
Post by: LoboLives on July 06, 2018, 11:09:42 PM
God...


I know ( I'm sure ) already asked here but...

Why no midi sequancer  transmission ?! Why ?

has someone ever had an answer for that ?

Does this mean it is currently impossible to use the Rev 2’s sequencer to control a Prophet 12 (which has no sequencer)?

Is this also the case with the Pro 2’s sequencer?

REV2's sequencer can't control the Prophet 12 but the Pro 2's sequencer can.
Title: Re: Feature Requests
Post by: flocked on July 07, 2018, 04:19:25 AM
I would love to be able use the keyboard as master keyboard. The current "local control" setting "deactivates" both the keyboard and knobs. I want the knobs to still affect the synth engine, while using the keyboard as master keyboard for my sequencer (which controls/plays all my synths including the prophet).

"Local control keyboard only" would be nice. is this something that would be technically possible?

EDIT: I just realize that this got requested quite often. Please add it :))
Title: Re: Feature Requests
Post by: Quatschmacher on July 07, 2018, 08:20:07 AM
God...


I know ( I'm sure ) already asked here but...

Why no midi sequancer  transmission ?! Why ?

has someone ever had an answer for that ?

Does this mean it is currently impossible to use the Rev 2’s sequencer to control a Prophet 12 (which has no sequencer)?

Is this also the case with the Pro 2’s sequencer?

REV2's sequencer can't control the Prophet 12 but the Pro 2's sequencer can.

Thanks.
Title: Re: Feature Requests
Post by: Razmo on July 14, 2018, 04:33:00 AM
I have a relatively simple feature request:

I would like that the BPM parameter was available in the Modulation Matrix as a destination, so that I can control the speed of a poly/gated sequence in real time from a physical control... the BPM encoder is not good enough for this because it's hard to control performance wise.
Title: Re: Feature Requests
Post by: musicmaker on July 24, 2018, 10:43:05 PM
the 16 voices that will cycle have the first 8 keystrokes being the right sound, but the next 8 in the cycle is
whatever is stored on layer B of the dump.


DSI says this cycling is intended behavior. It seems there is no real 16 voices mode in the REV2, but more alike "2x8".
You can notice this using both A and B outputs that the 1st 8 voices played go to Out A and next 8 voices played to out B. I put this down as a feature request in globals or misc parameters to force all voices to out A or B when both outputs plugged in so that I don't have to physically remove the plugs when I want all voices on one output, but that seems that is not going to happen since it seems hardwired. An option could be to have a Globals/Misc setting to force all 16 sounds to  follow" A only", "B only" layer settings and "default" for the way it currently behaves  to workaround if there is a  bug like you mentioned.
Title: Re: Feature Requests
Post by: MPM on July 24, 2018, 11:05:06 PM
Sequencer note retrig, like 3 x 1/16 repeat in a step.

So I don’t have to shorten a 64 step by reving up the BPM to get AWESOME Bass lines.
Title: Re: Feature Requests
Post by: Razmo on July 25, 2018, 11:56:44 PM
the 16 voices that will cycle have the first 8 keystrokes being the right sound, but the next 8 in the cycle is
whatever is stored on layer B of the dump.


DSI says this cycling is intended behavior. It seems there is no real 16 voices mode in the REV2, but more alike "2x8".
You can notice this using both A and B outputs that the 1st 8 voices played go to Out A and next 8 voices played to out B. I put this down as a feature request in globals or misc parameters to force all voices to out A or B when both outputs plugged in so that I don't have to physically remove the plugs when I want all voices on one output, but that seems that is not going to happen since it seems hardwired. An option could be to have a Globals/Misc setting to force all 16 sounds to  follow" A only", "B only" layer settings and "default" for the way it currently behaves  to workaround if there is a  bug like you mentioned.

Yes, it's normal behavior, but what I'm talking about is the edit buffer dump bug ... if you change preset on the front panel of the REV2, then Layer A is copied to layer B, if it is a 16 voice program, so that you do not hear that it's actually two daisy chained synths on the inside (except if you're having both stereo outputs connected which gives it away by this bouncing)... but if the REV2 recieve an Edit Buffer Dump SysEx message, and the program is a single layer (16 voice) sound, then it does NOT copy Layer A to Layer B, which result in what i described; first 8 sounds being right (playing from layer A), but the next 8 plays wrong (Layer B) because it has not been properly initialized by copying layer A to layer B somehow.

So in general, it is already following Layer A's data... you cannot circumvent the bouncing in any way, but the Edit Buffer Dump bug is certainly fixable... Following Layer A in 16 voice modes is what it is already doing by copying Layer A to B on initialization, so I do not think that an option in the globals would be of much help... the bouncing on the two stereo outs will always be there in 16 voice modes as long as the B outs are in use, there just is no way around this as it's a hardwired thing, like on any dual timbral synth from DSI.
Title: Re: Feature Requests
Post by: chapelier fou on July 26, 2018, 05:04:54 AM
I'd love to have an option for the Gated Seq to be "quantized" to a time value. So the sequences waits for the next tick (value specified) to happen.
That raises the question : what about the first note ? I'd love an option for all the sequencers to be quantized to a clock as well.
Title: Re: Feature Requests
Post by: chapelier fou on July 27, 2018, 04:02:48 AM
I'd love an option for the gated sequencer to not add another voice when you hit a note that is already held.
Title: Re: Feature Requests
Post by: chapelier fou on July 30, 2018, 06:05:55 AM
Automatic Clock synchro would be awesome.
I'm so tired of changing this settings in the Global menu every time I stop my DAW and want to play !
Title: Re: Feature Requests
Post by: chapelier fou on July 31, 2018, 12:18:13 AM
I'd love a quick way to recall the program at its saved state. Tweak, mess it up, then recall it.
A button combo, like hold Global and press Split A/B would be perfect.
Elektron MD users will know what I'm talking about !
Title: Re: Feature Requests
Post by: chapelier fou on July 31, 2018, 11:57:00 AM
Another that would be incredible for the Gated Sequencer : ability to force to a scale when using the oscillator pitch as a destination. This thing can make so beautiful arpeggios. But most of the time I limit myself to fifths and octaves otherwise it can be quickly dissonant when more notes are held.
Thoughts ?
Title: Re: Feature Requests
Post by: Sleep of Reason on August 02, 2018, 03:41:34 PM
Is there any hardware limitation for why the hold button has to play the exact same role as sustain? Can an option for the ability to reset upon changing a note/chords be implemented for the hold button?

Also, is it possible to have an option to enter a sequence for both layers to avoid those repeated notes in the background without having to replay the sequence again? I know the REV2 sequencer requires notes to be entered at all times, so it would make it less noticeably janky to have this option.
Title: Re: Feature Requests
Post by: Djinn on August 03, 2018, 04:18:05 AM
I would like to request 14 bit resolution update for cutoff rez etc switchable to 7bit  in global would be great
Title: Re: Feature Requests
Post by: latoxine on August 04, 2018, 01:05:00 AM

Also, is it possible to have an option to enter a sequence for both layers to avoid those repeated notes in the background without having to replay the sequence again? I know the REV2 sequencer requires notes to be entered at all times, so it would make it less noticeably janky to have this option.

+1
Title: Re: Feature Requests
Post by: Indigo V. on August 04, 2018, 05:43:06 PM
I would love to be able to define global offset values to specific parameters PER VOICE like:

- Default 50% Pulsewidth (very annoying on Rev2)
- Filter Cutoff (specifically HP filters on Prophet 6 and Propet 12)
- Volume & Pan (specifially rev2 and Prophet 12)

Thanks for considering  :)

Title: Re: Feature Requests
Post by: aaronsimsg on August 06, 2018, 04:16:48 AM
Not sure if this feature is available after an update, but I hope to be able to copy and paste sequences from 1 layer to another e.g. U1P1A to U4P100B. I know that copying layers between programs has been enhanced; what about sequences only?
Title: Re: Feature Requests
Post by: Razmo on August 06, 2018, 04:37:55 AM

Also, is it possible to have an option to enter a sequence for both layers to avoid those repeated notes in the background without having to replay the sequence again? I know the REV2 sequencer requires notes to be entered at all times, so it would make it less noticeably janky to have this option.

+1

Many have requested this by now, but the response from DSI has been kind of disappointing... they just tell you to copy the sequence from one layer to another... even though that is a tedious process to have to do every time you record something with a stacked program... I'll opt for such a feature too... the more of you who request it, the bigger the chance they may reconsider...
Title: Re: Feature Requests
Post by: Razmo on August 06, 2018, 04:41:55 AM
Not sure if this feature is available after an update, but I hope to be able to copy and paste sequences from 1 layer to another e.g. U1P1A to U4P100B. I know that copying layers between programs has been enhanced; what about sequences only?

Hit both split and stack buttons simultaneously... now turn the parameter knob until you find the copy/swap functions for the sequences... they are there ;)

unfortunately that only works within the same program... the feature where you can load any layer into any program layer is not available for sequences only... unfortunately.
Title: Re: Feature Requests
Post by: aaronsimsg on August 06, 2018, 09:38:56 PM
Yeah it works within the same program. Would love to see it enabled for copy/paste sequences across different programs :)
Title: Re: Feature Requests
Post by: RonGerrist on August 09, 2018, 12:05:00 AM
Now that we have the sequencer sending out midi notes, I would like some more.
The gated sequencer sending out notes and midi control messages for the destinations assigned to the tracks.

Something else I would like to see is ratcheting. And while we're on it Roland 100m M185 style of sequencer. I use the HY-SeqCollection (it has a m185 style sequencer) and it is super awesome. You can fiddle with it all night.
Title: Re: Feature Requests
Post by: eXode on August 10, 2018, 12:18:12 PM
Minor request, but would be useful to be able to set at least one of the LFOs to global/mono. I know there's key sync, but it's not quite the same thing, imho. :)
Title: Re: Feature Requests
Post by: LoboLives on August 10, 2018, 05:47:39 PM
I’m thrilled that the sequencer now has beat Sync and can send midi notes out....but it still can only be transposed by holding down the record button? Is it just not possible to implement this?
Title: Re: Feature Requests
Post by: brinnandeskepp on August 19, 2018, 07:32:17 AM
I would like to request 14 bit resolution update for cutoff rez etc switchable to 7bit  in global would be great
Full res NRPN controls for ALL the front panel pots as an option in globals, please. Any 'stepping' on these are a hinderance to the music I want to write and perform on this thing.
Title: Re: Feature Requests
Post by: guyaguy on August 19, 2018, 01:39:19 PM
Another that would be incredible for the Gated Sequencer : ability to force to a scale when using the oscillator pitch as a destination. This thing can make so beautiful arpeggios. But most of the time I limit myself to fifths and octaves otherwise it can be quickly dissonant when more notes are held.
Thoughts ?
I think you might want to use the arpeggiator rather than the gated sequencer. The gated sequencer will play exactly the notes you program with the ability to shift the key by playing a different note. If you want other notes to play simultaneously you can either program them in another seq slot or on another Layer.
Title: Re: Feature Requests
Post by: eXode on August 21, 2018, 09:08:05 AM
These features could be implemented in several DSI products (where applicable):

#1 Global LFO mode, alternatively "Free Sync". I miss being able to set the LFO to global operation, i.e. one LFO for all voices. If it's not possible to make an option to have one of the LFOs operate as a global LFO, an alternative could be something called "Free sync" (as opposed to Key Sync), basically that the LFOs are free running, but in sync with each other.

#2 Random (per voice) modulation source. Basically a random source in the mod matrix where each voice/note gets a new random value (bipolar). I've seen this feature in some soft synths, and it's great for getting some natural detuning between voices in a chord for an example, but can also be used for i.e. envelope times, etc to get some more variation between voices. This could also be super cool if it could be used in conjunction with unison if applied to i.e. filter cutoff with a high resonance setting (each voice getting it's own random cutoff value).

#3 Clock sync option for modulation effects. The Phaser and Flanger effects in particular could benefit from having a clock sync option.

#4 Frequency and time values on LFOs and EGs. When not in CLK SYNC mode, the LFOs would show the actual Hz rate, and the EGs would show the time in ms to sec.
Title: Re: Feature Requests
Post by: roberth909 on August 21, 2018, 06:40:41 PM
I just want facilities to get the oscillator pulse widths very finely calibrated, by ear, since the calibration routine seems to have limited capabilities.  The rest of it is plenty of analog synth, for me.
Title: Re: Feature Requests
Post by: skipgilles on August 23, 2018, 06:44:43 AM
A pretty simple suggestion: It would be very useful to be able to let A be active at the UPPER part of the keyboard and B be the LOWER part of the keyboard.

This would offer two great utilities:
1) Be able to edit the upper layer directly after selecting a preset. Now you have to press EDIT B to do so. (I often have a base patch on the left, which I don't want to tweak while playing; I do want to tweak my upper timbral patch)
2) Be able to have a typical lead sound in a preset where split is not activated, to which you can add the lower layer for your left hand (Layer B) by simply pressing SPLIT. (So I can save a nice preset with and without basepart easily in one preset)

Currently, only the opposite is possible, where you can only directly edit the lower timbral patch and where only the upper timbral layer can be added or removed from the preset.

Title: Re: Feature Requests
Post by: Kasimir Effekt on August 30, 2018, 04:23:10 AM
Regarding additional features, I think the following suggestions would be useful:

- Much important for me: poly seq should keep running when you enable or disable split or stack. Otherwise there is no possibility to add an additional sound to a running sequence.

- If possible, add new mod-destinations "Osc1 / Osc2 level" (this was even mentioned in an earlier version of the manual)

- Please implement the ability to octave Osc 1 & 2 without scrolling through semitones (useful for programming). Furthermore this would allow you to octave only one layer when playing split sounds (which is not possible with the transpose buttons).

- It would be nice to have clk sync for modulation effects and Env3 looping


One more question: Anyone knows if there's a way to set the duration of the note steps in the gated sequencer? In the polysequencer as well, you only have the choice between a (for my taste) too short step-duration and "tie".
Title: Re: Feature Requests
Post by: psionic11 on September 06, 2018, 07:12:39 PM
Two requests on my wishlist for the Rev2:

1) Ability to *transmit* on 2 channels when in split mode.  Master MIDI controllers need to transmit, only modules need receive only.

2) MIDI merge (with or without clock) on DIN MIDI to USB MIDI, and vice versa.  This would grant a master controller Rev2 many modern features:
-- play (via USB) Mainstage / DAW / VST / iPad from Rev2 and/or other DIN-connected MIDI keyboards
-- allow (via USB) Mainstage / DAW / VST / iPad to sequence / program change the Rev2 and any other downstream keyboards, drum machines, guitar multiFX pedalboard, etc

Currently one must choose either the USB world or the DIN world, but not both.  Nary shall the two meet without merge capability.
Title: Re: Feature Requests
Post by: Syngenor on September 06, 2018, 11:21:43 PM
I would like to second psionic11’s request for a 2 channel transmit.
Title: Re: Feature Requests
Post by: Razmo on September 07, 2018, 12:58:17 AM
Regarding additional features, I think the following suggestions would be useful:

- Much important for me: poly seq should keep running when you enable or disable split or stack. Otherwise there is no possibility to add an additional sound to a running sequence.

- If possible, add new mod-destinations "Osc1 / Osc2 level" (this was even mentioned in an earlier version of the manual)

- Please implement the ability to octave Osc 1 & 2 without scrolling through semitones (useful for programming). Furthermore this would allow you to octave only one layer when playing split sounds (which is not possible with the transpose buttons).

- It would be nice to have clk sync for modulation effects and Env3 looping


One more question: Anyone knows if there's a way to set the duration of the note steps in the gated sequencer? In the polysequencer as well, you only have the choice between a (for my taste) too short step-duration and "tie".

The separate Osc volume will not happen... it's the way the Curtis chip works internally... it's set with a MIX parameter, and if I'm remembering right, it's a CV input that control the mix... so it's impossible to create, and if you look at DSI's hybrid synths that has digital oscillators you'll also see that they do have separate oscillator volumes... simply because it's possible to control it in the oscillator DSP... any synth from DSI that use the Curtis "Synth in a chip" will have this Mix parameter... no way around it :)
Title: Re: Feature Requests
Post by: ffx on September 07, 2018, 03:56:12 AM
Hi,

I am very impressed by the Prophet REV-2 (1.1.4.5) and the sound. So I would like to suggest some feature and workflow ideas:

- The LFOs do not seem to be able to run "globally", non-restarting, so really "free". Seems to be kind of dependent on the playing voice? Can you add a real global-free running mode, too? Or did I something wrong?

- It would be awesome, if the glide would work for polyphonic mode, too! So simply the notes in release phase are pitched to the new playing note. Lot of synths have that, esp. VSTis.

- I wish the unison mode could play polyphonic, too! So if you set the unison mode to 2x, on the 8-voice model, there could play 3 additional notes...

- An inertia value for each OSC FREQ parameter would be great to SYNCed sounds, so you won't hear a stepping while manually modulating the OSC1 FREQ. Or a range parameter for OSC FINE TUNE, so you can actually expand the finetune frequency range EDIT: Ok found that under MISC PARAMS

- Can you add a bit more control to the noise parameter? Like some prefiltered/BPed (maybe not possible) noise types? Maybe that is not possible due hardware limitations?

- If you moved a knob of a section, let's say the "OSC1 FREQ" of the OSCILLATORS section, the display could show instead the section name additionally like:

OSCILLATORS
Osc 1 Freq
D#3

Then the PARAMETER and VALUE knobs could give access to additional, not directly accessible parameters of that section, without pressing MISC PARAMS, e.g. OSC 1 FREQ INERTIA. So it would maybe feel like the natural extension menu of the used section.

- A layer finetune parameter, so you could slightly detune the 2nd layer.

- The HP filter effect next to the other, main effect. I guess this section works digitally?

Thanks for consideration!
Title: Re: Feature Requests
Post by: Robot Heart on September 07, 2018, 03:20:21 PM
Two requests on my wishlist for the Rev2:

1) Ability to *transmit* on 2 channels when in split mode.  Master MIDI controllers need to transmit, only modules need receive only.

Already possible. Use Multi mode for this.
Title: Re: Feature Requests
Post by: eXode on September 08, 2018, 01:22:16 AM
- The HP filter effect next to the other, main effect. I guess this section works digitally?

An additional HP filter, even if it's just a simple non-resonant 6dB / 1 pole HPF (a'la Juno/Jupiter, iirc) that you could use along side the main effect would be very useful.

I would also like to see the unison voice selection work for polyphonic sounds, so you could have a 4 voice unison, 4 note polyphonic sound (for an example), if you own the 16 voice REV 2.
Title: Re: Feature Requests
Post by: psionic11 on September 09, 2018, 06:25:26 AM
Two requests on my wishlist for the Rev2:

1) Ability to *transmit* on 2 channels when in split mode.  Master MIDI controllers need to transmit, only modules need receive only.

Already possible. Use Multi mode for this.

I confirmed that the Rev2 transmits on 2 consecutive channels, which is exactly what I expected and needed.  Thanks!
Title: Re: Feature Requests
Post by: guyaguy on September 09, 2018, 08:40:50 AM
Regarding additional features, I think the following suggestions would be useful:

- Much important for me: poly seq should keep running when you enable or disable split or stack. Otherwise there is no possibility to add an additional sound to a running sequence.

- If possible, add new mod-destinations "Osc1 / Osc2 level" (this was even mentioned in an earlier version of the manual)

- Please implement the ability to octave Osc 1 & 2 without scrolling through semitones (useful for programming). Furthermore this would allow you to octave only one layer when playing split sounds (which is not possible with the transpose buttons).

- It would be nice to have clk sync for modulation effects and Env3 looping


One more question: Anyone knows if there's a way to set the duration of the note steps in the gated sequencer? In the polysequencer as well, you only have the choice between a (for my taste) too short step-duration and "tie".

The separate Osc volume will not happen... it's the way the Curtis chip works internally... it's set with a MIX parameter, and if I'm remembering right, it's a CV input that control the mix... so it's impossible to create, and if you look at DSI's hybrid synths that has digital oscillators you'll also see that they do have separate oscillator volumes... simply because it's possible to control it in the oscillator DSP... any synth from DSI that use the Curtis "Synth in a chip" will have this Mix parameter... no way around it :)
The Evolver uses a Curtis synth on a chip and has per osc level control.
Title: Re: Feature Requests
Post by: eXode on September 09, 2018, 08:58:00 AM
The Evolver uses a Curtis synth on a chip and has per osc level control.

The evolver uses two curtis chips in a stereo configuration (one DCO per channel), so it's not quite the same.
Title: Re: Feature Requests
Post by: guyaguy on September 09, 2018, 09:43:34 AM
The Evolver uses a Curtis synth on a chip and has per osc level control.

The evolver uses two curtis chips in a stereo configuration (one DCO per channel), so it's not quite the same.
Not being the same was my point: It has individual osc levels! I'm reading between the lines but I'm assuming that the Evolver pulls this off by not utilizing one of the DCOs per chip, which is a bit wasteful on a 4-voice or mono but downright expensive on a 16-voice poly.

https://forum.sequential.com/index.php/topic,1894.msg20858.html#msg20858
Title: Re: Feature Requests
Post by: Razmo on September 09, 2018, 01:44:41 PM
The Evolver uses a Curtis synth on a chip and has per osc level control.

The evolver uses two curtis chips in a stereo configuration (one DCO per channel), so it's not quite the same.
Not being the same was my point: It has individual osc levels! I'm reading between the lines but I'm assuming that the Evolver pulls this off by not utilizing one of the DCOs per chip, which is a bit wasteful on a 4-voice or mono but downright expensive on a 16-voice poly.

https://forum.sequential.com/index.php/topic,1894.msg20858.html#msg20858

I actually thought the same when reading this... that means that the Evolvers could have utilized two analog oscillators and one digital per channel (L/R)... I wonder why Dave did not do that back then... would not have been that many more parameters to add...
Title: Re: Feature Requests
Post by: guyaguy on September 09, 2018, 02:06:52 PM
The Evolver uses a Curtis synth on a chip and has per osc level control.

The evolver uses two curtis chips in a stereo configuration (one DCO per channel), so it's not quite the same.
Not being the same was my point: It has individual osc levels! I'm reading between the lines but I'm assuming that the Evolver pulls this off by not utilizing one of the DCOs per chip, which is a bit wasteful on a 4-voice or mono but downright expensive on a 16-voice poly.

https://forum.sequential.com/index.php/topic,1894.msg20858.html#msg20858

I actually thought the same when reading this... that means that the Evolvers could have utilized two analog oscillators and one digital per channel (L/R)... I wonder why Dave did not do that back then... would not have been that many more parameters to add...
It would have added a couple more rows to the matrix interface of the desktop but probably could have been pulled off more easily on the key versions.: add a couple of buttons for the Analog Osc section, maybe tweak how sync works a bit, and the rest would be software changes. Maybe we'll see that in the PEK Rev2.  ;D
Title: Re: Feature Requests
Post by: chrisqhq on September 12, 2018, 07:14:37 AM
Hi,

I'm very happy with my Rev 2 and I especially enjoy using the sequencer to add rhythmic variations to sounds. Often however it doesn't fit to other elements of my track due to the sparse swing settings under "clock divide".
It would be great if you could add more of them. "No swing", "half" and "full" are useful but it would be fantastic to have more options in between.



Title: Re: Feature Requests
Post by: Razmo on September 12, 2018, 08:55:49 AM
I'd like to see a new form of voice trigger mode... not only for the REV2, but in synthesizers in general that are polyphonic.

The mode I'm thinking about is one that mimics real acoustic instruments that are "polyphonic" like stringed instruments.

With the normal polyphonic voice allocation in polyphonic synths, if you press the same key multiple times, a new voice is allocated for that note, but in acoustic instruments, if you (like on stringed instruments for example) play the same note, it does not double... if you hit the same string twice, that string is in essence "monophonic".

This behavior is impossible to simulate on any polyphonic synth that I know of, simply because they have no voice allocation mode that take this into account.

I think it would be rather straight forward to implement... when a voice is allocated, all you need to do is store that voice's "key number" with it, and if that note comes up again later on, then simply check all voices note allocations, and if one of them has the same note, then allocate that voice instead of a new one...

Another positive result from using such a method is that it will at the same time seem like it gives you more polyphony... if you have a sound with a long release, and in sequence play three notes over and over again, it will use all 16 voices in a round-robin way... with the proposed trigger method, it would only use 3 voices since the respective voices will be retriggered whenever it's stored note value gets another keypress with that same note...
Title: Re: Feature Requests
Post by: Gomjab on September 12, 2018, 12:02:23 PM
I'd like to see a new form of voice trigger mode... not only for the REV2, but in synthesizers in general that are polyphonic.

The mode I'm thinking about is one that mimics real acoustic instruments that are "polyphonic" like stringed instruments.

With the normal polyphonic voice allocation in polyphonic synths, if you press the same key multiple times, a new voice is allocated for that note, but in acoustic instruments, if you (like on stringed instruments for example) play the same note, it does not double... if you hit the same string twice, that string is in essence "monophonic".

This behavior is impossible to simulate on any polyphonic synth that I know of, simply because they have no voice allocation mode that take this into account.

I think the Roland Super Natural engine is the only thing that came close in the Integra 7.  I remember demos of their guitar patch that had modeled behavior similar to that. 
Title: Re: Feature Requests
Post by: psionic11 on September 12, 2018, 07:29:39 PM
I'd like to see a new form of voice trigger mode... not only for the REV2, but in synthesizers in general that are polyphonic.

The mode I'm thinking about is one that mimics real acoustic instruments that are "polyphonic" like stringed instruments.

With the normal polyphonic voice allocation in polyphonic synths, if you press the same key multiple times, a new voice is allocated for that note, but in acoustic instruments, if you (like on stringed instruments for example) play the same note, it does not double... if you hit the same string twice, that string is in essence "monophonic".

This behavior is impossible to simulate on any polyphonic synth that I know of, simply because they have no voice allocation mode that take this into account.

I think the Roland Super Natural engine is the only thing that came close in the Integra 7.  I remember demos of their guitar patch that had modeled behavior similar to that.

I really like the way the Integra SuperNatural Acoustic voices trigger expressive articulations.  It was a big reason to add it to my modest arsenal.  The way their guitars articulate with legato playing and with physical controllers are somewhat similarly executed in Yamaha's Expanded Articulation and Korg's DNC (https://www.youtube.com/watch?v=Ej69-ptRNXI).

From what I'm understanding of Razmo's description, it sounds like poly-chained Slim Phattys and Minitaurs or poly-chained Boog D's utilize this, shall we say, "multi-monophonic" voice allocation.   ;D
 
And doesn't DSI utilize this voice allocation method as well with poly-chained Mophos and Tetras?  Here's a video demonstration (he stops talking and starts playing at the 11 minute mark):

https://www.youtube.com/watch?v=qtjNqCK2dgY
Title: Re: Feature Requests
Post by: Razmo on September 13, 2018, 12:00:42 AM
I'd like to see a new form of voice trigger mode... not only for the REV2, but in synthesizers in general that are polyphonic.

The mode I'm thinking about is one that mimics real acoustic instruments that are "polyphonic" like stringed instruments.

With the normal polyphonic voice allocation in polyphonic synths, if you press the same key multiple times, a new voice is allocated for that note, but in acoustic instruments, if you (like on stringed instruments for example) play the same note, it does not double... if you hit the same string twice, that string is in essence "monophonic".

This behavior is impossible to simulate on any polyphonic synth that I know of, simply because they have no voice allocation mode that take this into account.

I think the Roland Super Natural engine is the only thing that came close in the Integra 7.  I remember demos of their guitar patch that had modeled behavior similar to that.

I really like the way the Integra SuperNatural Acoustic voices trigger expressive articulations.  It was a big reason to add it to my modest arsenal.  The way their guitars articulate with legato playing and with physical controllers are somewhat similarly executed in Yamaha's Expanded Articulation and Korg's DNC (https://www.youtube.com/watch?v=Ej69-ptRNXI).

From what I'm understanding of Razmo's description, it sounds like poly-chained Slim Phattys and Minitaurs or poly-chained Boog D's utilize this, shall we say, "multi-monophonic" voice allocation.   ;D
 
And doesn't DSI utilize this voice allocation method as well with poly-chained Mophos and Tetras?  Here's a video demonstration (he stops talking and starts playing at the 11 minute mark):

https://www.youtube.com/watch?v=qtjNqCK2dgY

I have not tried a polychain myself, but I do not believe that this works like the method i proposed here... it actually rather work just like a real polysynth round-robbin allocation I think... If you look in the manual of a Mopho Keyboard, you can see that each device in the chain needs to have a global parameter set, that indicate exactly how many voices are "behind it"... that way each device will know (after it's own polyphony is used up) that when the right number of note-ons has been passed on, maximum polyphony on all devices together has been reached, and the next incoming note on should start to steal notes... in essence it's exactly the same as if you had one synth with the same number of voices internally.

This is normal polyphonic triggering... not what I proposed... in what I proposed, if the same C4 key is hit repeatedly, it should NOT allocate a new voice on each successive hit... it should restart the same voice again and again like on a monophonic synth, that is, until you hit a different note than C4... then it should start a new voice and so on and on. it is simply a method i want, that is in essence "Note Monophonic"... if that makes any sense.
Title: Re: Feature Requests
Post by: psionic11 on September 13, 2018, 06:03:33 AM
Ah, sounds more like MIDI MPE.
Title: Re: Feature Requests
Post by: psionic11 on September 14, 2018, 06:34:17 PM
When in Split or Stack mode, it would be awesome to balance volume levels of Layer A to Layer B relative to each other.

Suggested button combination:

Press and hold EDIT LAYER B while turning OSC MIX. 
Title: Re: Feature Requests
Post by: psionic11 on September 15, 2018, 07:24:25 AM
These features could be implemented in several DSI products (where applicable):

#1 Global LFO mode, alternatively "Free Sync". I miss being able to set the LFO to global operation, i.e. one LFO for all voices. If it's not possible to make an option to have one of the LFOs operate as a global LFO, an alternative could be something called "Free sync" (as opposed to Key Sync), basically that the LFOs are free running, but in sync with each other.

#2 Random (per voice) modulation source. Basically a random source in the mod matrix where each voice/note gets a new random value (bipolar). I've seen this feature in some soft synths, and it's great for getting some natural detuning between voices in a chord for an example, but can also be used for i.e. envelope times, etc to get some more variation between voices. This could also be super cool if it could be used in conjunction with unison if applied to i.e. filter cutoff with a high resonance setting (each voice getting it's own random cutoff value).

#3 Clock sync option for modulation effects. The Phaser and Flanger effects in particular could benefit from having a clock sync option.

#4 Frequency and time values on LFOs and EGs. When not in CLK SYNC mode, the LFOs would show the actual Hz rate, and the EGs would show the time in ms to sec.

+1 for global LFO and modulation clock sync

++1 for a Random mod source.

Would also be very cool to have a slew or smoothing parameter, or at least a choice of linear, exponential, or logarithmic curves.  Most useful on filter and volume (and pitch) envelopes, esp in the attack and decay portion.  If you think about it, the envelope is often a defining feature in many vintage sounds.
Title: Re: Feature Requests
Post by: psionic11 on September 15, 2018, 07:34:47 AM
A pretty simple suggestion: It would be very useful to be able to let A be active at the UPPER part of the keyboard and B be the LOWER part of the keyboard.

This would offer two great utilities:
1) Be able to edit the upper layer directly after selecting a preset. Now you have to press EDIT B to do so. (I often have a base patch on the left, which I don't want to tweak while playing; I do want to tweak my upper timbral patch)
2) Be able to have a typical lead sound in a preset where split is not activated, to which you can add the lower layer for your left hand (Layer B) by simply pressing SPLIT. (So I can save a nice preset with and without basepart easily in one preset)

Currently, only the opposite is possible, where you can only directly edit the lower timbral patch and where only the upper timbral layer can be added or removed from the preset.

This is already possible.  All you have to do is swap the layers in your desired sound, which will then bring the lower sound to the right side of the keyboard split, and vice versa.  Here are the steps:

1) Select the sound you wish would have the layers reversed (bottom on top, top on bottom).
2) Press and hold both the Split and Stack buttons at the same time.
3) Use the Parameter knob to select "swap layer A and B"
4) Press Write.
5) Audition the sound to verify it is what you intended.  You can also change the split point by holding Split and pressing a note on the keyboard, and then save this with the program.
6) Press WRITE again to save the new program.

Hope that helps.  It's great having your feature request implemented, even if it was already there in the first place =)
Title: Re: Feature Requests
Post by: hageir on September 15, 2018, 04:49:49 PM

++1 for a Random mod source.

Would also be very cool to have a slew or smoothing parameter, or at least a choice of linear, exponential, or logarithmic curves.  Most useful on filter and volume (and pitch) envelopes, esp in the attack and decay portion.  If you think about it, the envelope is often a defining feature in many vintage sounds.

Ok,
Random Mod Source = LFO (say) 4 set to Random, Use the Modulation matrix to route said LFO (as Source) to anywhere.

Slew/Linear/Exponential = Use the AUX Envelope and set it to the Decay parameter of any envelope you want to alter. Then you have to shape the AUX Envelope so it starts working its magic. This will speed up or slow (and various "slopes" are available as well) the target Attack/Decay parameters you have as destinations there.
You could also add keyboard tracking to the Attack or Decay portion of said AUX Envelope to emulate a well known "Rate" parameter from other synths...
Title: Re: Feature Requests
Post by: hageir on September 15, 2018, 04:51:06 PM
Are the LFOs analog? Because an audio-rate multiplier (somehow implemented) would be amazing for AM and FM synthesis.
Title: Re: Feature Requests
Post by: hageir on September 15, 2018, 06:28:58 PM
(dang couldn't edit that post above)

2) The Prophet remembers the Octave Transpose on reboot (saved to memory) -this would save one a almost-second-nature task of needing to transpose it, each time one turns it on.

3) In the newest beta (1.1.4.18) whenever I hit Write and am editing Layer B the patch gets written but takes me back to Layer A *edit* There is a setting for that in Global 'Save Edit B' (might need some copywriting revision!)

4) Pitch Bend Range, possible to up the ante on this to 24 or even 48? That would be nuts!

5) The Sub-Oscillator is, what appears to be a Octave-Divided solution, is it bound only to a Squarewave shape, or would be possible for an option of it inheriting the shape of Oscillator A (which is its 'master)?

I'm having quite strange results with the 'Audio Out' mod source, it would be interesting to expand on that one a bit...
Title: Re: Feature Requests
Post by: Razmo on September 16, 2018, 12:40:01 AM


You can simulate exponential and logarithmic response curves in the envelopes quite easy in any synth with a mod matrix that allow you to change envelope speeds as destination... Just route the envelope you want to shape, to it's own attack, decay or release parameter... Positive or negative amounts will make the curve either exponential or logarithmic... I use this trick a lot.

Title: Re: Feature Requests
Post by: hageir on September 16, 2018, 06:27:01 AM
Modulation Matrix Sources 1-8 Depth ALL -as a destination for the matrix itself (that way you could use the Mod Wheel to introduce Depth to ALL Sources 1-8 at the same time)
Title: Re: Feature Requests
Post by: psionic11 on September 16, 2018, 07:27:38 AM


You can simulate exponential and logarithmic response curves in the envelopes quite easy in any synth with a mod matrix that allow you to change envelope speeds as destination... Just route the envelope you want to shape, to it's own attack, decay or release parameter... Positive or negative amounts will make the curve either exponential or logarithmic... I use this trick a lot.

Thanks, I forgot about this trick.  Just tried it on filter env decay, and now it responds closer to what I think. Count yet another feature request fulfilled for me.

Another recent feature request I also found a workaround for -- separate levels of the layers.  The Env Amount works as a sort of program level, so I'm using that to balance the levels of the 2 layers.  Not perfect, but workable.  Someone mentioned in an old thread that you could set Program Volume as a destination, but I can't find that anywhere in the Mod Matrix destinations.  I wonder where that parameter is....

Title: Re: Feature Requests
Post by: maxter on September 16, 2018, 09:07:44 AM
(dang couldn't edit that post above)

2) The Prophet remembers the Octave Transpose on reboot (saved to memory) -this would save one a almost-second-nature task of needing to transpose it, each time one turns it on.

3) In the newest beta (1.1.4.18) whenever I hit Write and am editing Layer B the patch gets written but takes me back to Layer A *edit* There is a setting for that in Global 'Save Edit B' (might need some copywriting revision!)

4) Pitch Bend Range, possible to up the ante on this to 24 or even 48? That would be nuts!

5) The Sub-Oscillator is, what appears to be a Octave-Divided solution, is it bound only to a Squarewave shape, or would be possible for an option of it inheriting the shape of Oscillator A (which is its 'master)?

I'm having quite strange results with the 'Audio Out' mod source, it would be interesting to expand on that one a bit...

4) It's possible to get the pitch bend up to 24 or 48, but at the cost of a slot in the mod matrix. So it's possible already, but it would make sense to have that option without using the mod matrix.

5) I suspect this is a basic octave divider, which only outputs a square wave, so I don't think it would be possible, but I don't really know.
Title: Re: Feature Requests
Post by: maxter on September 16, 2018, 09:11:38 AM


You can simulate exponential and logarithmic response curves in the envelopes quite easy in any synth with a mod matrix that allow you to change envelope speeds as destination... Just route the envelope you want to shape, to it's own attack, decay or release parameter... Positive or negative amounts will make the curve either exponential or logarithmic... I use this trick a lot.

Thanks, I forgot about this trick.  Just tried it on filter env decay, and now it responds closer to what I think. Count yet another feature request fulfilled for me.

Another recent feature request I also found a workaround for -- separate levels of the layers.  The Env Amount works as a sort of program level, so I'm using that to balance the levels of the 2 layers.  Not perfect, but workable.  Someone mentioned in an old thread that you could set Program Volume as a destination, but I can't find that anywhere in the Mod Matrix destinations.  I wonder where that parameter is....

There is already a parameter for "Program Level", one for each layer, in the Misc Par section.

There is no Program Level as destination though, but there is VCA, which could work depending on what you're trying to achieve with it, but it's not the same thing as Program Level.
Title: Re: Feature Requests
Post by: psionic11 on September 16, 2018, 09:24:23 AM
Nevermind, I found Program Volume under Misc Parameters.

Another "feature" request, unless I just can't find it in the manual  --- All Notes Off (called Panic mode in some synths).

(Not so) fun fact:  You can create a program with stuck notes, write the program to memory, reboot the Rev2, and when you call up that program it will play stuck notes without even touching any keys yet.
Title: Re: Feature Requests
Post by: guyaguy on September 16, 2018, 09:39:06 AM
Nevermind, I found Program Volume under Misc Parameters.

Another "feature" request, unless I just can't find it in the manual  --- All Notes Off (called Panic mode in some synths).

(Not so) fun fact:  You can create a program with stuck notes, write the program to memory, reboot the Rev2, and when you call up that program it will play stuck notes without even touching any keys yet.
Sounds like a feature not a bug!
Title: Re: Feature Requests
Post by: guyaguy on September 16, 2018, 09:42:21 AM
Are the LFOs analog? Because an audio-rate multiplier (somehow implemented) would be amazing for AM and FM synthesis.
They’re digital and kinda/sorta do some AM/FM but not quite. Audio Out does FM a bit better but obviously without control over the wave shape; the audio is modulating itself.
Title: Re: Feature Requests
Post by: maxter on September 16, 2018, 10:10:26 AM
Nevermind, I found Program Volume under Misc Parameters.

Another "feature" request, unless I just can't find it in the manual  --- All Notes Off (called Panic mode in some synths).

(Not so) fun fact:  You can create a program with stuck notes, write the program to memory, reboot the Rev2, and when you call up that program it will play stuck notes without even touching any keys yet.
Sounds like a feature not a bug!

Definitely! I wonder if psionic11 is referring to programming a positive value for the VCA parameter, which makes the notes drone? Or how else do you program "stuck notes"?
Title: Re: Feature Requests
Post by: guyaguy on September 16, 2018, 11:43:55 AM
Nevermind, I found Program Volume under Misc Parameters.

Another "feature" request, unless I just can't find it in the manual  --- All Notes Off (called Panic mode in some synths).

(Not so) fun fact:  You can create a program with stuck notes, write the program to memory, reboot the Rev2, and when you call up that program it will play stuck notes without even touching any keys yet.
Sounds like a feature not a bug!

Definitely! I wonder if psionic11 is referring to programming a positive value for the VCA parameter, which makes the notes drone? Or how else do you program "stuck notes"?
I'd like to know too. Would be cool to select a patch and have a drone start with pre-programmed notes. Normally if you select a patch with the VCA open it plays notes played on whatever patch you were just on.
Title: Re: Feature Requests
Post by: psionic11 on September 16, 2018, 04:07:47 PM
The stuck notes were an accident, and the drone notes aren't controllable or predictable.

I created a basic program, and created a split.  I wanted the left hand bass to be thicker, so I put it in unison.  I was messing with unison detune and number of voices when I got stuck notes.  Having already spent 20 minutes fine tuning the upper layer, I didn't want to lose my work so I opted to save at that point.   I figured I could scroll to another program and back to stop the stuck notes.  Nope,  still there.   So I rebooted.   Still there.

Worse yet, if I took it out of split mode, I got additional very high sounding stuck notes.

So this is very much a bug.  And is also why I was asking if there was an All Notes Off command. 

Come to think of it, I was also dabbling with the VCA Env amount and levels, trying to balance the 2 layers volume wise.
Title: Re: Feature Requests
Post by: Quatschmacher on September 16, 2018, 04:12:09 PM
Nevermind, I found Program Volume under Misc Parameters.

Another "feature" request, unless I just can't find it in the manual  --- All Notes Off (called Panic mode in some synths).

(Not so) fun fact:  You can create a program with stuck notes, write the program to memory, reboot the Rev2, and when you call up that program it will play stuck notes without even touching any keys yet.
Sounds like a feature not a bug!

Definitely! I wonder if psionic11 is referring to programming a positive value for the VCA parameter, which makes the notes drone? Or how else do you program "stuck notes"?
I'd like to know too. Would be cool to select a patch and have a drone start with pre-programmed notes. Normally if you select a patch with the VCA open it plays notes played on whatever patch you were just on.

Latched looping envelopes would achieve this. My Subsequent does this.
Title: Re: Feature Requests
Post by: chapelier fou on September 17, 2018, 05:28:46 AM
I'd like to see a new form of voice trigger mode... not only for the REV2, but in synthesizers in general that are polyphonic.

The mode I'm thinking about is one that mimics real acoustic instruments that are "polyphonic" like stringed instruments.

With the normal polyphonic voice allocation in polyphonic synths, if you press the same key multiple times, a new voice is allocated for that note, but in acoustic instruments, if you (like on stringed instruments for example) play the same note, it does not double... if you hit the same string twice, that string is in essence "monophonic".

I was about to post the exact same request !
It's very important to me. For instance if you hold the sustain pedal to maintain some chords for a long time while you tweak the sound and then you play another chord (releasing the key but not the pedal), you end up triggering the common notes twice. This is really annoying.
Title: Re: Feature Requests
Post by: chapelier fou on September 17, 2018, 05:31:08 AM
Another one really important : an "automatic" Clock Mode, that would grab an incoming clock when there's one and switch to internal if there in none.
I am so sick and tired to change this in the Globals 648 times a day !!! (or am I missing something ?)
Title: Re: Feature Requests
Post by: chapelier fou on September 19, 2018, 05:19:14 AM
Here's another one.

When using "passtrhru" knob mode, the screen currently updates the tweaked parameter name and value only when you reach the actual value. This would be much more useful to instantly display the parameter that you're tweaking with the actual value "stuck" until you reach it.

Also some sort of flashing indicator would be very useful when you cross the "original" value saved with the patch.

And (but that's a bug) : when you hit "show" to know a parameter value, the passthru seems to grab the knob movement, so when you get back to the knob, you actually have a parameter jump.
Title: Re: Feature Requests
Post by: eXode on September 22, 2018, 09:37:50 AM
I understand this won't happen but I like to think about what if the REV2 effect section would have been arranged in a bus configuration instead. That is the ability to send both layers to both effects, with custom dry/wet for each effect and layer, and finally an option to run the effects in either series or parallel.

Example: I want Layer A to go through a phaser on effect 1 that is then routed to a delay on effect 2 while Layer B is routed directly to effect 2.

Or I want both layers to go through a chorus and delay.

The possibilities.
Title: Re: Feature Requests
Post by: psionic11 on September 22, 2018, 11:16:56 AM
Agreed it would be very nice to have FX in a bus configuration as often found on workstations.

Also, having a dedicated final EQ section would really help sound shaping and room correction as well.  A simple high shelf, low shelf, and a parametric mid section with adjustable Q, sweepable frequency, and level would suffice.  You could notch out some of the nasal quality or push up the low end for bass (although admittedly there must be something there to augment in the first place, hehe).
Title: Re: Feature Requests
Post by: psionic11 on September 22, 2018, 11:19:02 AM
For the record -- I'd like to request that aftertouch transmission on layer B be implemented ;)
Title: Re: Feature Requests
Post by: Razmo on September 26, 2018, 09:17:07 AM
After messing around with the arpeggiator for some time, I feel that I'd like to have a switch that would duplicate the arpeggiated notes at the start and end of the pattern... an example:

pressing C,D,E & F with up/down would then be this sequence: C,D,E,F,E,D,C,D,E... etc.

with duplicating the start and end notes is would be this sequence: C,D,E,F,F,E,D,C,C,D,E... etc.

The reason I want this option is that if the start and end notes are duplicated, then pressing down 4 keys would ensure that the pattern would also fit the time signature of four notes... with the up/down pattern as it is now, holding down 4 keys will give you a 6 note repeating pattern, and not 8 notes which would be nice to be able to achieve.

Title: Re: Feature Requests
Post by: araucaria on September 27, 2018, 10:06:23 AM
I'd like to see a new form of voice trigger mode... not only for the REV2, but in synthesizers in general that are polyphonic.

The mode I'm thinking about is one that mimics real acoustic instruments that are "polyphonic" like stringed instruments.

With the normal polyphonic voice allocation in polyphonic synths, if you press the same key multiple times, a new voice is allocated for that note, but in acoustic instruments, if you (like on stringed instruments for example) play the same note, it does not double... if you hit the same string twice, that string is in essence "monophonic".

This behavior is impossible to simulate on any polyphonic synth that I know of, simply because they have no voice allocation mode that take this into account.

The Elektron Analog Four is a poly that can do this, using a voice allocation method called 'reassign'. See page 28 of https://www.elektron.se/wp-content/uploads/2017/10/Analog-Four-MKII-User-Manual_ENG-2.pdf
Title: Re: Feature Requests
Post by: skipgilles on October 01, 2018, 05:36:43 AM
There is this nice short cut: press modulation source & move modulation wheel, which allows you to assign a modulation to the wheel. Now, if you already have a modulation assigned to the modulation wheel, this short cut doesn't do anything anymore. That's a pity, I often want a second destination to the mod wheel.
Title: Re: Feature Requests
Post by: hageir on October 02, 2018, 06:22:48 AM
Uhm, I've got an idea:
'Below 0' as a static "speed" for the Flanger/Phaser/Chorus (Rate controlled effects)
that could be nice; the Phaser would then become a static notch filter so it could be used as a pseudo EQ sort of?

If there was a setting below 0 = static/stop,
but then, how would we sweep the frequency of the effect? Would depth 'tell' it where the point is?

(I guess it is possible to send an inverted LFO to the rate parameter?)
Title: Re: Feature Requests
Post by: OneLittleFonzie on October 03, 2018, 02:12:22 AM
1. Gate sequencer sending midi notes
2. And have a midi control message as destination
Title: Re: Feature Requests
Post by: Razmo on October 04, 2018, 04:27:54 AM
I'd like to see two simple additions to the LFOs:

1. Slew parameter
2. Phase Start (when the LFO is in key-sync mode)

the reason is simple: to be able to create a lot more shapes from combining the LFOs (routing one LFO to the Rate or Amount parameters of another LFO), and also smooth out edges in the S&H/Square/Saw/rev.Saw shapes.

Especially when you key-sync two LFOs, and also clock sync them... if two LFOs are running at the exact same speed via clock sync, and you let one control the other's amount parameter, it's basically like Amp modulating an LFO within a single LFO cycle, and this can create many interesting modulations... also when the modulating LFO is in time multiples of the modulated LFO... and if you have the ability to control the phase offset of an LFO, you can create many more interesting curves from this... add slew and you get even more results.

I bet SCI already have the code for this, as I know you have slew as a parameter on the P12 for example... cannot be that much work to implement this (?).

Title: Re: Feature Requests
Post by: dsetto on October 10, 2018, 11:02:36 AM
respectfully,

1. Independent amplitude envelope control of oscillators in one layer.
2. Delay added to front of ADSR amp envelope (DADSR)

(obviously, I don't have an idea of limitations, of whatever type. thank you.)
Title: Re: Feature Requests
Post by: jok3r on October 10, 2018, 12:05:09 PM
respectfully,
2. Delay added to front of ADSR amp envelope (DADSR)

Isn't there a Delay knob in this section? Or am I missing something? ;-)
Title: Re: Feature Requests
Post by: Razmo on October 10, 2018, 01:43:50 PM
I know this has been asked before and wiped off the table by DSI, but I'm really sick and tired of the way recording stacked mode programs with the polysequencer works, so I'm asking this again and hope others will start chiming in on this so that maybe someday it will be implemented:

I can understand, that you would want to record a separate sequence for layer A and B when you are in SPLIT mode, or using the REV2 as a dual timbral synth... I agree that far... but when I'm playing a stacked program, where both layers join up to create the instrument as a whole, then it's really annoying that I have to either record each layer separately, or enter a menu afterward to copy one layers sequence to the other to get both layers playing the same sequence... this really is a nobrainer! ... when you record on the sequencer with a stacked program, both layers should be recorded into at the same time.

I use the sequencer as a scratchpad... I never ever store a sequence with the program because why would you!? you'd want to play different melodies depending on what score you're working on, you really have no need for a "one timer sequence" that will only be used once... therefore it's irritating and very unintuitive to have to record twice, or enter a menu to copy it... you may make more than one try when recording... maybe you did not get it right, maybe you want a different melody going, but every single time I have to do these convoluted workarounds to get the same played sequence into the sequencer layers... it's counter intuitive!

At least, as things stand with the editing of the layers, you can always edit both layers simultaneously by holding down layer B for a second (LED start flashing)... but when I do this, the record button is unavailable!? ... why!? would it not follow the design philosophy to let you record to both layers when in that mode? Everything else is going to both layers in this mode (!)

Please SCI! ... consider this feature... it would make the sequencer a lot more intuitive to use... as it is now it confuses people when they try to record a stacked program, leaving bogus old material playing on a stacked program's B layer, and even split the two layers tones that should go together making it sound completely wrong... there is not even a quick way to erase this B layer.

and sorry if I come out a bit harsh, but this is getting quite annoying... it makes me not wanna use the sequencer at all.
Title: Re: Feature Requests
Post by: OneLittleFonzie on October 11, 2018, 03:35:36 AM
respectfully,
2. Delay added to front of ADSR amp envelope (DADSR)

Isn't there a Delay knob in this section? Or am I missing something? ;-)

well, the amp adsr has one, just not in front of it (visually).
Title: Re: Feature Requests
Post by: skrohmer on October 13, 2018, 01:35:21 PM
Almost one year ago, but for me still valid:
HOLD functionality user defined:

1. the 'DSI' way: adding notes to until full polyphony is reached
2. the 'regular' way: latch the played tones / chords until next tone / chord is played.

Only one example: I have been working on a stacked patch with a pad on layer A and a lead on layer B. B uses the arp, A doesn't. I cannot use the hold function. Layer B relatches fine, layer A collects all notes which is not what I want. When playing the arp I would like layer A playing the chord.

Switching the functionality in the global menu would be fine.
Title: Re: Feature Requests
Post by: chapelier fou on October 17, 2018, 12:58:22 AM
Am I the only one to think that an "Auto" clock sync would be very important ?
I am using the Rev2 always with a DAW and it's really a massive pain for the workflow. I'm not even talking about bringing it on stage, and have to go to the globals to be able to just PLAY a program that has a gated sequencer in it (like 90% of my sounds).
Title: Re: Feature Requests
Post by: eagleman on November 05, 2018, 11:03:55 AM
Just wondering. Is there a reason why theirs no modulation destiny for LPF sustain and modwheel.  Especially the modwheel would be nice as it would save some mod slots. Is this possible to implement in the future update?
Title: Re: Feature Requests
Post by: Razmo on November 20, 2018, 02:48:55 AM
I've been working quite a bit and deeply with the REV2 now for about 6 months doing sound design, and in the course of that time, I've found a couple of features that I would have liked to have on the REV2 quite often. I hope that Sequential will consider these options... they would have no impact on backward compatibility, just simply a few simple additions, some of them already present in other synths they've done.

1. LFO 1-4 Slew parameter. I've wanted this rather often, so that i can smooth out abrupt changes in the LFO's. I often combine several LFO's to obtain complex new waveforms, but as soon as either Saw, Rev.Saw, Pulse or Random is involved, there will be abrupt changes in the curve... I would really like to be able to smooth these out.

2. LFO 1-4 Quantize parameter. This parameter would be really nice for doing complex tonal patterns (when routed to pitch for example). It should be located BEFORE the Slew parameter of course so that the resulting steps can be smoothed out if you want to. With several LFO's using this at different setting, and routed to the same destination, some really long and evolving patterns could be created for all kinds of modulation.

3. LFO 1-4 EG-Trigger. Per see, this may seem odd, but I once had this feature on a small analog synth (M.A.R.S.) and it allowed for some really cool triggering effects, especially in the FX department. Every time an LFO start it's cycle anew, it triggers all envelopes... this is perfect if you want to create stuff like "twinkling stars"... tiny "blips" of sound that is triggered by a running LFO... by changing LFO speed you can change the time between the "twinkling stars", and with multiple LFO's retriggering the envelopes, complex random S&H like patterns can be created... Currently, the only way to obtain retriggering of the envelopes while a key is held, is via the arpeggiator or gated sequencer, but this always run at the same speed which greatly limit it's use for this purpose.

4. "Key Random" source in the list of modulation sources. This has been asked by others as well. It's a very handy source for a lot of different tasks, and should not be that hard to implement.

5. "Key-Off Velocity" source in the list of modulation sources. I don't know why this is not already present (?) ... it's an integrated value in the note-off command already, so why not let it be available in the sources? I'm sure some users will find a use for it.

that's about it really... I hope some of them will find their way into any of the Sequential synths both current and new ones.
Title: Re: Feature Requests
Post by: guyaguy on November 20, 2018, 05:28:07 PM
I've been working quite a bit and deeply with the REV2 now for about 6 months doing sound design, and in the course of that time, I've found a couple of features that I would have liked to have on the REV2 quite often. I hope that Sequential will consider these options... they would have no impact on backward compatibility, just simply a few simple additions, some of them already present in other synths they've done.

1. LFO 1-4 Slew parameter. I've wanted this rather often, so that i can smooth out abrupt changes in the LFO's. I often combine several LFO's to obtain complex new waveforms, but as soon as either Saw, Rev.Saw, Pulse or Random is involved, there will be abrupt changes in the curve... I would really like to be able to smooth these out.

2. LFO 1-4 Quantize parameter. This parameter would be really nice for doing complex tonal patterns (when routed to pitch for example). It should be located BEFORE the Slew parameter of course so that the resulting steps can be smoothed out if you want to. With several LFO's using this at different setting, and routed to the same destination, some really long and evolving patterns could be created for all kinds of modulation.

3. LFO 1-4 EG-Trigger. Per see, this may seem odd, but I once had this feature on a small analog synth (M.A.R.S.) and it allowed for some really cool triggering effects, especially in the FX department. Every time an LFO start it's cycle anew, it triggers all envelopes... this is perfect if you want to create stuff like "twinkling stars"... tiny "blips" of sound that is triggered by a running LFO... by changing LFO speed you can change the time between the "twinkling stars", and with multiple LFO's retriggering the envelopes, complex random S&H like patterns can be created... Currently, the only way to obtain retriggering of the envelopes while a key is held, is via the arpeggiator or gated sequencer, but this always run at the same speed which greatly limit it's use for this purpose.


You REALLY need to start digging into the gated sequencer, Razmo.  :)

1. LFO Slew: Set mode to no gate, set seq1 destination as desired, step 1 to 75, step 2 to 25, and step 3 to reset. Now set seq1 destination to slew, steps 1 and 2 to 75, and step 3 to reset. You've just made your own slewed LFO! Adjust to taste. If you make a longer sequence the sequence becomes a custom wave shape--like a looping EG.

2. Quantize: Step sequencers are all about quantization!

3. EG trigger: Yep, gated seq. Set mode to normal, destination to EG amount, and each step to the amount you want the EG triggered.

Title: Re: Feature Requests
Post by: Razmo on November 20, 2018, 05:53:04 PM
I've been working quite a bit and deeply with the REV2 now for about 6 months doing sound design, and in the course of that time, I've found a couple of features that I would have liked to have on the REV2 quite often. I hope that Sequential will consider these options... they would have no impact on backward compatibility, just simply a few simple additions, some of them already present in other synths they've done.

1. LFO 1-4 Slew parameter. I've wanted this rather often, so that i can smooth out abrupt changes in the LFO's. I often combine several LFO's to obtain complex new waveforms, but as soon as either Saw, Rev.Saw, Pulse or Random is involved, there will be abrupt changes in the curve... I would really like to be able to smooth these out.

2. LFO 1-4 Quantize parameter. This parameter would be really nice for doing complex tonal patterns (when routed to pitch for example). It should be located BEFORE the Slew parameter of course so that the resulting steps can be smoothed out if you want to. With several LFO's using this at different setting, and routed to the same destination, some really long and evolving patterns could be created for all kinds of modulation.

3. LFO 1-4 EG-Trigger. Per see, this may seem odd, but I once had this feature on a small analog synth (M.A.R.S.) and it allowed for some really cool triggering effects, especially in the FX department. Every time an LFO start it's cycle anew, it triggers all envelopes... this is perfect if you want to create stuff like "twinkling stars"... tiny "blips" of sound that is triggered by a running LFO... by changing LFO speed you can change the time between the "twinkling stars", and with multiple LFO's retriggering the envelopes, complex random S&H like patterns can be created... Currently, the only way to obtain retriggering of the envelopes while a key is held, is via the arpeggiator or gated sequencer, but this always run at the same speed which greatly limit it's use for this purpose.


You REALLY need to start digging into the gated sequencer, Razmo.  :)

1. LFO Slew: Set mode to no gate, set seq1 destination as desired, step 1 to 75, step 2 to 25, and step 3 to reset. Now set seq1 destination to slew, steps 1 and 2 to 75, and step 3 to reset. You've just made your own slewed LFO! Adjust to taste. If you make a longer sequence the sequence becomes a custom wave shape--like a looping EG.

2. Quantize: Step sequencers are all about quantization!

3. EG trigger: Yep, gated seq. Set mode to normal, destination to EG amount, and each step to the amount you want the EG triggered.

1. I'd rather have a parameter for this in the LFO section. It will never be the same with the sequencers... they are synced to each other, and cannot have separate speeds... neither can they give you the same shapes as the LFOs would be able to.

2. Nope... you will not be able to create the kind of combined LFO stepped patterns the same way with the sequencers... yes, you can create different lengths, but not speeds like you would be able to with the LFOs combined...

3. Nope... the sequencers again run at a fixed speed, so I'll not be able to get retriggers that vary in speed... it's just not possible.

but with that said... you can certainly make some interesting things with the tricks with your suggestions :) ... I just find that the features I'm asking for would be nice to have, without having to rely on using the sequencers for this... I'd like those free for other tasks.
Title: Re: Feature Requests
Post by: guyaguy on November 20, 2018, 07:18:21 PM
1. I'd rather have a parameter for this in the LFO section. It will never be the same with the sequencers... they are synced to each other, and cannot have separate speeds... neither can they give you the same shapes as the LFOs would be able to.

2. Nope... you will not be able to create the kind of combined LFO stepped patterns the same way with the sequencers... yes, you can create different lengths, but not speeds like you would be able to with the LFOs combined...

3. Nope... the sequencers again run at a fixed speed, so I'll not be able to get retriggers that vary in speed... it's just not possible.

but with that said... you can certainly make some interesting things with the tricks with your suggestions :) ... I just find that the features I'm asking for would be nice to have, without having to rely on using the sequencers for this... I'd like those free for other tasks.
Just saying you can do 90% what you are asking for already if you don’t want to wait for features that probably will never make it. Seqs are locked to the clock but can have different rates if you program the steps and slew right, e.g. skipping steps halves the speed. You can also get pretty much any shape the LFO offers. Min/max 2 step is a square, slewed 25/75 is a triangle, trigger an envelope for saw and a lot more options not in the LFOs. No Rate Modulation but you can skip steps for variation.
Title: Re: Feature Requests
Post by: Razmo on November 21, 2018, 06:27:25 AM
1. I'd rather have a parameter for this in the LFO section. It will never be the same with the sequencers... they are synced to each other, and cannot have separate speeds... neither can they give you the same shapes as the LFOs would be able to.

2. Nope... you will not be able to create the kind of combined LFO stepped patterns the same way with the sequencers... yes, you can create different lengths, but not speeds like you would be able to with the LFOs combined...

3. Nope... the sequencers again run at a fixed speed, so I'll not be able to get retriggers that vary in speed... it's just not possible.

but with that said... you can certainly make some interesting things with the tricks with your suggestions :) ... I just find that the features I'm asking for would be nice to have, without having to rely on using the sequencers for this... I'd like those free for other tasks.
Just saying you can do 90% what you are asking for already if you don’t want to wait for features that probably will never make it. Seqs are locked to the clock but can have different rates if you program the steps and slew right, e.g. skipping steps halves the speed. You can also get pretty much any shape the LFO offers. Min/max 2 step is a square, slewed 25/75 is a triangle, trigger an envelope for saw and a lot more options not in the LFOs. No Rate Modulation but you can skip steps for variation.

I'v not dived that far into the gated sequencer yet, so I may be missing out on some things you are mentioning... but that said, there are still advantages to the proposed features i came with... the first and most important is that since the BPM is not a modulation destination, whatever you program in the gated sequencers will run side by side on all four sequencers, at a predetermined speed... it puts some limitations on what you can do compared to having these ekstra parameters in the LFO's themselves... I know (being a programmer myself), that those features are not very demanding... they should be relatively easy to make... a simple quantize parameter is probably no more than a few lines of code in the right place, plus reservation of the parameter in memory and a short extention of the modulation destinations to include these new parameters... that is yet another reason to have them separate; you woul dbe able to modulate both slewspeed and quantize in the matrix for even more fun.

Try to imagine the possibility of four LFO's acting together to control pitch... one could be a very slow random source, another a sine with quantize, a third a ramp and a third a sine... all these routed to pitch, with LFO's at different speeds and amounts and slew... now think these intermodulating eachother as well.... it would give so many different curves that could potentially evolve for several minutes... you could modulate speed and amounts from controllers... a lot of things you cannot do with the gated sequencers... I'd really like to have these options available as they give so many more modulation options for long and evolving parameter modulation.

I know that many want new features, and that not everything will find it's way into the OS... I'll even survive if these did not see their way into a future OS... but if I do not ask, then surely it will not happen... At least the P12 has slew as a dedicated LFO parameter, so I'd hope for at least that... they probably already have the code for it since it is in the P12.

Quantize could be partially done with the gated sequencers, so that would be my second wish after slew... and gating envelopes via LFO would be my last one.
Title: Re: Feature Requests
Post by: jok3r on November 22, 2018, 12:47:47 AM
I would also like to have slew on the LFOs. Especially for the S&H waveform it's really nice if the values don't jump so abruptly.

I did a very nice wind patch on my PEAK by modulating filter cutoff with slewed random LFOs. It has two LFOs that both modulate the cutoff, while modulating their frequencies mutually. It sounds like a very big storm is coming up and the wind gusts never repeat... I think this patch could still be better on a Rev2 with 4(!) slewed LFOs.
Title: Re: Feature Requests
Post by: Razmo on November 22, 2018, 01:36:00 AM
Actually ot would be cool if the quantize parameter could instead be a list of different musical scales that the LFO could be scaled to.
Title: Re: Feature Requests
Post by: noir on November 27, 2018, 12:56:40 AM
I thought it was a bug but I've been told that this is intended behavior so I'm kindly asking here for a minor change with big impact:

How to reproduce:

Current behavior:
There's no feedback about the value of the current parameter until the saved value is reached.

Expected behavior:
As soon as the poti is turned the saved value should be displayed on the screen while the value is not changed until the saved position is reached.

Why:
In most cases when a program is recalled, pretty much all visible parameters have a different internal value. With the current implementation, it is difficult to figure out what value every single parameter has since every poti has to be turned to the saved position while the "show" button is pressed. This takes some time and it needs both hands on the device. However, I suppose that most users would like to have their hands rather on the keyboard most of the time while tweaking the parameters. Especially in live performance situations, the current behavior is an obstacle in the workflow.
Title: Re: Feature Requests
Post by: Kasimir Effekt on November 27, 2018, 04:54:17 PM
I think that this is a useful suggestion. In addition, it should be said that this behavior applies to the passthrough knob mode.


I thought it was a bug but I've been told that this is intended behavior so I'm kindly asking here for a minor change with big impact:

How to reproduce:
  • Recall a program
  • Turn a poti to adjust a parameter
  • Look at the screen

Current behavior:
There's no feedback about the value of the current parameter until the saved value is reached.

Expected behavior:
As soon as the poti is turned the saved value should be displayed on the screen while the value is not changed until the saved position is reached.

Why:
In most cases when a program is recalled, pretty much all visible parameters have a different internal value. With the current implementation, it is difficult to figure out what value every single parameter has since every poti has to be turned to the saved position while the "show" button is pressed. This takes some time and it needs both hands on the device. However, I suppose that most users would like to have their hands rather on the keyboard most of the time while tweaking the parameters. Especially in live performance situations, the current behavior is an obstacle in the workflow.
Title: Re: Feature Requests
Post by: Tugdual on November 28, 2018, 04:45:38 AM
A sort of slow down mechanism on knobs to have more accuracy.
In some occasion, picking the right frequency note is very tricky and I keep jumping around my choice.
Title: Re: Feature Requests
Post by: jg666 on November 28, 2018, 05:58:44 AM
A sort of slow down mechanism on knobs to have more accuracy.
In some occasion, picking the right frequency note is very tricky and I keep jumping around my choice.

In a lot of these cases you can switch to using the Value knob next to the display as this can be more precise. You can use the Value knob to change the displayed amount.

Title: Re: Feature Requests
Post by: eXode on December 02, 2018, 02:14:31 AM
Would be nice with an ensemble effect (solina/eminent style) for all the instruments that have digital effects.
Title: Re: Feature Requests
Post by: psionic11 on December 03, 2018, 11:23:03 PM
Polyphonic unison please =)
Title: Re: Feature Requests
Post by: iJean on December 04, 2018, 04:53:56 AM
Voice limitation in poly mode (not only16/8 voices). To make polyphonic glide usefull. :)
Title: Re: Feature Requests
Post by: Razmo on December 04, 2018, 05:21:38 AM
Would be nice with an ensemble effect (solina/eminent style) for all the instruments that have digital effects.

I agree on this one... and I've requested this long ago... the answer is always the same: "there are no space for more FX"...
Title: Re: Feature Requests
Post by: elliottjkeen on December 04, 2018, 12:38:27 PM
Hi everyone,

This is my first post/comment on the forum ever so I apologise if this question has been asked already. I've had my Rev2 since the end of November and I've not had time to do much exploring as yet. I noticed today that the sustain for the envelopes is not assignable as a destination to modulate. If DSI updated the firmware or something would this be made possible or is this something that cannot be changed?

Cheers

Elliott

The sustain stage has never been available as a modulation destination on any synth, or at least none I can currently think of. It's a level parameter, not a temporal parameter like Delay, Attack, Decay, and Release. You can implicitly modulate it by modulating the filter cutoff or the VCA level directly, depending on what level you'd like to modulate.

My apologies for the extreme late reply on this one haha! This is something I have done on my MatrixBrute which was the first big boy synth I purchased!
Title: Re: Feature Requests
Post by: psionic11 on December 05, 2018, 09:02:08 PM
Hi everyone,

This is my first post/comment on the forum ever so I apologise if this question has been asked already. I've had my Rev2 since the end of November and I've not had time to do much exploring as yet. I noticed today that the sustain for the envelopes is not assignable as a destination to modulate. If DSI updated the firmware or something would this be made possible or is this something that cannot be changed?

Cheers

Elliott

The sustain stage has never been available as a modulation destination on any synth, or at least none I can currently think of. It's a level parameter, not a temporal parameter like Delay, Attack, Decay, and Release. You can implicitly modulate it by modulating the filter cutoff or the VCA level directly, depending on what level you'd like to modulate.

My apologies for the extreme late reply on this one haha! This is something I have done on my MatrixBrute which was the first big boy synth I purchased!

I have a few synths where the sustain stage can be a modulation destination like in the MatrixBrute. 

Alesis Andromeda, Fusion, and Micron
Moog Slim Phatty and Minitaur have it as a destination CC 
My Moog One has in its Mod matrix EG1,2,3 sustain as a destination

Would be nice to see sustain as a destination in the Rev2, esp for the filter envelope.

Although, I'd prefer to have polyphonic unison first, as that is much more useful for fattening up voices while retaining polyphony, especially in split mode.
Title: Re: Feature Requests
Post by: Tugdual on December 06, 2018, 04:08:31 AM
A sort of slow down mechanism on knobs to have more accuracy.
In some occasion, picking the right frequency note is very tricky and I keep jumping around my choice.

In a lot of these cases you can switch to using the Value knob next to the display as this can be more precise. You can use the Value knob to change the displayed amount.
Didn’t know that trick VERY usefull.
Thanks!
Title: Re: Feature Requests
Post by: LoboLives on December 08, 2018, 10:30:56 AM
Voice allocation.
Title: Re: Feature Requests
Post by: LoboLives on December 11, 2018, 11:19:12 AM
Another feature I’d like to see is a feature from the Prophet 10 which was a mode called alternate which alternated between layer a and layer b every other note. It produced some really nice sounds, especially if you held down chords.
Title: Re: Feature Requests
Post by: maxter on December 12, 2018, 10:42:17 AM
Minor request here. It would be great to have the pitch bend range extended from +/-12 to 24, or possibly 36. This is possible by using an extra modulation slot in the matrix from pitch bend to pitch, but it would of course be nice not having to sacrifice a modulation slot to achieve this extended pitch range.
Title: Re: Feature Requests
Post by: Djinn on December 13, 2018, 03:32:46 AM
I'm also glad arp works now I agree with others Increased pitch range and lfo slew would both be desirable
Plus I will continue to champion increased filter bit rate changeable in global cheers  :)
Title: Re: Feature Requests
Post by: Razmo on December 13, 2018, 03:39:02 AM
I suppose that the REV2 envelopes are digitally created (DSP)... and if they are, I'd really like to see an extra envelope trigger mode where the envelope's current state value is reset to zero when it receives a trigger.

Currently, the state of the envelope simply continue from where it was currently at when it receive a new trigger, like with an analog envelope... but being able to reset the envelope to zero when it receive a trigger can be handy in some cases.
Title: Re: Feature Requests
Post by: Razmo on December 14, 2018, 03:35:22 AM
I know this is probably not that important, but would it be possible to use a different font on the display for showing the program name? ... the way it works right now, in many situations, the name cannot be shown all at once in the display and is truncated with a ".."

I'm not sure if the display has a resolution big enough for this... but it shure would look better if the names were not truncated.
Title: Re: Feature Requests
Post by: luk.vermeir@gmail.com on December 14, 2018, 07:38:23 AM
my biggest requests still are:

- RELATCH notes or chords when HOLD is active (like what's possible already with the ARP)
- CHORD MEMORY: more than 4 notes / voices please!! Beceause 5-note chords (or sometimes even 6) are also beautiful :)

thanks thanks thanks...
Title: Re: Feature Requests
Post by: luk.vermeir@gmail.com on December 14, 2018, 07:48:43 AM
Is there any hardware limitation for why the hold button has to play the exact same role as sustain? Can an option for the ability to reset upon changing a note/chords be implemented for the hold button?

I know already some time that I'm not the only one requesting this... :) Hold + Relatch = Thank You Very Muchas!
Title: Re: Feature Requests
Post by: luk.vermeir@gmail.com on December 14, 2018, 07:58:32 AM
Almost one year ago, but for me still valid:
HOLD functionality user defined:

1. the 'DSI' way: adding notes to until full polyphony is reached
2. the 'regular' way: latch the played tones / chords until next tone / chord is played.

Only one example: I have been working on a stacked patch with a pad on layer A and a lead on layer B. B uses the arp, A doesn't. I cannot use the hold function. Layer B relatches fine, layer A collects all notes which is not what I want. When playing the arp I would like layer A playing the chord.

Switching the functionality in the global menu would be fine.

And yes, another one...
Title: Re: Feature Requests
Post by: luk.vermeir@gmail.com on December 14, 2018, 08:05:23 AM
Minor request here. It would be great to have the pitch bend range extended from +/-12 to 24, or possibly 36. This is possible by using an extra modulation slot in the matrix from pitch bend to pitch, but it would of course be nice not having to sacrifice a modulation slot to achieve this extended pitch range.

and additionally: being able to set different values for 'UP' range and 'DOWN' range, so you can play with the same 'musical interval' one octave up or below the actual note / chord.

For example: bend up = 5 / bend down = 7 
in this scenario, if you play a Cmaj chord, the fully PB up result will be a Fmaj chord above the original Cmaj chord, while the fully PB down result will ALSO be a Fmaj chord, in this case below the Cmaj chord. And yes, that's really nice. :)

Thanks again!

Title: Re: Feature Requests
Post by: Quatschmacher on December 15, 2018, 03:23:42 PM
I know this is probably not that important, but would it be possible to use a different font on the display for showing the program name? ... the way it works right now, in many situations, the name cannot be shown all at once in the display and is truncated with a ".."

I'm not sure if the display has a resolution big enough for this... but it shure would look better if the names were not truncated.

Or scrolling text perhaps?
Title: Re: Feature Requests
Post by: eXode on December 16, 2018, 01:55:06 AM
CLK SYNC for the CHORUS, PHASER(S), and FLANGER(S), please. That cannot be too difficult or time consuming to implement imho.
Title: Re: Feature Requests
Post by: jg666 on December 16, 2018, 03:26:49 AM
I know this is probably not that important, but would it be possible to use a different font on the display for showing the program name? ... the way it works right now, in many situations, the name cannot be shown all at once in the display and is truncated with a ".."

I'm not sure if the display has a resolution big enough for this... but it shure would look better if the names were not truncated.

Or scrolling text perhaps?

Personally scrolling text would be better for me because if the text was any smaller I'd need my reading spectacles on all the time to be able to read it. I suspect that would apply to a lot of us 'more senior' owners :)
Title: Re: Feature Requests
Post by: Razmo on December 16, 2018, 09:16:15 AM
my biggest requests still are:

- RELATCH notes or chords when HOLD is active (like what's possible already with the ARP)
- CHORD MEMORY: more than 4 notes / voices please!! Beceause 5-note chords (or sometimes even 6) are also beautiful :)

thanks thanks thanks...

I bet the reason it's only four notes is because of the REV2 8 voice model... an 8voice model will not allow more than 4 voices since it has no more than 4 voices per layer... but with that said, it should be possible to take this into account... it does so when you allocate more voices to unison than what the model can handle.
Title: Re: Feature Requests
Post by: Razmo on December 16, 2018, 09:21:12 AM
I know this is probably not that important, but would it be possible to use a different font on the display for showing the program name? ... the way it works right now, in many situations, the name cannot be shown all at once in the display and is truncated with a ".."

I'm not sure if the display has a resolution big enough for this... but it shure would look better if the names were not truncated.

Or scrolling text perhaps?

Would be fine with me... it just seems weird that they added another 4 characters from the P08 (now up to 20), if some of them is not even seen on the screen.

The problem for me is, that I use the first four characters to designate a category... DSI never did any categorization of the programs, so I have to find a solution myself... I place the category name in the beginning because otherwise it may not even show on the screen, and also because it's easier to sort the programs this way too... but with four characters in the beginning for a category, there is even less space for a program name after that... that is why it irritates me that i cannot see the whole name at once actually.
Title: Re: Feature Requests
Post by: Quatschmacher on December 16, 2018, 03:20:11 PM
I know this is probably not that important, but would it be possible to use a different font on the display for showing the program name? ... the way it works right now, in many situations, the name cannot be shown all at once in the display and is truncated with a ".."

I'm not sure if the display has a resolution big enough for this... but it shure would look better if the names were not truncated.

Or scrolling text perhaps?

Would be fine with me... it just seems weird that they added another 4 characters from the P08 (now up to 20), if some of them is not even seen on the screen.

The problem for me is, that I use the first four characters to designate a category... DSI never did any categorization of the programs, so I have to find a solution myself... I place the category name in the beginning because otherwise it may not even show on the screen, and also because it's easier to sort the programs this way too... but with four characters in the beginning for a category, there is even less space for a program name after that... that is why it irritates me that i cannot see the whole name at once actually.

Indeed. Categorisation is an incredibly useful and much-desired feature.
Title: Re: Feature Requests
Post by: Razmo on December 27, 2018, 10:22:03 AM
I'd like to see a parameter for setting downward pitchbend differently than upward... it's much more musical to have these at different values pretty often.
Title: Re: Feature Requests
Post by: proteus-ix on December 27, 2018, 10:49:51 AM
XY pads, and... a modulation display like the new Arturia Pigments VST has.  It truly is one of the most useful features on any synth hardware or software that I have ever used.  You get an instant view of what each modulation shape/wave/function is, in realtime, as the sound plays.  Impossibly useful for design and troubleshooting.
Title: Re: Feature Requests
Post by: Quatschmacher on December 27, 2018, 01:50:37 PM
I'd like to see a parameter for setting downward pitchbend differently than upward... it's much more musical to have these at different values pretty often.

I was a bit gobsmacked to learn that this feature is missing. Especially on a synth this deep. I often use +2, -12.
Title: Re: Feature Requests
Post by: Razmo on December 27, 2018, 03:36:00 PM
I'd like to see a parameter for setting downward pitchbend differently than upward... it's much more musical to have these at different values pretty often.

I was a bit gobsmacked to learn that this feature is missing. Especially on a synth this deep. I often use +2, -12.

Yes... and other values as well... if you set it for a range of 5 up, having 5 down simply sounds unmusical... -2, -7 or -12 would be more fit in that case... makes the pitchwheel a lot more useful when using both directions.
Title: Re: Feature Requests
Post by: Quatschmacher on December 28, 2018, 05:50:22 AM
I also think it might be nice to make the oscillators mutable from the wave selection button via a long press or something so that one could switch oscillators in and out without having to cycle through the wave shapes.

It could be implemented such that one could still cycle through the waveforms whilst being muted in that quick presses would illuminate the light (perhaps blinking) and cycle through, then go off again after a short time delay (if still muted).
Title: Re: Feature Requests
Post by: luk.vermeir@gmail.com on December 29, 2018, 03:36:36 PM
I'd like to see a parameter for setting downward pitchbend differently than upward... it's much more musical to have these at different values pretty often.

Something I've also requested a couple of times already.

Hope one day DS will be able to do this, together with HOLD RE-LATCH.
These are two requests that appear here from time to time, and are very useful for live-performance / better live playing of the synth.


Title: Re: Feature Requests
Post by: keston on January 02, 2019, 09:50:44 AM
Hi all! This is my first time chiming in here. My feature request is to make Glide Amount a MOD destination. I'm imagining mapping it to velocity so that hitting a key harder (or softer when in the negative) increases the glide. I've had my Rev2 just over a month and find it is quite an expressive synth. So much so that I haven't touched much of anything else in my studio since!
Title: Re: Feature Requests
Post by: LoboLives on January 02, 2019, 11:30:12 PM
I'd like to see a parameter for setting downward pitchbend differently than upward... it's much more musical to have these at different values pretty often.

I was a bit gobsmacked to learn that this feature is missing. Especially on a synth this deep. I often use +2, -12.

Yes... and other values as well... if you set it for a range of 5 up, having 5 down simply sounds unmusical... -2, -7 or -12 would be more fit in that case... makes the pitchwheel a lot more useful when using both directions.

I’m sure this will be implemented as you can set each pitch directional range to a different amount on the PX.
Title: Re: Feature Requests
Post by: cedrelo on January 03, 2019, 01:10:54 PM
Reload function to reload the sound to his original state whiteout silence like on Electron machine!!!!!
Title: Re: Feature Requests
Post by: Tugdual on January 05, 2019, 05:05:43 AM
I'm sure this was already requested but sometime #of requests is expected to put some weight on decisions.
Here we go:
Title: Re: Feature Requests
Post by: Razmo on January 06, 2019, 12:29:06 AM
I'd like to see a parameter for setting downward pitchbend differently than upward... it's much more musical to have these at different values pretty often.

I was a bit gobsmacked to learn that this feature is missing. Especially on a synth this deep. I often use +2, -12.

Yes... and other values as well... if you set it for a range of 5 up, having 5 down simply sounds unmusical... -2, -7 or -12 would be more fit in that case... makes the pitchwheel a lot more useful when using both directions.

I’m sure this will be implemented as you can set each pitch directional range to a different amount on the PX.

That may give it a greater chance then... But I'll believe it when I see it... I have not seen many features added to the REV2 lately... But one can hope... Pitchbend for both directions, key-random mod source and LFO slew rate is probably my greatest wishes, because these are what I have missed the most during my soundbank creation over the last half year... Especially LFO slew rate.
Title: Re: Feature Requests
Post by: eisblau on January 07, 2019, 01:54:10 PM
key-random mod source and LFO slew rate is probably my greatest wishes, because these are what I have missed the most during my soundbank creation over the last half year... Especially LFO slew rate.

Yes, these would be my biggest wishes as well.

And if the could improve the behaviour of the LFOs at audio rate, it seems to me they are aliasing very much and become brittle when reaching the audio range.
Title: Re: Feature Requests
Post by: lft303 on January 07, 2019, 05:50:59 PM
Hi all! This is my first time chiming in here. My feature request is to make Glide Amount a MOD destination. I'm imagining mapping it to velocity so that hitting a key harder (or softer when in the negative) increases the glide. I've had my Rev2 just over a month and find it is quite an expressive synth. So much so that I haven't touched much of anything else in my studio since!


2nd this motion - thanks y'all!
Title: Re: Feature Requests
Post by: Kasimir Effekt on January 11, 2019, 10:15:09 AM
I still ask to add some featues to this great instrument:

- PolySeq / Arp should continue running when Split or Stack is pressed
- yes to "hold release"!
- Osc Level should be added as ModDestination
- variable release time of the gated sequencer
- BPM Sync for Phaser / Chorus and Env3
Title: Re: Feature Requests
Post by: Groove on January 12, 2019, 12:16:35 PM
my english is bad,,  but i try to write my wishes for my rev2

1: Sound init..so i can start design my own presets from zero.

2: in the arpegiator mode would be a chord mode fine...and some arpegiator Banks with presets.

    Arpegiator presets if in future implemented could be a source for modulations too.


    thank you for this beautiful instrument.
     









Title: Re: Feature Requests
Post by: AlainHubert on January 12, 2019, 12:35:31 PM
my english is bad,,  but i try to write my wishes for my rev2

1: Sound init..so i can start design my own presets from zero.


Welcome.

If your read the manual on page 18, you will see that in the Global Settings there is item number 24: Basic Program (which loads a basic template program to start from scratch). You can also recall that same Basic Program using the shortcut of pressing and holding Down and Up (transpose) and pressing Hold.

Your english is fine.

Title: Re: Feature Requests
Post by: brinnandeskepp on January 19, 2019, 07:32:02 AM
A high res control mode you can enable in global settings. 1024 values instead of 128, for all the controls. Like on a Korg or other modern analog synth with a digital control interface. The staircase effect when slowly changing a parameter sounds very cheap. The synth already has 14-bit MIDI, so it would be super easy to implement. Otherwise, how about releasing the firmware open source like the Linnstrument bravely did?
Title: Re: Feature Requests
Post by: Djinn on January 21, 2019, 04:00:32 AM
I'm repeating myself but high res control mode and slew rate for lfos would be great turning this good synth into a fantastic synth pleeeasse!!!!
Title: Re: Feature Requests
Post by: shiihs on January 26, 2019, 02:12:51 PM
Maybe it's been asked before, although I didn't quickly find it: how about having bpm (tempo) as a mod destination?



Title: Re: Feature Requests
Post by: philroyjenkins on January 29, 2019, 09:49:24 AM
Higher max resonance for the 2 pole filter.
Title: Re: Feature Requests
Post by: Djinn on January 29, 2019, 10:01:46 AM
Higher resonance for 2pole if possible is a nice idea!!
Title: Re: Feature Requests
Post by: Razmo on January 30, 2019, 11:12:45 AM
I can certainly be the spoilsport here and tell the last two posts, that this will never happen... the 2-pole has always been non-selfoscillating in the Curtis chips... Sequential cannot change how the analog chip works, so it simply cannot be done... Curtis chips do have some rather disappointing aspects, but you'll just have to live with them as they are :)
Title: Re: Feature Requests
Post by: hageir on February 01, 2019, 03:04:32 PM
Assignable (separate) MIDI OUT Channel
(currently it's sending on the same channel as MIDI IN?)
Title: Re: Feature Requests
Post by: Kasimir Effekt on February 02, 2019, 02:54:02 PM
I think it would be great if you could switch layer a or layer b independently to mono on the corresponding outputs!
Great for combining stereo keys/pads and synth bass patches...
Since the rev2 was designed as "two synths in one", this should probably be easy to implement in a software update ..?
Title: Re: Feature Requests
Post by: justice86 on February 04, 2019, 01:58:39 AM
It would be great if the sequencer functions were expanded. To me, the sequencer at its current state is clearly the biggest downside to this otherwise great synth (especially when coming from my Moog). Some of the following feature requests have been made time and again.


Title: Re: Feature Requests
Post by: Djinn on February 04, 2019, 03:29:51 AM
I have my doubts anyone at sequential is reading this thread or any other apart from the bug report but a way to lock program change when designing sounds would be good as I and many others and I have lost all are hard work editing with an accidental touch of the wrong knob around the screen area
cheers
Title: Re: Feature Requests
Post by: Razmo on February 04, 2019, 03:38:32 AM
It's a waste of time writing requests in all these request threads... nothing is being implemented anyway, not even the requests that are being frequent, nor any of the requests that are actually rather simple to implement (like LFO slew for example... they already have most of the code for that in other products)...

On the other hand, I'd rather see them fix bugs first...
Title: Re: Feature Requests
Post by: OneLittleFonzie on February 04, 2019, 12:35:49 PM
I have my doubts anyone at sequential is reading this thread or any other apart from the bug report but a way to lock program change when designing sounds would be good as I and many others and I have lost all are hard work editing with an accidental touch of the wrong knob around the screen area
cheers

I would remove the patch and bank knob :-)
Title: Re: Feature Requests
Post by: Djinn on February 04, 2019, 01:13:46 PM
I have my doubts anyone at sequential is reading this thread or any other apart from the bug report but a way to lock program change when designing sounds would be good as I and many others and I have lost all are hard work editing with an accidental touch of the wrong knob around the screen area
cheers

I would remove the patch and bank knob :-)

I hope ur taking the piss have u even got a rev2 pulling knobs is like extracting teeth
Title: Re: Feature Requests
Post by: OneLittleFonzie on February 05, 2019, 01:22:23 PM
I have my doubts anyone at sequential is reading this thread or any other apart from the bug report but a way to lock program change when designing sounds would be good as I and many others and I have lost all are hard work editing with an accidental touch of the wrong knob around the screen area
cheers

I would remove the patch and bank knob :-)

I hope ur taking the piss have u even got a rev2 pulling knobs is like extracting teeth

Yes, I do. It is very easy!
I've done it. No problems with accidental loss of a nice patch.
Title: Re: Feature Requests
Post by: Djinn on February 05, 2019, 01:28:51 PM
Fair play apologies I just assumed they would be the same as all the other pots but  your right that does work

Cheers soz
Title: Re: Feature Requests
Post by: OneLittleFonzie on February 05, 2019, 01:31:43 PM
Fair play apologies I just assumed they would be the same as all the other pots but  your right that does work

Cheers soz

No problem. Funny fact, I hardly save presets so for me it is extremely important. I have quite some base patches as go from there. Same with my Sub Phatty (it only has 16 spots anyway).
Title: Re: Feature Requests
Post by: meister_philipp on February 13, 2019, 06:44:44 AM
Glide Mode: Exponential, like on the sub37
Title: Re: Feature Requests
Post by: maxter on March 04, 2019, 04:44:43 AM
Request: Osc Fine Tune as modulation destinations.

Please see creativespirals thread on how this would make possible to mimic VCOs without using up extra mod slots.
https://forum.sequential.com/index.php/topic,3412.0.html

Title: Re: Feature Requests
Post by: hageir on March 05, 2019, 04:01:41 PM
Guys, what is this? Synths and Hardware 101?
More resonance on the 2-pole for example is totally hardware based (not software)
you've gotta use Keyboard Tracking to make your 'resonance' stronger on a 12dB filter, it's ALL about the Frequency of the Cutoff, the Envelope amount and the KBD Tracking (which in this mode, all of a sudden becomes the "resonance")

Oscillator Mix as destination would be handy, but is it a programmable pot/digital or analog with sequential reading only used for storing the value in the patch, that's the question.

Selectable MIDI OUT channel, on the other hand, is software related. hehe

Bit better implementation on the Intonation/Alternative Tunings;
Check out the Kurzweil way of doing it, it's brilliant because you can freely set the 'IntonaKey' (the reference key for the tuning)
Keeping the 'slots' separate would also be smoother; to "hot-swap" the tables out one-by-one and fully manage them.
What about bringing back the manual tuning of the Prophet 5 REV2/3?, where on a certain startup key-combination 12 knobs in a row became the tuning pots for individual notes. Brilliant!

Adios.
Title: Re: Feature Requests
Post by: Razmo on March 06, 2019, 06:47:16 AM
Guys, what is this? Synths and Hardware 101?
More resonance on the 2-pole for example is totally hardware based (not software)
you've gotta use Keyboard Tracking to make your 'resonance' stronger on a 12dB filter, it's ALL about the Frequency of the Cutoff, the Envelope amount and the KBD Tracking (which in this mode, all of a sudden becomes the "resonance")

Oscillator Mix as destination would be handy, but is it a programmable pot/digital or analog with sequential reading only used for storing the value in the patch, that's the question.

Selectable MIDI OUT channel, on the other hand, is software related. hehe

Bit better implementation on the Intonation/Alternative Tunings;
Check out the Kurzweil way of doing it, it's brilliant because you can freely set the 'IntonaKey' (the reference key for the tuning)
Keeping the 'slots' separate would also be smoother; to "hot-swap" the tables out one-by-one and fully manage them.
What about bringing back the manual tuning of the Prophet 5 REV2/3?, where on a certain startup key-combination 12 knobs in a row became the tuning pots for individual notes. Brilliant!

Adios.

Oscillator Mix is already a destination in the Matrix...
Title: Re: Feature Requests
Post by: hageir on March 08, 2019, 06:57:12 AM
Guys, what is this? Synths and Hardware 101?
More resonance on the 2-pole for example is totally hardware based (not software)
you've gotta use Keyboard Tracking to make your 'resonance' stronger on a 12dB filter, it's ALL about the Frequency of the Cutoff, the Envelope amount and the KBD Tracking (which in this mode, all of a sudden becomes the "resonance")

Oscillator Mix as destination would be handy, but is it a programmable pot/digital or analog with sequential reading only used for storing the value in the patch, that's the question.

Selectable MIDI OUT channel, on the other hand, is software related. hehe

Bit better implementation on the Intonation/Alternative Tunings;
Check out the Kurzweil way of doing it, it's brilliant because you can freely set the 'IntonaKey' (the reference key for the tuning)
Keeping the 'slots' separate would also be smoother; to "hot-swap" the tables out one-by-one and fully manage them.
What about bringing back the manual tuning of the Prophet 5 REV2/3?, where on a certain startup key-combination 12 knobs in a row became the tuning pots for individual notes. Brilliant!

Adios.


Oscillator Mix is already a destination in the Matrix...


Yeah, I'm sorry there was some request for that a bit back (maybe I read it too fast)
Maybe it was Oscillator Volume, actually...
Title: Re: Feature Requests
Post by: Razmo on March 10, 2019, 11:10:51 AM
Guys, what is this? Synths and Hardware 101?
More resonance on the 2-pole for example is totally hardware based (not software)
you've gotta use Keyboard Tracking to make your 'resonance' stronger on a 12dB filter, it's ALL about the Frequency of the Cutoff, the Envelope amount and the KBD Tracking (which in this mode, all of a sudden becomes the "resonance")

Oscillator Mix as destination would be handy, but is it a programmable pot/digital or analog with sequential reading only used for storing the value in the patch, that's the question.

Selectable MIDI OUT channel, on the other hand, is software related. hehe

Bit better implementation on the Intonation/Alternative Tunings;
Check out the Kurzweil way of doing it, it's brilliant because you can freely set the 'IntonaKey' (the reference key for the tuning)
Keeping the 'slots' separate would also be smoother; to "hot-swap" the tables out one-by-one and fully manage them.
What about bringing back the manual tuning of the Prophet 5 REV2/3?, where on a certain startup key-combination 12 knobs in a row became the tuning pots for individual notes. Brilliant!

Adios.


Oscillator Mix is already a destination in the Matrix...


Yeah, I'm sorry there was some request for that a bit back (maybe I read it too fast)
Maybe it was Oscillator Volume, actually...

probably yes... many have requested this, but it's never going to happen because the Curtis chip is designed the way it is... it has a pin called "OSC MIX", and it's a CV pin... so it's an internal thing that software cannot change... for volume control over each OSC you need one of the digital synths like P12, Pro2 or PX.
Title: Re: Feature Requests
Post by: psionic11 on March 10, 2019, 11:27:33 PM
Requesting Polyphonic Unison again.  Thicker Layer while keeping some polyphony.
Title: Re: Feature Requests
Post by: OneLittleFonzie on March 15, 2019, 02:25:57 AM
Destination MIDI CC for Gated Sequencer