Is there a way to catch the current value of a knob or slider in ableton for example the actual cue value and if i turn a potentiometer on a midi device the cue should not jump to the potentiometer value. Instead of this, the pot value changes while turning and if the send pot value matches the value in ableton can than change smoothly. Sorry a bit confusing but you might get the idea behind this. I am shure that this will work but i can't find the right search item to find the solution for this "catch first and do not jump problem"
I would like to discuss some control features with remotify but I can't contact remotify via the web site cuz of email filter, it says that my email is invalid.. How can I contact with remotify developers?
your software is great tbh, and planning on buying it. i have a minor problem that i personally don't know how to fix. if you search up my controller which is the impact lx25+, you can see clips and scenes buttons next to the pads for launching the selected track's clips. These buttons only work on specific daws like bitwig, if they don't have integration "like ableton" then they don't even send a cc message. I managed to make them send a cc message to ableton by intentionally crashing bitwig, only problem is that they dont switch the cc message of the pads as they don't have the intended bitwig script to change their messages. so how can I make these two buttons switch the pads functionality for clip and scene launching?
If inputs are not sending midi messages when you press them then potentially there's a problem the unit. Maybe try contacting the manufacturer? Scripts don't change the behaviour of the controller's own firmware.
@@remotify nektar themselves specifically say that the two buttons do nothing if the controller doesn't fully support the daw you are using. In bitwig (which is supported) the buttons send cc messages, 16/117 and 118 but ableton doesn't receive them. Is there any way to remove the constraints that the manufacturer put to block the buttons from functioning?
@@kapsxd "if the controller doesn't fully support the daw you are using" this is abit vague. We can build scripts which "fully support" Ableton to our needs, but I wouldn't have thought it would change the controller's own setup.
