Making many channels into one channel

Hi Stephen,

If you send me your Obsession II show I will take a look at it to see why you aren't getting the Mac 2Ks.  If there is a personality in the Eos library that exactly matches your data, I can probably find a way to force it to use that personality.  Otherwise, there are a few other tricks that might work. 

Send an email to eos@etcconnect.com attacth the file and mention my name on it somewhere, and it will get to me.

Ann

Hi Stephen,

After importing your show file I can see that you are getting all of the personality types except for the one you had named "LTS M2kAni".  This fixture type did not import because there is nothing in the Eos library which has a similar footprint.  Under these circumstances, there are a couple of ways to deal with this.

1)  You can choose the "Import as Custom Fixtures", which should play back your show correctly and use the parameter names that were in the Obsession show.  However, you won't have access to any of the library data which Eos has, like ranges for gobos, wheels, etc.

2)  You can import twice and then merge the results.  To do this, choose the "Import As Library Fixtures", and then save the show file as an Eos show.  Then, go back and choose the "Import As Custom Fixtures", and delete all channels except 701 and 732, the two channels that didn't come in correctly the first time.  Now Merge the saved show into this one.   Now you should have all of the fixture data and control, although the custom personality will have different names for the parameters.  (Eos show files can be merged, but imports overwrite everything.) 

3)  You can request an addition to the fixture library.  The downside here is that we receive many requests, and it does take time to process each.

Thanks for sending in the show.  It was helpful to see what the problem was.

Ann

Hi Stephen,

After importing your show file I can see that you are getting all of the personality types except for the one you had named "LTS M2kAni".  This fixture type did not import because there is nothing in the Eos library which has a similar footprint.  Under these circumstances, there are a couple of ways to deal with this.

1)  You can choose the "Import as Custom Fixtures", which should play back your show correctly and use the parameter names that were in the Obsession show.  However, you won't have access to any of the library data which Eos has, like ranges for gobos, wheels, etc.

2)  You can import twice and then merge the results.  To do this, choose the "Import As Library Fixtures", and then save the show file as an Eos show.  Then, go back and choose the "Import As Custom Fixtures", and delete all channels except 701 and 732, the two channels that didn't come in correctly the first time.  Now Merge the saved show into this one.   Now you should have all of the fixture data and control, although the custom personality will have different names for the parameters.  (Eos show files can be merged, but imports overwrite everything.) 

3)  You can request an addition to the fixture library.  The downside here is that we receive many requests, and it does take time to process each.

Thanks for sending in the show.  It was helpful to see what the problem was.

Ann

I have a similar question.  

I have a show that started on an original Obsession, then moved to Obsession II, now moved to EOS.  At some point while we were still on Obsession II we added a bunch of LED fixtures, they were all patched as individual channels for each parameter of each light.  Is there any way turn these individual channels into LED fixtures, they would like to write some effects this year, but this would be easier if I could make them into LEDs.

-Bryan

Try this thread: http://community.etcconnect.com/forums/p/2370/9057.aspx#9057

I read that thread and I assume the syntax I want is:

[cue] 1 [thru] [enter] 201 [thru] 236 {offset} 3 [copy to] 301 [thru] 312 {red} [enter]
(and so on for each color parameter) 

Am I wrong about the syntax?

However, when I try to enter this command, {red} is not available in the CIA, only {Intens} is available.

I have already patched 301-312 as Generic RGB LED.

-Bryan

You need to read the fine print of the post :-)

In order to get the target parameter to show up, you need to write it as a macro.  Actually, you can simply write three macros, one each to enter {red} {blue} and {green}.

Ideally, you would be able to use Recall From to pull the intensity channel in to the LED parameter, but last I tried it, that syntax didn't work.

-Josh

I just tried that same command this time as a macro.  When I executed the macro the {red} was missing from the command line and it copied the data into the intensity parameter for channels 301thru 312.

I tired this in both Live and Blind, and re-wrote the macro twice to make sure I didn't miss something.

-Bryan

I was playing with this last month in preparation of having to do this for an upcoming show. I found a couple things. First and foremost, I could not get it to work any which way I tried. This includes the exact sample that Ann posted in the other thread.

If I try to type it manually, you find that you can't get all the parameters as the NP selection box will only show you available NP's for the source channel, not the destination channel.  So if you are trying to copy an intens channel into the RED part of a RGB unit, red is not an option. So I tried adding a Red NP to Part 2 of my intensity channel.

This allowed me to Type in [1] {Intens} [Copy] To [10] {Red} into the command line. The problem of course being that as soon as I pressed {Red} I got a syntax error.

I also tried  [Recall From], and this did not work.

If I try as a Macro, I have the same problem as Bryan had with {Red} missing. This is because when the Macro is running, the syntax error occurs, but if you press enter when a Syntax error occurs, it just closes the command line.  If you remove your last [Enter] form the macro, you will see the synax error.

What it boils down to is that it looks like the console does not allow you to copy data from one parameter type to another.

Ann & Anne... am I wrong in this conclusion? Are you guys able to move different types of data to different places and I'm just missing something? I have a feeling it is the desk being too smart for its own good and it is throwing the syntax error as it thinks you are making a mistake.

Thanks

EDIT:

Just went back and played with it again. I made a blanket statement that Ann's example didn't work. Ann's example does work to copy a NP to an Intensity Parameter. I can't get the inverse to work.

I believe the key to making this work is to make sure that you are including {Intens} in the macro.

e.g.

1 {intens} [Copy To] 5 {Red} [Enter] 

2 {Intens} [Copy To] 5 {Green} [Enter]

3 {intens} [Copy To] 5 {Blue} [Enter]

Try this using the macro editor to build the macro. 

Just want to give the thread a bump. Has anyone successfully been able to copy an Intensity Parameter into a Non intensity Parameter? I' have been able to get a NIP into a Intensity channel. Just wondering if I"m missing something basic.

And yes, marmenda, I do have Intens in my macro.

Thanks,

Now that my run is over, I was able to try the suggested method on my console (Now it's become a challenge to get this to work instead of a requirement, plus if I get it to work I'll have it for next year) and I was unsuccessful.  I put {intens} into my macro and still nothing.  The previous post imply that this was possible in 1.4.something.  I'm running 1.8.0, is there something that has changed in the software that is causing this not to work?

On a side note, I tried downloading the 1.4 offline editor, but it couldn't open my 1.8 show file (which I half expected).  Is there a way to downgrade a 1.8 file to 1.4?

I’m sure it’s not possible to copy an Intensity to a NIP.

This wasn’t possible in version 1.4.3 either. I tried to copy my revolutions intensity to the scroller fan and it wasn't possible then or now.

I just tested it in 1.8 to sure and it does work.  Be sure that you are using the macro editor to build the macro.  Also, when you are done the macro should look something like the photo I attached. 

Here is what the execution looks like.

Select the Cues in blind Spreadsheet.

Then, run the macro.

Just worked for me as well in the 1.8 OLE.

-Josh

Thanks Matt.

Not sure what I missed the first few times I tried it on the console. But I was also just able to make it work using the off line editor. I swear I did exactly what you did, but hey. I'm happy its working now. Thanks!

I've actually only tried moving intensity data to a NIP in the OLE.  Is it possible that the CopyTo method doesn't work directly on the console?  Maybe someone with console access can confirm.

-Josh

I used the console for my tests.