Device Details

Great idea! It seems that the hold button is inactive. At least for me. Win 7 & live 10.04. Thanks for sharing!

I appreciate your feedback!

Unlike MIDI's hold (CC#64), you must keep notes on to continue bouncing.
With HOLD on, the device keeps bouncing after bouncing time has reached Minimum knob's time.
With HOLD off, bouncing ends when the time has reached Minimum.
I am considering to add this to the description or change "Hold" label.
Or should be to add MIDI-like hold function?

HOLD's default value is off intentionally and I checked again that
the button state is saved in Live sets and it functions like above.
In Live 10, may the button seem to disable (grey color) or unable to click?

I thank again for your feedback and sorry for my poor English..

hi, something weird on my max/ableton - the buttons on the display dont have the text visible. I checked the device and maybe the colors aren't saved correctly - "Label Text Color" is black, so had to change it.
Windows Ableton 10.1.13b1 (beta)
Max 8.1.3

Device works well and animates very nicely (compared to JBouncingBall 0.1 by frosty) .
I wish there was another mode that creates the triggers just on note on.

Actually its very interesting the way it is now too, now that I understand how to use it a bit more. The way you designed it allows easier programming of the effect without having to change device settings or mute the effect.

another suggestion:
Maybe Velocity drop off could be 0-200%

also would be cool to have maybe 4 or more mappable controls so you can automate parameters of an instrument

Took a look at the device and the mappable controls would have to parse the right note to trigger the value. I'll see if i can make a companion device that reads a particular range of midi note and velocity to a mappable control.

*also forget the velocity thing, unnecessary

was very easy to add mappable parameters with modulat from isotonik actually..
thanks again for device, sorry for spam!

@hatyn Thank you very much for great informative feedbacks!
I can't make quick reply because I am not native for English.
It is very pleasure to get many responses, anyway.

Now I understood the device's display problem in Max 8.
Because "Label Text Color" property/message was added in Max 8, the problem is not fixable including Max 6/7 environment.
I decided to forget label display mode of live.text objects and change to default display mode.
The velocity Dry/Wet calculation may also have a problem and be considered to find a solution.
So sorry for inconveniences. The fix update will come soon.

> another mode that creates the triggers just on note on
I have been considering that, but I decided to stop bouncing with note off
to avoid the risk that the device produces uncontrollable numberless notes.
I keep to consider true MIDI-ish hold function.

> Maybe Velocity drop off could be 0-200%
I have been considering to implement as "inversed bouncing" mode for a future update.
("Inv" button is hidden in the patch and automation list, as you saw)
It seems more intuitive that bouncing becomes inversed at Rebound parameter exceeds 100%. I am considering that method.

> JBouncingBall 0.1 by frosty
I searched the device library once but I couldn't find a similar device.
(once the device name was "bounce echo" and I searched for "bounce" or "ping pong")
Bouncing Ball 1.0 by aminoplacid seems predecessor of frosty's.
I guess the devices are another approach but might be informative.
Thanks again for the information!

> mappable controls
It seems a higher charenge for me because I never tried live.object/live.path, but I wish I could develop as an another device.
It is very pleasure that this device contributes someone's creativity!

Amazing Job h1data! This is awesome. I look forward to your next creation!

I upload the device which includes live.text's display mode and minor refine.
Because I still don't own Live 10/Max8,
would you please inform if this update fixed the display problem in Max 8?
Thank you for your feedback.

@AYA, thanks again for your comment!
After read M4L production guidelines (which were updated in 2020, by the way) ,
I realized several issues in my previous devices.
I would like to deal with those for a while.
I still have some other ideas which are not formed properly yet, but I wish I could make it happen someday!

Some elemental language mistakes in midnight...
I just uploaded the device which changes live.text's display mode and includes minor refine.

Aaaaaay perrillo rifado!! tas cabrón mijo! (very cool device, nice work!)

I have mentioned that velocity wet/dry calculation might be buggy, but I checked before the release of 1.04 and confirmed it's okay.

@Hacktive, ¡Gracias por el comentario! Espero que este perrito rifado te haga disfrutar.
(sorry for a reply completely relied on Google translate, but stay safe folks!)

This is a fun little M4L thing

This is a REALLY elegant implementation of a "bouncing ball delay"-type MIDI effect! I've tried others that were harder to use, but this is easy to dive into — PLUS it's polyphonic! Thank you for sharing this, and I encourage you to keep creating M4L devices.

@Torley Thanks for your words!
It is my pleasure to share stuffs which solves my own demands.
And hope someone use it for unexpected way!

@Syn Thank you for making a comment for my devices! I like little devices too.

@h1data I continue to enjoy "bouncing notes", thank you again for this gem.

Is there a way to set the total duration of the playback? For example, if I want to clamp/restrict bouncing notes to end after 4 bars? Right now in Ableton Live, I'm mainly doing some guessing and then using warping afterwards to constrain the length.

It would be great for transition effects and ramping up intensity if the total length could be specified.

Also, is there a way to reverse the direction, so that it starts out bouncing very quickly but then gets slower?

@Torley Thanks for your feedback!

I am sorry but there is no way to change note duration except changing 'Minimum' knob or releasing the original note.
I had never considered limiting note duration by elapsed time.
There might be several ways to implement it, so I would like to share images somehow.

Reverse or inverse mode is the most required feature, I understand.
Perhaps I will update after Live 11 released...?
(I have to research or recreate my past patches..)

Hi, I love this device, but use an older update because of the visual bug in the new one when the rate slows down, After a certain point the ball gets spasms.

@nikitaklaartje I appreciate your report!
Sorry, but I cannot reproduce the situation with my 10yo PC.
Could you tell me the version number that works fine?
Further information like captured video is welcomed.

It may not matter, but I remind about stroboscopic effect.
It would depends on the minimum bounce time
and the refresh rate aka FPS of your monitor display.

I had a plan to make a MIDI Generator version of this for months, but I found a suitable device in the official MIDI Tool pack.
Try Phase Pattern if you want to generate bouncing sequences in a fixed duration.
https://www.ableton.com/packs/midi-tools/

@h1data I'm glad you continue to be active and reply to comments. It's funny because I was asking the Phase Pattern creator if he'd make a realtime version of it (and I adore it too)... it's funny because since my last comment, I ended up using that for some bar-locked transitions.. and in recent hindsight, I rediscovered bouncingNotes! I'll have to set up a new MIDI record setup so I can grab clips for editing.

I experience momentary freezes on macOS Ableton when I have HOLD on and Minimum = 1.00 ms in an arrangement where a lot is going on with other MIDI tracks, but maybe that's "expected" due to the sheer note density?

@Torley
Yes, but it depends on the instruments after this effect and the load of your CPU.
Please let me know if recorded MIDI tracks do not cause freezes in the same setup.

Because this has no bouncing limit like the official bouncy one,
you should freeze your track to audio when there are too many loads.

P.S. When the MIDI Tools were introduced, I thought it was time to finish the homework from you.
However, I was not focused enough to accomplish it before Phase Pattern arrived...