On Wednesday, July 19, 2017 10:27:47 you wrote: > Hi, > I noticed that years ago, but never been able to investigate it, thanks for > fixed it. (I used loopmode=one_shot to partially resolve this) While you > are watching the EG behaviour, could you please check the ahdsr ramps? > Weeks ago I started to write documentation for these opcodes, and I noticed > two things I don't know are corrects: 1. Ampeg_decay value should be the > time (in seconds) the AMPEG envelope takes to go from "hold" to "sustain", > but actually is shorter. 2. Ampeg_release ramp is not linear, while attack > and decay are linear.
No idea about those two. Maybe Andreas can comment on this? It could be a left over from the gig engine's EGs. Because the sfz engine was originally "branched" from the gig engine and then elements were replaced one by one for the required, expected sfz behaviors. Since I am going to address the other EG issues mentioned by me as configurable options on gig file format level, I take from your response that we must also address this for the sfz engine, right? If yes, are there precise suggestions for sfz opcodes? CU Christian ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
