The Official Sequential/Oberheim Forum
SEQUENTIAL/DSI => Prophet-5/Prophet-10 => Topic started by: OurDarkness on May 29, 2022, 10:30:13 PM
-
Vote for what you would like to see implemented in a possible update. :)
-
Vote for what you would like to see implemented in a possible update. :)
I voted "something else", because I'd like to see the aftertouch response fixed so that it doesn't go ballistic at the smallest amount of pressure. Existing features fixed before new stuff added, please.
-
Keyboard octave transpose (per part).
-
Vote for what you would like to see implemented in a possible update. :)
I voted "something else", because I'd like to see the aftertouch response fixed so that it doesn't go ballistic at the smallest amount of pressure. Existing features fixed before new stuff added, please.
+ 1 for a AT fix : )
BTW, just one vote ... for one new feature ? : /
I see at least 2 things that I would like to see in a update : )
Cheers !
-
MPE would be great and should be easily within its reach
-
I would like to control the filter cutoff with the modwheel, so that I could control the filter on layer A and B in stack mode ;D
-
For me :
Behavior of the expression at the cutoff (The existing steps are terrible for a synth like this ! )
Hold on/off per part
Pitchwheel-amount possible down to zero for more performance in splits and layers
Transpose +/-24 (for the keyboard-value) stored in a patch
-
I would love to see a way to adjust the aftertouch max filter cutoff modulation. Global or even better, per patch.
-
I would like to see:
-Octave transpose shortcut
-Per patch auto-glide mode like Pro One
-Per patch RR/P5 Allocation
-Per patch alternate tunings
Having these very important parameters (voice allocation and alt tuning) relegated to Global just makes them nearly useless to me. Why go through the trouble to implement them, if they are useless in a live setting and slow you down tremendously in the studio?
-
Maybe in a couple of years a third party will offer a new Mod/Pitch wheel section with 2 transpose buttons (+/- octave), LEDs to indicate the transposition and possibly a global Pitch LFO. I'd gladly pay for such an upgrade.
-
I would like to see the octave transpose and other requested features implemented the same way that pitch bend select is done with the [freq A] + [Group -] + [Bank +] buttons.
For octave transpose: [freq B] + [Group/Bank] is my vote.
For arp: [PWM A], [PWM B], and [Filter] could be rhythmic division, number of octaves, and directions/rhythms.
-
Transpose octave +/- out for use as a controller and more granular AT curve options aka a fix for that.
-
The only one I really care about from those is an improved Vintage knob... pref one that doesn't detune/go out of tune so much toward '1'... but would still retain the env and other looseness.. i.e make it actually usable!
I think the other stuff is starting to take the Prophet away from one of it's main plus-points... focus!
What I *have* felt would be great yet streamlined additions are:
1. Reverse Saw for the LFO - By holding down the current SAW button until it flashes (or to bring up a menu on the screen to select 'norm' or 'rev'). Absolutely simple and clean to implement and yet massively potent for all kinds of sounds. Reverse SAW is one of my favourite things to add to a filter for that rhytmic boink boink sound... sounds great on the OB-6 but would sound awesome on a Prophet 5/10. I'd prefer the long press instead of the menu... and the light could flash or pulse on the LFO waveform to show its in reverse mode. You could do the same for the other 2 but there it would be polarity.
2. LFO SYNC!!! come on it's 2022.. we don't always wanna hook up midi to the DAW and send CC.. a simple switch or option to enable sync to incoming clock/tempo.... could access this by holding down any of the LFO wave buttons for say 5 seconds and then it flashes to the incoming BPM. For subdivisions you could step through them using thee usual group/bank to show the 4/8/16/d/t etc while holding down all three lfo wave buttons while in LFO sync mode.
These 2 additions would push the amazing Prophet 10 upto a new level and yet retain the simplicity and ease of use.
Many other options get a bit hacky sounding, like third party mod upgrades. I think the LFO 'fixes' or 'uprgades' would be relatively simple to get in, bug free, vs adding tons of new features.
The only other real complaint is the 200 user banks vs 500 on the OB-6, even if we could sshift select another hidden 200 storage I'm guessing the memory doesn't exist on the mainboard to do so.. that ship has sailed I guess.
EDIT: I forgot also... I think an LFO that can go twice as fast 'hi rate' would be cool, so again we could just hold down one of the LFO buttons (or all 3) and select 'norm' or 'hi' to switch the LFO to be much faster, inline with more modern synths...
-
If folks want any feature upgrades then you are advised to submit them to the sequential support email where they will be added to the tally. I recently emailed some and Carson indicated that they’d been added to the count.
-
i only wish for really fast LFO .. i'd be already happy with the 500Hz that are mentioned in the manual (which are 50 Hz)
-
Negative filter envelope mod would be super great imo.
I also like SynthHead's suggestions regarding reverse saw LFO and LFO sync, but I don't think the press and hold method is a good idea. A button combo where you don't have to hold a button for a fixed amount of time is better. Holding buttons to engage any function in the moment of jamming is a real buzzkill.
-
I vote All of the above + I'd like different types of portamento modes: like that of the OB-8's portamento glide modes.
-
I wonder if any of those features will ever be implemented...
-
Write over the factory presets, can't believe this is not possible.
-
Write over the factory presets, can't believe this is not possible.
As posted in your other post. It is possible to overwrite the factory presets. Just do a search for it as I posted the procedure for you in your other thread.
-
Write over the factory presets, can't believe this is not possible.
Indeed. The way the minilogue handles this is elegant. One can overwrite them but a system restore menu allows one to reset just the factory presets, system settings or both.
They could implement a global menu “factory presets memory protect” option, enabled by default, but then switching it off would allow them to be replaced.
-
Looks like I’m in the minority with different envelope curves :( I’d love to see this on my pro 3 as well
-
The P5 has been my dream synth since I was old enough to, well, have a dream synth. I'm old enough now to be on my 3rd Prophet 5. It's great having a slick, reliable version at hand, always ready to rock. Of all the new rev4 features, I use... MIDI and... maybe that's it. I rarely use velocity or AT. The Prophet was built so thoughtfully first time around and it works so well as it is. I'm lucky to have a range of other gear to do other whatevers with, but I've never felt the P5 lacking for anything. Not even for extra voices! I played piano before I got my first 5, but my hands adapted immediately to having no more than 5 voices to work with. It's fab that people have the option of grabbing a P10 or upgrading their 5s, but for the way I do music, the Prophet 5 is perfect and sits at the center of almost everything. Just as I never wish my cat also functioned as a 3-D printer, it's never occurred to me to wish the new Prophet 5 could also do... things it doesn't do.
-
The P5 has been my dream synth since I was old enough to, well, have a dream synth. I'm old enough now to be on my 3rd Prophet 5. It's great having a slick, reliable version at hand, always ready to rock. Of all the new rev4 features, I use... MIDI and... maybe that's it. I rarely use velocity or AT. The Prophet was built so thoughtfully first time around and it works so well as it is. I'm lucky to have a range of other gear to do other whatevers with, but I've never felt the P5 lacking for anything. Not even for extra voices! I played piano before I got my first 5, but my hands adapted immediately to having no more than 5 voices to work with. It's fab that people have the option of grabbing a P10 or upgrading their 5s, but for the way I do music, the Prophet 5 is perfect and sits at the center of almost everything. Just as I never wish my cat also functioned as a 3-D printer, it's never occurred to me to wish the new Prophet 5 could also do... things it doesn't do.
Word! :)
-
Vote for what you would like to see implemented in a possible update. :)
Voted something else. Would like to see , (as has been mentioned/suggested elsewhere), adjustable depth for velocity and aftertouch control of the filter/amp/LFO separately.
Would probably need awkward finger pressing of switches and control pots to operate adjustments in firmware/software, but I believe it would be a great addition to the new velocity and aftertouch control of a classic synth.
Probably worth a few finger twists and addition of a nose for multiple key presses!
-
My previous post was in the spirit of "I like it just the way it is/was!" but I can say an easy octave transpose option wouldn't offend my delicate old skoo sensibilities. I'd intended to use the P5 as controller keyboard when I first got it, but the octave issue made that too tricksy. Which is fine, really... I don't actually want to use the P5 as controller. It's its own creature. I've got the P6 as controller again, with my Casio Privia hooked up via USB running Pianoteq software.
-
Vote for what you would like to see implemented in a possible update. :)
I voted "something else", because I'd like to see the aftertouch response fixed so that it doesn't go ballistic at the smallest amount of pressure. Existing features fixed before new stuff added, please.
I absolutely agree. I use polyAT on my Linnstrument to control AT on my P10 desktop. Even with sensitivity set to lowest on the LS, the Prophet literally overshoots the slightest finger movement. Not very musical and quite challenging to wield it in a controlled way. So even for the Desktop P5/10, an improved AT curve control would be very welcome.
-
For me :
Behavior of the expression at the cutoff (The existing steps are terrible for a synth like this ! )
Hold on/off per part
Pitchwheel-amount possible down to zero for more performance in splits and layers
Transpose +/-24 (for the keyboard-value) stored in a patch
+ Direction change for the pitchwheel would be fine. In the OB-X8 it also works
But the really important thing would be the behavior of the expression-pedal
-
Hello Sequential Team,
I voted for „something else“. The listed features are great but above all I wish for a long standing improvement, probably since the introduction of the original Prophet 5. You most likely guessed it:
- If technical possible, please increase the resolution of all continuous parameters… (including the resolution of ‘unison detune’ if possible)
====
Other nice features I would welcome but with much lower priority compared to the above:
- An option to invert the filter envelope would be great as it would allow to create sounds currently not possible
- A ‘depth’ parameter for ‘velocity’ and ‘aftertouch’ would help to fine tune their dynamic range. Especially ‘aftertouch’ would greatly benefit from such a parameter as its current range is rather large
Thanks for reissuing this classic instrument
-ts-
-
Others have mentioned octave transpose. I think a really simple implementation would be:
Keyboard button plus Group select (octave decrease) or Bank select (octave increase).
Currently holding the keyboard button lets you switch the key priority mode. This could easily be moved to holding the filter Keyboard button. it's not something you need easy access to, whereas octave transpose would be.
You can tell that live performing keyboardists were the beta testers - because I feel like most studio users would want something like the Prophet 5/10 to be a master controller, and octave transpose is pretty indispensable, at least for me. So it can't be my master controller, which totally sucks. This does not surprise me given the way things like Arps were implemented in the Prophet 12 (pretty awful IMO).
Second to this - I would love a way for the Prophet 10 - is keeping it in live panel mode even after power down. Even the System 8 allows this.
-
Hello Sequential Team,
I voted for „something else“. The listed features are great but above all I wish for a long standing improvement, probably since the introduction of the original Prophet 5. You most likely guessed it:
- If technical possible, please increase the resolution of all continuous parameters… (including the resolution of ‘unison detune’ if possible)
====
Other nice features I would welcome but with much lower priority compared to the above:
- An option to invert the filter envelope would be great as it would allow to create sounds currently not possible
- A ‘depth’ parameter for ‘velocity’ and ‘aftertouch’ would help to fine tune their dynamic range. Especially ‘aftertouch’ would greatly benefit from such a parameter as its current range is rather large
Thanks for reissuing this classic instrument
-ts-
Just thinking:
- Currently if all LFO waveforms are switched off the LFO is “silent” unless there is some Noise dialed-in. If instead of being silent the “LFO” would produce a constant DC voltage the mod wheel could be used to control any or all of the LFO destinations directly.
- As far as I know both filter chips (CEM/SSI) of the Prophet rev.4 provide a 2pole [12db] output (among other filter types). Provided the Prophet hardware is capable of switching to other filter outputs it would be cool to provide an option to switch either of the filter chips to another mode (both filter LEDs active). My preference would be the 2pole of the SSI 2140 chip. Naturally this would push the Prophet somewhat into the territory of the Oberheim sound. I understand that this may not be wished for. It’s just a thought.
-
As far as I know both filter chips (CEM/SSI) of the Prophet rev.4 provide a 2pole [12db] output (among other filter types). Provided the Prophet hardware is capable of switching to other filter outputs it would be cool to provide an option to switch either of the filter chips to another mode (both filter LEDs active). My preference would be the 2pole of the SSI 2140 chip. Naturally this would push the Prophet somewhat into the territory of the Oberheim sound. I understand that this may not be wished for. It’s just a thought.
The Rev4, like Rev1-3 uses 4 pole filters.
-
Just thinking:
...
- As far as I know both filter chips (CEM/SSI) of the Prophet rev.4 provide a 2pole [12db] output (among other filter types). Provided the Prophet hardware is capable of switching to other filter outputs it would be cool to provide an option to switch either of the filter chips to another mode (both filter LEDs active). My preference would be the 2pole of the SSI 2140 chip. Naturally this would push the Prophet somewhat into the territory of the Oberheim sound. I understand that this may not be wished for. It’s just a thought.
This is not possible without a new pcb, as it needs additional parts to route and switch the different pole depths.
-
Keyboard octave transpose. Please.
-
Just thinking:
...
- As far as I know both filter chips (CEM/SSI) of the Prophet rev.4 provide a 2pole [12db] output (among other filter types). Provided the Prophet hardware is capable of switching to other filter outputs it would be cool to provide an option to switch either of the filter chips to another mode (both filter LEDs active). My preference would be the 2pole of the SSI 2140 chip. Naturally this would push the Prophet somewhat into the territory of the Oberheim sound. I understand that this may not be wished for. It’s just a thought.
This is not possible without a new pcb, as it needs additional parts to route and switch the different pole depths.
Makes sense… I expected as much… was just contemplating.
-
octave transpose - I use the p10 as my main controller (or trying to at least!)
-
Adjustable limit for aftertouch (mostly) and velocity amount. It's almost unusable without it (especially aftertouch).
-
Aftertouch fixed in 2.0.4 and works great!
Thanks Sequential | Oberheim!
-
octave transpose - I use the p10 as my main controller (or trying to at least!)
Why is this one so low on the list for folks? I too would like it as my main controller. I've asked Sequential since November 2020 to implement it, but it just seems to be thrown off to the wayside. After another update (yesterday/today), it's clear its unlikely to happen. It's too big of a synth to have off to the side for me.
EDIT: Heard from the developers (on Reddit no less) and they said: "It's definitely on our list and something we considered for addition this time around. However, we identified some potential operational gotchas and felt that the feature should be better thought through and designed before implementation.
Not to worry, we heard you and the feature is still on our radar."
That was awesome to hear!
-
I wonder if an option to turn stepped vs no stepped filter sweeps are doable? In the smooth filter sweep setting I would assume digital/midi control would not be available but I wouldn’t mind this limitation for this option when turned on.
-
Would love to see the ability to slow OSC 2 in Low Mode. It just doesnt go slow enough for nice long filter / PWM sweeps.
-
Dont know if this has been mentioned before but the ability to unlock the oscillators semitone lock would add a vast array of different timbres to the Rev4.
-
Voted something else:
- 2nd LFO AND reverse saw shape in the first at least
- AT fix at cutoff
- hold functionality
-
I only want an onboard reverse sawtooth LFO. I think adding too many features would take away from the appeal of the simplicity of this synth. Any other modulation I can do via MIDI if I wanted to.
-
Don't own a p5 or p10 yet but I would like to see a secondary LFO in software that at least just does vibrato leaving the main LFO open for something more interesting. Being able to select the modwheel for filter sweeps would also be great. Just those two simple features would make the synth pretty much complete for me.
Oh and transpose octave up/down should be a must add as well.
-
Also proper nrpn implementation would be nice…
-
Don't own a p5 or p10 yet but I would like to see a secondary LFO in software that at least just does vibrato leaving the main LFO open for something more interesting. Being able to select the modwheel for filter sweeps would also be great. Just those two simple features would make the synth pretty much complete for me.
Oh and transpose octave up/down should be a must add as well.
Octave up/down would be nice, I do miss it at times. Don't forget that the oscillators are so full on the P5/10, that you can easily sacrifice the second oscillator to use in LFO mode, and still have a great sound. Endless great tunes created on single oscillator Junos can't be wrong.. plus if the single osc isn't enough, put it in polyunison-2 mode and detune if you have a P10.
-
Got the synth! It sure is beautiful. I'll add that separate midi channels for splits/stacks would be great. Also maybe it's not the best idea to use the volume knob for adjusting volume between splits and stacks.
-
One thing that’s be a nice option would be to allow the user to adjust the percentage the pitch-wheel(aftertouch) affects the LFO destinations.
For instance, individually the we could select 50% of the pulse width A, and say 30% for pitch A, then 70% for filter etc.
By holding the buttons we can adjust individually, between 0-127, for each mod wheel destination.
Perhaps this could even be applied to the Polymod destinations as well.
Thanks :)
-
My pet feature would be that button states be saved in panel (Preset off) mode.
When Globals is pressed three times, it saves the startup preset. But when Globals is pressed three times when Preset is off, it would instead save the states of the buttons on the panel (including the state of the Preset button itself), so when you cycle power, the Prophet starts back up where you left off.
-
My pet feature would be that button states be saved in panel (Preset off) mode.
When Globals is pressed three times, it saves the startup preset. But when Globals is pressed three times when Preset is off, it would instead save the states of the buttons on the panel (including the state of the Preset button itself), so when you cycle power, the Prophet starts back up where you left off.
Sounds good, please email support with that suggestion.
-
Many great ideas in this thread. I particularly would welcome the option to invert the filter envelope.
In addition I like to suggest to maybe revise the filter and amp envelope velocity depth parameters slightly. Currently, if I’m not mistaken, the max possible envelope depth is scaled down by the velocity depth parameter. As a result the sound of any given preset is getting duller and quieter when lowering the vel depth parameter. An alternative implementation found in many synth is to raise the minimum env depth for vel = 1 (instead of lowering the maximum env depth for vel = 127 as I think is currently implemented).
The suggested approach lowers the envelope responds to velocity by the same amount as the current implementation but with the added benefit that overall the volume and cutoff stays closer to the programmed values i.e. the sound you get when velocity is turned off.
What do you think?
-
Many great ideas in this thread. I particularly would welcome the option to invert the filter envelope.
In addition I like to suggest to maybe revise the filter and amp envelope velocity depth parameters slightly. Currently, if I’m not mistaken, the max possible envelope depth is scaled down by the velocity depth parameter. As a result the sound of any given preset is getting duller and quieter when lowering the vel depth parameter. An alternative implementation found in many synth is to raise the minimum env depth for vel = 1 (instead of lowering the maximum env depth for vel = 127 as I think is currently implemented).
The suggested approach lowers the envelope responds to velocity by the same amount as the current implementation but with the added benefit that overall the volume and cutoff stays closer to the programmed values i.e. the sound you get when velocity is turned off.
What do you think?
I already submitted a detailed request for this very thing as I agree with you. Here is what I sent:
Hi,
this point is aimed primarily at the Prophet 10 but applies to other devices too.
It probably comes down to a question of design philosophy but for me the velocity-to-envelope-depth control seems backwards. When setting up a patch, I’d want the sound made when the velocity button is on and a key is struck at maximum velocity to always be exactly the same as the sound made when when the velocity button is turned off. So maximum velocity from the keys should always trigger the depth set by the envelope depth knob, irrespective of the velocity-to-envelope-depth value set. The velocity-to-envelope-depth value, I feel, should simply scale the depth achieved by the lowest velocity. So a value of 0 velocity-to-envelope-depth should sound exactly the same as when the velocity button is simply turned off, i.e. no velocity scaling is being applied.
Implemented as above makes sound design easier as one can program the sound without velocity first and then, when adding it, only one variable is being altered as the depth value is set, namely what depth the lowest velocity produces; maximum velocity will always achieve whatever was initially programmed. As soon as the velocity switch is turned on and a depth of anything other than maximum is set, the originally programmed sound is unobtainable without having to adjust the envelope depth knob to compensate. This obviously causes difficulty if a desired sound already has the envelope depth knob at or near maximum before the velocity switch was enabled.
Furthermore, from a sound design point of view, one may also not always want for the lowest velocity to produce zero envelope depth. Your current implementation unfortunately does not allow for the lowest velocity to produce a non-zero envelope depth when the velocity switch is engaged.
(For reference, my suggestion is how velocity-to-envelope-depth is implemented on synths such as the Moog Subsequent 37.)
Please would you consider changing the implementation as suggested to allow for better control over what happens at the lower velocity values. I realise that there may be some reluctance as it may cause already-programmed patches to sound different. In which case, much as you did with the addition of vintage mode for P6 and OB-6, perhaps you could make the new behaviour be a globally selectable option so that current patch behaviour could be preserved, if desired.
Thanks and best wishes,
_____
Hi Brian,
thanks for your reply.
For the prophet 10, I understand the interface constraints. What I suggested wouldn’t really require anything more than is currently implemented when setting the value - as is the case now, one would simply hold down the the velocity button and use the +/- buttons to set the value between 0 and 127. What I’m asking for is a change to the mathematical operation that determines the envelope depth when it is controlled by velocity. Currently the velocity depth setting determines what maximum envelope depth is at maximum velocity and always maps low velocity to minimal envelope depth. I’m asking for it to be changed so that maximum velocity is always mapped to the amount set by the envelope depth knob and that the velocity depth control instead controls what the minimum envelope depth is at low velocity values. So with velocity depth at 0, envelope depth at minimum velocity would be the value set by the envelope depth knob. With velocity depth at 127, minimum velocity would equate to envelope depth of 0.
Basically, the velocity setting currently alters the maximum envelope depth value achieveable, minimum is always zero. Instead I’d like it so maximum value achievable is always fixed at the value set by the envelope depth knob, and the velocity setting should choose what the minimum velocity value achievable is.
The only interface addition would be in the globals menu (page 3, where there are at least 5 unused slots) to choose between the current implementation and my suggested implementation.
Yes, much easier with a screen on Pro 3.
Best wishes,
-
Sample and Hold please
-
I would like to see MPE support if possible :)