I just made a small donation, so I hope that helps a bit. (at very least office coffee round)
Vuo really is fantastic, and as Paul mentioned is very important for many of us. I look forward to a bright future for Vuo, and hopefully in the not too distant future multi-platform support. (Window most probably would be financially sensible- but Linux for installation playback etc)
I really appreciate the dual license nature of Vuo. It allows us to see aspects of Vuo (source code) and have a connection to the deeper workings of Vuo. Can't wait for Vuo 1.3!
On a side note: HAP playback has made a huge difference to me- as has the amazing work done in completely fixing the x4000 AMD GPU bug!
While you can still use JPG and PNG images, those formats are STRONGLY discouraged.
Instead, you should use the .dds format with either DXT1 or DXT5 compression.
We recommend ImageMagick for converting. In a terminal, just go:
$ convert image.png image.dds
It's that simple.
So why this new format?
Before, the way a texture image was loaded was this (for a 4k/UHD 3840x2160 image):
1. Load PNG compressed data;
2. Decompress PNG into RAM (using 32MB of RAM)
3. Flip the image vertically on CPU (using another 32MB of RAM).
4. Send this data to the OpenGL Drivers
5. OpenGL drivers compress data into DXT1 or DXT5 using up another 8MB RAM
6. OpenGL drivers write the texture to VRAM
Now the process is shorter:
1. Load DDS image into RAM (using 8MB ram)
2. OpenGL drivers write the pre-compressed texture data directly to VRAM
Alastair (@usefuldesign) I know it's yet another language, however python makes trivial many logic based operations in C. So for logic and composition control python is very flexible, just not fast enough for processing large data quickly.
Added to this that python is an extremely popular language- and used in many 3D softwares already.