Plot vue

No Coments?

Hmm...maybe we should think something even better :)

looks like kind of vistaish!!!!! but really dunno
What about if you have a relly huge rig.
lets say 400 rgb fixture and 100 or more movers! how would you manage the plot window. Loads of informations in a small place. Might be kind of messy!!!
obviously I might be wrong......
Marco:hogsign:

Well, if they end up going with color labels, wouldn't this all be possible in the groups view...just set up your different groups and apply color labels?

But, yes, it does look very "Vista-ish"....next, you'll want a pen to stab yourself in the eye with. (That was for Matt....)

Hello,

yes I copy the idea of Jon too, with the color labels and the Group Window, it will help a lot on large rigs. I can live very well with this type of solution

Tom

I've seen many semi-visualizing solutions in consoles and few them are good. We should really think what is the usefull amount of information, cause easily we can end up having just too much to handle and we have real visualizers also. Something neat, nice and simple would be nice. Example for me the vista way is just too much...

[quote=bellons] how would you manage the plot window. Loads of informations in a small place.
I was thinking about 3 or 4 plots (layer?) max, so we can sort layers by fixture or position (up, Middle, Floor...), according to the preferences of each one, and of course a tool to select numbers of lines and colunnes.

First time i saw that, it was on Compulite MLC, i fond this vues very helpful, and we can, with one eye, see and do lot of things quickly.

This must be very simple, but, for me, that's a powerful tool.

[quote=srautane] vista way is just too much...

Agry with that point.

Thanks

i guess there is many ways this can be improoved if we(or they, as in developers) just comes up with an idea that is good enough..

-but i guess i probably will be very satisfied with color coding, and some icon/bitmap coding.. that together with a "Zoom" so that i can make those buttons as small/large as i wan't or need.. -The zoom part is something i'd really like to see soon.. those pallette buttons are way to big for my liking..

[quote=ahelgor]i guess there is many ways this can be improoved if we(or they, as in developers) just comes up with an idea that is good enough..

-but i guess i probably will be very satisfied with color coding, and some icon/bitmap coding.. that together with a "Zoom" so that i can make those buttons as small/large as i wan't or need.. -The zoom part is something i'd really like to see soon.. those pallette buttons are way to big for my liking..

That "Zoom" sounds nice or at least a few options how many palletes per view. Maybe also an option for Show fewer buttons which removes unused groups but doesn't compact the view.

I like the Idea of the Zoom function........
As Anders said..... we don;t need the buttons to be that big.

Would the pallets per page thing work???
Because everybody displays there pallets differently,
Like some will have a full page for Beam and half pages for everything else etc etc.

So to do that would mean having a set page size.
But having the zoom would mean we can just shrink the buttons to create more space :):):)

Kris.

[quote=jxgriffi]Well, if they end up going with color labels, wouldn't this all be possible in the groups view...just set up your different groups and apply color labels?

But, yes, it does look very "Vista-ish"....next, you'll want a pen to stab yourself in the eye with. (That was for Matt....)

Of course not, it's perhaps not detailed enough, each cell without X is a fixture, each color is the color of the fixture on stage, G is if a gobo is used, circle if iris is not @full. That more a vizual output than a group view.


And yes it's perhaps "Vista-ish", "Gran MA-ish", "MLC-ish" ...... But if an idea is good we can use it as Vista, Gran MA, MAXXYZ .... had used Hog II goods ideas

thanks
Steph

We've discussed the possibility of adding a basic plot or wireframe stage view to the Wholehog 3. This is currently logged as feature request #6035.

I think what's important here is to give users as much information as possible, along with the ability to visually select fixtures, without trying to implement a full visualizer. I certainly think this is possible and it's already on the to-do list.

I'm totaly agree with you, and impatient to see this function.
I think that the limit of most information as possible is that the console keep full speed.

I know it's been a while . . . but what about something like what the ETC Emphasis where it has WYG built in . . . now granted thats an extreme example. . . but what the ability it import a drawing in some common format like a PDF or the drafting programs actual file? I understand this is a huge idea . . . but maybe it can lead somewhere.

Eric,

Being able to import a file to use as a 2D or 3D stage view is a good idea that we've considered.

Implementing a full-featured on-board visualizer has the potential to cause more hassles than it fixes. Here's why:

1) Visualizers are extremely resource intensive. I want all of my console's available resources dedicated to generating DMX.

2) Visualizers are constantly improving and as they do, they take advantage of the latest hardware and generally require even more from hardware and software. Console hardware isn't generally field upgradable and doesn't change often enough to keep up.

3) By offering ethernet connectivity to ESP Vision, WYSIWYG, Capture, and MSD, users can choose the visualizer that they like best and run it on a dedicated pc (even a laptop) sitting next to the console.

There's a number of other considerations, including the significant development that would be required to develop our own visualizer or the royalties that would have to be dealt with if we partnered with an existing visualizer.

In the long run, I think it's best to keep any stage view on the console fairly simple. I think it should present basic information about position, colour, and beam and I think it should offer a visual interface for selecting fixtures.

I do, however, like the idea of importing CAD files or possibly image files for use in this effort. Once we've decided on interface and functionality, these will play a part in what file types would make sense.

Thanks.