Thats the same as saying that if someone accidently touches the volume up button it will eventually go to the max volume.
Accidentially hitting the volume up button would be a single push resulting in a single increment. Now if they were to inadvertantly hold the volume up button that would trigger multiple increments but upon release it would stop. With the bargraph if you touch the top accidentially you go to that level with a single push and even if they realize what they just did and tapped the bargraph in a lower location that first command typically has to execute before the 2nd command.
Accidentially hitting the volume up button would be a single push resulting in a single increment. Now if they were to inadvertantly hold the volume up button that would trigger multiple increments but upon release it would stop. With the bargraph if you touch the top accidentially you go to that level with a single push and even if they realize what they just did and tapped the bargraph in a lower location that first command typically has to execute before the 2nd command.
Not to mention that some processors don't like to be banged on that much and I've seen a couple situations where the thing got stuck in the 'too loud' setting before locking up.
I tend to put the buttons over the fader as well but keep the graphic off to the side. I put a rectangle over the actual button in the 2nd graphic. That way they can hit either thing to get some kind of action.
Accidentially hitting the volume up button would be a single push resulting in a single increment. Now if they were to inadvertantly hold the volume up button that would trigger multiple increments but upon release it would stop. With the bargraph if you touch the top accidentially you go to that level with a single push and even if they realize what they just did and tapped the bargraph in a lower location that first command typically has to execute before the 2nd command.
Wrong. If you use an active bargraph and set the range up time to 10 seconds, it takes 10 seconds to range from the lowest value, to the highest value.
If you press the top portion of an active bargraph it will range up, but will stop immediately when you release it...
If you press the top portion of an active bargraph it will range up, but will stop immediately when you release it...
I thought it worked more like a fade in or ramp up feature and not a hold to fade or hold to ramp feature. If that's the case I take back everything I said and thought and humbly appoligize for being wrong.
If this is the case a 10 second range time up or down as you & I think Phreak suggested is probably more than adequate.
I'll have to play around with this and see if I need to re-evaluate my views on active bargraph usage cuz this sounds like a useful tool now. I am suprised though that in all the other threads on active bargraph this never came up or maybe it did and I had my blinders on, hmmm. It's like waking up one day and discovering the world really is flat.
I thought it worked more like a fade in or ramp up feature and not a hold to fade or hold to ramp feature. If that's the case I take back everything I said and thought and humbly appoligize for being wrong.
If this is the case a 10 second range time up or down as you & I think Phreak suggested is probably more than adequate.
I'll have to play around with this and see if I need to re-evaluate my views on active bargraph usage cuz this sounds like a useful tool now. I am suprised though that in all the other threads on active bargraph this never came up or maybe it did and I had my blinders on, hmmm. It's like waking up one day and discovering the world really is flat.
try it, it works
I think the fade feature you're referering to is the "drag" feature.
Ok, it does work exactly as Yuri said. I set the range time up & down to 100 (10 seconds) and if I push & hold the active bargraph at the top (range low 0 & range high 100) until it maxed I get this in diagnostics:
Line 1 (13:38:05):: Rcv'd Level Value-1. line-<2306>$0D$0A
Line 2 (13:38:05):: Rcv'd Level Value-2. line-<2306>$0D$0A
Line 3 (13:38:05):: Rcv'd Level Value-3. line-<2306>$0D$0A
Line 4 (13:38:05):: Rcv'd Level Value-4. line-<2306>$0D$0A
Line 5 (13:38:06):: Rcv'd Level Value-5. line-<2306>$0D$0A
Line 6 (13:38:06):: Rcv'd Level Value-6. line-<2306>$0D$0A
Line 7 (13:38:06):: Rcv'd Level Value-7. line-<2306>$0D$0A
Line 8 (13:38:06):: Rcv'd Level Value-8. line-<2306>$0D$0A
Line 9 (13:38:06):: Rcv'd Level Value-9. line-<2306>$0D$0A
Line 10 (13:38:06):: Rcv'd Level Value-10. line-<2306>$0D$0A
Line 11 (13:38:06):: Rcv'd Level Value-11. line-<2306>$0D$0A
Line 12 (13:38:06):: Rcv'd Level Value-12. line-<2306>$0D$0A
Line 13 (13:38:06):: Rcv'd Level Value-13. line-<2306>$0D$0A
Line 14 (13:38:07):: Rcv'd Level Value-14. line-<2306>$0D$0A
Line 15 (13:38:07):: Rcv'd Level Value-15. line-<2306>$0D$0A
Line 16 (13:38:07):: Rcv'd Level Value-16. line-<2306>$0D$0A
Line 17 (13:38:07):: Rcv'd Level Value-17. line-<2306>$0D$0A
Line 18 (13:38:07):: Rcv'd Level Value-18. line-<2306>$0D$0A
Line 19 (13:38:08):: Rcv'd Level Value-19. line-<2306>$0D$0A
Line 20 (13:38:08):: Rcv'd Level Value-20. line-<2306>$0D$0A
Line 21 (13:38:08):: Rcv'd Level Value-21. line-<2306>$0D$0A
Line 22 (13:38:08):: Rcv'd Level Value-22. line-<2306>$0D$0A
Line 23 (13:38:08):: Rcv'd Level Value-23. line-<2306>$0D$0A
Line 24 (13:38:09):: Rcv'd Level Value-24. line-<2306>$0D$0A
Line 25 (13:38:09):: Rcv'd Level Value-25. line-<2306>$0D$0A
Line 26 (13:38:09):: Rcv'd Level Value-26. line-<2306>$0D$0A
Line 27 (13:38:09):: Rcv'd Level Value-27. line-<2306>$0D$0A
Line 28 (13:38:09):: Rcv'd Level Value-28. line-<2306>$0D$0A
Line 29 (13:38:10):: Rcv'd Level Value-29. line-<2306>$0D$0A
Line 30 (13:38:10):: Rcv'd Level Value-30. line-<2306>$0D$0A
Line 31 (13:38:10):: Rcv'd Level Value-31. line-<2306>$0D$0A
Line 32 (13:38:10):: Rcv'd Level Value-32. line-<2306>$0D$0A
Line 33 (13:38:10):: Rcv'd Level Value-33. line-<2306>$0D$0A
Line 34 (13:38:10):: Rcv'd Level Value-34. line-<2306>$0D$0A
Line 35 (13:38:10):: Rcv'd Level Value-35. line-<2306>$0D$0A
Line 36 (13:38:10):: Rcv'd Level Value-36. line-<2306>$0D$0A
Line 37 (13:38:10):: Rcv'd Level Value-37. line-<2306>$0D$0A
Line 38 (13:38:11):: Rcv'd Level Value-38. line-<2306>$0D$0A
Line 39 (13:38:11):: Rcv'd Level Value-39. line-<2306>$0D$0A
Line 40 (13:38:11):: Rcv'd Level Value-40. line-<2306>$0D$0A
Line 41 (13:38:12):: Rcv'd Level Value-41. line-<2306>$0D$0A
Line 42 (13:38:12):: Rcv'd Level Value-42. line-<2306>$0D$0A
Line 43 (13:38:12):: Rcv'd Level Value-43. line-<2306>$0D$0A
Line 44 (13:38:12):: Rcv'd Level Value-44. line-<2306>$0D$0A
Line 45 (13:38:13):: Rcv'd Level Value-45. line-<2306>$0D$0A
Line 46 (13:38:13):: Rcv'd Level Value-46. line-<2306>$0D$0A
Line 47 (13:38:13):: Rcv'd Level Value-47. line-<2306>$0D$0A
Line 48 (13:38:13):: Rcv'd Level Value-48. line-<2306>$0D$0A
Line 49 (13:38:14):: Rcv'd Level Value-49. line-<2306>$0D$0A
Line 50 (13:38:14):: Rcv'd Level Value-50. line-<2306>$0D$0A
Line 51 (13:38:14):: Rcv'd Level Value-51. line-<2306>$0D$0A
Line 52 (13:38:14):: Rcv'd Level Value-52. line-<2306>$0D$0A
Line 53 (13:38:14):: Rcv'd Level Value-53. line-<2306>$0D$0A
Line 54 (13:38:14):: Rcv'd Level Value-54. line-<2306>$0D$0A
Line 55 (13:38:14):: Rcv'd Level Value-55. line-<2306>$0D$0A
Line 56 (13:38:14):: Rcv'd Level Value-56. line-<2306>$0D$0A
Line 57 (13:38:14):: Rcv'd Level Value-57. line-<2306>$0D$0A
Line 58 (13:38:14):: Rcv'd Level Value-58. line-<2306>$0D$0A
Line 59 (13:38:14):: Rcv'd Level Value-59. line-<2306>$0D$0A
Line 60 (13:38:14):: Rcv'd Level Value-60. line-<2306>$0D$0A
Line 61 (13:38:14):: Rcv'd Level Value-61. line-<2306>$0D$0A
Line 62 (13:38:15):: Rcv'd Level Value-62. line-<2306>$0D$0A
Line 63 (13:38:15):: Rcv'd Level Value-63. line-<2306>$0D$0A
Line 64 (13:38:15):: Rcv'd Level Value-64. line-<2306>$0D$0A
Line 65 (13:38:15):: Rcv'd Level Value-65. line-<2306>$0D$0A
Line 66 (13:38:15):: Rcv'd Level Value-66. line-<2306>$0D$0A
Line 67 (13:38:16):: Rcv'd Level Value-67. line-<2306>$0D$0A
Line 68 (13:38:16):: Rcv'd Level Value-68. line-<2306>$0D$0A
Line 69 (13:38:16):: Rcv'd Level Value-69. line-<2306>$0D$0A
Line 70 (13:38:16):: Rcv'd Level Value-70. line-<2306>$0D$0A
Line 71 (13:38:16):: Rcv'd Level Value-71. line-<2306>$0D$0A
Line 72 (13:38:16):: Rcv'd Level Value-72. line-<2306>$0D$0A
Line 73 (13:38:16):: Rcv'd Level Value-73. line-<2306>$0D$0A
Line 74 (13:38:16):: Rcv'd Level Value-74. line-<2306>$0D$0A
Line 75 (13:38:17):: Rcv'd Level Value-75. line-<2306>$0D$0A
Line 76 (13:38:17):: Rcv'd Level Value-76. line-<2306>$0D$0A
Line 77 (13:38:17):: Rcv'd Level Value-77. line-<2306>$0D$0A
Line 78 (13:38:17):: Rcv'd Level Value-78. line-<2306>$0D$0A
Line 79 (13:38:17):: Rcv'd Level Value-79. line-<2306>$0D$0A
Line 80 (13:38:17):: Rcv'd Level Value-80. line-<2306>$0D$0A
Line 81 (13:38:18):: Rcv'd Level Value-81. line-<2306>$0D$0A
Line 82 (13:38:18):: Rcv'd Level Value-82. line-<2306>$0D$0A
Line 83 (13:38:18):: Rcv'd Level Value-83. line-<2306>$0D$0A
Line 84 (13:38:19):: Rcv'd Level Value-84. line-<2306>$0D$0A
Line 85 (13:38:19):: Rcv'd Level Value-85. line-<2306>$0D$0A
Line 86 (13:38:19):: Rcv'd Level Value-86. line-<2306>$0D$0A
Line 87 (13:38:19):: Rcv'd Level Value-87. line-<2306>$0D$0A
Line 88 (13:38:19):: Rcv'd Level Value-88. line-<2306>$0D$0A
Line 89 (13:38:19):: Rcv'd Level Value-89. line-<2306>$0D$0A
Line 90 (13:38:19):: Rcv'd Level Value-90. line-<2306>$0D$0A
Line 91 (13:38:19):: Rcv'd Level Value-91. line-<2306>$0D$0A
Line 92 (13:38:19):: Rcv'd Level Value-92. line-<2306>$0D$0A
Line 93 (13:38:20):: Rcv'd Level Value-93. line-<2306>$0D$0A
Line 94 (13:38:20):: Rcv'd Level Value-94. line-<2306>$0D$0A
Line 95 (13:38:20):: Rcv'd Level Value-95. line-<2306>$0D$0A
Line 96 (13:38:25):: Rcv'd Level Value-96. line-<2306>$0D$0A
Line 97 (13:38:25):: Rcv'd Level Value-97. line-<2306>$0D$0A
Line 98 (13:38:25):: Rcv'd Level Value-98. line-<2306>$0D$0A
Line 99 (13:38:26):: Rcv'd Level Value-99. line-<2306>$0D$0A
Line 100 (13:38:26):: Rcv'd Level Value-100. line-<2306>$0D$0A
So it sends a level change out for every increment. On the negative side if I'm going straight to the device I'd probably kill it with this many command in this short amount of time. If I'm queueing commands to regulate their delivery I could possibly overfill the queue or fill the queue and have the queue continue sending long after I've stop holding the bargraph.
If I return to 0 and start again by pushing & holding the top of the bargraph but this time release after a few seconds it does indeed stop like they said.
Line 1 (13:40:42):: Rcv'd Level Value-1. line-<2306>$0D$0A
Line 2 (13:40:42):: Rcv'd Level Value-2. line-<2306>$0D$0A
Line 3 (13:40:42):: Rcv'd Level Value-3. line-<2306>$0D$0A
Line 4 (13:40:42):: Rcv'd Level Value-4. line-<2306>$0D$0A
Line 5 (13:40:42):: Rcv'd Level Value-5. line-<2306>$0D$0A
Line 6 (13:40:42):: Rcv'd Level Value-6. line-<2306>$0D$0A
Line 7 (13:40:42):: Rcv'd Level Value-7. line-<2306>$0D$0A
Line 8 (13:40:42):: Rcv'd Level Value-8. line-<2306>$0D$0A
Line 9 (13:40:43):: Rcv'd Level Value-9. line-<2306>$0D$0A
Line 10 (13:40:43):: Rcv'd Level Value-10. line-<2306>$0D$0A
Line 11 (13:40:43):: Rcv'd Level Value-11. line-<2306>$0D$0A
Line 12 (13:40:43):: Rcv'd Level Value-12. line-<2306>$0D$0A
Line 13 (13:40:43):: Rcv'd Level Value-13. line-<2306>$0D$0A
Line 14 (13:40:44):: Rcv'd Level Value-14. line-<2306>$0D$0A
Line 15 (13:40:44):: Rcv'd Level Value-15. line-<2306>$0D$0A
Line 16 (13:40:44):: Rcv'd Level Value-16. line-<2306>$0D$0A
Line 17 (13:40:44):: Rcv'd Level Value-17. line-<2306>$0D$0A
Line 18 (13:40:44):: Rcv'd Level Value-18. line-<2306>$0D$0A
Line 19 (13:40:44):: Rcv'd Level Value-19. line-<2306>$0D$0A
Line 20 (13:40:44):: Rcv'd Level Value-20. line-<2306>$0D$0A
Line 21 (13:40:45):: Rcv'd Level Value-21. line-<2306>$0D$0A
Line 22 (13:40:45):: Rcv'd Level Value-22. line-<2306>$0D$0A
Line 23 (13:40:45):: Rcv'd Level Value-23. line-<2306>$0D$0A
Line 24 (13:40:45):: Rcv'd Level Value-24. line-<2306>$0D$0A
Line 25 (13:40:45):: Rcv'd Level Value-25. line-<2306>$0D$0A
Line 26 (13:40:45):: Rcv'd Level Value-26. line-<2306>$0D$0A
Line 27 (13:40:46):: Rcv'd Level Value-27. line-<2306>$0D$0A
Line 28 (13:40:46):: Rcv'd Level Value-28. line-<2306>$0D$0A
Line 29 (13:40:46):: Rcv'd Level Value-29. line-<2306>$0D$0A
Line 30 (13:40:46):: Rcv'd Level Value-30. line-<2306>$0D$0A
Line 31 (13:40:46):: Rcv'd Level Value-31. line-<2306>$0D$0A
The only benefit I see to this is that it acts like a regular up/down button being held with the benefit of having a cut off point (it won't go past the point where it's being held).
For lighting I definitely prefer having the time range time up & down set to 0. Even the default 2 (2/10th of a second) might cause problems if you could possibly push and release it fast enough and so the sent level turns out to be some mid way point. If I use it with Lutron and have the level issue a button push then the Lutron programming will handle the fade in/out feature.
For volume the press & hold bargraph seems sort of counter intuitive and would require some text to explain how it functions. Ideally I like to design a TP so a guy walking off the street can use it. Having to hold a bargraph inorder to get it to work complicates things. Likewise after trying the "drag" function I don't think I care for that either.
At least I learned something that I erroneously thought I already knew but I'm still in favor of up & down buttons for volume control and not active bargraphs. I still like bargraphs and/or numerical readouts for volume display.
a press and hold bargraph can be pretty easy to use if your graphic is just a couple of arrows, that look just like volume buttons...it will give the same result at the end of the day.
I use the drag-style only for 'mixer-style' level control e.g. matrix switchers (on an advanced page away from everyday user muckaroundage), but there's so much more fun to be had with levels than just controlling volume and lights...
Instead of tracking online/offline status of the touch panel, you can add a channel code to the level button and only adjust when the button is pushed.
Instead of tracking online/offline status of the touch panel, you can add a channel code to the level button and only adjust when the button is pushed.
Comments
Not to mention that some processors don't like to be banged on that much and I've seen a couple situations where the thing got stuck in the 'too loud' setting before locking up.
I tend to put the buttons over the fader as well but keep the graphic off to the side. I put a rectangle over the actual button in the 2nd graphic. That way they can hit either thing to get some kind of action.
Wrong. If you use an active bargraph and set the range up time to 10 seconds, it takes 10 seconds to range from the lowest value, to the highest value.
If you press the top portion of an active bargraph it will range up, but will stop immediately when you release it...
If this is the case a 10 second range time up or down as you & I think Phreak suggested is probably more than adequate.
I'll have to play around with this and see if I need to re-evaluate my views on active bargraph usage cuz this sounds like a useful tool now. I am suprised though that in all the other threads on active bargraph this never came up or maybe it did and I had my blinders on, hmmm. It's like waking up one day and discovering the world really is flat.
try it, it works
I think the fade feature you're referering to is the "drag" feature.
Preciseamundo.
If I return to 0 and start again by pushing & holding the top of the bargraph but this time release after a few seconds it does indeed stop like they said. The only benefit I see to this is that it acts like a regular up/down button being held with the benefit of having a cut off point (it won't go past the point where it's being held).
For lighting I definitely prefer having the time range time up & down set to 0. Even the default 2 (2/10th of a second) might cause problems if you could possibly push and release it fast enough and so the sent level turns out to be some mid way point. If I use it with Lutron and have the level issue a button push then the Lutron programming will handle the fade in/out feature.
For volume the press & hold bargraph seems sort of counter intuitive and would require some text to explain how it functions. Ideally I like to design a TP so a guy walking off the street can use it. Having to hold a bargraph inorder to get it to work complicates things. Likewise after trying the "drag" function I don't think I care for that either.
At least I learned something that I erroneously thought I already knew but I'm still in favor of up & down buttons for volume control and not active bargraphs. I still like bargraphs and/or numerical readouts for volume display.
I use the drag-style only for 'mixer-style' level control e.g. matrix switchers (on an advanced page away from everyday user muckaroundage), but there's so much more fun to be had with levels than just controlling volume and lights...
For example:
level_event[dvTp,1]{ if([dvTp,201]) send_string dvAudio,"'VOL',itoa(level.value),10,13"; }I did not come up with this, but it seems like a good way to handle things.
Jeff
I hadn't thought of that one. I'll try that next time. That should stop the Levels-to-Zero Offline Event.