Custom (Mixes) Scripts take one or more values as inputs, do some processing in Lua code, and output one or more values. Each model can have several Mixes Scripts associated with it, and these scripts are run periodically. They behave similarly to standard EdgeTX mixers, but at the same time they provide a much more flexible and powerful tool.
Typical use cases:
* replacement for complex mixes that are *not critical* to model function
* complex processing of inputs and reaction to their current state and/or their history
* filtering of telemetry values
{% hint style="warning" %}
If the script output is used as a `mixer source` , and the **script is killed** for whatever reason, then *the* **whole mixer line is disabled**! Exercise caution when using them for primary controls. It is advisable to have a fallback mixer line, that will be used if for whatever reason the Mixer Script is terminated.
{% endhint %}
Inputs and Outputs for Mixer Scripts
Here is an example of mixer script that accepts a source and constant value, and has two outputs that will be selectable in the mixer as sources.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://manual.edgetx.org/color-radios/model-settings/custom-scripts.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.