• Date
    hydrogen
  • Date
  • Replies 6 replies
  • Subscribers 187 subscribers
  • Views 3071 views
  • Users 0 members are here

Various issues/annoyances with a recent show

Hi Friends,

Another show, another set of weirdities that I end up finding.  

1)  Having a channel active with a color property, and picking a color in the color picker, then doing +% changes the hue by the % rather than the intensity.  While it almost makes sense where this is coming from, I'd have to imagine that most use cases are going to prefer that to change the intensity rather than the hue, especially as the color picker is an already terminated command.

2) Is there any way to control which pane new tabs open in? My current setup has one monitor divided into four panes of direct selects, and one large monitor split into two panes of cues and live table.  I'd love for new windows to open on the large monitor rather than one corner of a 19" touch screen.

3) On the same layout note.. It seems like half of the time when I switch from blind to live I end up back in workspace one instead of remaining in workspace two on my larger monitor.  I can't find any rhyme or reason to when this happens though.

4) It would be nice if recalling channels from a prior cue also recalled their effect status and the rate/scale of the effect in that cue. In general I find effects do not behave the same way as most other data on the eos family, and it would be nice if they did.

Parents

  • 1) this is actually consistent with other parameters. Chan 1 Pan 50 Enter, +% will affect Pan. this is intended behaviour. Select Last +% will do what you're after.

    2) click the gears at the bottom left of the pane that should receive new tabs, choose "Open new Tabs here"

    4) can't tell you if this secifically will be solved, but in an upcoming version, effect data behaviour will get closer to how other data works.

  • in reply to ueliriegg
    1) I understand where the idea is coming from, I just disagree with it :). I think the difference is that if I manually put Pan on the command line, I'm probably going to want to modify the pan with +%. Most of the time I'm modifying the pan with the encoder though, and +% after using the encoder doesn't change pan. The color picker posts hue/saturation to the command line though, I'm not manually entering the hue, and so it seems wrong that eos assumes +% after the color picker wants to modify the hue (And why not the saturation?) 2) Great, Thanks! I hoped there was a way. 4) Can't wait!
  • in reply to hydrogen
    on 1) I have to agree with hydrogen just m 2p
  • in reply to FloBaeumler

    There may have to be a special rule if you use the colour picker and if you want to adjust Hue you'd then need to reselect Hue.

    We can not make this change for every other parameter, most of us are using this command hundreds or thousands of times a day for shutter controls.

Reply Children
  • in reply to Nick Simmons
    I'm not trying to take away from the valid use cases. Manually putting shutter on the command line and then modifying it is something I do frequently as well. However, I can't tell you the last time I clicked around on the color picker to find the right color, and then said "No, I think I want the hue 10% more or less". If anything I might want to adjust the saturation... but even then it's easy enough to get to. If I had to guess about a possible soltuion, I'd suggest making the color picker work in the background? Does the Hue/Sat values being posted to the command line benefit anything? Dan,
Related

www.etcconnect.com