a better search for max devices
Best About
gtm.humaniser screenshot

gtm.humaniser

by Metrosync

Note: only compatible with Live 11.1 and above due to relian...

View on maxforlive.com Website

Type
MIDI Effect
Author
Metrosync
Version
1.0
License
Commercial
Live version
11.1
Max version
8.2
Downloads
0
Updated
2022-03-09

Description

Note: only compatible with Live 11.1 and above due to reliance on get_all_notes_extended Live API call.

gtm.humaniser is a simple Max for Live MIDI device that alters the velocity, velocity deviation, timing, and probability of notes within a clip. It is possible to lock/unlock the timing position of the first note(s) in a clip in order to avoid the note(s) being shifted back in time, thus causing them to start before the beginning of the clip.

Video demo: https://youtu.be/OIkdM_vpCMo

Comments (8)

  • discoparadis · October 27 2022
    gtm.humaniser + gtm.tempoctrl not working in Live11.2.5
  • Metrosync · October 27 2022
    Both are working fine for me and I haven't received any other reports of the devices not working with 11.2.5. gtm.MIDIdrone was updated after the Live 11.2 update to work with minor changes made to the Live API, but there have been no changes in the 11.2.5 update which impact on the functionality of either device. If you have purchased the devices through Gumroad you should be able to message me with screenshots of the issues you are having, etc., so please feel free to do so. Without more information there isn't much I can do to help you resolve your issue.
  • discoparadis · October 28 2022
    maybe its a silicon compatibility issue @Metrosync I'll check if I can fix it + let you know
    thanks
  • Metrosync · October 28 2022
    Are you getting an error in place of the device GUI when loading it into a track that says something about externals not working with your architecture? If so, I’ve noticed this issue with some of Ableton’s own Max for Live devices since the Live 11.1 update and the solution (for me at least) seems to be simply hotswapping the affected device back into the track and then everything works fine, including recall of any parameters saved with a Live Set. Off the top of my head, I’m fairly certain there are no externals in either device so, if this is the case, it seems this message is popping up erroneously and it is perhaps a bug with Live rather than an issue with certain devices. I’ve had it happen with the Envelope Follower device and what is strange is that all parameter mappings linked to the device still work even when the device is displaying the error message in place of its GUI. After hotswapping the device back in the device GUI is loaded properly and all settings are as they were when saved with the Live Set. Let me know if this is your issue and if this solution works for you.
  • Metrosync · October 28 2022
    For some reason maxforlive.com has replaced all my apostrophes with question marks so sorry about that!
  • discoparadis · October 28 2022
    no worries @Metrosync got them working
    unfreeze+save solved it for me
  • Metrosync · October 28 2022
    Sorry, I forgot the final stage in this workaround I found to resolve the issue with the Envelope Follower device:
    1. Device loads and gives error message about external incompatibility with architecture.
    2. Use hot swap button to replace the affected device with itself. This will replace the device with a functional one but setting will be device defaults.
    3. Undo the hot swap action and the new, default device will be replaced with the a working instance of the device with full parameter recall from the saved Live Set.
    As I say, I think this is a bug with Live so I will report it to Ableton and hopefully they can fix it.
  • Metrosync · October 28 2022
    Ah, that's good to know. Glad you got them working.

Related MIDI Effects

← Back to search