Changes

==Launching broadcast==

===Transition from versions 2.0.х to version 2.1 and higher===

From September, 10, 2013, upgraded version of the engine (2.1.6) for Ubuntu, Debian and CentOS is available.

Before using a new version for production, we recommend to test it on one or several broadcasts, if possible.

<span style="color: #900;">ATTENTION!</span> In the nearest future support for older versions will be stopped.

** instead of <tt>acestreamengine-client-gtk</tt> you should launch <tt>acestreamengine --client-gtk</tt>

* log system is changed. In old versions the engine output all debug information into STDERR and redirecting the output was required to write logs into a file. In a new version it is possible to define in options, where to write logs - into STDOUT, into STDERR, into a file or syslog. Rotation of logs by their size is supported for files. You can read description of all options in [[#acestreamengine command|acestreamengine command]]

===acestreamengine command===

*<tt>--cache-dir CACHE_DIR</tt> - directory for creating service files (broadcast cache and others)

*<tt>--publish-dir PUBLISH_DIR</tt> - directory, in which acelive-file will be created

*<tt>--duration DURATION</tt> - size of broadcast cache in format HH:MM:SS (by default, one hour: 01:00:00)

*<tt>--host HOST</tt> - set address of local tracker manually

*<tt>--pid-file-dir PATH</tt> - the directory where engine's pid file is created. Default is /tmp.

*<tt>--provider-key</tt> - provider key (for an affiliate program)

*<tt>--permanent</tt> - mark the broadcast as 24/7 (it's available all the time)

*<tt>--date-start YYYY-MM-DD HH:mm:ss</tt> - set the data and time of the broadcast start (for the broadcasts which runs during a limited time)

We launch the source on server 192.168.1.1:

--name "test" \

--title "Test broadcast" \

--publish-dir "/home/www/streams" \

--cache-dir "/tmp/streams" \

<tt>--add-authorized-peers</tt> option adds the list of authorized nodes to acelive-file (in this case, it's the source: 192.168.1.1).

In this example we assume that XBT Tracker is installed and launched on server 192.168.1.1.

Now broadcast's launch will look like:

--name "test" \

--title "Test broadcast" \

--add-authorized-peers \

--skip-internal-tracker \

<tt>--skip-internal-tracker</tt> option disconnects embedded tracker, <tt>--tracker</tt> option connects external tracker.

using <tt>--support-node</tt> option:

--name "test" \

--title "Test broadcast" \

--tracker "udp://192.168.1.1:2710/announce" \

--support-node "192.168.1.2:8621" \

Launch support nodes on servers 192.168.1.2 and 192.168.1.3 (commands are the same):

--url "<nowiki>http://192.168.1.1/streams/test.acelive</nowiki>" \

--state-dir "/tmp" \

--source-node "192.168.1.1:7764" \

Option <tt>--source-node</tt> sets source address.

On server 192.168.1.2 it will look like:

--url "<nowiki>http://192.168.1.1/streams/test.acelive</nowiki>" \

--state-dir "/tmp" \

--allow-source-download \

--support-node "192.168.1.3:8621" \

On server 192.168.1.3:

--url "<nowiki>http://192.168.1.1/streams/test.acelive</nowiki>" \

--state-dir "/tmp" \

--allow-source-download \

--support-node "192.168.1.2:8621" \

====Private source with two support nodes====

To make the source private, option <tt>--private-source</tt> must be specified:

--name "test" \

--title "Test broadcast" \

--support-node "192.168.1.2:8621" \

--support-node "192.168.1.3:8621" \

Notice that in this configuration tracker's address is changed to <tt>udp://192.168.1.2:2710/announce</tt>. It was made to support old versions of clients, which do not process a list of authorized peers (more details here [[#Authorized peers|Authorized peers]]).

Launch support nodes on servers 192.168.1.2 and 192.168.1.3 as usual:

--url "<nowiki>http://192.168.1.1/streams/test.acelive</nowiki>" \

--state-dir "/tmp" \

--source-node "192.168.1.1:7764" \