Video Input organization

[Tomas Lohin]

Hello,

I'm dealing with multiple video destinations from one source and I've found that video input organization is a little confusing, especially talking about crop of an input as the video source. When I make a crop, I deal with pixels of a chosen input, in the input list I find dimensions in percentage (which is way better). What I also miss is a possibility to give a crop a custom name. In short, it would be nice to be able to see Input list and edit it outside editing video objects scenario. Or am I missing something?

Thanks

[bbudzon]

6 hours ago, Tomas Lohin said:

Hello,

I'm dealing with multiple video destinations from one source and I've found that video input organization is a little confusing, especially talking about crop of an input as the video source. When I make a crop, I deal with pixels of a chosen input, in the input list I find dimensions in percentage (which is way better). What I also miss is a possibility to give a crop a custom name. In short, it would be nice to be able to see Input list and edit it outside editing video objects scenario. Or am I missing something?

Thanks

These are good pieces of feedback we have not gotten before! You aren't missing anything, unfortunately.

 

Giving custom names to these video sources is particularly interesting and I'm surprised we hadn't thought of it! I can also see how dealing with percentages vs pixels might be easier. I think the reason we stuck with pixels in that portion of the dialog is so that you can get very precise crops (ie; pixel perfect) if need be.

 

There's a sort of renewed energy within the company surrounding pre-visualization at Vectorworks because of Showcase shipping in 2025. So, now is a great time for providing feedback! Thank you!!

[Tomas Lohin]

1 hour ago, bbudzon said:

These are good pieces of feedback we have not gotten before! You aren't missing anything, unfortunately.

 

Giving custom names to these video sources is particularly interesting and I'm surprised we hadn't thought of it! I can also see how dealing with percentages vs pixels might be easier. I think the reason we stuck with pixels in that portion of the dialog is so that you can get very precise crops (ie; pixel perfect) if need be.

 

There's a sort of renewed energy within the company surrounding pre-visualization at Vectorworks because of Showcase shipping in 2025. So, now is a great time for providing feedback! Thank you!!

Let's make the world a better place! 🙂

 

One or two more notes related to this topic from my current experience:

1) Everytime I reload the show, I have to deal with Video input setup again. For every single object. In most cases there is some noise displayed and I have to reassign video input to its name, if I remember it. Or reset video input (and here comes the guessing game which crop is which). Behaviour is somewhat unpredictable.

2) For some reason Vision often crashes after reasigning or resetting some video inputs. In current project I have about 10 objects to deal with and after numerous crashes I've decided to work with just three of them and make the rest invisible

 

 

[bbudzon]

49 minutes ago, Tomas Lohin said:

Let's make the world a better place! 🙂

 

One or two more notes related to this topic from my current experience:

1) Everytime I reload the show, I have to deal with Video input setup again. For every single object. In most cases there is some noise displayed and I have to reassign video input to its name, if I remember it. Or reset video input (and here comes the guessing game which crop is which). Behaviour is somewhat unpredictable.

2) For some reason Vision often crashes after reasigning or resetting some video inputs. In current project I have about 10 objects to deal with and after numerous crashes I've decided to work with just three of them and make the rest invisible

We have seen inconsistencies in the ability to load crops. This is something we need to investigate to try to figure out what is going on. It's, at least in part, due to the conversion of pixels into percentages which is necessary to preserve the crop position when changing an NDI stream between high and low bandwidths. It seems that sometimes we lose "precision" in the percentage. And so, when you open the file, we're looking for a crop that is say 95.37% for a given corner but we can only find a crop whose corner is at 95.36%. I'm not sure if this is possible for you or not, but one workaround is to do this cropping on the media server side. You can then send out multiple NDI streams such that no cropping is required in Vision.

 

Regarding your second point, it's hard to say if this will work or not... but keep your eye out for Vision 2025 Update 2 😉 There were a lot of problems that we found with similar functionality in Showcase in 2025U0/U1. And, when we fixed these in Showcase, we made sure to address these issues in Vision as well. So, there are at least some fixes for Vision's video dialogs that are going into 2025 Update 2. I do think one fix missed the Update 2 window and got pushed back to Update 3. But, I hope the Update 2 fixes resolve your issues and if not please let us know! That will keep us informed and kick off further investigations.

 

Thanks again!!