Changes

Jump to: navigation, search

Streaming/en

1,090 bytes removed, 12:36, 11 September 2019
→‎Recent scripts and configuration examples
Repository should be selected according to operating system.
''Debian 6+:''
<tt><nowiki>deb http://repo.acestream.org/debian/ squeeze main</nowiki></tt>
or
Note: packages in sid repository are assembled with dependencies that correspond to official sid-repositories of Debian.
If you don't know, which repository to choose, use squeeze.
 
''Debian 7:''
<tt><nowiki>deb http://repo.acestream.org/debian/ wheezy main</nowiki></tt>
''Ubuntu 11.10:''
''Ubuntu 12.10:''
<tt><nowiki>deb http://repo.acestream.org/ubuntu/ quantal main</nowiki></tt>
 
''Ubuntu 13.04:''
<tt><nowiki>deb http://repo.acestream.org/ubuntu/ raring main</nowiki></tt>
'''Step 2'''
For Debian only the engine (acestream-engine) is available.
<!--
=== Installing ACE Stream package on Ubuntu from deb-package ===
You can install ACE Stream on Ubuntu without using repository. To do this you need to download the installation package by one of links below and install it using a package manager (for example, by double click on downloaded package).
This intallation package is an analog of <tt>acestream-full</tt> package from repository. It includes the engine, player and plug-in for browsers.
-->
 
=== Installing Ace Stream on the CentOS ===
Requirements:
* installed python 2.6
* installed module python-argparse
 
To install Ace Stream on CentOS you need:
* download an archive that corresponds to your CentOS version (links are below)
* extract files from archive and copy contents to /usr dir
 
The following packages are available at this moment:
*'''CentOS 5 64bit''': http://dl.acestream.org/centos/5/acestream-engine-2.1.6_4-centos5-x86_64.tar.gz
*'''CentOS 6 64bit''': http://dl.acestream.org/centos/6/acestream-engine-2.1.6_4-centos6-x86_64.tar.gz
 
