[Repro-1] Public Beta

[Urs]

I noticed the mod wheel position is not saved as part of a patch.

Given that the "wheel" modulation path is a fairly fundamental feature to some patches, as it potentially controls a bunch of modulations - should the current mod wheel position be persisted as part of the patch?

I'd argue yes, as already I saved a patch, and on recall, found it didn't sound like it should, and I had to re-find the mod wheel position to get back what I expected...

I'm not sure. I'd argue that yes, for a Minimoog which has the ModWheel as the only contribution to modulation depth I'd agree, but the Pro-One also has the direct path. Not sure where to draw the line.

But okay, I'll happily consider it for a future update.

[EvilDragon]

I don't think it makes sense to save modwheel position in the patch when this is supposed to be inputted via MIDI. Would you save which keys were pressed in a patch? I hardly think so. I vote against.

[ew]

I smell hundreds of support emails if people accidentally change the Osc scaling

Why not just route KeyFollow onto Osc tune in the Perform section?

Ah- yeah, that would be much simpler (and cut down on support requests)

I need more coffee... this waking up thing's not going well today.

ew

[beely]

I don't think it makes sense to save modwheel position in the patch when this is supposed to be inputted via MIDI. Would you save which keys were pressed in a patch? I hardly think so. I vote against.

I think where I'm coming from is that, of course, when used as a performance control, say, for vibrato, or filter cutoff, then I don't really need it saved as part of a patch.

But if I'm making a more complicated patch, which requires both modulation paths doing specific things, then the mod wheel is being used less as a performance control, but more as a specific parameter in the modulation path, which is required for that patch to sound like it's supposed to - ie, lets say you found a sweet spot where the patch sounded amazing - there is no way to store this patch in it's current state, unless you resort to something like noting the mod wheel position in the patch notes.

Yes, we have some options to recreate some mod paths using the matrix, but I guess I feel like the wheel path isn't only to be used for performance, it's just part of the synths modulation architecture, and it just feels to me (at this point) that having patches I've set up that I can't save correctly (ie recalling to sound exactly the same) is a bit weird.

At the same time, I haven't really come across this as an issue in other synths, but then most other synths usually don't have the wheel as an explicit modulation path - there's usually loads of other ways of setting up specific modulations.

Anyway, just giving some feedback of things I've encountered...

[david.beholder]

I noticed the mod wheel position is not saved as part of a patch.

Given that the "wheel" modulation path is a fairly fundamental feature to some patches, as it potentially controls a bunch of modulations - should the current mod wheel position be persisted as part of the patch

I'm not sure. I'd argue that yes, for a Minimoog which has the ModWheel as the only contribution to modulation depth I'd agree, but the Pro-One also has the direct path. Not sure where to draw the line.

But okay, I'll happily consider it for a future update.

I actually agree with beely - for certain patches it would be nice to have modwheel - it's inconvenient in comparison with others but very logical in Repro-1.

I don't think it makes sense to save modwheel position in the patch when this is supposed to be inputted via MIDI.

Nobody is asking for restricting MIDI input - but what's wrong with saving initial position for patch.

Would you save which keys were pressed in a patch?

They do, see sequence tab ))

[seamoss]

My Moog Sub Phatty saves Mod Wheel positions in the patch and it's really nice. It's actually an option that can be checked on or off

[Viktor [TUC]]

Might not be the solution you're looking for, but you can always adjust the modulation depth so that the very top position of the modwheel makes the exact intended sound, that way you don't have to always find the modwheel sweetspot at a difficult-to-find value.

[Elektronisch]

dont know if this has been answered, but are there plans to add 4 voice poly mode like The Legend has ?

Hehe, I answered that in the other thread, but why not?

As it happens, we do have a Prophet-5 now. If we would like to do a poly version, it would be a P-5 emulation. A few features less, less CPU per voice, slightly different sound but mostly the same sonic character. Lush stuff.

However, our schedule is busy. We have loads of construction areas. We do not know yet if and when we go there.

But tempting it is. And the intro offer won't come back for it

"Smells" like Pro 1 might become Pro Ultimate ? That does sound more tempting now

[Urs]

dont know if this has been answered, but are there plans to add 4 voice poly mode like The Legend has ?

Hehe, I answered that in the other thread, but why not?

As it happens, we do have a Prophet-5 now. If we would like to do a poly version, it would be a P-5 emulation. A few features less, less CPU per voice, slightly different sound but mostly the same sonic character. Lush stuff.

However, our schedule is busy. We have loads of construction areas. We do not know yet if and when we go there.

But tempting it is. And the intro offer won't come back for it

"Smells" like Pro 1 might become Pro Ultimate ? That does sound more tempting now

Hehehe, I'm just pre-empting regrets of not going for it now when/if things change later. As in, you can't later say "... but you ruled polyphony out!" - because we only did for this particular plug-in whereas the product might at some point contain more than one.

But as I said. We're quite busy and it won't be decided this year anymore.

[oli67]

Hi. I don't fully understand the Modulation Control panel (section 2.11 of the manual). Can someone please explain the following to me: open the Trumpet preset, look at the Modulation Control panel Mod Fil Env To section: OSC A Freq is positioned to WH. Now move this to DIR instead: no more freq. modulation of OSC A. Why? Looking at the diagram (manual) above section 2.11, the direct path also goes to OSC A freq. modulation.

[Urs]

Hi. I don't fully understand the Modulation Control panel (section 2.11 of the manual). Can someone please explain the following to me: open the Trumpet preset, look at the Modulation Control panel Mod Fil Env To section: OSC A Freq is positioned to WH. Now move this to DIR instead: no more freq. modulation of OSC A. Why? Looking at the diagram (manual) above section 2.11, the direct path also goes to OSC A freq. modulation.

You have to route either Osc B, Filter Env or LFO to Direct in order to make PWM from Direct heard.

So it's a 3 step system to set up 2 distinct modulation paths:

1. Select which modulator you want on Direct or Wheel
2. Select which target you want to modulate via Direct or Wheel
3. Choose the depth of the modulation with the 3 knobs on left and the Modwheel

It's a confusing system at first, but it's been pretty much the most powerful of its time.

[beely]

Hi. I don't fully understand the Modulation Control panel (section 2.11 of the manual). Can someone please explain the following to me: open the Trumpet preset, look at the Modulation Control panel Mod Fil Env To section: OSC A Freq is positioned to WH. Now move this to DIR instead: no more freq. modulation of OSC A. Why? Looking at the diagram (manual) above section 2.11, the direct path also goes to OSC A freq. modulation.

Because there's no modulator on the direct path. You've said "modulate OSC A freq by whatever modulation is on the direct path", and there's no modulator.

For instance, now turn the mod lfo to direct, now the mod lfo is modulating the direct path, and thus any destination also on that path.

[pdxindy]

Might not be the solution you're looking for, but you can always adjust the modulation depth so that the very top position of the modwheel makes the exact intended sound, that way you don't have to always find the modwheel sweetspot at a difficult-to-find value.

When the Modwheel might be controlling multiple parameters, it is not easy to find the exact settings that make that particular sound. I also would like an option when saving a preset to save the modwheel position...

[AnX]

+1 to saving MW position with patch.

[oli67]

thanks @Urs, @beely, got it. I think the manual could be improved at section 2.11 to explain this potentially with examples.