-
Posts
2,518 -
Joined
-
Last visited
-
Days Won
35
Posts posted by Jon Hole
-
-
Hi Huber,
It's not possible at the moment, but this syntax has already been requested as issue ZOS-5370.
You could go into Tracking Mode, make the change you want, and then jump back into Non-Tracking mode?
Best regards,
-
Would pressing the clear button after an update solve my other problem of an update not always working?
Almost certainly :-)
-
Dan's method should work, but you'll also want to change a setting within the submaster.
Go into the submaster setup window (hold SETUP and press the flash button of the submaster), choose 'Submaster Controls' and then choose 'Colour'. Now, the colour will be added as you move the fader, instead of being triggered at the trigger level.
-
Hi,
When you take a channel up and then bring it back down, you've put '0%' into the programmer, so submasters and memories can't affect that channel until you clear the programmer (the programmer always wins!).
Press the clear button, and then your submasters and memories should work fine?
Regards,
-
No need - I've added you to our Beta Test group.
You should find an extra forum within 'ZerOS Consoles' called 'Beta Test' which will have all the instructions and downloads.
Give me a couple of hours... after lunch I'll upload a new version of software (7.6.23)
-
Hi Sfalken,
it would be great if these command-syntax could support an additional TIME or FADE-command, like GO X.Y FADE 3.0 or something like that in order to use the same chasers in different scenes with different timing
I've been coming up with a very similar specification, but I can't promise this too soon I'm afraid :-)
we would really appreciate if at least the Solution XL would come closer to the ORB concerning some programming features
I think you will definitely find this over time. However, the processors are not as powerful in the Solution, so we can't bring you all the features of the ORB! We'll have to do some tests on Solution software to see what we can do.
Originally, we also had a look at the ORB, but as sometimes external productions also use our consoles, we needed that amount of faders to have a quick and simple access to every channel
I think several people were in this situation, which is why we released the ORB XF with the 60 faders which can be Channels, Submasters or Playbacks.
-
Perfect, thank you.
Added as issue ZOS-5441, our software team will look into adding support for this.
-
Hi Mike,
No problems. There is a possible bug that might be causing this, which has been fixed in the Beta software, so it might be worth giving it a go.
Best regards,
-
Hi Mike,
OK, let's try another method of finding out what's going on here.
If you open the system information window (listed under 'Other Windows' in the Output Window) the touch screen should be listed as a USB device. If you can copy the UID/PID from there, it may help track down what driver/kernel version is needed for us to support the Touch Screen.
If you're not sure what you're looking for, feel free to take a photo of that screen (you might need to take a couple of photos, as part of the window scrolls).
Best regards,
-
Hi Yattasin,
I believe we've sorted this with you by email now?
If that's not correct, please let us know!
Best regards,
-
Hi Mike,
I have upgraded to the beta build and dropped back to 7.6.0 and am still seeing the behaviour.
Did you see the behaviour whilst running the beta software, or just whilst running 7.6.0?
-
Hi Mike,
Please can you send me a photo of this list?
If you unplug the USB Keyboard and Mouse (so the touch screen is the only USB device plugged in) do you get anything in the list?
If so, select whatever is in the list, and see if you get a load of text appear on the screen when touching the touch screen
-
You could create a macro that says:
@@ RECORD ENTER @ . NEXT
That would speed it up and make it very quick
-
Hi Mike,
Thanks for trying this.
Unfortunately the link you supplied doesn't appear to be working, and I expect they only had Windows drivers there anyway... which ZerOS doesn't run on.
However, if it's possible to briefly install the Beta Software again, in SETUP> Desk Setup > Peripherals there's a button called "Input Capture".
If you go into this screen, select the touchscreen from the drop down list, and then move your finger around the screen, we will capture all the data that the monitor is sending through the USB port, which will help us determine why your monitor isn't working. Ideally, move your finger right to the edges, and into the corners, so we can capture as much information as possible.
There is a standardised protocol for touch screens (and two additional protocols for multi-touch screens) and we support all three of these in the latest beta, and have proved them working on other monitors. This suggests that BenQ aren't quite following the protocols somewhere. I'm not trying to shift the blame - they aren't the only one, and we've managed to add in patches for other monitors with similar problems, so hopefully we can do the same here!
Many Thanks,
-
Hi Lars,
Have you got any more news on this? Have you got any debug files?
We haven't been able to recreate any of these issues I'm afraid - it's all working fine, apart from the one bug I mentioned above.
Best regards,
-
Hi Huber,
The 'effects' palettes and window are 'wave' based effects, whereas the 'chases' are step based effects
Hope that clears things up
-
Hi Sfalken,
Can you in addition say if there is any plan to implement those commands similar to the ORB in later releases?
There aren't any plans at the moment, so I've added this request as ZOS-5439
do you have any idea concerning my prior question about the fixture levels window?
I've just replied to the topic: http://zero88.com/forum/topic/6561-edit-tracking-in-chaser-fixture-levels-window/
Best regards,
-
Hi Mike,
Thanks, that would be great.
If you have a few minutes after the show, maybe you could install the Beta Software and test the Touch Screen monitor. You can then backdate the software back to 7.6 afterwards if you prefer.
Please let me know how you get on :-)
Thanks
-
Hi sfalken,
Thanks for the feature requests. The second one isn't currently possible either, so I've recorded them both:
I've recorded your request to add the ability to edit steps in the fixture levels window as issue ZOS-5435, and to be able to get the tracking options directly from the console as ZOS-5437
Best regards,
-
Hi,
You can do this on a new cue stack.
Select a new cue stack by typing STACK x ENTER
Now, create 10 cues, Cue 1 with 1 at 100%, Cue 2 with 2 at 100% etc etc etc
Then, click 'Stack Setup', choose 'Chases' and click 'Turn into chase'. When you do this, you'll get several chase settings appear.
Hope this helps,
-
Hi Dan,
If you are interested in testing some Beta Software, I can add you to our Beta Test group? We just released the first Public Beta of the software today.
Regards,
-
I'm contractually obligated not to say.
(Actually, I'm not, but it makes it sound much more exciting...)
-
We've done a little spring clean of our forum to prepare us for the Summer!
Here are the changes:
- Operator Database has been moved up a level, so is now visible from the main screen.
- General Chathas been combined into a single forum, instead of split into several categories
- The old Light Factory link has been removed. For support on Light Factory, please visit their dedicated Yahoo! Group
- Beta Test forum (only visible to Beta Testers) has been cleaned up with the addition of an Archived Discussions forum for legacy topics.
If you have any questions or suggestions, please let us know!
-
At the moment, I setup the submaster flash button to Latch and record a Macro containing pressing the flash button
This is how I do it too.
An alternative (which gets a bit complicated) is to patch some channels onto a 'spare' universe (Universe 4 for example), and then connect Universe 4 to the DMX In on the back of the console with a small DMX cable. You can then assign that DMX In address to a submaster (Setup > Desk Setup > Inputs).
When programming, you can programme that channel into the memory, which will then trigger the submaster when playing back the memory stack.
There's no 'proper' way to do it, unlike the ORB.
Solo Function For Moving Lights
in ORB & ORB XF
Posted
Hi,
I've asked our software team to look into this for you, as I'm seeing the same thing in Non-Tracking mode (works fine in tracking mode). I've recorded it as issue ZOS-5469
Best regards,