I'm just glad that at this stage of my learning Pianoteq I'm only using Stage   So I don't have so many silly questions to ask!

thanks,

Ian

Trying to word it differently: Freezing applies to the parameters currently in the GUI, NOT to those in the saved presets.

Or to put it yet another way: freezing only modifies the behaviour upon loading a preset. Nothing prevents you from altering a freezed parameter after freezing it. The 'frozen' state just means that it is not overwritten when you switch presets.

I'll try to make an example, maybe that clears things up.

1. Set the main volume to 0dB.

2. Store the current preset.

3. Set the main volume to -10dB.

4. Freeze the volume parameter.

5. After freezing, change the volume to -20dB.

6. Load the preset you stored in the beginning: the volume will stay at -20dB.

7. Unfreeze the volume.

8. Load the preset again: the volume will be at 0dB.

Freezing is not yet another snapshot of the value. In the example above, when freezing the volume, Pianoteq does not save the -10dB and switch back to this value when changing the preset. I repeat: freezing does not store a parameter's value: it just changes that parameters' behaviour.

Especially in the volume example, any different behaviour would be nonsensical, since it effectively would force me to 'refreeze' after every volume change, or have Pianoteq snap back to the last frozen volume whenever I switch presets. Were it to actually work like this it would be quite annoying, actually, making the feature useless in my eyes.

I read your reply several times trying to see whether you had understood my situation.   Your reply is basically saying how Pianoteq SHOULD work and I agree with you.  It is how I'm finding it in practice that differs.

If as you say a parameter like key-on velocity curve has been frozen why then if I change the curve, without saving anything, does Pianoteq retain my change after I open a new voice?  In other words it was not frozen after all

Ian

When you select a preset, this preset potentially includes values for all parameters Pianoteq knows. But when you 'freeze' a parameter, you tell Pianoteq that upon loading a preset, the currently selected value should not be overwritten.

For example, I have frozen the main volume, the equaliser and all the velocity curves. When I set the volume to e.g. -10dB and I store a preset, then this preset includes the -10dB volume setting: fair enough. When I load this preset and the main volume is not frozen, -10dB are restored regardless of what was set at that moment. When I freeze the volume, Pianoteq does not touch it anymore upon loading a parameter-- at all. So if I set it to-35dB and select my preset with the stored -10, the volume will remain at -35dB.

In the case of the velocity curve the behaviour is essentially the same. The preset contains a certain curve, and Pianoteq's current state also contains a certain curve. The two can be the same, but generally won't. Upon selecting a preset, only one of two things can happen: (1) the current velocity curve is replaced by the curve in the preset, or (2) the current velocity curve is kept (i.e., the velocity curve is frozen).

Certain parameters have their own preset manager, so you can save mini-presets just for a certain parameter or parameter set. The velocity curves are one example (one should only note that note-on, note-off and pedal velocity curves are treated as one group); the equaliser is another, as are the effects. But they will still be stored in a 'complete' preset, and the same behaviour happens when you freeze them.

Edit:

So I tried again but this time instead of moving it manually I pressed the curve rest button so the curve became a straight line.  Moving to a new voice still kept the straight curve even although the velocity was previously frozen.

Ian

I then used my backup file to restore the calibration.  I then hit calibration reset and the display showed the straight line velocity curve.   I then changed the voice.  Again the calibration stayed this time with the straight line.

Why does this happen if I have the calibration set to be unchanged?   Other parameters do stick.

Ian