Remote Settings

menu: (../images/Menu/Menu_Settings.png Settings) -> (../images/Menu/Menu_RemoteServer.png Remote Settings)
RemoteServer
Here the remote control for Android smartphones etc. can be set and managed.
All settings are automatically saved when the program is terminated!

Note: Alternatively or additionally, the mouse remote control can be used - see the playback control

Connecting
Quitting the Server
RemoteControl
    Direction
    RemoteBoard
    PlayControl
    Jingles
    Scenebook
    Master
    DMX lamps
Reading out the instructions from the scenebook
Notes

The remote control

The remote control allows remote control of the liveShow software via an Android smartphone or - Andoid MP3 player. In addition, scene changes and directing instructions can be transferred to the device and read out.
Conditions:

Install the LiveShowClientRemote software on the Android device.

The installation file "LiveShowClientRemote.apk" can be found in the LiveShow folder under Remote / Android. This file must be copied to your Android device (via USB connection). Then start the installation by clicking on "LiveShowClientRemote.apk" using a file explorer.
Since you receive the program free of charge and do not have to purchase through the Google market, you must be able to install software of unknown origin on the Android device. You can turn this on in the Android settings under "Security-Unknown Source / Sources".
Note: In order to ensure that you can work with the remote during a show and the device does not fall into sleep mode, various settings are made on the Android device that can affect the battery. You should therefore start the remote control just before use. Of course, these settings will be canceled when you exit the program.

Connecting the show computer to an Android device

Step 1 .) Connect show computer and Android devices with WLAN / Wifi.
For a WLAN connection between two and more devices it always needs a WLAN / Wifi access point, which has an SSID (name) and a security encryption (WPA2 SPK), with a password / key. Who uses WLAN at home, probably has a WLAN router, which works as AccessPoint. On the way, this router is no longer available, but there are also ways to set up an access point:

Possibility a) A Hardware AccessPoint (this is the best alternative)
There are cheap WLAN access points to buy (about 50, - €).
In this case the show computer and the Android device are connected to/via the access point.  On the hardware access point, an SSID/device name and security encryption, with a key/password, must be set up. In addition, make sure that the show computer and the access point work in the same IP address space.

Note: With newer phones (newer Android version), it can happen that the phone does not establish a WLAN connection to the hardware access point, despite correct network settings. This means that a connection is established for a short time and then immediately disconnected again. This game goes back and forth a few times. In this case, you have to change the WLAN settings on the cell phone for the connection to the access point:
  1. In the connection settings ('Advanced Options') the 'IP_Setting' must be changed from DHCP to static. Then you have to enter a matching IP address, usually the first three numbers of the IP address must match the IP address of the hardware access point and the last number must be different (between 1 and 254).
    Example: If the hardware access point has an IP address: 192.168.0.1, then an IP address 192.168.0.xxx must be set on the cell phone, where xxx must NOT be 1. In this case, xxx may be a number between (2 - 254).
  2. The two specifications for the DNS servers must be changed from e.g. 8.8.8 or 8.8.4.4 to 0.0.0.0 in each case!!!


Possibility b) One of the participating Android devices takes over the task of an AccessPoints (the computer needs to have WLAN)
On an Android device, a mobile hotspot (tethering) is set up. This can be found on Android under Settings - more - tethering & mobile hotspot. The show computer and the other Android devices are then connected to the Android hotspot.

Possibility c) The show computer plays the role of an AccessPoints (for this the computer must have WLAN)
The computer can be set up as a virtual access point under both Windows and MAC OSX. However, this is quite complicated because the computers usually only allow the hotspot/access point if there is an Internet connection.

Again: A connection over the domestic WLAN router only works at home, at the venue the domestic WLAN router will not be available! Here you must either carry a hardware Accespoint or you use the virtual access points on your computer or Android device.

Note: The Android device must be connected to the computer (LiveShow computer) via WLAN before you can establish a connection between the Android remote control and the LiveShow software.

Note: With the introduction of IP6 addresses, problems may occur if one of the devices connects to the access point using the IP6 protocol and the other device has connected using the old IP4 protocol. Both devices must be logged on using the same IP protocol. It is best to switch off the IP6 protocol - instructions are available on the Internet.

Step 2.) Start the server on the computer under RemoteControl and start the Android app LiveShowClientRemote

RemoteServer <->  RemoteClientConnection
a) Start the Server
Under the menu: Settings - Remote Settings in the LiveShow program, open the RemoteControl window,

Each program on a computer that is to be accessible via a network must occupy a port, this is a number between 1024 and 65535.
RemoteServerPort
In principle you do not have to change anything here. If, however, you start the program again (it runs twice on the same computer), the second program needs a different port.
Caution: one port could also be occupied by another running program (eg liveShowMediaServer), in which case you must try until you have found a free port.

Then start the server with 'Start server'.  RemoteServerStarten The control point on the right should turn green.
If the control point is not green, the port may be occupied by another program.

Under 'Server IP', all IP addresses (IP4, IP6) are displayed under which the computer can be reached. This is just an informal ad.

 Note: It is likely that the first time the firewall will make a message and ask if the software is allowed to use the port. You should allow this in any case.

b) Set up users who are allowed to control the program remotely

 RemoteServerUsers

ButtonPlus A new user is created and this is displayed in the table.
To change the user name and the user password, simply double-click on an entry in the table and change it.
ButtonDelete This button will delete a selected user from the table. If the user is connected, his connection is disconnected.

PermissionControl If "control" is selected, the user can control the program via the remote control.
PermissionListen If "listen" is selected, the scene changes and the directional instructions are read to the user.

Additionally, you can specify for the selected user which elements are visible on the remote control.
Direction the director's texts for the current scene are displayed
Play here you can jump to the next/previous scene
Scenebook the scene book is displayed on the remote control and scenes can be started
Jingle all jingle and jingle groups are displayed and can be started
Master The main controls for volume / brightness,... are displayed and can be changed
DMX lamps This is used to set up the DMX lamps. All lamps are displayed and can be changed.


c) Start Android-App LiveShowClientRemote



The Android application LiveShowClientRemote is now looking for independent liveShow remote servers.
Again: The Android device must be already connected to the computer via network (WLAN / Wifi).
The display refreshes approximately every 5-10 seconds.

If a liveShow remote server is found, it is displayed at the top.
If the liveShow software runs several times within a network, you can select the desired liveShow remote server at the top.

  

Enter the user name and password, as defined in the liveShow software.
Now you can use the Connect button to connect the LiveShowClientRemote app to the selected liveShow remote server.

There may be several situations:
  1. The connection could be established and you can use the remote control normally.
  2. After about 20 seconds, the message appears that the connection has not worked:
  3.  The message 'Name or password incorrect' is displayed. Then you have to check whether you have set up a user in the LiveShow software (see point b above), and whether the entries on the Android device match.
The Android device gives the following information by vibration: Automatic connection
If a connection is lost because the liveShow remote server has been terminated or you are moving out of the WLAN area, the LiveShowClientRemote will try to reconnect automatically as soon as possible.

Note: You should definitely test the WLAN range before you use the remote control. You may want to install a WLAN repeater or place an AccessPoint device closer to the position of the Android devices.

In the liveShow software, all connected users are displayed with their names in a list:
RemoteServerConnectedUsers


Terminating the server


Clicking on the "End Server" button closes the remote server and disconnects all connected users:
RemoteServerStop An orange box indicates that the server is not started.






Android Remote control

You can remotely control: In principle, the surfaces of the Android program work like the surfaces of the liveSHOWsoftware.
The surfaces of the Android program and the corresponding surfaces of the liveSHOW software are shown below.

PlayControl

RemoteClient_PlayControl    PlayControl
In the upper section you can see the previous scene transition (directly below the main scene transition)

In the middle you see the current scenes (sound, light and media scenes).
Note: If the Android device is rotated to landscape, the current scenes and playback buttons are not displayed. This is due to the size of the display.

In the under section you can see the the next main scene transition.
At the bottom, you'll see the next scene transition, this can be a normal scene transition or a main scene transition.

By tapping one of the scene transitions, it is started.

The small red point (SceneBridge_Stop) before the next scene transition shows you whether the stopper is set or not (if the point is filled in red, the stopover of the scene transition is set and the play cursor will stop automatically before the scene transition).
If a jump is set for a scene transition, this is indicated by the jump icon (Icon_Jump).

There is a colored frame around the upper and lower scene transitions:
green frame More than 30 seconds to the next scene transition
orange frame Max. 30 seconds to the next scene transition
red frame Max. 10 seconds to the next scene transition


RemoteBoard



The RemoteBoard can be configured in the liveSHOWsoftware, see RemoteBoard.
Tapping on a field will execute its assigned action.


Tapping on a field will execute its assigned action.

Jingles

RemoteClient_Jingles  Jingles
As in the jingle window jingles can be played here.

All jingle groups are listed here - see JingleWindowr
Jingle groups have two additional buttons:
FadeIn: the jingle group is faded in.when the last jingle of the Jinglegroup is fadet in, all jingles of the group are paused.
FadeOut: the paused jingles of the group are started, they continue to play.
If FadeOut is clicked during threading/continuing playback, all jingles of the jingle group are directly faded out.
All sound jingles are listed here.
Sound jingles have one additional button, if the jingle is started.
The sound is fadet out.
All DMX/light jingle are listed here.
DMX Jingle have two additional buttons:
FadeIn: the light is faded in and then paused.
FadeOut: the light is faded out.
All media/trigger jingle are listed here.
Media jingles have one additional button, if the jingle is started.
The media is fadet out.

To start a jingle group or a jingle tap on the jingle group or the jingle. When a jingle is played, the background changes.
To stop the group or jingle earlier, tap the jingle group or jingle again or tap the FadeOut-button .
Jingle objects have a playing time, which can be set in the liveSHOW software by double-clicking on a jingle.




The background also changes for jingle groups:
when all assigned jingles are played:

if at least one of the assigned jingles is played:


:If you tap on a jingle group while one or all assigned jingles are playing, the jingles will be stopped.
If you tap on a jingle group when no assigned jingle is playing, all assigned jingles will be started.






Scenebook

RemoteClient_Scenebook Scenebook

Here, as in the scene book, scene transitions can be jumped directly by tapping on a scene transition.

The current scene transition is displayed with a colored frame:
white frame The play cursor has been paused.
green frame The Playcursor is running
orange frame The playcursor is running and it is max. 30 seconds to the next scene transition
red frame The playcursor is running and it is max. 10 seconds to the next scene transition

In addition, there is a frame around the complete scene book, which displays the above PlayCursor states.

The symbols before the scene transitions correspond to the symbols in the Scenebook.
Scenebridge_Stop The stopper before a scene transition is set
Scenebridge_Acrive The scene transition is active
Jump_Active A jump is defined and active

The following rule applies to the playback of scene transitions:
  1. If scene transitions are in a row (they are at the same position in the timeline), all scene transitions (sound, light, and / or media) of this series are started when one of them is started.
    Main transitions are coupled sound, light, and media cues, which are always in the same position in the Timeline, they are always started simultaneously.
  2. If scene transitions are in different rows (they have different starting positions in the timeline), the scene transitions are started separately from each other.

Reading out the instructions from the scene book

To have text read aloud, 'listen' must be selected in the user settings.
RemoteServerUsers
The Android device must have a TextToSpeech output. By default, there is either Google Voice or Pico TTS. I have made acceptable experiences with the PicoTTS. This can be set in Android under Settings - Language & Input - Text-to-Speech output.

The currently started scene and the next scene with the respective stage instructions are read aloud.

The stage instructions are created in the scene book.

For a text to be transmitted, it must be placed in quotation marks.

StageDirection1

Text that is not quoted is not transferred and is only visible in the scene book of the liveShow Software.

Note: If you enter a scene transition name starting with a #, the scene name is not read, the directories are read out!

Text can also be transferred to only one specific user or user group.
Enter the text as follows:
"user#stageinstruction"

The text must be enclosed in quotation marks and the user name is separated from the statement text by the rhombus #.
To send texts to different users, you can enter multiple blocks with quotation marks, for example:
"User1 # statement to user1" "user2 # statement to user2", etc.

If you only type "user # statement", the statement is passed to user1 and user2.
Rule: Instructions are transferred to all users whose names contain the complete text before the #.


The following rules apply:
"statement" The statement is transferred to all, since no user is named here.
"user1#statement" The statement is only transferred to user1.
"user2#statement" The statement is only transferred to user2.
"user#statement" The statement is passed to both users.

This allows user groups to be created implicitly by entering the group name in the user name.
Excample: WardrobeLadies und WardrobeGentlemen


A text can be entered either before or after a scene transition.
Text which is before a scene transition, is already read a long time before the scene change - at the announcement of the previous scene transition!
Text, which after a scene transition, is read directly after the scene change!

