You can also disable alpha for your clip with these little toggles, so you might not need to re-render in such a case:

This issue should be fixed in the next release.

Workaround for now would be to grab your capture-input with something like OBS and then send it to Resolume via Spout or NDI.

Do you want to share the patch (if you prefer in a PM), then we can take a look at what happens there?

Try to use 'Gate' instead of 'Switch' (and yes the difference between them can be a bit confusing)

Yeah, this can indeed cause unwanted changes, we have a ticket for that and look into what would be the best solution.

Do you guys use the scrollwheel to change parameters in Arena?

Slice info in Wire only contains information about the input slices, currently you can't get information of output slice transformation from within Wire.

If it is an audio-only file convert it to an uncompressed .wav-file and add it to an empty clip slot and trigger it, just like any video clip:

https://resolume.com/support/en/prepari ... ompression

Audio input in its current implementation is only for FFT parameter animation and SMPTE audio timecode, you can not record audio inputs or send that to your audio output device. This can only happen for audio from files played from within Resolume, like .wav-files or video clips with an audio track.

The resolution in the patch panel does only define at what resolution this patch runs in Wire. If loaded as a plugin with Arena or Avenue then indeed the resolution will be set by the host, some nodes can also have a different specific resolution set in the node. Setting the resolution in the patch ...

Looks related to viewtopic.php?t=22600, for some users it helped to set the power management mode to "Prefer Maximum Performance" in Nvidia settings, there is also an older driver version mentioned in that thread that seems to fix the problem for most users.