Page 1 of 1
Grand: synth decay and attack settings not preserved??
Posted: 11 Jan 2020, 13:58
by JazzKars
Hi all,
Just received my Grand. It's awesome.
I'm trying out a piano & synth (strings) layer in LIVE mode. Strange behaviour. I suspect a bug as this is totally different than the Piano 3 behaviour:
When I change attack and decay settings, these settings are not preserved when switching to another synth instrument. So in case of the strings, I'm setting a slow attack and long decay, but this setting is reset when switching to another string sample, making it almost impossible to change strings while playing, as you have to set the decay and attack everytime when switching to another synht/string sample.
This makes working with the synth (especially strings in my situation) very difficult.
Is this the normal behaviour? On my Piano 3, the attack and decay settings where preserved, no matter which strings I choose.
Thanks
Kars
Re: Grand: synth decay and attack settings not preserved??
Posted: 11 Jan 2020, 14:45
by Mr_-G-
Hm... I wonder if those are the parameters that the new smp3 format has incorporated? (i.e. they are stored in the sample file itself, and hence do not respect the synth settings?). When you load a new sample, those parameters are set from the file.
I hope that is not the case; it would be surprising if Clavia did not anticipate this problem.
Re: Grand: synth decay and attack settings not preserved??
Posted: 11 Jan 2020, 15:04
by maxpiano
I think the point is that ON NG/NE/NP the user needs to save the changes at Program level, the Synth Sample otherwise uses the defaults saved in the .nsmp3 (which cannot be overwritten).
So I guess the solution is to save the changes as part of the Program(s) that synth sound is being used in: have you tried that?
Re: Grand: synth decay and attack settings not preserved??
Posted: 11 Jan 2020, 15:11
by baekgaard
Yes, this is because the nsmp3 format holds those parameters and they are loaded when you select a new sample. On the NS3 you can choose to either load only the sample of the sample with parameters, but I don't remember a way to do this on the NG or the NP4.
Re: Grand: synth decay and attack settings not preserved??
Posted: 11 Jan 2020, 15:13
by Mr_-G-
Thanks baekgaard, obviously Clavia did think about that.

Re: Grand: synth decay and attack settings not preserved??
Posted: 11 Jan 2020, 16:33
by JazzKars
I'm almost 100% sure this is not the case on my NP3. There, parameters are used on all samples while in the same live mode. I've never saved these parameters to a program.
I don't work with programs, only with live settings.
If this is correct behavior it would be a very, very disappointing thing

Re: Grand: synth decay and attack settings not preserved??
Posted: 11 Jan 2020, 17:10
by Schorsch
Hi, are the samples which you use available in both Sample Library 2 and Sample Library 3? If so it would be interesting to see what happens if you take the sample from Sample Library 2 (in .nsmp format) and load it with Sound Manager into the Grand. By this it will be converted into .nsmp3 format, but maybe it does not include and load any pre-settings which are availble in the native .nsmp3 version of this sample from Sample Library 3?
Re: Grand: synth decay and attack settings not preserved??
Posted: 11 Jan 2020, 17:17
by baekgaard
Double post deleted
Re: Grand: synth decay and attack settings not preserved??
Posted: 11 Jan 2020, 17:17
by baekgaard
JazzKars wrote:I'm almost 100% sure this is not the case on my NP3.
Correct. The NP3 does not load the nsmp3 format samples with saved parameter values, but only the nmsp(2) format as @Schorsch says.
The NP4 will load the parameters in the same way as your NG, as does the NE6 and the NS3 (although the latter allows you to choose to load the samples with it without parameters).
Re: Grand: synth decay and attack settings not preserved??
Posted: 15 Jan 2020, 18:42
by JazzKars
I can confirm the NG cannot load the older NMSP(2) format. Does this mean that there's no way to save the parameters to the samples? I'm really disappointed in this. I hope NORD can change this...