CustomMaschineMK3 - An open source Ableton MIDI Remote Script for Maschine MK3
Comments
-
This script is amazing, but I find the velocity to be a bit off. Maybe it's my older Mk3, but I find I have to hit the pads in the center with force to trigger them….
does anyone else have this issue? or a fix?
do you think changing the velocity curve from linear to something else will make a difference? is this a silly question?1 -
Wow!!! People will love you forever!!! Amazing work!!!
0 -
Note that the Pad sensitivity is way worse in MIDI mode than when directly controlling Maschine Software. Which remote script is used doesn't generally matter unless it is actively doing something to the velocities. This problem has existed forever.
Curves can help, but the minimum actuation force required to trigger a Pad in MIDI mode is always bad unless NI decides to address it.
3 -
Thank you so much Cheers
0 -
Hi, I just released version 1.1!
This release adds so many improvements and new features.
Manual update is also going on.I've worked a lot, so I would focus on making music for a while.
Don't worry, maintenance and support will continue!6 -
the custom remote script is not showing as one of remote scripts I copied and pasted into user library, and I have a "__pycache__" folder that was created inside "CustomMaschineMK3" folder but I'm not getting it to show under control surfaces. I've tried running as Admin on everything, I've removed my other custom scripts I had in the folder, I've reset multiple time. Im on the final version of Ableton 11. Any help from here would be huge I've been trying to get this working for weeks now.
0 -
I tested my script (version 1.1) with Ableton Live 11.3.35, 11.3.40, and 11.3.42 on Windows 11.
These combinations are working properly.I think an unknown error happens when loading the script.
Please open "Log.txt" file and search for "RemoteScriptError" to see if any error occurred. (like the picture below)Here's official help about the log file location.
0 -
Thank you for your excellent work.
Can I suggest some improvements for future releases?
Browser:
-Change the tempo of the project while listening to samples. Switching to this mode by pressing the TEMPO button (like in Mixer mode) would ideally work.
-Change the numbers of the buttons for calling collections to match the numbering order on the keyboard (1-7 - colors, 8 - jump to "browser top")Add at least 4 empty encoders and buttons for midi mapping in mixer and plug-in modes.
If possible, add commands to open:
- piano-roll window
- instrument window
- plug-in window
1 -
awesome work chiaki! really excited to watch this develop. so far I've tried installing once and realized that I changed my ableton user library location from default, while (apparently) the default location still exists, so I put the scripts in there and it did NOT work, once I realized my mistake it was as easy as you'd think (I describe all this in case someone makes the same mistake).
2 -
I tried to replicate your situation by changing user library location, and the script works correctly on changed location.
Please try moving "Remote Script" folder to the new location.Additionally, I would like to share about upcoming v1.2 release.
・Custom mapping mode
This mode enables the use of 8x knobs and buttons as separate, MIDI-mappable elements.
It's suitable for using with Ableton's MIDI mapping mode.・Playing note feedback
Visual feedback like Push is available on keyboard, drum rack, and simpler modes.
Demo video・Custom parameter bank
Extended bank configurations for Meld and Hybrid Reverb will be added.1 -
?
no problems here =) I pointed the behavior out cause it looked to me that others could maybe make (or already have made) the same mistake…. otherwise, I'm just looking forward to the updates and enjoying expanded control on the guitar side of my studio.
you rock 🤘
1 -
Sorry, I misunderstood…
Thanks for sharing install tips and feedback!0 -
Hi, Chiaki…
im not sure this idea, would be conducive to making your script more accessible… or more complexity… or even whether it is at all possible
as the idea behind this thought is to put a middleman in between the controller script…
whereby only midi values are sent to execute your scripts functions…. thereby making other midi controllers tap into the functionality of your script…
as i dont have the maschine mk3 ..hence the thought
0 -
I remember this generic template when I saw your post.
I could understand that people want to use my script with their own controllers.
Maybe it works in some aspects, but it's also inconvenient because of the difference in controller hardware design.
I made this very specific to Maschine MK3 / Plus.
Workflows and visual feedback are designed for use with those.On the other hand, Ableton's latest remote script API greatly reduces preparation for making custom script.
It offers more features (like step sequencer) and complex mapping feature with less effort to use.So, making generic template with modern API is a better way rather than making a converter, as far as I think.
Some parts of my script will be re-used to support features like clip editing, note repeat, fixed velocity, etc...
These don't exist in the stock API.
Even if people could customize template by talking with ChatGPT, everyone will no longer struggle with DAW integration issue.The only problem is... there's no time to do.
1
Categories
- All Categories
- 18 Welcome
- 1.7K Hangout
- 68 NI News
- 900 Tech Talks
- 4.6K Native Access
- 17.8K Komplete
- 2.2K Komplete General
- 4.8K Komplete Kontrol
- 6.3K Kontakt
- 1.1K Reaktor
- 407 Battery 4
- 923 Guitar Rig & FX
- 467 Massive X & Synths
- 1.5K Other Software & Hardware
- 6.4K Maschine
- 8.2K Traktor
- 8.2K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators