| MoveFaderAfterFaderStart | |||||
| If you are using TurboPlayer with a mixer console with active motor faders there might be a problem. If a user starts an element with a fader-start (which means: by grabbing the fader and moving it up) then it can happen that TurboPlayer wants to handle fades via controlling the motor of the fader, whileas the user has his finger at the fader and works against the motor. Therefore, TurboPlayer does not try to move the fader in such a situation by default.
As TurboPlayer does not know when the user has removed his finger from the fader, a simple (and not always fitting logic) has been implemented. Turboplayer will not execute any fades within the first half of an element. The fades in the second part and at the end of the element will be executed. This is the default behaviour, which can also be achieved by setting this parameter to false. If you set this parameter to true, TurboPlayer will always try to execute all fades. This might mean that the user has to work against the fader movements of TurboPlayer, if necessary, but this setting is especially useful if you have a mixer console, which has extra line open/close or on/off buttons and the users normally have all faders open and start elements by pressing the open/on button on the console. |
|||||
|
|||||