Jump to content
Zero 88 Community Support Forum

Edi

Regulars
  • Content count

    16
  • Joined

  • Last visited

  1. Hi kgallen, Yes I also experienced this. But only the first time I startet PhantomZerOS after a fresh installation. Thanks Edward. My machine is Acer Aspire 8930g Intel Quad Core I7 with 8GB of RAM and running Windows 10. So not really a weak machine, but probably that it was just recovered from sleep mode and some other things running in background. :-)
  2. I wanted to play around a little bit with PhantomZerOS (7.9.3) without any real lighting fixtures. So I tried to view the results of my programming in the DMX Output windows via the Z-Key. I added just a single Martin Rush MH1 Plus to the fixture schedule and used a "Vertical Line" effect on it. As soon as I opened the DMX output window, I saw the values changing, but PhantomZerOS did no more react to my inputs and mouse clicks. I had to shut it down with the task manager. Tried again... The same issue... Without continously changing DMX values (e.g. static dimmer values), there was no problem. It seems if the DMX output window allocates all the resources so no input get's through to the application... Can somebody confirm this happening for him, too? Is this just on PhantomZerOS or also on the real console?
  3. Hi Edward, Thanks for your response and logging it into your software tracker. Good to hear that I haven't done something wrong. By the way you and your team are making a really great job with you fast and good support! Best regards, Edi
  4. I patched four 1-ch DMX relays 1 - 4 to the console. The first cue I recorded to playback 1 activates relays 1 on channel 1. I then recorded a second cue to playback 1 which activates relays 2 on channel 2. In the cue settings for cue 2 I changed that this cue will be triggered with cue 1 after a wait time of 0,1 seconds. When playback 1 was fired with the MFF button everything works as expected. Relays 1 closes and Relays 2 closes shortly afterwards. I then changed the playback button to act as a flash button and again everything worked as expected. Cue 1 was fired and Cue 2 was automatically fired shortly afterwards, so Relays 2 closed with a short time delay after relays 1 and both fall back when the playback button was released. I then recorded another playback 2 where I did exactly the same for relays 3 and 4, and again changed the playback button behavior to act as a flash button. Now something strange happened... Playback button 1 no longer automatically triggered cue 2 in this playback. Only cue 1 was activated, the auto cue did not start... I changed the playback button back to "Go (fade)" and tried it, and the behavior was now again as expected - both cues were triggered correctly. I then changed back the button to "flash" and also now everything was ok. I played around a little bit an discovered, that each time I recorded another "relays cue", my flash buttons from the already recorded playbacks did not work as expected until I changed one of the playback buttons back and forth between "Go (fade)" and "Flash". All recordings have been done with basic tracking and disabled SmartTag on the current PhantomZerOS software. Have I done something wrong or is this a bug? I've attached my show file. I tried to save it at the state, when the buttons stopped working as expected, but I discovered that the problem did not exist when I loaded to show into the console. So to reproduce, you will have to record another playback as explained above. Relayproblem.isf
  5. Thanks Jon, I had some misunderstanding in my thoughts. I have not been aware, that I'm able to raise the intensity over the MaxValue, but I tried it on PhantomZerOS and saw, that only the output is limited but the target value for the intensity can go beyond that limit. Tracking (difference between basic / advanced) and "Smart Tagging" are really two topics which could need some visuals (e.g. flowchart) for easier understanding... I know this has already been discussed a lot, but I don't think that I've already completely got it.... Am I right with following understanding? - Snapshot: All fixtures and all attributes of them with their current values are recorded as they are NOW, independently if the fixtures are selected or the attributes are tagged (WYSIWYG) - SmartTag (without tracking): All fixtures with an intensity above 0 get recorded with all of their current attribute values independently if the fixtures are selected or the attributes are tagged (this is like a snapshot, but excludes all the fixtures with intensity @ 0) - SmartTag (with tracking): All fixtures with an intensity above 0 get recorded independently if the fixtures are selected, but only those attributes which have changed (the direction in which a changed attribute value is preserved depends on track forward / backward / both / cue only) What's the difference between basic / advanced tracking?
  6. Thanks Jon for the explanation. I understand how this is thought to be done, but I think I'd also like to have an overview of the home, default and limit values in an editable table style. Sure the home of one fixture can be edited when you select all fixtures, recall their home values, change the one fixture you'd like to adjust and again record it to home. But what if you'd like to raise the limited dimmer value of a fixture from e.g. 60% to 80% in the MaxValues? Do you first have to delete all MaxValues so you can set the intensity over its limit and afterwards redo all the limiting for all fixtures? I think this would be much easier in a table, also to have a quick answer why a light is just not as bright as it could be.
  7. Thanks Jon. Great to hear!
  8. Hi Kevin, This sounds reasonable to me. Another great possibility if your correct, but in my opinion this then should be an option in the MFF playback setup to have this as a "per fader decission". Regards, Edi
  9. I know that all lights with an intensity above 0 can be selected with ENTER ENTER. Especially for busking a show it would be great to have a possibilty to quick select all the active lights from a group of fixtures. For example while the front lights are active I would to quick select the four active moving heads in the back, which belong to a group of seven MH wash lights, to change the color. I could create a separate group with only those four MH's or could imagine to select the group of all seven back truss MH's followed by ENTER ENTER. Wouldn't it be great if the console then would automatically exclude all the MH's from my selection which have no intensity at the moment, so only the color parameters of the active lights are changed? That's just a thought if this could be of use for others too...
  10. I know that the values for Home can be changed by recording the values from the programmer to the home button by pressing REC followed by HOME. But what if I want to have different HOME values for different fixture types? For example the position for MH's on the back truss shall differ from those on the front truss and so on... Is there a possibility to keep them separate per fixture type? Same applies for setting MAX Levels and DEFAULTS. It seems that I'm missing the "Edit Fixture" option in the setup, which is explained in the FLX manual and has been replaced by the new Fixture Schedule. ..
  11. Can someone explain what the option "Page Holdover if active" does when it's enabled? I found nothing about it in the manual and forum. Thanks.
  12. Hi kgallen, Thanks for your response. Hmmmm, I'm not 100% sure if I understood for what this is for... When "Clear Fixture" removes just the fixture selection from the programmer, what do I do with the rest inside it? I played a little bit with it on PhantomZerOS and found only one situation where this could help: If you're programming fixtures during a playback and have entered e.g. "1 THRU 3" followed by ENTER and then "@ 75" and before applying the command with ENTER you have to adjust the intensity of a fixture currently playing back, then you can deselect the "grabbed" fixture and continue programming. (Commands in programmer turned to red letters when "playback fixture" is adjusted) But this does not work when the programmer only contains "1 THRU 3" or "1 THRU 3 @" or "1 THRU 3 @ 75". For me this is really confusing for what and when I can use this...
  13. Hi all, As I found nothing about those options in the manual and forum, could someone please explain following options which can be set on an empty UDK: - Knockout - Clear Fixture Thanks and regards, Edi
  14. Hi Edward, Thank you for your quick response and explanation how to remove the intensity data in relation with SmartTag. Also for clarifying the last step in the guide. Until now I just had the chance to play around with PhantomZerOS, but I'm really looking forward to get my hands on the real console. I like it a lot so far. Best regards, Edi
  15. Hi kgallen, Thank you for the quick answer. A very interesting article, although it's not answering my question, so don't mind, I really appreciate your suggestion. When I understood everything correct, the last step in the article programs a cue with following values (Intensity=0 / Red = 0 / Green = 0 / Blue = 0), so when the (latch) playback button is pressed, the fixture goes black. Is this for RGB-fixtures without a separate intensity channel? My question above is more about a possible bug in ZerOS or a misunderstanding of mine. :-) Regards, Edi
×