Resolume arena 5 ndi output3/20/2024 If we use Vectorworks to create an LED screen and send it to Vision, and Vision has the ability to crop an incoming NDI stream, why doesn't this just work? You can't fix an asymetrical scale as is occuring here. Playing with the texture scaling and offset in Vision does not help. The math certianly does not work for the downstage 3wide x 1high boxes. that one is stretched vertically and doubled. The Ctr Top crop is perfectly square, mapped to a perfectly square screen. The 2wide x 4high carts are the only ones that display the crop faithfully. Note the different scaling of the crops! Nothing seems to work out right, except the SR High and SL High set carts! So we get our square crop for our square video surface:Īnd we do it for each of the LED screens in the model:ĭuring this process, plan to spend a lot of time looking at this screen, waiting for Vision to "see" the NDI input that it "saw" just perfectly moments ago:Įventually we have created 13 separate crops of the NDI raster and mapped them to our LED screens. best to use the tools in Photoshop and write down the pixels. You can't zoom in on it, there's no grid or snap guide. So let's crop the NDI stream! I scaled my 1080 template down to 640X360 in Photoshop to determine the exact corners of every crop and wrote them down (analog, in a notebook with a pencil) because the cropping tool in Vision is rudimentary at best. We find the 1920x1080 NDI input that is being scaled by 1/3 to give us a raster of 640x360 for use in Vision. The NDI monitor on the Vision PC shows a smooth, steady video image in real time: The video input is fed via NDI from a MacBook Pro running Resolume Arena. Let's begin by selecting our first LED array (in this case the 4 tile square array top center) and choosing Assign Video Input: These two MVRs plus my Amphitheatre MVR merge together in to this model: The set carts that they travel in get exported as a separate MVR to keep things organized. OK, so now we move over to Vision, after exporting the LED tiles in their own MVR. These names do not correspond to the names that Vision ends up asking for, and you could put Fred or Ethel in the "Capture Source Name" field and you never see those names come up again throughout the process: I also wonder what the "Capture Source Name" and "Capture Source Number" are in the "Select Vision Video Source" dialog. I tried exporting MVRs with all of the Scale adjustments in this menu set to 100% and had the same results that are illustrated below. The image used for the texture is only two TVs wide, so this makes sense as applied to the still image in VWX.Ĭhanging this scale, however, has no effect on the eventual video mapping problem that we shall see in Vision. Notice that the Scale is set to 50% to get the image to display correctly (the illusion is a stack of TVs with different images). The image on the LED screens is set in "Edit Array Image" where a custom texture is selected. All of the display surfaces are LED Screen plugin objects with dimensions and pixels set correctly in the OIP as indicated: The set looks like the following screenshot. I'm having trouble mapping an NDI stream to various LED tiles placed on stage in set carts. Pour yourself a coffee and tuck in this is a long one!
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |