For both Hog 4 OS and Hog 3 OS this is the core rule of the remember fader values option:
If "remember fader values" is turned OFF: then when a list or scene is set to a level by a physical master and then that physical master goes away (page change) the list will not playback at that intensity level if executed from the directory. Instead it will playback at 100%
If "remember fader values" is turned ON: then when a list or scene is set to a level by a physical master and then that physical master goes away (page change) the list WILL playback at that intensity level if executed from the directory.
Now, here's where the difference is between Hog 4 OS and Hog 3 OS when "remember fader values" is turned OFF:
In Hog 3 OS the stored fader value is lost immediately once the master reappears on a playback bar. The physical position of the fader wins. (remember fader values off)
In Hog 4 OS the stored fader value is not lost. Instead the stored value is restored once the master reappears on the playback bar. The physical position of the fader moves to match the stored value. (remember fader values off)
Why the change in Hog 4 OS? Because with motorized faders we can put a playback's last known fader position right back onto the physical master to assist the user in restoring the page as it was when they left it. Since the playback is released it doesn't cause any harm to the look on stage. We feel this is a plus for users and is desired even when remember fader values is turned off. (it seems some disagree)
There debate here gets heavier when we look at this behavior as it pertains to HTP faders. When a list is set to HTP the Hog 4 OS restores the HTP's fader value (just like its LTP brothers) as well as puts it's intensity onstage when it appears on a physical master. This is problematic if the stored level of the HTP is not where the user wants the HTP fader value to be when they come to a page where the HTP fader is on a physical master. Where the user wants the value to go for an HTP master when it pops up on a page is not always the same.
The user may want one of three things to happen: 1) Restore HTP to wherever the current physical fader is set (HOG 3 OS)… not always the best thing since the physical fader may be at full 2) Restore HTP to wherever the stored fader value is (HOG 4 OS)… most consistent 3) Restore HTP to 0 to prevent the HTP from coming onstage (regardless of stored value or position of physical fader) (100% consistent and safe)
The current Hog 4 OS implementation only supports one method which is to restore HTP to wherever the stored fader value is set even when remember fader values is turned off.
I believe what I am hearing from this thread is that when "remember fader values" is turned off, the Hog 3 OS methodology is preferred despite the benefit that the motorized faders provide in the Hog 4 OS which is to always match the physical position of a fader to the stored value of the playback (even with RFV turned off)?
For both Hog 4 OS and Hog 3 OS this is the core rule of the remember fader values option:
If "remember fader values" is turned OFF: then when a list or scene is set to a level by a physical master and then that physical master goes away (page change) the list will not playback at that intensity level if executed from the directory. Instead it will playback at 100%
If "remember fader values" is turned ON: then when a list or scene is set to a level by a physical master and then that physical master goes away (page change) the list WILL playback at that intensity level if executed from the directory.
Now, here's where the difference is between Hog 4 OS and Hog 3 OS when "remember fader values" is turned OFF:
In Hog 3 OS the stored fader value is lost immediately once the master reappears on a playback bar. The physical position of the fader wins. (remember fader values off)
In Hog 4 OS the stored fader value is not lost. Instead the stored value is restored once the master reappears on the playback bar. The physical position of the fader moves to match the stored value. (remember fader values off)
Why the change in Hog 4 OS? Because with motorized faders we can put a playback's last known fader position right back onto the physical master to assist the user in restoring the page as it was when they left it. Since the playback is released it doesn't cause any harm to the look on stage. We feel this is a plus for users and is desired even when remember fader values is turned off. (it seems some disagree)
There debate here gets heavier when we look at this behavior as it pertains to HTP faders. When a list is set to HTP the Hog 4 OS restores the HTP's fader value (just like its LTP brothers) as well as puts it's intensity onstage when it appears on a physical master. This is problematic if the stored level of the HTP is not where the user wants the HTP fader value to be when they come to a page where the HTP fader is on a physical master. Where the user wants the value to go for an HTP master when it pops up on a page is not always the same.
The user may want one of three things to happen: 1) Restore HTP to wherever the current physical fader is set (HOG 3 OS)… not always the best thing since the physical fader may be at full 2) Restore HTP to wherever the stored fader value is (HOG 4 OS)… most consistent 3) Restore HTP to 0 to prevent the HTP from coming onstage (regardless of stored value or position of physical fader) (100% consistent and safe)
The current Hog 4 OS implementation only supports one method which is to restore HTP to wherever the stored fader value is set even when remember fader values is turned off.
I believe what I am hearing from this thread is that when "remember fader values" is turned off, the Hog 3 OS methodology is preferred despite the benefit that the motorized faders provide in the Hog 4 OS which is to always match the physical position of a fader to the stored value of the playback (even with RFV turned off)?
