To avoid confusion, please resend the questionable VI-frame to , and write something like "for Dietz" in the subject line. I'll forward the file internally.

Thanks a lot in advance!

Hi!

I had to send the mail to Martins private email, because the VSL mail server won't accept the email due to the attachements file size (13mb).
Just tried sending to your email account at VSL, but the mail was returned.

-tom

Ok, I see. I'll take care for that.

Kind regards,

 Hmm...I have to learn to test all possibliities before reporting a problem :)

After some more testing it seems as this GUI thing is NOT connected to my existing template. If you start an empty VE server, create lets say 2 instances of VE Pro. Load 5 VI Pro in each instance. Add MIR to all channels. Select a venue. Now everything works as intended. But, if i now save this new metaframe, close the VE Pro server. Restart the VE Pro server and load the metaframe containing the two VE Pro instances.
Now the GUI bug is there.

So on my system this GUI bug appears when reloading VE Pro Server metaframes. Can someone try this and see if it reproducable on other systems?

Thank you!

-tom

 Hi again.

An additional note on this "bug", which I had not noticed before - in MIR, the "grid" and "hotspots" overlay does not work here. Or, as mentioned above, it does not work after loading a metaframe.   

Also, I know that everything mentioned in this thread appeared after the latest update. There weren't any GUI issues on the previous versions.

-tom

@tommalm said:

 Hi again.

An additional note on this "bug", which I had not noticed before - in MIR, the "grid" and "hotspots" overlay does not work here. Or, as mentioned above, it does not work after loading a metaframe.   

Also, I know that everything mentioned in this thread appeared after the latest update. There weren't any GUI issues on the previous versions.

-tom

Oh! This sounds a lot like you're experiencing some kind of OpenGL-issue with your graphics card. Thanks for reporting.

The OpenGL venue hasn't changed since the first release version actually, so it's indeed more likely that you're having hardware/driver problems. Make sure to install the latest version of the Nvidia driver.

 Hmm. Yes it may seem to be a local problem, since nobody else has experienced the same. I will try updating my drivers.

Ok, I've done a clean install of the latest nvidia drivers, but it did not help.

One more note to the grid/hotspots issue. When I load up a metaframe the "grid" and "hotspots" does not respond. The grid shows, but cannot be turned off. The "Hotspots" overlay does not show and does not resond to the button.

Now, on a test metaframe I have 2 instances of VE Pro with 5 instances of VI Pro 2 each. In the first VE Pro instance, If I click all 5 VIs, no matter which order, each label will turn white. When going from one instance to the next, the unselected instance does not revert to blue. When I have clicked all 5 instances the "hotspots" overlay and "grid" suddenly will work. So if I have activated the "Hotspots" button, the lit-up overlay will not show UNTIL I click the final fifth (1 through 5) instance of VI Pro. The label issue, however, still is there - all instances will be white.
Also, when clicking the first instance of VI Pro (the icon representation inside MIR), the corresponding label of VI Pro in the channel rack to the left, will turn white. Now this label, whichever instance I click first, will stay white until I have clicked through all 5 instances. This means that in the channel rack, the first VI label will stay white, indicated that it is selected, even though another instance is selected. So until I've clicked through all instances, the channel rack indicates that two instances are selected. But it seems this is just a graphical glitch because, there are no group selection active. For example, I cannot move both instances simultainiously.

This is the same for each VE Pro instance which is hosted in the metaframe. Also as I've mentioned earlier, when creating a new VE Pro instance, either inside this test metaframe or a new metaframe, none of this issues are present. It is when the metaframe is reloaded the problems occur.

-tom

The same thing just happened to me today.  My icons in MIR will not deselect.  I just added a few new instruments to my project today and they deselect correctly but all the previous instruments I already had in the project stay selected once I have clicked on them.

Sorry to hear you're facing problems. If this happens again, please make sure to report to support@vsl.co.at , including as many details as possible (OS, host application, software versions, etc.).

Thanks a lot in advance! 

Hi Deitz,

I think it may just be a low quality graphics card on my computer that wasn't refreshing my screen properly because when I reopened MIR today, all the instruments were deselected except for one as they should be.  Now that I know it doesn't truly mean I had all those instruments selected, I am not concerned. 

Thanks,

Becky