Device Details
Overview
| Name | Version: | Rescale 1.0 |
| Author: | Morusque |
| Device Type: | MIDI Transformation |
| Description: | Remaps midi infos (velocity, note, duration) from one range to another, also allowing different values for the beginning and the end of a sequence. lastest updates : 2025 10 27 > started rewriting it entirely in js instead of hybrid Max/Js logic 2026 01 21 > values display |
Details
| Live Version Used: | 12.0.5 |
| Max Version Used: | 8.6.2 |
| Date Added: | Mar 19 2025 09:28:09 |
| Date Last Updated: | Jan 21 2026 21:19:33 |
| Downloads: | 736 |
| ⓘ License: | None |
Average Rating
(1) Log in to rate this device |
5 |
Files
| Device File: | M rescale.amxd |
Comments
Reminder for myself to try this later: cheers!
Posted on March 23 2025 by asayers |
Report Issue
It crashes my liveset :[ i run 12.2.6 on m4 mac.
Every time i touch a parameter in rescaler live freezes up on me.
Every time i touch a parameter in rescaler live freezes up on me.
Posted on October 24 2025 by hansolero |
Report Issue
It also crashes sometimes on my own computer, usually never when testing with just a couple of tracks but more often on fuller sets, sorry about this. I am trying to investigate why this happens but haven't found out why yet, I still hope to be able to fix this at some point.
Posted on October 24 2025 by Morusque |
Report Issue
I uploaded a new version that uses more js and less max. It's slower, doesn't have labels yet, but hopefully doesn't crash Live (at least on my computer sets that used to make it freeze on the next play now seem to work fine).
Posted on October 27 2025 by Morusque |
Report Issue
Hey there! I use this to scale/reduce the dynamic range and it works beautifully. Just curious why did you rewrite it?
I was wondering if you could bring back a few things from the original version (the theme was easier on the eyes IMO) and also add the velocity values label back again.
Could the retrieval be automatic for the velocity? Would make the worflow even smoother :)
Thanks for creating this!!
I was wondering if you could bring back a few things from the original version (the theme was easier on the eyes IMO) and also add the velocity values label back again.
Could the retrieval be automatic for the velocity? Would make the worflow even smoother :)
Thanks for creating this!!
Posted on January 21 2026 by whynotmore |
Report Issue
hello, thanks for the feedback.
the main reason why I had to refactor this was that it was making computers crash under certain circumstances (so even if that was rare I ended up not using it much just to avoid the crash). Now it's slower as a side-effect but I thought that was still preferable to crashes.
add the velocity values label back
>
sure, that sounds easy, I'll do it.
Could the retrieval be automatic for the velocity?
>
It depends what you mean by that. One known issue right now is that the device has to be set to "auto" to properly retrieve values (because the only way I found to simply read values was to pretend the patch was going to update them but then push them back unchanged) but this is on its way to be fixed.
But if you mean "always retrieve values on launch or selection with no way to prevent it" then I'd prefer not to since there are cases where retrieval can freeze the host for a long time and one might want to skip it.
"I was wondering if you could bring back a few things from the original version"
>
do you have anything else in mind beside values and retrieval ? I thought I reimplemented everything else.
the main reason why I had to refactor this was that it was making computers crash under certain circumstances (so even if that was rare I ended up not using it much just to avoid the crash). Now it's slower as a side-effect but I thought that was still preferable to crashes.
add the velocity values label back
>
sure, that sounds easy, I'll do it.
Could the retrieval be automatic for the velocity?
>
It depends what you mean by that. One known issue right now is that the device has to be set to "auto" to properly retrieve values (because the only way I found to simply read values was to pretend the patch was going to update them but then push them back unchanged) but this is on its way to be fixed.
But if you mean "always retrieve values on launch or selection with no way to prevent it" then I'd prefer not to since there are cases where retrieval can freeze the host for a long time and one might want to skip it.
"I was wondering if you could bring back a few things from the original version"
>
do you have anything else in mind beside values and retrieval ? I thought I reimplemented everything else.
Posted on January 21 2026 by Morusque |
Report Issue
Login to comment on this device.
Browse the full library