Jump to content
Vari-Lite Controls Support Forum

NPhillips

Regulars
  • Posts

    103
  • Joined

  • Last visited

Posts posted by NPhillips

  1. 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.

  2. 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.

  3. 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?

     

    If you only want to see the programmed memories in the memory stack - simply press F7 or click on the soft button in the top right hand corner of the CDW, and hey presto all the unprogrammed memories disappear 8)

     

    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.

     

    The intention is that you show all memories when you are programming the show and then switch to show programmed memories only when running through the memory stack.

     

    This mode also has the advantage that the current/next memories remain on view in the middle(ish) of the monitor screen as you progress through the memory stack using the Go button.

     

    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).

     

    Point Cues (or Insert memories as I think we prefer to call them) are under review at the moment as there have been similar comments about the unwanted ones which are permanently displayed and cannot be deleted.

     

    We intend to make the memory inserts function similar to the Frog method, eg if you insert a memory between 2 and 3, say 2.5 you only get (and see) 2.5 and not 2.1, 2.2, 2.3 ..... 2.9 as you do on the Illusion at present.

     

    Beauty, that is how I would expect it to be... we sure think a like... sometimes :lol:

  4. 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! :D

     

    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]

  5. Yes, one of our R&D guys also commented on this and after revisiting the Illusion after several years on Frogs, I agree :)

    ROCK ON!

     

     

     

    With regards your second point, I can see how being able to move channel data between parts would be useful. 8)

     

    Do you have any thoughts or ideas on how you would like to do this using the existing front panel controls :?

     

    Existing front panel controls being the key phrase here :lol:

    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...

  6. Would it be facetious if I said look at the submasters screen on the monitor :P

     

    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! :D

     

    I assume you mean by looking at the submaster section on the front panel of the desk itself :?:

     

    Yes, looking at the handle and knowing that there is something in it. Confirmed.

     

    Having checked through the spec again, I don't think we use a solid light in the submaster flash buttons at present; therefore this could be used to indicate that the sub contains data (channel data or transferred memory) as you suggest.

     

    However, a flashing light is already used to indicate that data is being output from a submaster, but not from the current page (ie Page overlay).

     

    Not such a big issue... one could get over it... 8)

  7. 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! :D:D

     

    We all know what happens in that case! :D:D

  8. 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.

  9. 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.

  10. 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)?

  11. 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.

  12. 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...

  13. 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.

×
×
  • 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.