Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

relationship between user/computed BPM for samples and patterns #45

Open
rvosa opened this issue Apr 1, 2021 · 4 comments
Open

relationship between user/computed BPM for samples and patterns #45

rvosa opened this issue Apr 1, 2021 · 4 comments
Labels
documentation Improvements or additions to documentation hardware Hardware Issue

Comments

@rvosa
Copy link

rvosa commented Apr 1, 2021

Hi Matthew,

first of all: bless you for making this app! I think this is going to be very helpful so I salute you for putting your spare time into this. I don't strictly speaking have an issue, but just a confusion.

I simply do not understand how the SP deals with the BPM of samples, how I can affect that in your app, and how this interacts with the BPM of my sequencer patterns. My workflow is as follows:

  • I compose patterns in Ableton live and export every instrument/loop warped to the same BPM (130)
  • I assign these loops to different pads, and the SP seems to recognize they're 130BPM in the display
  • I then sequence the loops in quantized patterns

(Unfortunately, I've been bugged a little bit by how the timing when triggering these loops in a quantized pattern seemed sloppy.)

Being new to your app I was surprised by a couple of behaviors of the SP. Apparently, the machine doesn't precisely compute the tempo: when I read the SD card after it's passed through the machine, I noticed that your app shows the computed BPMs are 129.9 according to the SP. The machine is wrong because the loop lengths are surgically precise to the same length as warped by Ableton.

So what is going on here and what should I be doing? What happens under the hood when I set it to 130 in the BPM fields? What do I do for tempo mode?

Thank you very much for any explanation you might be able to provide.

Cheers,

Rutger

@MatthewCallis
Copy link
Owner

How long are your loops? I can try recreating this this weekend to help better explain it.

@rvosa
Copy link
Author

rvosa commented Apr 1, 2021

8 bars @ 130 bpm. Thanks!

@MatthewCallis
Copy link
Owner

MatthewCallis commented Apr 4, 2021

I'm noticing the same issues, I believe it has to do with the internals of the machine and I don't see this documented in the manuals (only the mention of even and increments by 3 at higher BPMs which doesn't seem to be the case)- the values are written and read exactly as shown.

I will need to run some tests to figure out exactly what it happening. Thanks for bringing this to my attention, this is actually really interesting. 🧐

@MatthewCallis MatthewCallis added documentation Improvements or additions to documentation hardware Hardware Issue labels Apr 4, 2021
@rvosa
Copy link
Author

rvosa commented Apr 5, 2021

My pleasure 🙂 I wonder if this is simply a type of rounding error?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation hardware Hardware Issue
Projects
None yet
Development

No branches or pull requests

2 participants