Thanks Jean Marie , that was easy as 1-2-3, right? I totally learned a new trick from you (automating weird inputs with time), this will sure be useful <3
Any ideas though on how co create ripples for non-round shapes? Or a least a square shape. Somethings like this:
I'm interested in this as well. I rarely see macbooks on tour anymore - apart from simple QLab setups in theaters. In the scenarios I hear about them, it is usually problematic (dongles not working, overheating etc). We still have 2015 models running QLab/Keynote, and haven't had any compelling reasons hardware-wise to upgrade them apart from wear & tear/physical damage. USB-C has been a huge hit to reliability on the road. Going forward, we're limiting the builds to rackmount mac minis for QLab/Keynote, and Resolume/MadMapper will be running on PCs instead.
The new Mac Pros are also too little too late, and at a price point where they compete with dedicated media servers/solutions - I'm not certain they bring anything to the table. It does have the rackmount capabilities, but otoh you can build a rackmount crazy dual GPU powerhouse for the MP entry level price (which has 4GHz 8c/16t rx580/32G ram). My current home computer is better specced than that for half the price. Including a monitor. With a stand.
And to clarify, I'm not a disgruntled Apple customer - I just don't see the financial sense or prevalence in Apple equipment for this line of work any more.
It's not really that the Editor freezes, wrong words used, but more like it's struggling to deliver the 2 notifications, cause when you right-click in the dock to quit it, you hear that macOS error sound.
Though, this is on mac OS X 10.11 and 2011 hardware, if this does not happen on more recent hardware / macOS versions, I wonder how much team time is worth putting into this, guess the user base is more up to date, I'm just waiting for better macs to update ;)
Couple of things comes to mind. First it seems like you're always creating the full resolution image. In the case of the low-res selection, you only see the lower res one, but in the comp you also create the full-res one anyways. This is one of the major differences between QC and Vuo. In QC you wouldn't have created the one that wasn't selected, as it pulls the values to the output. In Vuo however, it pushes all calculations to the conclusion from the inputs enabling background calculations, but at the price of having to be a bit more careful about the values and blocking events.
I also wonder how you deal with the wrap-mode in QC? I haven't used this (vuo) node myself, but if I understand it correctly, it in this instance would check 4 4k frames/textures at every frame cycle. That is a pretty hefty operation - especially for older/mac hw. I would try removing those nodes to check performance.
I usually see some frames drops going fullscreen in Vuo too, compared to non-fullscreen even with a window the size of the screen.
Funnily enough usually checking the port events it does NOT register frame drops, but you can still see some chops.
But I did blame old 2011 hardware, or maybe the small amount of extra pixels rendered instead of the window bar.
There are also 2 fullscreen modes in Vuo if I'm right, cmd-f in the composition goes Vuo fullscreen, and the regular macOS fullscreen (green button).
Regarding timing, I guess the time published port instead of display refer is the way to go though for best results.
And instead of Fire Periodically use Allow Periodic Events.
Not that it will make a difference I guess, but it allows to be synced with the main time.
Not only is Quartz running this smoothly, so is Shadertoy via Google Chrome (100% performance in fullscreen). Using a .qtz as a screensaver, I have this same GLSL code running as a background element along with more complex animation layers in the office lobby, pulling settings and text content from a web server running on the same system. And that's all running on a stock 2011 Mac Mini; though there are a few frame drops periodically, it runs surprisingly well, and has for many months...after years of reliably running other versions of Quartz Composer screensavers.
Based on the poor performance I'm getting with Vuo on a newer Mac Pro with far higher end GPUs, I'm hoping this is a beta issue that will be resolved by the time its released. That's why I'm bringing it up now! There's no "happy medium" if Vuo is a trade down from a more reliable and performant (though deprecated) system like Quartz Composer.
So... lets do a thread necromancy. As the 2.0 is around the corner, any good news for the (freshly migrated) Windows user base?
(My latest workstations are pc-s, and I don't think I will even bother hackintoshing them anymore...)