I’m working on a MIDI-to-sub triggering setup in Eos and wanted to ask for clarification on a few behaviors I’ve run into while importing and exporting show control data via CSV. I don’t think what I’m seeing is a bug — I suspect these behaviors are by design — but I’d love to know if I’m missing something or if there are extra columns or formats that aren’t well-documented.
Submaster Actions: On / Off / Bump
When I import or export a show control CSV, I can reference Sub 1, Sub 2, etc. in the ACTION column — but the action always seems to default to a bump.
Even if the original show control entry was explicitly set to Sub On or Sub Off, the exported CSV just shows Sub 1, and when I re-import, it doesn’t restore the original action — it assumes bump behavior.
-
Is there currently a way to specify Sub On or Sub Off in the CSV?
-
Is there an additional column I should be including that defines the sub action more precisely?
Velocity, Thresholds, and “Threshold at 0 = Disabled”
In the Eos GUI, I can configure:
-
Velocity
-
Velocity Threshold
-
Threshold at 0 = Disabled (the checkbox)
But when exporting to CSV:
-
I only see the velocity (as part of the TRIGGER string — e.g., MIDI: 9N 3C 7F)
-
I don’t see any column that maps to Velocity Threshold or the Threshold at 0 checkbox
-
When importing, there’s no obvious way to define those fields either
So I’m wondering:
-
Are there columns I’m not seeing in the export that can be added manually to control Velocity Threshold or Threshold at 0?
-
Or are these parameters simply not accessible via import/export at this time?
To sum up, I’m trying to understand:
-
Whether submaster actions (on/off/bump) can be explicitly defined via CSV
-
Whether velocity threshold settings and the “threshold at 0 = disabled” behavior can be configured in a CSV import
-
And if any of these are possible, what column headers or formats I should be using
Thanks in advance for any insight.
