my mixer using alpha27.2-dx9ex sharing textures across 4 vvvv's (2 instances of my simple patch-switcher (md.bot), the gui for the mixer and the output renderer (md.mix))
what's the performance of the dx9ex shared textures like? any issues?
nope there are 9 shared textures accross this setup (2 from the switchers and 7 between the mixer gui and the renderer) and there's no performance impact at all. there's no fps impact even when the shared textures are used on separate monitors.
it's fast as hell:D
and the sample dynamic plugin is completely spreadable
I have tried finding the nodes to do this in the new alpha but can't find it. Where can I find it?
man this sounds good... so this multi monitor thing - can this fix our issues with span mode and win7?
so you receive a shared texture using SharedMemory(EX9.Texture), but how do you share one?
edit: ahh thanks
good job ;]
mrboni: you have to download this release: daily/core/vvvv_45alpha27.2-dx9ex-8df41c80b957481c2322ae3513fb319e7970a5c4.zip if you create a DX9Texture node and if that texture is used in an active renderer it's shared. the handle comes from a second output pin of DX9Texture
To note, this does let you share textures between devices so finally we no longer need to use span mode to share textures between multiple heads!
Do you have issues when renders are fullscreened like you did with mulitple versions of vvvv running (previously i could only get a 1024 fullscreen before other renderers would stop rendering)
whoa i haven't used native fullscreen in a while (maximize window and remove borders was fine for me) and the last time i tried out fullscreen with multiple instances (with beta24 i think) it was buggy if i remember well
anonymous user login