When changing an input (ie: change Button 1 from CC1 to CC2) any Reaction mapping that uses this input will stop working. I need to manually re-select the input both as Listener and as Condition item. A red box appeared for the Condition input menu stating that the input had changed and I needed to select it again, so at least there was some feedback telling me what happened, but having to manually go through all Reaction mappings to re-select is far from ideal, especially since I use a lot of them.

Hi, I'm trying to use the Clip Slot fire reaction and I'm getting an error. Here is the relevant messages in my log:

I'm using CSS 2.5.6, and I'm using ClyphX Pro to move the Session Box in my CSS script around. It works fine, until I change modes on my CSS controller. Once I do that, ClyphX Pro can no longer control the position of the Session Box.

It seems like maybe when I change modes on my CSS controller, that the Session Box in Mode 1 gets destroyed, and a new one is created for Mode 2. Is there something I could do differently so that the original Session Box persists across modes, and my ClyphX Pro script can continue manipulating it across CSS mode changes?

I've created a simple script for my MIDI Fighter Twister, where I'm controlling the volume and selection of 16 tracks. Encoders and buttons work fine, but the LED feedback behaves pretty weirdly.

// What I expect:
When a track is selected, I want my corresponding encoder to blink. This works by sending a value of 5 to the corresponding LED.

// What I'm experiencing:
By default, the first track blinks when I startup Live.

Hey,

I'm just testing out the web version on Ableton 10 with Open Stage Control. Sending Midi Channel 2 data to Ableton. Made very simple script to test (volume, panning, arm track) on track 3 and volume and panning work great. But the arm track button is spazzing out and sending loads of data. Goes away when I delete the track.

Hard to take a screenshot but its just flashing very fast and I can't un-trigger it in OSC. I tried setting thevalues of the button deifferently to a tap instead of toggle and changing CC values.

Any advice?

Cheers
Fabian

I can't seem to find a combination that works for my Pad Banks on my DDJ-RX Controller.

The Pads send a NOTE, Momentary signal (127 ON, 0 OFF).

I've setup with every combination between the Controller Template and the Control Script of Toggle, Momentary, Absolute, Snap ON/OFF and the best I can get is either;

1. Toggle Behaviour without any LED Feedback (Macro only goes to 100 instead of 127)
2. Momentary Behaviour with LED feedback (Macro goes to 127 but there's no LED Feedback)

I have long lists of eg controllers; when selecting I normally just type in the first 3 characters which bring up the indexed reference and it lets me navigate large areas very quickly

This no longer works and makes scrolling through long lists tiresome

Cheers

When i want to change a cc value in the editor it always changes back to it default value (with cc values channel 1 and value 1)

I want to set the button value to another midi value but it keeps changing back, please fix this.

Hi John,

I'm trying to create a script for my Korg nanoKONTROL2. It's based on djpaimon's korg_nanokontrol2.json controller template and has 11 modes... 5 primary 'a' modes, a shift mode, and 5 secondary 'b' modes.

Hello,

I just bought CSS and I'm trying to map a button on my controller to toggle a 0-127 parameter in the rack.

The first problem is that it only changes the value from 0 to 100, which I think is a bug. It maps the "Minimum" and "Maximum" values which are defined as a %, but it changes the parameter to 0 and 100 in the rack, and not 0 and 127.