StageDirection2

In the Android device looks like this:
RemoteClientStageDirection1  RemoteClientStageDirection2

The current scene is displayed at the top, then the editing text, which was entered in the scene book after the current scene transition..
The next scene is displayed at the bottom, before this is the editing text, which was entered in the scene book before the next scene transition.

When you tap on the scene transitions in the remote control window, the corresponding source text is read again.

 Note: Scene changes are read only if they have a name and do not start with #. If the scene name is empty or begins with #, only the directories are read.
Thus it is possible to set an empty scene transition (crossfade) in the middle of a scene in order to transfer stage instructions at a certain time.

Master

RemoteClient_Master  ../images/MainMixer.png

Here you can remotely control the overall volume (sound) and the overall brightness (dimmer DMX), the overall transparency / brightness (media) and the volume (media, projection) as is possible in the main mixing console.
 





 DMX Lamps

To light up a stage the element 'DMX lamps' in the remote control helps. In principle, the DMX stage view is shown in tabular form here. All changes are applied to the DMX stage view.
The display has three horizontal areas:

a) The Lamplist


All lamps are displayed. If the list is very long, certain lamps can be easily found by entering parts of the lamp name in the search field.
The list is reduced to those lamps whose names contain the search term.



Note: If there is a DMX address conflict (no DMX universe has been assigned or DMX channels overlap) the lamp is displayed with a red frame.

Each lamp can be 'deactivated', set to 'mute' or 'solo'.
By touching the symbol the lamp is deactivated/activated.
If the lamp is deactivated, all DMX values are set to 0.
A lamp is muted by touching the symbol.
For all muted lamps, 0 is transmitted for the dimmer channel.
The lamps are off.
By touching the symbol a lamp is set to solo.
For all lamps which are not set to solo, 0 is transmitted for the dimmer channel.
All other lamps are off.
 
Next to the search field there are the three symbols again, here all lamps can be set by touching a symbol.

b) Select lamps and display their controls

A short tap on a lamp name selects the lamp and the lamp controls or the shared controls of all selected lamps are displayed to the right of the lamp list.
A long tap on a lamp displays its settings to the left of the lamp list - see later.



You can also select all lamps in a lamp group and reset the selection:
  When you select a lamp group, the current selection is reset and all lamps in the lamp group are selected.
  Tap the icon to reset the current selection.
If no lamps are selected, all lamps are selected.


The controller properties are displayed above the controller:
Controller name ('Dimmer', 'Red',...)
Selection box for discrete controller settings.
Controller value in percent.


There are also several symbols:

If several lamps are selected, one controller is used to change the properties of several lamps. It is not always useful to set all values of all selected lamps to the same value, sometimes you want to keep the ratio of the values.
How the property of the lamp is changed when the controller is moved can be determined with the following symbols:
All at the same value
If the controller is moved, the same value is set for all lamps.
Keep difference
If the controller is moved and its values are at different values for the selected lamps, the distance between the values is maintained. 
Percentage change
For example, if the controller is moved by 10%, the values of the selected lamps are also changed by 10% of their current value.
Assimilate
If the controller is moved to 100% or 0%, the values of the selected lamps are adjusted proportionally until they are also at 100% or 0%.
In other words, the values meet at 100% or 0%.

Set the selected lamps completely to 0 or to their default values:
All controllers of the selected lamps are set to their default values.
These values are defined in the lamp type.
All controllers of the selected lamps are set to 0.

For moving heads/scanners, in addition to pan and tilt, two additional controls -X-  and -Y-  are displayed for calibrated movement.
The -X- and -Y- controls only work when the moving head or scanner is calibrated and the controls are within the calibrated range. See: PanTilt calibration


 

c) The settings for a specific lamp

A long tap on a lamp displays its settings to the left of the lamp list.



Here you can change the lamp name, the universe and the start address for a lamp.
Saves the changes.
Discards the changes.







Notes


Information on the net
Windows
http://www.tecchannel.de/pc_mobile/windows/2035894/virtual_wifi_windows_7_als_wlan_access_point_einsetzen/

The Mac also offers the possibility to set up a virtual access point
Hilfreiche Seiten:
http://osxdaily.com/2012/01/05/enable-internet-sharing-mac-os-x/
http://www.dummies.com/how-to/content/how-to-make-your-mac-a-wifi-access-point.html