Skip to main content

Ok, first let me explain how we have our scenes setup. We have many many scenes with a fairly large amount of fixtures tied to mydmx. A few of the heavy intense scenes have duplicate scenes, the duplicate scenes have gysers activated for 2 [or more] seconds and are set up to loop once then jump back to the matching scene without the gysers pumping smoke. Originally, this is how we had them keyed:

Scene Whatever
[SMK] Scene Whatever

The above two scenes would be hot-keyed as so:

"R"
"CNTRL+R"

The scene activate by the CNTRL+Key combo would be the smoke while the other is the same scene without the smoke.

The Issue:
The "CNTRL" key or any combination "CNTRL+Key" when used as key/scene bindings muffs the saved file object. The interface recognizes the "CNTRL+Key" combination while the scene file is loaded into memory for use, but as soon as you close the file and attempt to reload it, mydmx hangs up and will not load the file, thus rendering the file unusable. When we discovered this issue we tried to go into the file and make changes, but the saved files are serialized in binary format and not formatted xml files. This is an issue with both versions (feb and nov) of mydmx 2.0 for windows.

Has this issue/bug come up before? Is there plans to patch this on the next release?



Thanks...
Original Post

Replies sorted oldest to newest

Ok, you are correct, the "Nov" version does not allow "CNTRL+Key" for scene hotkeys at all - however, the "Feb" version does, and this is where the problem exists. When we created our scenes with the "CNTRL+Key" combinations, we did it in the "Feb" version and that is when we noticed the issue. When the file wouldn't load, we moved to the "Nov" version and had hoped it would load with that version, however it would not load.

Now, in our scene files that we created with the "Feb" version, we also had "SHIFT+Key" combinations, but the "Nov" version doesn't recognize (WILL NOT TRIGGER WITH SHIFT) those combinations. The November version will allow you to bind, for instance, "R" as a hot key and also "r" - however, it will not trigger the "R" with the "SHIFT+r" key combination, you have to hit "CAPS-LOCK-ON" then "r" to trigger "R", it will not trigger with "SHIFT-r". This is the reason why we have to go back to the "Feb" version as the "Feb" version works fine with "SHIFT+Key" combinations.

With that said, it now appears that maybe this "CNTRL+Key" issue came up sometime long ago in the past and as a quick fix the developers completely removed all "KET+" combinations which broke the "SHIFT+Key" combo in the November version.

Attached (link) is a scene file with 2 blank scenes, but with the "CNTRL+Key" combos active so you can see what it is doing when loading the file.

http://csmansys.com/F.zip
Hi Jpenn, yes I am aware of the SHIFT+ also not working. I was told recently that it will be back in the next release which we should start beta testing very soon here. So we do plan to have the SHIFT+ commands back. I had honestly never heard of the CTRL+ commands before your post. I'll give your file a look and let you know. Thanks! It might be possible if you send us your main .dlm file we might be able to have the engineer fix it that way it works for you in this latest release. If you wanna send a link for that also, i'm sure we will see what we can do for you if anything. Let me know. Thanks for your feedback! We appreciate it.
Jingles, we had a backup of the file so we really didn't lose much time.

As for the "CNTRL+Key" combination, that would be great if that also can be made to actually work properly in the next scheduled updated version. The issue is when loading the file with any "CNTRL+Key" combo bound to a scene, it appears to hang up right when it is 'constructing' the object from the file memory stream (maybe even during deserialization). I am thinking that is where it is at as even after you close the mydmx application it never clears from the workstations/computer processes list and you have to go in and terminate it manually.

Also, for reference, the file hangs/errors right when it hits the interpretation of the key command for the scene, for example:

SCENE 1
SCENE 2
SCENE 3
SCENE 4
SCENE 5
SCENE 6

Lets say you have your scenes ORDERED exactly as above, and you have [SCENE 5] bound to a "CNTRL+Key" combo, MyDMX will hang right as it is loading [SCENE 5] into memory - you can see this by closing the "loading scene" progress window when it hangs up and looking at your loaded scenes, 1 2 3 and 4 will be loaded but 5 and 6 will not.

BTW: We really enjoy using the software/controller, we have a very large amount of fixtures controlled by the software and our only issue thus far has been the key combo issue as noted in this thread.

Thanks

Add Reply

Post
×
×
×
×
Link copied to your clipboard.
×