jstrecker's picture

Jaymie (@jstrecker)


  • Vuo Founder
  • Team Vuo
jstrecker's picture

I wonder if this will be more CPU/GPU intensive since I am doubling the input

Your solution seems reasonable to me. While it may be technically more GPU-intensive, I'm not sure that it would be enough of a difference to be noticeable.

jstrecker's picture

Currently, the FxPlug's UUID is generated based on the bundle identifier. So if you keep the bundle identifier the same, the UUID will be the same, and it will maintain project compatibility.

If, on the other hand, you want to change the UUID, you can do so by altering the bundle identifier (e.g., add a .dev suffix, as in com.kingluma.invertImageColors.dev).

Does that meet your needs, kingluma? Or is there some reason you'd need to change the UUID independently of the bundle identifier?

jstrecker's picture
Jaymie commented on jon121's Discussion, “FFGL and Resolume Arena

FFGL plugins exported from Vuo work in Resolume Arena and Avenue versions 6 and 7.

Resolume 5 only supports 32-bit FFGL plugins, and thus can't use the 64-bit FFGL plugins exported from Vuo.

jstrecker's picture

add a secondary shortcut to hide the node library

We'll do that. Thanks for the suggestion, Bodysoulspirit.

jstrecker's picture
Jaymie commented on prackvj's Bug Report, “Pop up Windows strange behavior

Confirmed — with certain arrangements of displays, input editors appear on the wrong display. prackvj, thanks for reporting this bug.

Workaround: In System Preferences > Displays > Arrangement, drag the menu bar (the white line at the top of the blue screen) to the leftmost display.