we are trying to use 3 videoIns (3 identical webcams) and 3 videoOuts (3 videocards in 1 pc). what specialties do we have to take care of. (things like that the video out cannot be connected to multiple textures). what are your experiences? Are VideoTextures bound to a specific Renderer? will video stop/skip/freeze on all screens if we change the effect on one output? how does the Device (Manual) patch and the shareedMemory patch work exactly. whats the order of the devices in the Device patch and where is the videoIn on the SharedMemory patch?
at the end i would like to have one patch where i can specify the videoIn and three layerOut (with different effects applied to them) that should go fullscreen on different devices/monitors simultaniously.
This patch will then be instanciated three times in one main patch for the 3 webcam inputs.
maybe you can answer me on my email adress (tobi{at}isakeitdotde)
(by the way, i am german speaking. that will make it easier eventually)
i think my main problem is that a videotexture can only render for one renderer, but i would like to render to 3 different monitors.
but making 3 videoIn using the same webcam with their own videotextures doesn’t work either.
(patches attached for testing - sorry, doubled it)
you cannot use a S node in a module/subpatch that you instance multiple times AND use the R for that in the same patch… use normal links for that.
in order to render the same videotexture to 3 screens you will need one big renderer set to fullscreen on a matrox triplehead2go, there is no other solution which makes sense.
you connected the ‘node ID’ of the renderer to the ‘parent level’ pin of the SetRes module, that obviously wont work either like this…
hello, i (tonfilm) edited my post and that overwrote yours… dont know how that happend, but here is the answer regarding the S and R nodes in a subpatch:
yes, thats no problem, i was regarding to the issue in the patch from sybot, he has the S node in a subpatch, that subpatch is 3 times open, so the 3 S nodes in the subpatches become ‘devnul’, ‘devnul#1’ and ‘devnul#2’, that means you will have in all 3 patches the video texture from the first instance, because all R nodes listen to ‘devnul’.
thanks for all your help.
the S and R nodes in the patch because it was the first hint i got and i tried it right away.
but that is not the problem.
the problem is the videotexture node and the different devices (i dont know if someone tested it in dualview)
i would like to render on different monitors from one webcam source.
i think there might be a misunderstanding. (actually i’m pretty sure cause i work with sybot ;))
we have 3 video inputs which can be patched arbitrarily onto 3 different outputs. it’s one cam to one screen. so, while any cam input can end up on any screen, it will only end up on one screen at a time, not on all three screens together.
i guess that’s something we’ll discuss again today. I don’t remember exactly why we decided against it in the first place.
Also, i was incorrect in my above post, in theory the same camera’s input can end up on all three screens in some way or other. sorry for confusing it even more.
cheers
nadja
hi,
we are trying to use 3 videoIns (3 identical webcams) and 3 videoOuts (3 videocards in 1 pc). what specialties do we have to take care of. (things like that the video out cannot be connected to multiple textures). what are your experiences? Are VideoTextures bound to a specific Renderer? will video stop/skip/freeze on all screens if we change the effect on one output? how does the Device (Manual) patch and the shareedMemory patch work exactly. whats the order of the devices in the Device patch and where is the videoIn on the SharedMemory patch?
at the end i would like to have one patch where i can specify the videoIn and three layerOut (with different effects applied to them) that should go fullscreen on different devices/monitors simultaniously.
This patch will then be instanciated three times in one main patch for the 3 webcam inputs.
maybe you can answer me on my email adress (tobi{at}isakeitdotde)
(by the way, i am german speaking. that will make it easier eventually)
so you have 3 cams and want to show thme on 3 screens, cam not bound to one specific screen, but shifting sometimes, right?
Still, tonfilm first suggestion is best way to go. In span screen mode, which gives you triplehead2go for 3 screens, 3 monitors will be seen like one large. In technical matter this means that graficcard can address its memory as a whole.
If you have 3 seperate monitors but set side by side, its in technical matter 3 different memory storage, one for each monitor. So if you have a videotexture onto one monitor and moving it to second, it cant be shown as videotexture data is in memory storage of monitor one. Thats why it wont be visible on second.
There are workarounds possible with device, sharedmemory and so on, but easiest and best solution is span mode, even with 3 cams as input.
For 3 cams as input, you best search in forum. there have been some threads about this topic.
I hope it helps
so we are trying this spanmode thing with a dualhead and two extra monitors right now (we have no triplehaed at hand).
but …
my dualhead setup is 19201300 for the main screen and 12801024 for each of the other two connected to the dh2go.
the renderer in vvvv only has options to set to fullscreen mode in 16:9 or 4:3. so when i switch to fullscren the picture on both screens get chopped and my matrox setup software changes to single extra monitor but with only 12801024 once.
i tried setting the fullscreen resolution in vvvv with SetRes (with ID connected correctly :-)) to 25601024 but that has no effect.
in short:
when vvvv switches to fullscreen, matrox setup does too.
but matrox software should remain at double monitor and vvvv should set the renderer to 2560*1024.
any ideas?
patch attached if anyone has the hardware to test (gesamt is the main patch again)
