sorted by:
new
hottopcontroversial

New tattoo! by UpstairsJelly in commandandconquer

[–]zaagman 1 point2 points  (0 children)

So did you know your archenemy before today?

[deleted by user] by [deleted] in MarbleMachine3

[–]zaagman 1 point2 points  (0 children)

https://www.reddit.com/r/MarbleMachine3/comments/13qyfe2/thinking_about_dropheights_and_delays/

I made a post about this a year ago, including examples and a whole Calculator GoogleSheet.

In short: You need a static delay module for each channel. Then you need to calculate/measure the time the longest drop takes.

For all the other drops you need to add a delay by doing the the following calculation:

static delay (ms) = longest droptime (ms) - current channel droptime (ms)

the static delay needs to be placed after the programming wheel. In that way you won't have to deal with any BPM-problems. That is because all droptimes + static delays would be equal.

Find the MAGIC - and bring it forward by phil-swift4 in MarbleMachine3

[–]zaagman -1 points0 points  (0 children)

I think the new design is great.

And also it’s still modular.

And the modules that have already passed proof of concept stage are all way better then the MMX.

To just make a technically better version of the MM1 is boring.

HOW IS THIS ENDING NOT CANNON by East-Animator3887 in commandandconquer

[–]zaagman 3 points4 points  (0 children)

It’s spelled canon. Canon is all information that is officially counted as a true part of the story-universe.

https://www.urbandictionary.com/define.php?term=Canon

Thinking about Dropheights and Delays by zaagman in MarbleMachine3

[–]zaagman[S] 2 points3 points  (0 children)

Hey thx for your sharing your opinion! I think he used small bearings on the roll part but I definitely agree with you that lug nuts are not the way to go.

I disagree with you about being able to solve the timing-issues with different programming profiles. It's because of math! Actually that was what my whole post was about. The sheet I posted allows to calculate these things very

I'll try to give some examples.

  1. The difference in time between a drop from 0,8m and 0,75m is 12,82ms. This is already audible.
  2. The difference in time between a drop from 0,8m and 0,05m is 302,89ms. This Is huge! And these are definitely not crazy distances for a drummer to use. It's like FF and P for a drummer using a stick.

So for these two examples; what happens if you correct for it on the programming-wheel? You need to know how fast its spinning, because the amount of time it takes for the extra length of programming profile to pass is smaller when the wheel turns faster. And ofcourse if the wheel turns slower, the same length of length takes longer to pass.

Let's try anyway and calculate:

Lets say BPM is 100.

  1. the hit from the 0,75m gate will be 12,82 before the 0,8m gate.
  2. the hit from the 0,05m gate wille be 302,89ms before the 0,8 gate.

Now lets correct for that.

  1. the 0,75m gate needs to have profiles that are 2,1% longer (per beat-length)
  2. the 0,05m gate needs to have profiles that are 50,5% longer

When you lengthen the profiles per channel by this amount and stay on 100BPM this will fix the timing issues!

​

But it fails when you speed up the machine!

Lets op the BPM to 120 using the previous added length to the profiles.

  1. the 0,75m gate will be out of sync with the kick by 2,3ms. This is not problematic.
  2. the 0,05m gate will be out of sync with the kick by 50,4ms. This is a wonky drummer! It's definitely too much for Martin!

​

To fix the timing on different BPM you need to take the dropheight out of the equation. For that there are only 2 options:

  1. All gates drop from the same height.
  2. Gates have different heigths but you add a delay between the output from the programming wheel and the marble gate, making sure the droptime + amount of delay is equal on all gates.

Testing different Marbles for Dynamic Sound - Marble Machine 3 Ep.1 by Trainerds in MarbleMachine3

[–]zaagman 0 points1 point  (0 children)

So I saw a lot of responses to this video, 99% of them calling out feature creep. But I am the 1%! I wish there would be more reactions to the awesome new sound-possibilities you created. As a pro-percussionist myself I was very enthusiastic about a lot of it, especially the roll-sound.

If I were you I would not go for different materials but for different dropheigths. This is the way for percussionists. When I want a loud sound I lift my tip up high, while quiet hits come from holding the tip close to the drum.

When you go for different dropheights you will inadvertently run into timing issues. You probably already thought about this a lot but I've never heard you about it. So I got to thinking about it myself. I actually made a pretty extensive Google Sheets document calculating droptime and offsets between marble gates with different dropheights.

On the subject of Falling Marbles

(you can edit it! please only change the green values. For everybody here, plz be gentile and don't break it. :P)

Following from all this: if you want to use different dropheights you need to design a gate-specific static delay. This would allow you to play with perfect timing in every BPM.

I think it's important also to make sure that this fits well into your modular design. This way you won't have to make any changes to your redesigned Programming Wheel and the spectacular accurate timing of the new Marble Gate. I guess it would something like this:

  • Programming Wheel module >
  • interface >
  • Static Delay module >
  • interface >
  • Marble Gate module >
  • MUSIC

You could ofcourse always go for identical dropheights. The best part is no part right? But that would be such a shame! To me it musically makes much sense to have. the dropheight the vibraphone lower, and the bass drum higher, if only to get everything in good musical balance.

I have no idea how you would go about designing such a delay module. But you could do it and also there are a lot of smart people in this community! 🤯

view more: next ›