This package was tested on CentOS 5.8 and 6.3.
==Launching broadcast==
*'''Client''' - ACE Stream software, which is used to play 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 CentOSis available.
Новая версия доступна для тестирования по следующим ссылкам:Before using a new version for production, we recommend to test it on one or several broadcasts, if possible.
'''Ubuntu''':* http://dl.acestream.org/ubuntu/acestream-engine_2.1.6-1oneiric1_amd64.deb* http://dl.acestream.org/ubuntu/acestream-engine_2.1.6-1oneiric1_i386.deb* http://dl.acestream.org/ubuntu/acestream-engine_2.1.6-1precise1_amd64.deb* If you face any problems, please, write to the forum (http://dlforum.acestreamtorrentstream.org/ubuntu/) or email support@acestream-engine_2.1.6-1precise1_i386.deb* http://dl.acestream.org/ubuntu/acestream-engine_2.1.6-1quantal1_amd64.deb* http://dl.acestream.org/ubuntu/acestream-engine_2.1.6-1quantal1_i386.deb* http://dl.acestream.org/ubuntu/acestream-engine_2.1.6-1raring1_amd64.deb* http://dl.acestream.org/ubuntu/acestream-engine_2.1.6-1raring1_i386net.deb
'''Debian''':* http://dl.acestream.org/debian/acestream-engine_2.1.6-1squeeze1_amd64.deb* http://dl.acestream.org/debian/acestream-engine_2.1.6-1wheezy1_amd64.deb* http://dl.acestream.org/debian/acestream-engine_2.1.6-1wheezy1_i386.deb '''CentOS 6''':* http://dl.acestream.org/centos/6/acestream-engine-2.1.6_1-centos6-x86_64.tar.gz В репозитории repo.acestream.net пока доступны старые версии (2.0.8). Перед полномасштабным использованием новой версии мы рекомендуем по возможности протестировать ее на одной или нескольких трансляциях. При возникновении каких-либо проблем просьба писать на форум http://forum.torrentstream.org либо на почту support@acestream.net. Старые версии временно доступны в репозитории и по прямым ссылкамOld versions are temporarily available in repository and by direct links:
'''Ubuntu''':
* http://dl.acestream.org/centos/6/acestream-engine-2.0.8_7-centos6-x86_64.tar.gz
<span style="color: #900;">ВНИМАНИЕATTENTION!</span> В ближайшее время поддержка старых версий будет прекращенаIn the nearest future support for older versions will be stopped.
<span style="color: #009;">ВАЖНОIMPORTANT!</span> Все трансляции, созданные с помощью новой версии All broadcasts created via new version of Ace Stream (2.1 и вышеand higher) не поддерживаются клиентским ПО старых версий are not suppported by client software of old versions (2.0.х и нижеand lower). При попытке просмотреть новую трансляцию с помощью старого движка будет выдаваться ошибка If you attempt to watch a new broadcast using the old engine, an error "Cannot load transport file"will appear.
====Изменения в параметрах запускаChanges in launch parameters====В новой версии изменились некоторые параметры запуска источников и узлов поддержки из командной строкиSome parameters of the launch of sources and support nodes from the command line have been changed, поэтому запуск со старой командной строкой работать не будетtherefore the launch with the old command line will not work.
Основные измененияMain changes:* используется один исполняемый файл one executable file is used <tt>acestreamengine</tt>; различные режимы запуска different launch modes (источникa source, узел поддержкиsupport node) задаются опциямиare set by options:** вместо instead of <tt>acestreamengine-stream</tt> следует запускать you should launch <tt>acestreamengine --stream-source</tt>** вместо instead of <tt>acestreamengine-node</tt> следует запускать you should launch <tt>acestreamengine --stream-node</tt>** вместо instead of <tt>acestreamengine-client-console</tt> следует запускать you should launch <tt>acestreamengine --client-console</tt>** вместо 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 [[#Команда acestreamenginecommand|Команда acestreamenginecommand]]
===Команда acestreamenginecommand===Начиная с версии Starting from version 2.1 Ace Stream Engine для for Linux представляет собой один исполняемый файл represents a single executable file <tt>acestreamengine</tt>, который работает в различных режимах в зависимости от заданных параметровwhich works in different modes, depending on specified parameters.
Режим работы задается одним из следующих параметровWork mode is set by one of the following parameters:* <tt>--client-console</tt> - запустить движок в режиме клиента из консоли launch engine in a client mode from console (без графического интерфейсаwithout a graphic interface)* <tt>--client-wx</tt> - запустить движок в режиме клиента с графическим интерфейсом launch engine in a client mode with a graphic interface WX* <tt>--client-gtk</tt> - запустить движок в режиме клиента с графическим интерфейсом launch engine in a client mode with a graphic interface GTK* <tt>--stream-source</tt> - запустить источник трансляцииlaunch a source of broadcast* <tt>--stream-node</tt> - запустить узел поддержкиlaunch a support node* <tt>--create-transport</tt> - создать транспортный файл из существующего контента create a transport file from existing content (VOD)* <tt>--create-transport-multi</tt> - создать мультипотоковый транспортный файлcreate a multi-stream transport file* <tt>--version</tt> - показать версию движкаshow engine version
Каждый режим работы имеет свои обязательные и необязательные параметрыEach work mode has their own required and not required parameters, описанные в соответствующих разделахdescribed in appropriate sections.
Также всех режимов работы есть общие параметры, которые управляют выводом отладочной информацииAlso all work modes have common parameters that manage the output of debug information.* <tt>--log-stdout</tt> - выводить информацию в deduce information in STDOUT* <tt>--log-stderr</tt> - выводить информацию в deduce information in STDERR* <tt>--log-file PATH</tt> - выводить информацию в указанный файлdeduce information in a specified file* <tt>--log-max-size SIZE</tt> - максимальный размер файла maximum file size (в байтахbytes)* <tt>--log-backup-count COUNT</tt> - сколько резервных логов хранить how many backup logs have to be stored (резервный лог файл создается при достижении лимитаbackup log file is created when a limit, указанного паметром specified by a parameter --log-max-size, is reached)* <tt>--log-file-buffer SIZE</tt> - включить буферизацию вывода в файл enable buffering of output into the file (с использованием буфера указанного размера в байтахusing buffer of specified size in bytes)* <tt>--log-syslog HOST</tt> - выводить информацию в deduce information in syslog-сервер по указанному адресуserver at the specified address* <tt>--log-syslog-port PORT</tt> - порт syslog-сервераserver port* <tt>--log-syslog-facility FACILITY</tt> - используемый used facility* <tt>--log-syslog-buffer SIZE</tt> - включить буферизацию вывода в enable buffering of output into syslog (с использованием буфера указанного размера в байтахusing buffer of specified size in bytes)
===Common work scheme ===
The source accepts HTTP-stream to input (at this moment HTTP-streams with MPEG-TS encapsulation are supported) with original broadcast and creates a file with acelive extension after the launch. This file is a unique identifier of broadcast and it is used for connection and playback by clients.
===Syntax of acestreamengine--stream -source command===<tt>acestreamengine--stream-source</tt> command launches broadcast source.
''required parameters''
*<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>--piecesize PIECESIZE</tt> - piece size in bytes , power of two (if it's not specified, it's set automatically depending on bitrate)
*<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>--provider-key PROVIDER_KEY</tt> - provider's key (only for commercial broadcasts)
*<tt>--maxclients MAXCLIENTS</tt> - maximum number of peers, on which data from the source are given simultaneously
*<tt>--showlog-piecesdebug DEBUG</tt> - show set the debug level (default is 0 - minimum log level)*<tt>--source-read-timeout SECONDS</tt> - timeout for reading data from the original source (in log numbers seconds). Default is 30.*<tt>--source-reconnect-interval SECONDS</tt> - interval is seconds, after which the engine will try to reconnect to the original source in case of pieces connection lost. Default is 5.*<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>--sid</tt> - content identificator for statistics(for an affiliate program)*<tt>--permanent</tt> - mark the broadcast as they are created24/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)*<tt>--date-end YYYY-MM-DD HH:mm:ss</tt> - set the data and time of the broadcast end(for the broadcasts which runs during a limited time)*<tt>--premium</tt> - request a "premium" status for the broadcast*<tt>--upload-limit</tt> - limit upload speed (bytes/s, default is 0 - don't limit)*<tt>--max-connections</tt> - limit total number of connections (default is 1000)*<tt>--showmax-peers</tt> - periodically show in log list limit number of connected connections to other peers(default is 50)*<tt>--service-remote-access</tt> - enable remote statistics*<tt>--service-access-token</tt> - password for remote statistics access*<tt>--stats-report-interval</tt> - interval in seconds between internal statistics update (default is 60)*<tt>--debug DEBUGstats-report-peers</tt> - set debug levelupdate information about connected peers in the internal statistics (increases CPU load)
''additional''
*<tt>-h, --help</tt> - show commands' description
=== Syntax of acestreamengine--stream-node command===<tt>acestreamengine--stream-node</tt> command launches support node.
''required parameters''
*<tt>--allow-support-download</tt> - allow receiving data from other support nodes
*<tt>--allow-peers-download</tt> - allow receiving data from ordinary peers
*<tt>--max-incoming-connects MAX_INCOMING_CONNECTSconnections MAX_CONNECTIONS</tt> - maximum limit number of incoming total connections (from other peers) (by default: is 1000)*<tt>--max-outgoing-connects MAX_OUTGOING_CONNECTSpeers MAX_PEERS</tt> - maximum limit number of outgoing connections (to other peers) (by default: is 50)
*<tt>--max-upload-slots MAX_UPLOAD_SLOTS</tt> - maximum number of peers, on which data from support node are given simultaneously (by default: 7)
*<tt>--max-download-speed MAX_DOWNLOAD_SPEED</tt> - maximum download speed (byte/s). By default: 0 (no restrictions).
*<tt>--max-upload-speed MAX_UPLOAD_SPEED</tt> - maximum upload speed (byte/s). By default: 0 (no restrictions).
*<tt>--showlog-piecesdebug DEBUG</tt> -show in set the debug level (default is 0 - minimum log numbers of pieces as they are createdlevel)*<tt>--service-remote-access</tt> - enable remote statistics*<tt>--showservice-peersaccess-token</tt> - periodically show in log list of connected peers password for remote statistics access*<tt>--stats-report-interval STATS_REPORT_INTERVAL</tt> - set interval in seconds to show in log information about download/upload speep. By between internal statistics update (default: 0 (do not showis 60).*<tt>--debug DEBUGstats-report-peers</tt> - set debug levelupdate information about connected peers in the internal statistics (increases CPU load)
''additional''
We launch the source on server 192.168.1.1:
<tt>acestreamengine--stream -source \
--name "test" \
--title "Test broadcast" \
--publish-dir "/home/www/streams" \
--cache-dir "/tmp/streams" \
--add-authorized-peers \ > /tmp/test-source.log 2>&1</tt>
The last line is used to write logs into file /tmp/test-source.log. By default <tt>acestreamengine--stream-source</tt> shows outputs all debug information in console in STDERRthe STDOUT.
<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:
<tt>acestreamengine--stream -source \
--name "test" \
--title "Test broadcast" \
--add-authorized-peers \
--skip-internal-tracker \
--tracker "udp://192.168.1.1:2710/announce" \ > /tmp/test-source.log 2>&1</tt>
<tt>--skip-internal-tracker</tt> option disconnects embedded tracker, <tt>--tracker</tt> option connects external tracker.
using <tt>--support-node</tt> option:
<tt>acestreamengine --supportstream-node</tt>: <tt>acestreamengine-stream source \
--name "test" \
--title "Test broadcast" \
--tracker "udp://192.168.1.1:2710/announce" \
--support-node "192.168.1.2:8621" \
--support-node "192.168.1.3:8621" \ > /tmp/test-source.log 2>&1</tt>
Launch support nodes on servers 192.168.1.2 and 192.168.1.3 (commands are the same):
<tt>acestreamengine--stream-node \
--url "<nowiki>http://192.168.1.1/streams/test.acelive</nowiki>" \
--state-dir "/tmp" \
--source-node "192.168.1.1:7764" \
--allow-source-download \ > /tmp/test-node.log 2>&1</tt>
Option <tt>--source-node</tt> sets source address.
On server 192.168.1.2 it will look like:
<tt>acestreamengine--stream-node \
--url "<nowiki>http://192.168.1.1/streams/test.acelive</nowiki>" \
--state-dir "/tmp" \
--allow-source-download \
--support-node "192.168.1.3:8621" \
--allow-support-download \ > /tmp/test-node.log 2>&1</tt>
On server 192.168.1.3:
<tt>acestreamengine--stream-node \
--url "<nowiki>http://192.168.1.1/streams/test.acelive</nowiki>" \
--state-dir "/tmp" \
--allow-source-download \
--support-node "192.168.1.2:8621" \
--allow-support-download \ > /tmp/test-node.log 2>&1</tt>
====Private source with two support nodes====
To make the source private, option <tt>--private-source</tt> must be specified:
<tt>acestreamengine--stream -source \
--name "test" \
--title "Test broadcast" \
--support-node "192.168.1.2:8621" \
--support-node "192.168.1.3:8621" \
--private-source \ > /tmp/test-source.log 2>&1</tt>
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:
<tt>acestreamengine--stream-node \
--url "<nowiki>http://192.168.1.1/streams/test.acelive</nowiki>" \
--state-dir "/tmp" \
--source-node "192.168.1.1:7764" \
--allow-source-download \</tt> ====Recent scripts and configuration examples==== > Python-based launch scripts with configuration examples and some brief explanation available via https:/tmp/test-nodegithub.log 2>&1<com/acestream/tt>streaming-utils
Retrieved from "https://wiki.acestream.media/Special:MobileDiff/214...696"

Navigation menu