Multiple Addresses in the Address Text Field with Magic Sheet Channel Target

I am setting up a magic sheet on an Element console and I want to be able to see the patch information on the sheet (so I can print off one sheet and have all the current information about how the plot/console is set up). To do this I added a text field to each channel target object (just the traditional tombstones). Nearly all of my channels have only one address assigned to them but those that have more than one (two or three at most) do not display the full list of addresses assigned to them, instead they only display one of the addresses. I can't figure out how it is deciding what address of the multiple addresses to display in the text field (it doesn't seem to necessarily be the lowest one, highest one, etc). It also doesn't indicate in any way that there are more than one addresses assigned to that channel. Anyone know if it's possible to get it to display the full list of addresses in the address text field?

Parents
  • Most likely the address displayed in MS is the address patched to Part 1 (P1) of the Channel. The real gotcha here is that there is no way (that I am aware of) to assign a Channel Part to an object in MS.

    I don't have the direct fix for this and if anyone else has a better suggestion I would also like to know the best way to achieve this.

    The workaround I use for this is to assign the object in MS as an Address (Target) instead of a Channel (Target).  Adding a Channel Field to that object will still allow you to display that information along with Address (Absolute or Port/Offset).

    In the pic below, Channels 11, 13, and 15 all have multiple dimmers patched to them.  In this instance, the object is assigned to be an Address.  I added the Address (Port/Offset) and Channel information to the fields for that object.  The trade off is that you can't click on it and control it as you would a channel if using ML Controls, Direct Selects, etc.  This trick works well for displaying information but not for interactive control.  If you click in the object, Address populates on the Command Line as opposed to Channel.


    Another trick I have used for this is to create a second object below the Channel object.  The second object can simply be assigned to an Address (Target) with an Address field and you can take away any borders or fill colors so it mimics a label.  After the Address is assigned and I am done editing the two objects, I will group them together, that way if I need to move items around in an MS I only have to move one object.

    EVeik

  • maybe i'm not thinking this completely through, but i guess the solution would be to use objects with target = Channel (by address). you define the target by selecting an address, but when clicking it, it will post the channel to the command line.
Reply Children
  • Ah yes...I forgot about Channel (by address). I just tested this and the Target ID = Address number. Selecting the object for control does treat it like a Channel.

    LightGuy145 - Here is the caveat. The field to display the Address is Target ID. If you put Address or Port/Offset in the fields, it will display Part 1 of the Channel.

    Thanks Ueli.
  • I believe I understand the way you are working around the issue in your first post. I can see how that would be useful if you were trying to have your magic sheet also be a fully detailed lighting plot. I have considered going that route but I'm not sure if it's ideal for the venue and its users. The adding a separate address target and grouping it to the channel target is far from ideal because it requires a lot of manipulation of the magic sheet if the plot changes. I'm not following the "Channel (By address)" solution. If I take a symbol and make the target "Channel (By address)" for a channel that has multiple addresses assigned, and then add a field for "Target ID", I do not see more than one address listed. Did that work for you? Also, when I click on that symbol with the mouse I get "Chan Error: Number Out Of Range" posted to the command line.

    It would be handy if there were separate field options for different parts of a channel. It would also be handy if it just displayed the addresses as a list for an address field. Obviously, this would become problematic if you had a lot of addresses assigned to a single channel. My application is strictly conventional fixtures though, only one or two addresses assigned to most channels. I'm really just trying to get my patch information to also be part of the magic sheet so I can print the magic sheet and use it as a reference when making plot changes. Formal paperwork is rarely used or, if used, retained and properly updated in this small community theater so I'm trying to use the magic sheet in the console as the source of information about the plot (without necessarily making the magic sheet a fully detailed lighting plot, though as mentioned above I am still considering that option).
  • channel 1 has 2 parts, part 1 patched to address 100, part 2 at address 200. the two objects are Channel by Address, as target ID the address (100 or 200) and the field where it says 100 or 200 is set to Target ID
  • I think I am following you now. This would prevent me from using the traditional tombstones as objects because the number at the top of the tombstone would no longer be the channel number, instead it would be the address number, which would be confusing. Strangely, if I set up a non-tombstone object as described above I can click on it and get the correct channel number posted to the command line. If I do exactly the same thing with a tombstone object I get "Chan Error: Number Out Of Range" posted to the command line. So for some reason it doesn't like tombstone objects with this approach.

    This also requires me to have separate objects for every single address, which is what I was trying to avoid. I think this would be a workable solution for setting up a magic sheet that would double as a lighting plot though. I'll have to think more about how I want to set up the console and the sheet for this venue and the implications it has for users. I still think it would be handy to be able to display a listing of the addresses assigned to a channel.
Related