Jump to content
Zero 88 Community Support Forum


  • Content Count

  • Joined

  • Last visited

  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 next to play in the fader unless the operator were to key: [memory][1][0][0][enter]. That then selects memory 100 (as it had done before for edit live), making it next in the stack. The problem of updating changes in other memories can be solved with "update in". Memory 12 is active in the playback, I decide I want channels 1-4 @50 - this is where the command line comes in - where now I should be able to say, "update in memory 12 and memory 100 thru 400 enter"... see? This principal should work in both cue only and tracking modes of operation ... keeping in mind that cue only requires the operator to define track or not and tracking is the opposite, the operator defines cue only or not. Although, in the example above, say we were in tracking mode, would still be true as the update would be saved in those memories regardless of blocks or level changes. To say "update in memory 12 and memory 100 enter", while in tracking mode, would update 12 and 100 to track until change. "update in memory 12 cue only and memory 100 enter", would only affect the change in cue 12, but would track forward until change from memory 100.
  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 the end of the stack being the exception). Beauty, that is how I would expect it to be... we sure think a like... sometimes
  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: Yes, no problem with that. I am referring to a time key allowing the timing to be modified in the syntax which would read: [save][memory][1][2][time][7/6][delay 5][information][the party begins][enter]
  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...
  • 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.