bugreport ?

Hi

 

Is there any way I can report a bug on the Ion? 

Even the Wiki-search does not know anything.

 

Ill just post it here as well:

I made a cuelist L20, and loaded it onto the faderwing (eg fader 1)

Now I made a cuelist L29 (it's been automaticly loaded onto the wing at fader 11), don't know why, I did not ask for it...but anyway)

Now I wanted to move that cuelist to another fader( eg fader10), so I loaded it onto another fader (10), and wanted to delete (using shift+both buttons) the old one(11). 

But both were "removed" now.

And when I tried again to load the right one, both returned to both the faders (10+11). How can I delete one of them now?

*edit*

It only occures when i try to load the cue on the same fader again (at 10, 11 will load also, and viceversa).

Loading it onto another fader  (9) only gives me one cuelist (as I was wishing for), but then again, when I deleted that one(8) and reload it back to 10, both 10 and 11 are reloaded again.

 

ETC Ion, V2.1.0, 

 

 



[edited by: JustinM at 8:01 AM (GMT -6) on Wed, Jan 15 2014]
Parents
  • Edit; Hans beat me to the reply!

    This is currently the expected behaviour but is going to improve in the future.

    A cuelist will map to the first available fader when it's recorded and playback, which will happen it you have auto playback turn on and almost all people should. When the cuelist is auto played back and mapped to a fader it's given a playback number (which is different to the cuelist number).

    When you mapped the cuelist to fader 10, it's mapped with the same playback number as fader 2. This is because if you want the cuelist on different fader page you want them to be the same playback (by default). I don't want the cuelist on page one in Cue 15 and the same cuelist on page 5 still sitting in cue 0!

    When you first released the cuelist from fader 2, you were only removing the mapped cuelist from the playback and because fader 2 & 10 are the same playback number you removed the cuelist from both faders.

    What you needed to do was use Shift+Load a second time to make the fader unmapped.

    This can all be very confusing and this is why it's going to change in the future. This is a little clearer on a console with faders because an unmapped fader is black and when it has a blank playback it's a dark grey.

    I hope this helps.

    Nick 



    [edited by: Nick Simmons at 9:35 AM (GMT -6) on Wed, Jan 15 2014]
  • Hi

    Thanks for the answers. But still, it's not complete how it should be. Just try it yourself.

    Breaking the link by releasing both faders is not an option, becouse deleting one is deleting the other at the same time.

    Second, if I reload the same cuelist on a different fader, all seems okay. But when I reload it on the fader I had the original "error" the second fader is loaded also.

    Above is(or was at least until v2.0) also when loading a sub.

    And yes, ofcourse you can load a cuelist or fader to multiple pages. When changing pages you get a "arrowDown" to let you know the same cuelist is activated elsewhere. So that's not the issue I think.

    Ill look forward to any updates. I still have a lot of issues with this little kid and I'm only scratching the surface of it's capabilities. If it only could be a little less stubborn and accept some variaties in syntaxes, It would be apriciated by a lot of people here. 

    Thanks

Reply
  • Hi

    Thanks for the answers. But still, it's not complete how it should be. Just try it yourself.

    Breaking the link by releasing both faders is not an option, becouse deleting one is deleting the other at the same time.

    Second, if I reload the same cuelist on a different fader, all seems okay. But when I reload it on the fader I had the original "error" the second fader is loaded also.

    Above is(or was at least until v2.0) also when loading a sub.

    And yes, ofcourse you can load a cuelist or fader to multiple pages. When changing pages you get a "arrowDown" to let you know the same cuelist is activated elsewhere. So that's not the issue I think.

    Ill look forward to any updates. I still have a lot of issues with this little kid and I'm only scratching the surface of it's capabilities. If it only could be a little less stubborn and accept some variaties in syntaxes, It would be apriciated by a lot of people here. 

    Thanks

Children
  • Yes, sorry this is difficult to explain even in person sometimes (which is why it's going to change). It is working as it should, sadly not as you're expecting. When you start working with multi cuelist you need to have a good understanding of how the console works. There are lots of reference materials to help, and this should help with the other syntax problems you're having. But post here and people will help.

    http://community.etcconnect.com/forums/t/6560.aspx

    When you say deleting you are just removing the cuelist from that playback and at the moment both of these faders are the same playback. So removing (deleting) one will remove the other one because they are the same.

    If you go to Setup {Displays} {Setup} {Show} {Show Setting} in the top right corner you will see 'Fader Config' in here you have 4 options for each fader. Sub, Playback, Grandmaster, Unmapped. At the moment you will have two faders set to Playback and they will have the same 'Mapped To' number, this is the playback number NOT the cuelist number. In this display you could make another fader a playback with the same number and then you go back to live you will see the cuelist on the third fader.

    In the fader config, when you set a fader to Sub and change the mapped to number you are setting the sub number but this isn't the case with playback, you can not set the cuelist number in here!

    What you need to do it 'Unmap' both of these fader and then map the cuelist on the fader you want. You can make these faders unmapped in the fader config section of setup or by using Shift+Load (both bump buttons) twice. You need to do it twice because the first time is just removing the cuelist (this is what you are seeing) the second time makes the fader unmapped!

    Sorry you are having problems but multi cuelist isn't the easiest place to start.

    Shift+Load Twice on both faders (even when they look empty) and then load the cuelist again and you should be set.



    [edited by: Nick Simmons at 2:57 PM (GMT -6) on Wed, Jan 15 2014]
Related