Have a feature request or suggestion? Post your idea here!

Post

2 followers Follow
0
Avatar

Toraiz SP-16 not detecting the right number of bars when loading a new sample...

I just bought this lovely machine, it's a fantastic rhytm workstation and finally I can use my brush and jazz swing loops with rides all over the place and flip tempo as I feel like without hickups.

Though most often when I load a sample the tempo is not properly detected, as the Toraiz mis-analyses the number of bars in the sample and instead I get the double tempo and have to manually fix this in the sample edit.

Not a total showstopper, but it's a 1000 euro piece of pro gear, and there's no computer software I've been using that is getting this wrong ever...

Is this already on the list for next bug fix update?

When is the next update planned? I see it was last time in the end of 2019, I assume there's something coming up soon? 

Cheers!

OldKeyJock -:

Official comment

Avatar

Thank you for providing this feedback.  Brush and jazz swing loops are probably the most difficult rhythms to analyze for tempo data because of the very light-touch on bass and snare hits and an irregularity in hi-hat and cymbal patterns.  Add to that a swing or shuffle and it can get tricky to analyze when compared to electronic genres in a wider usage like house or techno... But this is very helpful feedback and I think it would be very helpful for the engineers if they could get an example.  Would you mind pointing me to an audio file somewhere that exemplifies the type of sample which gets mis-analyzed? Also, so to confirm, Ableton for example analyzes the tempo correctly of a sampled loop which Toraiz SP-16 does not?  Unfortunately I am not given information on the product update schedule, but I hope to be able to help at least by facilitating the improvement of the tempo analysis capabilities.

 

Rhythm Droid
Comment actions Permalink

Post is closed for comments.

3 comments

0
Avatar

Hi,

That of course depends on the beat detection algorithm (I work in software for audio myself...), and in this case it fails on quite simple tasks where the beat energy is clearly dividable into proper beats. 

I'm in contact with support already so I'll continue the discussion there.

OldKeyJock -: 0 votes
Comment actions Permalink
0
Avatar

And I got the reply from support here today:

"As simple analysis methods are used for calculation, the number of bars may not be always correct. If a sample with similar BPM or length is used, bars may be shown in different number. The only way to fix these is adjusting the number manually. "

So it seems SP-16 is not using a more advanced detection algorithm, oh well, not a dealbreaker.

OldKeyJock -: 0 votes
Comment actions Permalink