Clicking loops
-
- KVRer
- Topic Starter
- 10 posts since 30 Nov, 2014
I am noticing that TX16Wx clicks on loops where other programs do not. For example, I imported sample that I use in Kontakt. In Kontakt with the same loop type and start and end points it loops perfectly. In TX16Wx it clicks. Is there a known problem with sample looping? It doesn't happen on every sample. I have it set to play from Ram.
-
- KVRAF
- 2398 posts since 27 May, 2005 from Stockholm
If you have a sample that does not play back correctly, please send it so I can check what is wrong.
TX16Wx Software Sampler:
http://www.tx16wx.com/
http://www.tx16wx.com/
-
- KVRer
- Topic Starter
- 10 posts since 30 Nov, 2014
Let me know where I can send it (it won't let me attach it here). It is only 130k or thereabouts. I've tried it in two programs and they both loop it fine. The loop is embedded in the WAV but here are the details just in case:
Loopstart: 52045
Loopend: 66749
Looptype: bidirectional
Loopstart: 52045
Loopend: 66749
Looptype: bidirectional
-
- KVRAF
- 2398 posts since 27 May, 2005 from Stockholm
Use any file sharing service, or simply share it from google drive or similar. This forum is filled with examples.
TX16Wx Software Sampler:
http://www.tx16wx.com/
http://www.tx16wx.com/
-
- KVRer
- Topic Starter
- 10 posts since 30 Nov, 2014
Sorry, I was lazy. Here is the link to the file.
https://drive.google.com/file/d/1y5R77q ... sp=sharing
https://drive.google.com/file/d/1y5R77q ... sp=sharing
-
- KVRAF
- 2398 posts since 27 May, 2005 from Stockholm
Thanks for the interesting bug repro.
First off, the sample does not have a bidirectional loop in the wav info afaict, but setting it to bidir does indeed uncover not one but two suble bugs: One that reverse DFD buffer fill in a corner case had badly linked code, causing it to be complete gobletigook (hello c++ type widening), and the second a poor choice of RAM interpolation window filling mechanism for bidirectional loops, which only really manifests on a loop so poor in coherence as this one (and ending right at the end of wave).
Both issues should be fixed in the new build.
First off, the sample does not have a bidirectional loop in the wav info afaict, but setting it to bidir does indeed uncover not one but two suble bugs: One that reverse DFD buffer fill in a corner case had badly linked code, causing it to be complete gobletigook (hello c++ type widening), and the second a poor choice of RAM interpolation window filling mechanism for bidirectional loops, which only really manifests on a loop so poor in coherence as this one (and ending right at the end of wave).
Both issues should be fixed in the new build.
TX16Wx Software Sampler:
http://www.tx16wx.com/
http://www.tx16wx.com/
-
- KVRAF
- 4864 posts since 19 Apr, 2002 from Utah
Yay!! Great news!elcallio wrote: ↑Sun Jun 16, 2019 2:07 pm Thanks for the interesting bug repro.
First off, the sample does not have a bidirectional loop in the wav info afaict, but setting it to bidir does indeed uncover not one but two suble bugs: One that reverse DFD buffer fill in a corner case had badly linked code, causing it to be complete gobletigook (hello c++ type widening), and the second a poor choice of RAM interpolation window filling mechanism for bidirectional loops, which only really manifests on a loop so poor in coherence as this one (and ending right at the end of wave).
Both issues should be fixed in the new build.
C/R, dongles & other intrusive copy protection equals less-control & more-hassle for consumers. Company gone-can’t authorize. Limit to # of auths. Instability-ie PACE. Forced internet auths. THE HONEST ARE HASSLED, NOT THE PIRATES.
