Jump to content
Zero 88 Community Support Forum


  • Content Count

  • Joined

  • Last visited

Everything posted by NPhillips

  1. Hmmm... lots of figuring to be done on this idea... How would the 20 across display be effected? How about the ability to move/organize channels graphically? :?
  2. I would continue to check that for I know it is rare that I use the mouse to save memories or groups for that matter...
  3. No problem, but the above post from K-Nine is a reference number regarding the review of the suggested feature "inhibitive submaster". Currently the Illusion 500 does not have the provision for such a submaster.
  4. Sounds like Carl is looking for an inhibitive submaster (working in reverse). I would have to agree. In your example K-Nine, channels 1 thru 10 would be at zero (unless captured as a captured channel 8) ) unless the submaster inhibiting them was placed at full (or any point in between). This is useful for many reasons especially in situations as described by Carl as well as with ML's. This would be a submaster type.
  5. Having a command line all the time would solve this... I am running a technical rehearsal and [GO] on cue 12. We are now in cue 12. When I want to modify channels 1-4 @ 50, the operator simply keys [edit live][1]thru][4][@][50][save][enter]. Done. So I am sitting in cue 12 and now want to modify cue 100 live. The operator keys [memory][1][0][0][edit live]. Memory 100 is live in edit live while memory 12 remains in the fader. Saving or simply closing edit live memory 100 puts me back in memory 12 on stage since it remained in the fader. Memory 13 (or the next memory from 12) will be the
  6. I agree, [@][clear] would be a good way of releasing captured channels... In the command line: [clear] = clears last 1 entry [clear][clear] = clears command line entire
  7. Paul, I have sent the file your way...
  8. I am questioning whether or not this is necessary, or if it is (which in some situations I quite like it), if there is a way to get rid of it when cueing a show with gaps? Yes, this I know, the problem is it switches back to shall all once one edits a memory. I believe it should remain in stay or follow indefinitely as defined by the user. I am finding that switching between the two modes following an automatic switch caused by a save from edit live is not acting as such. The display, when [F7] to follow, jumps ahead beyond the current and next memories in the stack (with th
  9. I understand that (fading that is)... but how does one quickly bring up a handle and yet have the ability to have a timed fade?
  10. I don't have any problem suggesting that we swap the fade up/down times around - I assume that the delay up/down times should also be swapped for consistency Yes, this would be a correct assumption! Having checked other screens on the Illusion (eg Submasters) and various screens on the Frog series of desks, the Memories screen does seem inconsistent and I cannot think why it was never noticed before :? US designers... :twisted: Onto your second point, you can enter a fade time using the front panel numeric keypad, an external keypad or by using the control wheel. :wink
  11. Existing front panel controls being the key phrase here The user can go to a part and say: [channel][1][enter] and now channel one is in the part the user is currently in. The problem comes with offering the ability to have channels move in differing parts...
  12. No, you could say that... but I will say this back: That cannot be done if you are doing something else on the console (AT present time that is). Example: edit live, mofify channel data, save, loose changes, or cancel... the designer is working and I just want to know if a handle has something in it or not! Yes, looking at the handle and knowing that there is something in it. Confirmed. Not such a big issue... one could get over it... 8)
  13. I agree with you completely (except for the date format -- just depends on what you grew up with!). Primarily I noticed it in the disking functions where a write to disk has a time/date stamp. When it comes to disks and files, it is best not to confuse the operator! We all know what happens in that case!
  14. And the undo of channel edits need to be workd out, eh?
  15. Yeah, we are use to that already though... Ken Billington walks in and starts calling out, "@50, @75, @05" Jennifer Tipton walks in and starts calling out, "@ 2, @25, @5 percent" You know how that goes...
  16. I agree. Although, we must find a way to eleminate an entire string of commands in the command line with a single or double key press.
  17. I am talking about the Channel Data Display and the CDW! In my post the Channel Display Window = CDD Channel Display Window (Channel or edit live, etc.) = CDW
  18. Guest, Please note that this is a minor crash problem compared with crashes/bugs I have experienced with the likes of ETC Expressions, or Wholehogs, or Compulite consoles. The Illusion 500 reboots rather quickly, no data is lost (including the changes which caused the crash). Please do not so hastily judge a product.
  19. Ok, so an arrow up followed by and number, and an arrow down followed by a number would not fit on the memory bar when zoomed in? The problem with running in Cueline is that the designer cannot glance up at memory and get the timing. The timing must be graphically calculated, taking more time than the memories screen. Anyway, I guess my point is that cueline is not likely to be used as much as it should as it does not provide the designer with quick timing information.
  20. The biggest problem we are having with the colors of the channels is in the Channel Display Window where one would be running the rehearsal from. The designer has no way of know what the channels have done or are doing as they are all white. As for the other displays, what if the bar graph or channel number had an arrow to indicate up, down, or no movement (tracking)?
  21. But clearing selected channels would be fine as long as they remain captured (their modified levels remain regardless of console state). It is a real problem that only one thing can be done on the console at a time. [@][enter] has been used on the Obsession and Strand for many years, and every Broadway designer and programmer usees it daily.
  22. I guess this is just an Obsession thing where the syntax can adapt to the designer... One can easily say "@ 2" and the light is at 20%, "@ 25" and the light is at 25%, "@ 02" and the light is at 2%. Using the decimal just adds another keystroke to something that could be done without the extra stroke. Perhaps this is not "single digit percentage" but a new mode...
  23. OK, I can see that, but cannot [undo edit] be that safety net? I think the process needs to be sped up to keep highend users happy for sure.
  24. So in the course of programming this festival, I am finding the saving of groups to be quite time consuming. I, and the designers, are waiting for a group to "save show". Is this necessary? It makes the process rather slow. Also, this "saving show" occurs when making a loop or others in the memory stack... it takes time.
  25. Is it necessary to save the memory information? On other consoles, it is not necessary to save a cue to get it to hold a label or a timing information.
  • 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.