I used to use the Multiplexer node in QC for switching between various video sources and was wondering if there is a VUO equivalent yet or if it's coming soon? I've found the Select Input series of nodes but unless I'm missing something they are limited to 2 inputs only at the moment. I'm looking for a node that will allow me to expand to how ever many inputs I need like the QC Multiplexer did.

Comments

Chris (@cwilmsloyalist):

smokris's picture
Submitted by

Chris (@cwilmsloyalist): That's coming in a few months. In the Vuo 1.0 release, we're planning to improve the Select Input nodes so they can be expanded, similar to the draggable list ports. It's listed on the roadmap as "Select and OSC nodes with variable number of ports".

(It's not implemented yet since it requires some modifications to the compiler and editor so that list elements can granularly block events — not trivial.)

Ah ok, I see.

mnstri's picture
Submitted by

Ah ok, I see.

But the Get Item from List could be used to switch between more than two images in similar way that you would in QC with multiplexer, right? Videos might cause some problems because of the non-blocking if I understand correctly? Or if the items receive a lot of events.

It looks like the "Select and

cwilms-loyalist's picture
Submitted by

It looks like the "Select and OSC nodes with variable number of ports" feature got moved back to v1.10 in the schedule at some point. I hope it doesn't get pushed any further back, I'm really looking forward to this one. ;)

I can't really complain though, things are moving along very swiftly overall, and I'm really looking forward to quicktime video capture support tomorrow in version 0.9.0 release!

I'm also really hoping the Node set for Blackmagic video capture gets moved into one of the dated Roadmap slots and it will be pretty awesome someday when UVC eventually gets support WITHOUT a Quicktime wrapper, then we could someday see camera control options (Exposure, Focus, White-balance etc) for some webcams too!

Christopher,

jmcc's picture
Submitted by

Christopher,

The "Select Input" nodes do support images and videos an input. Please let us know if you think we can improve our documentation on that point, or if you've encountered problems trying to work with those sources. For playing videos, you might want to look at "Select Event Output." That node might be more efficient, depending on your goal.

Thank-you for your quick

cwilms-loyalist's picture
Submitted by

Thank-you for your quick response, I thought it worked with images and I just figured out what happened! I was using the (Fetch Image - Select Input (8) - Render Image to Window) and I could not get them to connect to each other last night however I had accidentally first connected the Select Input (8) Node to a Scene Object source first before realising I had grabbed the wrong source, then when I disconnected the scene object source and tried to connect the Fetch Image node it wouldn't connect because it was now set to work with scene objects.

I think this may be a slight bug and now that I know what is happening I think I've run into this before with other nodes. I would expect that if you disconnect all sources from a node it should revert back to it's default state and accept any supported file type again rather than retaining a preference only for the last file type it was connected to. Thoughts?

I've attached an example composition to show the issue. The cyan coloured nodes have been used for images while the magenta coloured nodes have been used for scene objects; even though they have now been disconnected you cannot use the image nodes on the Select Input (8) node that was previously used for scene objects or vice versa.

We are thinking about some

jmcc's picture
Submitted by

We are thinking about some other improvements on how we handle and explain generic ports, and we'll certainly look at your suggestion in conjunction with those. Once a Vuo port becomes specialized, to manually revert it to its generic type right click on the port for the context menu, "Revert to Generic Data Type." Taking this action might delete some input and output cables if the node is connected to other nodes.

After posting I did find the

cwilms-loyalist's picture
Submitted by

After posting I did find the "Revert to Generic Data Type" action. I didn't find it immediately intuitive to look for that because there was no visual change in the node to indicate that it was now specialized. Is there a functional reason for a node to stay specialized when no other cables are connected to it anymore?

If you have entered data into

jmcc's picture
Submitted by

If you have entered data into the node's input ports, that data could be lost when you "Revert to Generic Data Type." For example, if you are using a "Count within Range" node, and have all the values set to real numbers, reverting the node will erase all those values. We didn't think that deleting cables should cause user-entered data to disappear.