Modartt user forum - PianoTeq7 - Next Step

Re: PianoTeq7 - Next Step

2021-08-13T10:55:42Z

Smilie wrote:

can you change the effect or just switch on/off and fiddle with the parameters of the one already set in the FXP ???

Ah, no, I can only see how to turn each effect on/off and change the parameters. I don't see a way to, for example, swap out "delay" and put "fuzz" in its slot. It would be nice if they could add "effect type" as a parameter. But I still don't see the need for SysEx :-)

Re: PianoTeq7 - Next Step

2021-08-12T17:11:55Z

hanysz wrote:

Smilie wrote:
What you can't map is the effect on/off; type or settings per effect
I can see parameters called "Effect 1 Switch", "Effect 1 Param 1", "Effect 1 Param 2", and so on. Don't these do what you want?

Well spotted - but can you change the effect or just switch on/off and fiddle with the parameters of the one already set in the FXP ???

Re: PianoTeq7 - Next Step

2021-08-11T00:01:53Z

Smilie wrote:

What you can't map is the effect on/off; type or settings per effect

I can see parameters called "Effect 1 Switch", "Effect 1 Param 1", "Effect 1 Param 2", and so on. Don't these do what you want?

Re: PianoTeq7 - Next Step

2021-08-10T17:56:50Z

Thanks for those clarifications Smilie. It's clearer now, although some confusion still remains.

I hear a few specific feature requests. MIDI assignability for some parameters that don't yet have it seems to be the main idea here. That's a very reasonable and easy to understand request, perhaps unnecessarily made more confusing by the suggestion that it be solved using SysEx.

Probably it's clearer to just state the feature request itself, and then leave it to the devs to figure out how it should be addressed? Maybe they'll find that SysEx is a good solution, but my hunch is they'll solve it differently. Either way, if they add it, it gets added, you know?

And indeed, there is a limit to how many CC's and PC's can control the same instance of a plugin, but is that limit really in play here? My guess would be that we aren't even close. Again, I might be wrong or missing something, happy to stand corrected if so.

Re: PianoTeq7 - Next Step

2021-08-10T11:29:08Z

hanysz wrote:

..you can't map the metronome settings...

Yes you can map the metronome start/stop and speed up and speed down through CC and have live access to it.

What you can't map is the effect on/off; type or settings per effect and this kind of thing is usually accessed through SysEx - perhaps my original pole is just too confusing - still I'll let it run just for the fun of it.

Re: PianoTeq7 - Next Step

2021-08-10T08:42:20Z

When you buy Pianoteq, you get both a standalone version and a plugin version (VST/AAX/AudioUnit). The plugin is designed to be used with DAW software such as Reaper, Cakewalk, Garageband, ... With your DAW, you can map any of those parameters to any MIDI CC, TouchOSC or other external device you want.(Except that you can't map the metronome settings -- but that's OK, because your DAW will have its own built-in metronome.) Look for the word "automation" in your DAW user manual.

Basically, SysEx is obsolete now that there are better ways of doing this.

I'd much prefer the Pianoteq developers to keep improving the piano sound, and adding new instruments, rather than spending their time to duplicate features that you can already get via a DAW.

(On the other hand, updating the Pianoteq user manual might be a good idea. When I first bought Pianoteq, I didn't know what a DAW was, and what the VST version was for. I had to learn this from other online forums.)

Re: PianoTeq7 - Next Step

2021-08-08T15:04:27Z

DonSmith wrote:

What's the question?

Is this for me? If so, I guess my question is: We can control PianoTeq's parameters in real-time already, so why is MIDI SysEx necessary?

Sorry if it was unclear in my previous message, I just figure I'm certainly missing something here, and am asking for clarification.

Re: PianoTeq7 - Next Step

2021-08-08T14:43:46Z

What's the question?

Re: PianoTeq7 - Next Step

2021-08-08T13:14:34Z

I think I don't understand the idea, let me check if I get what you're saying.

It seems to boil down to two problems, and the idea that MIDI SysEx messages can solve them. First, some parameters can't be assigned to be MIDI-controlled from an external controller, and second there are some limitations to which devices can serve as controllers?

If that's what you're saying, the first part makes sense to me (but I'm not sure that it needs to be solved with SysEx specifically), the second part is the one I'm not sure I understand.

I gather you want to control PianoTeq 7's parameters from an external piece of gear in real time. Makes sense, but a MIDI-controller with dials/faders for CC's will do that just fine? I'm not completely sure what I'm missing here. Help me to get it.

Re: PianoTeq7 - Next Step

2021-08-08T11:00:44Z

Certainly would be very helpful for people who use Pianoteq for live performances - would make it much easier to make modifications on-the-fly without need for a mouse or a really small finger to make modifications to the UI on a tablet, etc., all while playing tunes in public in a dark space with both hands [much of the time] on a keyboard.

PianoTeq7 - Next Step

2021-08-08T10:34:26Z

Most MIDI products have a MIDI-Implementation chart and allow access via MIDI to internal parameters - this is currently possible in a limited way via PianoTeq and it is set on a parameter by parameter basis via CC commands.

I would love to see SysEx implementation and be able to set [hitherto unavailable] parameters such as:

• temperament diapason value
• temperament preset 1-24 / custom
• equaliser on/off
• equaliser preset 1-16 / custom
• effect slot 1-5 on/off
• effect slot 1-5 type
• effect type parameter value(s)

perhaps by using something like: TouchOSC to control the programme from another device (iPhone, iPad, PC, Mac, Android) for example.

In other words, gain total control over the shape and sound produced in PianoTeq in real time.

Why SysEx? and not the limited number of CC commands that already exist - there's your answer - 'limited.'