On headless machines the Player is accessed from a web dasboard accecible from another machine on the same network from an IP address that is issued with DHCP. To determine the local IP of Player from terminal issue “ip addr show” Your IP will appear like 192.168.1.100. 127.0.0.1 is a local loop back IP. You might also get into your router and look at the DHCP Client list and see the players IP that way. Recomended that Players be setup with a static IP address as DHCP can often change.
From a web browser type
a login window will prompt for user and password. If there is a timeout and/or network unreachable message try these steps to resolve.
From Terminal Ping “localhost” replies indicate internal networking working
From Terminal Ping “IP-of_Router/Gateway” replies indicate networking working to router.
From Terminal Ping “IP-of-Other-Device-on-Network” replies indicate Player and router are able to communicate to other Devices.
From Terminal Ping “google.com” replies indicate network is able to communicate through router to the real world internet.
If you are unable to access the player dashboard, do not have local access or running in a virtual service, you’ll want to verify the Player appears as a process.
ps -ef | grep python
Lists all Python process including the obplayer. If this is not showing then obplayer is not running.
To check all running processes, including obplayer and Icecast
In this example both obplayer and Icecast are highlighted
Ensure the player device is able to access the internet Terminal “ping google.com” and can reach the management server as specified in sync settings under the Sync tab. The format can be “localhost/remote.php”, “127.0.0.1/remote.php” or http(s)://IP-of-Server/remote.php” Do not forget to include the trailing /remote.php.
Check the sync url exisits by pasting into browser and you should see the
Confirm/Re-enter passwords and Device to match player in Player Manager in Server
Restart DB and Reset from Admin Tab. Forces a reset of media sync.
Use the test signal to confirm your audio setup is working correctly.
To test the on-board sound card:
To test an external USB sound card:
If no audio output is produced, check the Status page for errors in the log and observe VU meter for activity:
gstreamererrors indicating problems with audio mode settings.
Disable the test signal once audio setup is working. Enable Audio In Source, if necessary.
Pulse is the default and recommended audio to use with OBPlayer. When audio mode settings are changed, Reboot. Once rebooted, audio slider controls will be present in the dashboard under PULSE to set input and output levels.
On the Outputs Tab, set audio output mode to PULSE. Disable the Test Signal From Sources__Tab enable the __Audio In Source setting audio mode to PULSE.
If using the GPIO switching Relay, connect a serial cable from the Player to the Switching Relay. On the Emergency Alerts tab, under Advanced Settings, enable the RS-232 DTR Alert signal. The RS-232 Device Filename should be set to the serial port (/dev/ttyS0 for Port 1, /dev/ttyS1 for Port 2).
There are no input level GUI controls “out-of-the-box” with Jack audio, so if further control over the input level is desired, the configuration must be updated to include jack-mixer. Using jack-mixer programs requires a modified jack.plumbing configuration with connections defined between the openbroadcaster ports, the jack-mixer control and system output.
/etc/jack.plumbing) contains the correct connection definitions.
~/.pulse/client.confis set to enable Pulse to autospawn. Create a new configuration file called .jack.plumbing in the home directory (make sure it has the preceeding dot). This will override the system defaults.
obsuser@obsource:~$ `nano ~/.jack.plumbing` #connect Audio Inputs to OpenBroadcaster Inputs (connect "system:capture_1" "openbroadcasterin:in_audiosrc_1") (connect "system:capture_2" "openbroadcasterin:in_audiosrc_2") #Connect Openbroadcaster Outputs to Audio Outputs (disconnect "openbroadcasterout:out_audiosink_1" "system:playback_1") (disconnect "openbroadcasterout:out_audiosink_2" "system:playback_2") (connect "openbroadcasterout:out_audiosink_1" "jack_mixer:OB_In L") (connect "openbroadcasterout:out_audiosink_2" "jack_mixer:OB_In R") (connect "jack_mixer:OB_In Out L" "system:playback_1") (connect "jack_mixer:OB_In Out R" "system:playback_2")
If Jack is already running, it will load the new configuration. Open the jack-mixer this will open a mixer control, with an input channel on the left and Main output channel is on the right. The sliding control for the input channel can be used to set the level for the line-in (input) signal.
If Jack is not running ensure it is configured in the Dashboard, and reboot the Player, and open the jack-mixer control from desktop.
NB: When using jack mixer, the jack-mixer control must be opened manually from the Panel Icon to activate the control. Once the control is closed, the output will stop playing. The control must be visible and indicating signal bars for output signal to be audible. The mixer control must be reopened after a reboot, or no sound will be produced.
To open the jack mixer control in headless mode), use the command:
jack_mixer -c ~/.openbroadcaster/init_mix_vol --no-lash.
To restore the original configuration of jack.plumbing, without the jack-mixer control, edit ~/.jack.plumbing file to define the following connections:
#obsuser@obsource:~$ nano ~/.jack.plumbing #connect Audio Inputs to OpenBroadcaster Inputs (connect "system:capture_1" "openbroadcasterin:in_audiosrc_1") (connect "system:capture_2" "openbroadcasterin:in_audiosrc_2") #Connect Openbroadcaster Outputs to Audio Outputs (connect "openbroadcasterout:out_audiosink_1" "system:playback_1") (connect "openbroadcasterout:out_audiosink_2" "system:playback_2")