Forum

Building a new system / advices welcome

vvvv beta question
#1

Hi,

I am quite new to vvvv, and I would like some advices for a future project that I hope to run with vvvv.

The project will involve 3 video projectors:
1 x resolution 2560x1600
1 x resolution 1280x800
1 x resolution 1024x768

  • I will need 1 control/patch screen ( 1920x1080 )

It will aldo involve 2 HD cameras, captures with BM Decklink duo.
The cameras need to be displayed on the 3 projectors at the same time.

I am wondering if I should use 3 machines or only one.

One would be easier for programming, budget and touring setup.
But I’m a bit afraid of how to deal with such different resolutions with vvvv. And about the limitations to use the videoin on all outs.

I use mostly videoin & filestream . And some 3d objects, but no strong generative stuff.
I also use some geometry correction ( homography & grid edit ).

I am wondering if one pc can handle all this.
Do I need to go to strong dual xeon stuff ? Or would a good spec. i7 based machine work ?
Is ati eyefinity a good choice for that kind of use ?

Thank you

#2

After some tests it looks impossible to set one renderer across multiple different resolution screens ( at least the ati drivers refuse to group these screens ).

So I get stoped by the limitation of using direcshow one one output.

I looked at the solutions for sharing textures.
Has someone performance feedbacks about this, knowing that my goal is to use two captured hd streams ( using decklink sdi ) on 3 outputs at the same time?
Or maybe an other solution to reach my goal.

#3

you should first try this: vvvv.nodes.decklink

its amazing, i am running 3 HD inputs with two cards and very low latency on one machine right now. maybe this texture can be displayed on multiple heads? haven’t tried it…

#4

Question:
Wouldn’t some things become a little easier if you had a few beamers with the same resolution? Or is that an absolute ‘must’?

#5

Hi

tonfilm: I tried, the texture created by the decklink node can’t be displayed
on multiheads.
At least I don’t manage.

ft: I want to use the 2560x1600 beamer ( “main” beamer to cover the stage ).
Replacing it by let’s say 4 1024x768 machines is not a solution because of stage setup conditions.
I need two other beamers to project on spaces that will not be covered by the first one.

#6

And I don’t manage to use the decklink node in /dx9ex mode. Did you tried ?

#7

You could use a different renderer for each projector with different view transforms

#8

sunep:
That’s how I’m actually working, but I have this problem that I need to send videoin on the 3 screens and the texture out of videoin refuses this.

#9

Maybe Filestream (Textue.VLC) can help you out, not entirely shure, but worth a shot. If it plays your stream, you should be able to have it on all your displays.

(Check out the info about it in Contributions though, as getting video in is not as straightforward as the ‘normal’ FileStream)

#10

Hi FT

For file playback I kind of manage it between Filestream (Texture.VLC) and Player (EX9.Texture).

I am getting problems for sending videoin across the screens.

The Videoin (Decklink) seems to be perdect for my use, but I don’t manage to get it working with the dx9ex mode to be able to share the texture between renderers on multiple screens.

#11

this is something elliot has to solve. if vvvv is in dx9ex mode the plugin writer has to handle textures slightly different… you could bug him a bit, maybe he finds the time.

#12

Ok,
I will write him on the node page.
Thanks

#13

The production I’m working with at the moment needed the decklink input going to two output heads. We had really limited time to troubleshoot it, ended up simply using two identical intensity cards on the same feed, but I can confirm this works at least. You can address them with a getslice on the List Devices (decklink) node.

#14

Everyoneishappy:
On this project I have 2 HDSDI live streams.
And 3 projectors.
That would mean 3 decklink duo and a total of 6 HD streams to capture… I’m afraid it’s going to be too heavy.
Thanks for the idea

© vvvv group