Wavetable Index at 100% Kills Sound
-
I ran into the same problem, I thought it was just something with my particular wt so didn't look into it any further.
-
@d-healey thanks for confirming. I was afraid to call it a bug just because you can hear a fast fade out between 98% and 100% but it's giving me all kinds of problems.
-
@CyberGen I ran into the same bug and also thought this is a issue with my WT. So can confirm
-
It might be something to do with the import process. I have some wavetables that cut off, but others that don't.
Here are two wavetables. For me ffm1 cuts off at 100%, while ffm2 continues to produce a sound.
https://github.com/publicsamples/Shapey/releases/download/0.1.3/WaveTableTest.zip
When I get a chance, I'll play around with original wavs I used and see if there's some obvious discrepancy.
-
@modularsamples Interesting, I tested your WTs and as you said one of them does not cut off. I suppose it could be one of several settings in the conversion to wavetable. Possibly the number of slices or even the FLAC compression? I'll start importing with different setting permutations, hopefully if I'll get lucky.
thank you. -
@CyberGen So yeah, Slices.
I've successfully converted 3 different waveforms that don't cut off. Below the settings that are working for me.
Thank you all.
-
@CyberGen New findings update: Even though changing the slices setting had initially yielded positive results, it was not solving the problem 100% of the time for me. After much trial and error I found a better fix by going into the sample editor window and moving the sample end just a few cycles short from the very end. This has been giving me consistent wavetable all the way to the end.
Hope this helps. Cheers.
-
-
-
@CyberGen Glad you found a way to make it work, although it's sounds more like a workaround rather than a fix... @Christoph-Hart?
-
@ustk you are right. It’s a not a real fix. But a momentary workaround. I was too eager to mark something as solved!. I’ll change it back to question.
-
-
@CyberGen Thanks, it worked. It's as if the wavetable conversion were capturing a longer SampleEnd than the real one and "recording" an empty space. Seems like a bug.