Noisemaker 2.57 automation of pulldowns malfunction

[david.beholder]

On Windows XP 32bit, Cubase SX3 and Automap v 3.4.1 having problem with automation of pull-down menus.

When I'm trying to record automation for filter or destination of ad envelope
altho filtertype and freeaddestinaudio it receives value more than 1 but Cubase doesn't puts 1 instead.

Automap doesn't allow me to have such high value (>1) too, so it became permanent one.

It looks like during initialization of automap parameter there's something like boundaries, that are set between 0..1 instead of say 1..6, that's why cubase disallows higher values

This behavior is consistent with every pulldown menu. All other controls (knobs, faders and sync button) are working ok.

Thank you for really nice synth, sounds damn good, have to admit it.
Actuall, it was mentioned recently by Urs as 'only competitor to U-he Tyrell'.

[ToguAudioLine]

On Windows XP 32bit, Cubase SX3 and Automap v 3.4.1 having problem with automation of pull-down menus.

When I'm trying to record automation for filter or destination of ad envelope
altho filtertype and freeaddestinaudio it receives value more than 1 but Cubase doesn't puts 1 instead.

Automap doesn't allow me to have such high value (>1) too, so it became permanent one.

It looks like during initialization of automap parameter there's something like boundaries, that are set between 0..1 instead of say 1..6, that's why cubase disallows higher values

This behavior is consistent with every pulldown menu. All other controls (knobs, faders and sync button) are working ok.

Thank you for really nice synth, sounds damn good, have to admit it.
Actuall, it was mentioned recently by Urs as 'only competitor to U-he Tyrell'.

I know that issue. Will try to find a solution, but maybe its difficult without affecting existing presets. There is a chance to fix this for midi CC data, but no chance for the automation itself, i think.
Will take account to this problem when i make new plugins. Thanks for the info and it makes me happy that Urs like the plugin, he helped me a lot to make the different filter types and a clean triangle waveform

[david.beholder]

I know that issue. Will try to find a solution, but maybe its difficult without affecting existing presets. There is a chance to fix this for midi CC data, but no chance for the automation itself, i think.
Will take account to this problem when i make new plugins. Thanks for the info and it makes me happy that Urs like the plugin, he helped me a lot to make the different filter types and a clean triangle waveform

Thanks for quick response.

Well, may be it make sense to do some converter old format fxp -> new format fxp. I can even take myself c# or java and do it myself if you point me on necessary data.