No prob, good luck with the release.
Have you tried allowing for visual feedback to be disabled? I was a
bit surprised that in Borce's "my drums" app it actually made a
noticeable difference. Of course, the same may not apply to your code.
One way I can consistently reproduce the issue - hit a snare twice
quickly in succession. Then wait and hit the snare again. The third
one will be truncated regardless of how long it's been since the first
two. This is probably only observable with a cropped snare with a very
quick attack/decay transient (it's not as noticeable with some
samples, even snares).
I'll try to record an example later if you have trouble reproducing
it.
On Jan 25, 7:24 am, Ivan Memruk <
iwan.mem...@gmail.com> wrote:
> The sound cuts itself (if you hit a pad twice the second sound will
> immediately stop the first one) but it will never start playing from the
> point other than 0 (start).
> So if that's the case, please report us how exactly that happens.
> However, please check that your sample does not have silence at its
> beginning, which might be confusing in this situation.
>
> Latency has been our top priority. However, it is still different on various
> devices that run various background processes etc.
>
> Yes, we will have WAV export for sure.
>
> Sorry for a late answer - been working on the release version a lot ;)
>
> >
su-preme-mpa...@googlegroups.com<
su-preme-mpa%2Bunsu...@googlegroups.com>