# Mux node **URL:** \ **Category:** Flame Questions\ **Tags:** mux\ **Created:** [March 1, 2026, 10:43am UTC](https://forum.logik.tv/t/mux-node/14189 "2026-03-01T10:43:13Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![paul\_round](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/paul_round/32/389_2.png) [@paul\_round](https://forum.logik.tv/u/paul_round)\ **Post date:** [March 1, 2026, 10:43am UTC](https://forum.logik.tv/t/mux-node/14189/1 "2026-03-01T10:43:13Z")
Does anyone else find it odd that theres a mismatch between amount and selection? Surely the numbers should correlate. ---
**Author:** ![cicero](https://avatars.discourse-cdn.com/v4/letter/c/ecae2f/32.png) [@cicero](https://forum.logik.tv/u/cicero)\ **Post date:** [March 1, 2026, 2:34pm UTC](https://forum.logik.tv/t/mux-node/14189/2 "2026-03-01T14:34:49Z")
I remember asking that when I was first trying to learn Flame (well, Smoke) and was told, ‘Engineers start counting at zero’. So I guess the person who designed one box was an engineer and the other wasn’t. ---
**Author:** ![cnoellert](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/cnoellert/32/559_2.png) [@cnoellert](https://forum.logik.tv/u/cnoellert)\ **Post date:** [March 1, 2026, 2:46pm UTC](https://forum.logik.tv/t/mux-node/14189/3 "2026-03-01T14:46:29Z")
No the math works. 1 port is port zero. Zero ports would be useless lol. ---
**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\ **Post date:** [March 1, 2026, 5:22pm UTC](https://forum.logik.tv/t/mux-node/14189/4 "2026-03-01T17:22:48Z")
It only bothers me when I have more than just a few inputs. It can get confusing when you start wrangling double digits. I would rather see them correlate. ---
**Author:** ![GPM](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/gpm/32/4224_2.png) [@GPM](https://forum.logik.tv/u/GPM)\ **Post date:** [March 1, 2026, 9:58pm UTC](https://forum.logik.tv/t/mux-node/14189/5 "2026-03-01T21:58:49Z")
The issue for me has been the incongruity between the MUX numbering, and pretty much all other numbering in Flame. It makes expressions quite awkward for complex operations. Normally in Flame, “1” equals “1”. ---
**Author:** ![andy\_dill](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/andy_dill/32/15475_2.png) [@andy\_dill](https://forum.logik.tv/u/andy_dill)\ **Post date:** [March 1, 2026, 11:34pm UTC](https://forum.logik.tv/t/mux-node/14189/6 "2026-03-01T23:34:31Z")
Yeah, i don’t like it either. It’s confusing. ---
**Author:** ![GPM](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/gpm/32/4224_2.png) [@GPM](https://forum.logik.tv/u/GPM)\ **Post date:** [March 1, 2026, 11:48pm UTC](https://forum.logik.tv/t/mux-node/14189/7 "2026-03-01T23:48:32Z")
\*I did flag this when MUX was introduced, and the response was that it basically doesn’t matter. ---
**Author:** ![Jonhollis](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/jonhollis/32/11832_2.png) [@Jonhollis](https://forum.logik.tv/u/Jonhollis)\ **Post date:** [March 2, 2026, 10:02am UTC](https://forum.logik.tv/t/mux-node/14189/8 "2026-03-02T10:02:09Z")
totally agree Paul ---
**Author:** ![kily](https://avatars.discourse-cdn.com/v4/letter/k/a88e4f/32.png) [@kily](https://forum.logik.tv/u/kily)\ **Post date:** [March 2, 2026, 12:17pm UTC](https://forum.logik.tv/t/mux-node/14189/9 "2026-03-02T12:17:55Z")
For all developers, the 21th century, began in 2000. ---
**Author:** ![Sinan](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/sinan/32/155_2.png) [@Sinan](https://forum.logik.tv/u/Sinan)\ **Post date:** [March 2, 2026, 1:15pm UTC](https://forum.logik.tv/t/mux-node/14189/10 "2026-03-02T13:15:32Z")
Please add your upvotes to the request, which is actually 10 years old. [Fl-00529](https://feedback.autodesk.com/project/feedback/view.html?cap=5afe6c84-5cb3-447a-b36c-cbd7f0688f84&uf=c0d41890-901c-4dbd-b44b-06a84c8a2c7a&nextsteps=1&nextstepsf=8fbadb72-c1b4-44ad-b55e-888e3fdc17e4&nextstepsuf=c0d41890-901c-4dbd-b44b-06a84c8a2c7a) ---
**Author:** ![Sinan](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/sinan/32/155_2.png) [@Sinan](https://forum.logik.tv/u/Sinan)\ **Post date:** [March 2, 2026, 1:16pm UTC](https://forum.logik.tv/t/mux-node/14189/11 "2026-03-02T13:16:35Z")
@Peter also has a great workaround on the feature request page: As a workaround, add one more input than needed, and then add the 1st source into mux input 1 and ignore the 0 input. Then the numbers line up and it keeps things easier to follow ---
**Author:** ![bryanb](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/bryanb/32/136_2.png) [@bryanb](https://forum.logik.tv/u/bryanb)\ **Post date:** [March 2, 2026, 1:16pm UTC](https://forum.logik.tv/t/mux-node/14189/12 "2026-03-02T13:16:44Z")
At this point they’re going to say it would break old setups to make this change so they won’t be doing it. ---
**Author:** ![Sinan](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/sinan/32/155_2.png) [@Sinan](https://forum.logik.tv/u/Sinan)\ **Post date:** [March 2, 2026, 1:17pm UTC](https://forum.logik.tv/t/mux-node/14189/13 "2026-03-02T13:17:55Z")
Well, opening an archive of a project that used the ACES1.1 workflow in 2026 with OCIO/ACES2.0 breaks everything. So there’s that. ---
**Author:** ![hildebrandtbernd](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/hildebrandtbernd/32/3038_2.png) [@hildebrandtbernd](https://forum.logik.tv/u/hildebrandtbernd)\ **Post date:** [March 2, 2026, 1:50pm UTC](https://forum.logik.tv/t/mux-node/14189/14 "2026-03-02T13:50:06Z")
Using mux nodes a lot and it never was bothering somehow. It’s like counting the first frame, some software uses 0 and other uses 1. ---
**Author:** ![allklier](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/allklier/32/4309_2.png) [@allklier](https://forum.logik.tv/u/allklier)\ **Post date:** [March 2, 2026, 3:28pm UTC](https://forum.logik.tv/t/mux-node/14189/15 "2026-03-02T15:28:23Z")
Flame is full of odd choices, I don’t think this would make the top 10. And y’all survived for 10 years with it all accounts. In politics you’d consider this a slow news day. ---
**Author:** ![paul\_round](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/paul_round/32/389_2.png) [@paul\_round](https://forum.logik.tv/u/paul_round)\ **Post date:** [March 2, 2026, 4:33pm UTC](https://forum.logik.tv/t/mux-node/14189/16 "2026-03-02T16:33:37Z")
> [@Sinan](#): > > also has a great workaround on the feature request page: > As a workaround, add one more input than needed, and then add the 1st source into mux input 1 and ignore the 0 input. > Then the numbers line up and it keeps things easier to follow That is a brilliant idea! ---
**Author:** ![paul\_round](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/paul_round/32/389_2.png) [@paul\_round](https://forum.logik.tv/u/paul_round)\ **Post date:** [March 2, 2026, 4:34pm UTC](https://forum.logik.tv/t/mux-node/14189/17 "2026-03-02T16:34:01Z")
It’s something that has bugged me for years, TBH. ---
**Author:** ![andy\_dill](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/andy_dill/32/15475_2.png) [@andy\_dill](https://forum.logik.tv/u/andy_dill)\ **Post date:** [March 3, 2026, 12:36pm UTC](https://forum.logik.tv/t/mux-node/14189/18 "2026-03-03T12:36:27Z")
> [@allklier](#): > > In politics you’d consider this a slow news day. I’m just happy this thread isn’t about ML. ---
**Author:** ![cnoellert](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/cnoellert/32/559_2.png) [@cnoellert](https://forum.logik.tv/u/cnoellert)\ **Post date:** [March 3, 2026, 1:42pm UTC](https://forum.logik.tv/t/mux-node/14189/19 "2026-03-03T13:42:12Z")
While we’re talking about the mux and ML I do wish we could get an update to it so that it behaved like the get and set nodes in Comfy and do away with the semi-hidden lines. For those that don’t use Comfy you give the set a name and then in order to to fetch its output you add a get node and select the name of the set node. In this way you can massively decouple your node positions from flow without losing all readability. Bonus points if the colors could match on both nodes automatically. Unpopular opinion perhaps but it would be dope. ---
**Author:** ![andy\_dill](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/andy_dill/32/15475_2.png) [@andy\_dill](https://forum.logik.tv/u/andy_dill)\ **Post date:** [March 3, 2026, 3:24pm UTC](https://forum.logik.tv/t/mux-node/14189/20 "2026-03-03T15:24:16Z")
Almost a “teleport” node. Yeah. That would be a lovely way of moving a lot of channels around in a setup. [Next page](https://forum.logik.tv/t/mux-node/14189.md?page=2)