Jump to content
Zero 88 Community Support Forum


  • Content Count

  • Joined

  • Last visited

Everything posted by karleaton

  1. Thanks, good to know that's in the pipeline. By the way the new play-backs are really cool. Cheers, Karl.
  2. I've just been looking at the release notes for the new ZerOS version 7.9.2 and playing with the Phantom version of the ORB XF with a view to upgrading our desk. I have just checked to see if there is a new version of the manual and it appears the latest edition available is from 2010 for version 6 of the software. Are there any plans to produce an updated manual?
  3. OK. Not exactly intuitive that a minus sign indicates no change but I suppose it's as good as anything else. However last night I recorded six or seven consecutive cues all of which were blackouts (hence no changes between cues) and some had the '-' and some didn't depending on the syntax used to record the cue. I'm also sure we have in the past had cues that were definately not the same where the second one had a '-' and acted as a snap fade. Editing the fade times manually from '3-' to just '3' resulted in the fade working properly. Unfortunately I'm not at the theatre at the moment so I can't try to recreate that scenario. Next time I'm over there I'll see if I can test this out.
  4. For a while we've had a problem with cues recording with negative fade up/down times. I've had a play around and have identified the circumstances. We have an ORB XF with Zeros 7.3 (although this also occured at previous versions). We run the desk in none tracking mode and the default fade time is set to 3 second. If we record a cue using "[Record] [Cue] n [snapshot] [Enter]" then it correctly records the cue with the default 3 second fade. This is the way I usually record cues in order to include any submasters that are active. If we specify that we want to use the default time "[Record] [Cue] n [Default times] [Enter]" then it also works correctly. However, if we record a cue using "[Record] [Cue] n [Enter]" then it records the fade time as 3- and the cue executes as a snap. Strangely, on switching the desk to tracking mode I find that "[Record] [Cue] n [snapshot] [Enter]" and "[Record] [Cue] n [Enter]" work. And it is the "[Record] [Cue] n [Default times] [Enter]" syntax that produces the 3- fade times! Any ideas as to what is going on?
  5. Just thought I'd update this topic to include the resolution that was arrived at via email (just in case anybody else encounters the same problem). I should mention that Jon provided the resolution way back in Feb, shortly after the above post, I just didn't think to update this topic until today. When control passes from one cue stack to another the desk checks to see if any of the channels are still controlled by the original stack (i.e. tracking is dependent on the previous stack). If no channels are still taking their level from the previous stack then the old stack is tidied up (or 'stomped'). Because we run in non-tracking mode the new cue stack (with the chase in it) grabbed all the channels and the old stack was therefore stomped. When we returned to the old stack after the chase it reverted to its initial state - hence the problem. Apparently the solution is to patch an extra (imaginary) fixture after the chase has been recorded and then record a cue on the old stack including the new fixture. I haven't had chance to test this out yet but it should do the trick.
  6. I'm currently pulling my hair out trying to add a chase to a cue. I have set up a second cue stack and recorded the chase steps to it. I have then converted this cue stack to a chase. So far so good. I have worked out that to start or stop this chase from cues in the default cue stack I need to add a macro to the cue. What I can't do is work out what macro commands to use. I did manage to get a cue to start running a chase using G2 but when I try to stop it in the next cue using R2 it dumps me back to the beginning of the cue stack (so pressing GO takes me to cue 1). Also is there an easier way of creating a simple generic chase and adding it to a cue because this way sucks!
  7. I have used the Windows Remote Monitor software with our ORB XF desk a number of times in Hand Held mode during focusing, etc. This has worked fine. Last night I decided to try using Remote Monitor in Monitor Mode to plot a show. I selected the Panel view and set up a lighting state. I then wanted to flip to the Desktop 1 view to see what level a certain channel was at. As soon as I flipped views the stage plunged into blackout. Flipping back I discovered the GM was now at zero. Every time I flipped views the same thing happened. I gave up and went back to using the actual desk (and running up and down stairs to check how states looked). Half way through the evening I suddenly lost all output. After a bit of head scratching I noticed the GM level on the screen was zero even though the GM control was up at full. Taking the GM down and back up resolved the problem. It transpired that somebody had decided to shut the computer down as I wasn't using it and this had also forced the GM to zero. The PC in question is a laptop running Windows7.
  8. Does the Orb have the facility to make noise? Yes, I know it's for lighting not sound But I'd really like it to beep at me when I enter invalid syntax or do something equally foolish. I'd even be happy if it called me a plonker. Anything to alert me to the problem so I don't soldier on in ignorance. And yes I know it turns the command line red when the syntax is wrong but to be honest I don't tend to look at the screen that much (I'm usually too busy looking for the keys I want to press). Similarly when the Orb wants me to do something (like confirm an overwrite whilst recording) it would be good if it gave the equivalent of a polite cough. Obviously, the ability to turn the sound off would be good as well for those who think lighting desks should be seen and not heard.
  9. On the OrbXF there is a Help key and the manual says 'The HELP key (ORB XF) can be used to access the online help on ORB XF.' Pressing the Help key seems to do precisely nothing. Is this intentional? Is it a feature which will be implemented in a later release? Or am I just not pressing it properly! Just wondering.
  10. OK, this is a probably a bit of a wild idea but I think it would be useful to have a Simple Mode setting. Let me explain. The Orb desks are really powerful desks with loads of really advanced features, which is great when you need those features. But, sometimes you don't: you just want to do basic stuff. At these times all that clever stuff can get in the way. Also, for anyone coming to the Orb from less powerful desks all of these bells and whistles can be intimidating. Hence I thought that having a Simple Mode would be good. Basically you could select Tracking, Non Tracking or Simple. When in Simple Mode: tracking would be turned off. recording (cues, subs, etc.) will record all of the current output. (what you see is what gets recorded - no need to worry about tagging). there could be an easy way to create chases without having to setup extra playbacks and macros and stuff. Perhaps a bit like on the Jesters. advanced options would not be displayed. The idea being that if you just want to program a couple of dozen simple cues you don't have to worry about tracking, tagging, snapshots, etc. You just set the output how you want it (using channels or subs) and do a "record cue n enter" then move on to the next. This would be a great help to people coming to the Orb for the first time. They could be productive from day one rather than needing to attend a course first or spend days working out how to get things to do what they want. They can then explore the good stuff later at their leisure. As I say a bit of a random idea but I thought I'd suggest it anyway. What do you think?
  11. Many thanks, you've answered all of my questions. I knew I was missing something (well, several things). It's always the problem with manuals - they're fine if you know what you're looking for. I did eventually find the master fader myself but that opened up a whole other can of worms. I moved both of the faders and then couldn't fathom out why all of my cues were snapping despite having fade times set, DOH! Any way I'm slowly getting the hang of things. Again, many thanks.
  12. I have been using our lovely new OrbXF for the first time in anger over the last few days, programming in cues for a show. Having perused the manual and using a bit of trial and error I got the job done but I'm sure I'm making it harder than it need be. Is there anything I can do to make things easier/quicker. Here's what I've been doing: The show has a number of lighting areas that are lit in various combinations. I first recorded each area as a submaster. For the first cue I brought up sub 1 and sub 2 using the faders and then did '[Record] [Cue] 1 {Snapshot} [Enter]'. That worked fine but bringing the submaster faders down didn't take me back to blackout as the desk was now outputting the newly recorded cue 1. I thought I'd be able to go to cue 0 but there wasn't one. So I did '1 thru 99 @ 0 [Enter]' to get back to a blackout but then I couldn't use the submaster faders because this command takes priority. So I recorded the blackout as cue 0 which the desk allowed me to do. However it didn't seem to like cue 0 and when I restarted the desk cue 0 went AWOL. Eventually I recorded a blackout as cue 99. For my second cue I brought up sub 1 and sub 4 and did '[Record] [Cue] 2 {Snapshot} [Enter]'. Then I selected cue 99 and pressed the [Go] button to get to a blackout before recording the next cue. And so on. I apparently need the {snapshot} to make the recorded cue include the submasters - is there a way to make this the default so I don't have to hit it every time? Is there a way to prevent cues being output as soon as they are recorded? Or a quick way to get back to a null cue? What's the position regarding cue 0. Other desks I've used always have a predefined cue 0 which is a black out. The Orb doesn't seem to do this and will let you record a cue 0 but then behaves oddly. Any advice will be gratefully received!
  13. Thanks Jon and Peter, I know it seems odd but I'm happier for knowing how the syntax works - too long spent in IT probably. Not sure how sensible this suggestion is but I'll put it forward anyway: CUE n RECORD <UDK> -> records the cue on the appropriate UDK, CUE n RECORD ENTER -> records the cue in the same way as the RECORD CUE n ENTER method. Not sure if that breaks anything else or if it's wise to bend the syntax in this way.
  14. Ah ha! When you put it like that it does make sense. I wasn't looking at the setting of levels when recording cues as being part of the RECORD syntax. Thanks for clearing that up. There is one unfortunate thing about having the "CUE n RECORD <UDK>" syntax and that is that when I slip into Strand mode and try recording a cue using "CUE n RECORD" it doesn't indicate I've messed up, it just sits there waiting for me to specify which key I want to record it to. If you're like me and you don't bother looking at the screens very often you can plod away 'recording' cues only to find none of them have actually worked. I know there's nothing you can do about that and it's probably a rare combination - a numpty who routinely uses the wrong syntax and doesn't bother looking at the screens after every command. I'm just so used to using that syntax and if the desk doesn't bleep in complaint I assume it's worked. Any way I shall get into the habit of using "RECORD CUE n". Fortunately Strand desks will accept that syntax as well so I'll still be all right when I visit other local venues that still use the 300 and 500 series desks.
  15. Yes, they are the correct syntax. However, on the Orb it seems that you can also delete cues using "CUE n DELETE" but you can't record them using "CUE n RECORD". It just confused me a bit because on the Strand desks you could use "CUE n RECORD" and when I forgot and did that on the Orb it just ignored me. However if I get it wrong when deleting a cue and try "CUE n DELETE" it works. I only originally posted because I wondered if it should/could also accept "CUE n RECORD" (for those of us converting to the Orb from other systems) but as Peter pointed out that syntax is already used elsewhere on the Orb. The simple answer, of course, is for me to use the correct syntax.
  16. Ok, so CUE n RECORD is reserved for use in recording a cue to the UDKs. But it still bothers me a bit. If you have to use RECORD CUE n to record cues then why not enforce the use of DELETE CUE n when deleting? Using a verb noun imperative actually does make more sense if you are aiming at english speaking users (i.e. RECORD CUE 1 is good English whereas CUE 1 RECORD isn't). Having said that using CUE n RECORD <UDK> promptly breaks the convention - something like RECORD <UDK> CUE n would seem to fit better. Sorry, I know I'm being pedantic but twenty odd years in IT has taught me that interfaces are far easier to learn and use if they are consistent (which is why Linux hasn't overthrown Windows).
  17. Many thanks, for the quick reply. I knew I was missing something obvious. I definately need to spend some time reading the manual and to get myself on the training.
  18. This is probably a silly question but how do you include subs when recording cues? I usually work by setting up a number of subs (cool wash, warm wash, cyc, etc.) and then build cues up using these subs. I've tried this on our Orb XF and I can't get it to work. I recorded the subs and put the faders into subs mode. Bring up the faders results in the subs being output as I would expect. If I then record a cue it doesn't seem to record any of the levels set using the subs. I just record cues with all channels set to 0. I'm sure I got this to work on the Phantom Orb some time ago but have no idea what I did to achieve it. I think I need to get myself on some training but in the meantime can anybody tell me what I'm doing wrong please?
  19. Just got our new Orb XF and have been 'playing' with it. Great stuff! I have spotted a minor inconsistency in the syntax. I'm used to the old Strand desks where you can record cues with the 'CUE n RECORD' syntax (I believe you can also use 'RECORD CUE n' but I never have). Other records e.g. subs work the same. The Orb only seems to support the 'RECORD CUE n' syntax, which is fine I can live with that. However when deleting cues it will accept either the 'DELETE CUE n' or the 'CUE n DELETE' syntax, which seems odd. Just thought I'd mention it.
  20. It's actually the TL Xtra that we've got. My question really revolves around work to implement requested features in the software. For example the ability to use submasters when programming memories, ability to use the Edit key to edit the current memory in run mode, provision of a back key, possibility to set times on memories using keypad (preferably blind), some form of blind edit, etc. Are there any plans for further software releases in the near future, if so which if any of the outstanding feature requests are likely to be included? Are any of the requests unlikely to ever get incorporated? The original Jester 12/24 is very intuitive and easy to work with. The TL and TL Xtra seem to have issues that make them less intuitive and at times extremely frustrating. Most of these issues (blind edit excepted) would seem to be fairly straight forward to address. I keep hoping that a new release will appear that fixes them.
  21. Given that half the topics in the TL section seem to be mine and the last posting before this was 10th December 2009 is it fair to say that the TLs are not exactly popular? Are there any plans for further software releases or has development now stalled? As lighting director for a local amateur venue I bought a TL to replace an aging and temperamental Strand LBX. In theory it does everything we need. Unfortunately there are several niggles which I have raised on the forum and with Peter Kirkup at the PLASA North show. These issues mean the TL is not popular with all of the people who have used it at the venue (about a eight people to date) and many still prefer to drag out the old Strand instead. If there is no chance of these issues being sorted any time soon we are going to have to start looking for a replacement desk. This would be a pity as I have a Jester 12/24 which I love and the TL should be every bit as good but for some reason it seems to drive people mental when they have to program it.
  22. We have had an issue recently with the key pad on our TL becoming unresponsive. When this happens all of the keys on the numeric pad seem to stop responding in program/record mode (except the @ key oddly). So typing "20 @ 50 <Enter>" produces just "@". Switching into setup mode and going into the test option indicates that the keys are working and are sending the correct values. The only way to get the keypad back into normal operation seems to be a restart. We have version 2.3 installed and I notice in the release notes for version 2.4 that it fixes JES 2713 which says "the command line is now enabled/disabled correctly after closing pop-up windows on the Main LCD in Program Mode". I was just wondering if what we are experiencing is related to that fault. I don't know if the problem has followed a pop up window as it hasn't done it to me, and the guy it did happen to isn't sure what leads up to the problem. I plan to upgrade anyway but won't be able to do so for a couple of weeks.
  23. Further thought - would it be possible to have the SHIFT + EDIT allow editing of the current memory instead of the selected? Not sure how difficult this would be to implement.
  24. Ah! that makes sense. If it was me I'd still have the Edit work on the current memory rather than the selected one as I'm most likely to want to tweak the one I'm currently looking at rather than the next one. And being a dipstick I'll probably forget back-step the selection to the current memory before editing. But that's just me !
  25. If I had to choose one thing to change it would be the ability to use subs in program mode (JES-2956). I have been showing a couple of people how the desk works and they have both picked up on the same thing. The thing with the edit key caught me out during a final dress rehearsal when I needed to tweak a level. I hit Edit made the change hit Edit again and overwrote the following memory by mistake. Using Edit in Record mode outputs the selected memory and allows it to be edited. Pressing it in Play mode leaves the current memory on the outputs and then saves the changes to the selected memory. Having noticed that I had overwritten the wrong cue ("Why does the preview look exactly like the current outputs? Oh ****!") I realised there was no way of correcting the mistake - which was were the desire for blind editing cropped up! What's worse I've since repeated the same error several times . I've now adopted the policy of tweaking by switching to Program mode, selecting the required memory and then using Edit. That way the worst I can do is output the wrong memory which is better than overwriting the wrong one. Guess that one goes down as user error!!!
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.