Your OLE visualizer experience Sucks

Hi Matt.  Thank you for your input.  We can certainly consider changing some of this behavior.  But you make it sound as though this has been an ongoing complaint that we are simply ignoring.    We don't think that is the case.  I didn't do a forum search, but believe me, if this had been a complaint, we would have responded and looked into it.  I do recall that we've gotten posts asking why we do what we do - one just after your post, in fact.   And there may have been comments that people might prefer it didn't slow the refresh rate, but not to the degree that they thought it was impeding their work. 

 Have you been speaking with people off of the forum about this topic?

Just so you know, we respond to "far too polite posts" and "angry, passionate" posts with the same level of importance.   Also, this is an open forum.  As such, we have NEVER deleted a post from anyone.  And we won't.

Again, thanks for the input.  We will take your comments under consideration.

Take care,

a

Hello Anne.

Please have your team investigate how you can make your OLE visualizer experience a better one for those who do not own a console.  Around the world there are many console programmers who cannot effectively program a decent show with the limited plotting times allocated by their hirers.  So naturally we often do this from home.  Certainly not an ideal situation but definately a reality for many of us.

Although I have never written to your staff in the past to address this issue ( this forum post aside ), I would be very surprised if nobody has ever addressed this as a major corcern with the EOS/ION OLE design.

I do find it odd that your software programmers did not foresee, in the initial program concept design, how the software protection is really going to work against the end user ie show programmers in my position.  It's actually enough to cast someones impression of your console range into a negative light and therefore not good for your company.

If there is any doubt to how irritating it is to program a moderately complex show on the current OLE through a visualizer then try it, as an exercise, for an hour or two.  You too will see that it is a terrible experience.

For any personal rudeness taken I do humbly apologize as I am actually a very reasonable and laid back person in day to day life.  Upsetting people is not the norm for me.

And thankyou for your response.

Yours sincerely

Matt

Are you referring to Capture Polar, or Cast WYSIWYG?

I am a WYSIWYG user.

Anne,

I wanted to share a scenario from last month that I think is relevant to the discusion of the OLE capabilities. I am an ION owner (for my company/freelance work) and as of last January I work full time in the Music department of CSUSB. Since I am a theatre guy and we share a building with the Theatre department I of couse hang with the tech theatre folk here on campus and offered to loan them my ION for there fall musical. This has already spurred a search for funding to replace the aging Express and Hog500 desk that are currently installed.  

I love the Ion and I think that as a theatre desk it, and the EOS family are my first choice for theatre (and why I bought one). So then my tech who I hire for my summer gig, calls and wants to use the ION for his schools Fall production at another school. 

Problem is they load in and rehearse  the day that the other production closes. So I suggested that they use the OLE and I even did what you guys don't want and hooked it up to an artnet node and tested the output. 

In the end the flashing is just to much, even to get through a rehearsal, load in or focus. If it was at a longer interval the OLE would be useful in these situations.

However, I fully understand the logic behind not wanted the OLE to be used as a full fledged console that would allow every two bit cheapskate to  use the offline in lue of paying a few thousand dollars on an Element. If an organization is that hard up they should get a smart fade. It's the fact that you control your hardware and software that allows you to provide the type of suport that I have come to praise every chance I get. 

So all of this is to say, I agree with and understand the logic behind keeping the ION/EOS software locked down. But I can be added to the voices that would ask for it to be a bit more usable even for say a load in, a work call, demo to students etc. But to be useful in these situations I would also ask for ETCNET2 output. 

As always, thanks for your devotion to creating and continually improving the EOS family, they are amazing consoles!