Bug 302 - LinuxSampler sfz default fade in?
Summary: LinuxSampler sfz default fade in?
Status: RESOLVED FIXED
Alias: None
Product: LinuxSampler
Classification: Unclassified
Component: other (show other bugs)
Version: 2.0.0
Hardware: PC Linux
: P5 normal
Assignee: Christian Schoenebeck
URL:
Depends on:
Blocks:
 
Reported: 2017-02-14 10:44 CET by Nicola Pandini
Modified: 2017-02-14 15:09 CET (History)
0 users

See Also:


Attachments
white noise test (24.49 KB, image/png)
2017-02-14 10:44 CET, Nicola Pandini
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nicola Pandini 2017-02-14 10:44:47 CET
Created attachment 85 [details]
white noise test

I think there is a small fade in when LinuxSampler plays a sample.
I only notice that if I play samples that have distinctive sound like frame drums: the very first part of the sample (i.e. the sound of the finger hitting the skin) is not audible, but if I play that file in Audacity I can hear it correctly.
I made a test recording white noise from LinuxSampler and I take a screenshot that shows the 1~2ms fade in.

I tried .sfz solutions with a one second of white noise:
<region> sample=./1sNoise.wav key=36 loopmode=one_shot
<region> sample=./1sNoise.wav key=37 loopmode=one_shot ampeg_attack=0

and another one with a one second of silence + one second of white noise:
<region> sample=./1sSilence-1sNoise.wav key=39 offset=44100 loopmode=one_shot

with same result.
Can you confirm this? Is this editable?
Thank you.
Comment 1 Christian Schoenebeck 2017-02-14 15:08:41 CET
Looks like a bug in the SFZ engine that just recently had been fixed. Checkout the latest SVN version of LinuxSampler, which should fix this issue for you. For more details have a look at the following discussion about this issue on the mailing list:

https://sourceforge.net/p/linuxsampler/mailman/linuxsampler-devel/thread/1934141.ZpXSLkKDZj%40silver/

Please note that as I pointed out in my last messages of that mailing list thread, there might still be SFZ files where this bug could still be encountered. At least from what I see from the SFZ engine code: Specifically if there are volume modulators defined in the SFZ file which shall become active after a certain delay. If you stumble over one of such cases let me know!