This would still result in upsampling, thus creating unecessary data, wouldn’t it?
Unless… I should probably convert to 48kHz in ffmpeg and only THEN do the slicing in logic. That would be more reliable, I guess.
1 Like
Yes, this is exactly what’s happening here.
1 Like
Maybe you missunderstood me here. What I wanted to say: As long as the music in the sample I use is quantized, the auto-slicing of the DT works for me. I have samples where the single hits are not matching a hard grid (because it was recorded live without klick and with swing etc). In those cases slicing it in a fixed amount of even sized chunks doesnt do the work. For those samples people ask for manual slicing for ages. The DT Alternative is Trigvalueing startpoints.
Yes.
Can’t Logic import and convert different rates ?
Theoretically DT2 equally divide the sample according to slice grid, whatever BPM is.
If I remember well, DT1 use zero-crossing detection, so results can differ.
2 Likes
That was my understanding as well.
1 Like
As DT2 isnt doing zero-crossing detection because of Stereo, the dividing part should be more accurate than the DT1 version.
1 Like
Because of wavetables too.
Needs to be equal.
An option for zero-crossing would be interesting though.
Sure.