X-fade doesn't save when saving sample + other stuff

[jasonrwong5]

many times when i save a sample or a program, my x-fade value resets to 0 and it doesn't save to the new file (when copy content is checked) or the original (copy content unchecked).

also when importing a file to the key mapper, i drag to a key and then hold shift and drag on the keyboard to the highest (or lowest) key where i want my region to end. this doesn't work.

also when adjusting numerical values i didn't see a difference in coarse or fine-tuning when holding shift. on the modulation table, i set it to the frequency cutoff alot and i always just have to type in 24000 in the amount field. is there a way to do this faster?

i like this sampler a lot it's really great and thorough and i appreciate you all putting out a free version of it. it took a minute to understand the basics and i'm still learning it but i've enjoyed it a lot. thanks!

[elcallio]

many times when i save a sample or a program, my x-fade value resets to 0 and it doesn't save to the new file (when copy content is checked) or the original (copy content unchecked).
 

Partially verified. X-fade is saved in WAV file, but restoring it overwrites the value due to legacy attribute processing. Need to special case when it is explicitly set by TX save.

also when importing a file to the key mapper, i drag to a key and then hold shift and drag on the keyboard to the highest (or lowest) key where i want my region to end. this doesn't work.
 

You are dragging a sample without root info. The manual is somewhat misleading; Only samples with root/bounds info are handled by explicit bounds drag. This is due to non-root:ed samples (i.e. mapped into fixed range key width) _can_ be mixed with samples that have either root _or_ explicit bounds set, in which case, if the outer bounds are respected, you can get weird behaviour/results.

On the other hand, this is perhaps a less likely use case, so it might be worthwhile to do an optimistic approach key range expansion in this case.

also when adjusting numerical values i didn't see a difference in coarse or fine-tuning when holding shift. on the modulation table, i set it to the frequency cutoff alot and i always just have to type in 24000 in the amount field. is there a way to do this faster?
 

Key frequency modulation (and other similar) will adjust in increments of one (1) cent by default, and 10 cents with shift held. Similarly, drag-editing the value will apply a factor of 10 with shift.

Obviously, when entering larger numbers, this might be tedious, but I prefer not to drop fine control here.

Also, frequency modulation are in key cents, which means 24000 is 20 octaves. Perhaps a bit much...

[elcallio]

New version up which fixes the crossfade loading, plus adds regions range mapping for non-rooted samples.