- How to contact tech support?
- Can I run other server software along with Flussonic Media Server?
- Which operating systems, 32-bit or 64-bit, are supported by Flussonic?
- How to set up adaptive streaming?
- What kind of hardware best suits my needs?
- What types of disks are required for an archive?
- How to set up Stalker and Flussonic Media Server?
- Troubleshooting missing sound from camera
- Dividing load between servers
- Why has my trial ended prematurely?
When contacting technical support via email or forum PM, give a full description of the problem (time, stream name, how to replicate the error. It is advised to provided screenshots), upload and specify UUID logs (they can be uploaded trough the **Support* tab of the Flussonic’s web interface. UUID will be displayed after the uploading is complete.)*.
Technically, it is possible. You can run any other service on the same server. However, do not be surprised if some of the software conflict with each other, or if the server becomes unstable and there are issues with video streaming.
We recommend you run only Flussonic on the server. Read our OS tuning recommendations and do not forget to turn off SWAP.
If you are an experienced system administrator, you can set up various combinations of services. However, when you contact tech support, we might ask you to remove services that look suspicious to us (primarily, apache2/nginx and other video servers).
Flussonic provides an easy way to set up adaptive streaming. To do this, you need to turn on the transcoder and specify several bitrates for video. Usually 2-3 "profiles" would be enough: low, medium and high.
For example, if you have an HD TV channel with a resolution of 720p and bitrate of 2 Mbps, specify the following line in transcoder settings:
vb=copy vb=1200k preset=fast vb=700k size=854x480 preset=fast ab=96k
As a result, you will have a stream with three bitrates: original stream, 1200 kbps stream with default resolution; 700 kbps stream with 854x480 resolution and 96 Kbps audio track.
Flussonic Media Server will automatically generate streams with adaptive bitrate for the protocols HLS, DASH, and HDS. Instructions on playing them are given in the corresponding article.
More on transcoding
It is not easy to pick the hardware that would best suit your needs and budget. Server load depends heavily on transcoding settings, incoming traffic, archive input and the number of users. Processors differ in price and performance.
To begin with, please see the system requirements to Flussonic Media Server.
To calculate storage space multiply total bitrate of recorded streams by storage period.
For example, you have 30 cameras with the average bitrate of 2.8 Mbps. You need to store your data for a month (30 days). The total bitrate would be 84 Mbps (as can be seen in Flussonic’s web interface), which estimates to 10.5 MBps (8 Mbit = 1 MB). For ease of calculation, let’s find out how much space you will need in order to store 1 hour of recording: 10.5MB * 3600 seconds = 37,800MB (~ 37 GB) The rest is simple, since we know how many hours are there in a natural day and how many days there are in a month and in a year:
- 1 hour - 37GB.
- 1 day (24h) - 888GB.
- 7 days - 6,216GB.
- 30 days - 26,640GB (27TB).
- 6 months - 159,840GB (160TB).
- 1 year - 319,680GB (310TB)
Bitrate can fluctuate and sometimes data is not saved (for example, if cameras are not online), but it is still recommended to purchase a data storage with 5-10% more space than you would need for the maximum amount of data you plan to store.
Flussonic Media Server can cache «hot content» to SSD, so the performance of the drive is not an issue.
If you expect the archive to be accessed A LOT, consult with your hardware dealer and us.
In Flussonic settings, specify the address of the Stalker server. During channel creation in Stalker, select «Flussonic» in the tabs «Temporary links» and «TV archive».
More on Stalker setup in this article
Most IP cameras can stream sound only in PCMA/PCMU codecs (also known as G.711a and G.711u).
These codecs can be transferred only using RTMP and HDS protocols. To receive sound via other protocols, turn on IP camera sound transcoding.
More in this article
There are numerous ways to divide the load between servers in a cluster. Each of them has their pros and cons.
- DNS round robin. Clients will reach the servers by rotation, regardless of server load.
- Geo DNS. Useful if you have lots of clients from different countries and need users to be directed to regional servers.
- Balancing via Middleware. Your website/portal can generate links to different servers, with/without regards to server load and GeoIP.
- Client chooses. The client receives a list of all servers and selects the most suitable one based on certain parameters (distance, load, accessibility).
- A special balancing service/script/solution. A third party tool, essentially the same as Middleware. Transparent for clients and Middleware.
Using HTTP API Flussonic Media Server gives out all information needed to perform balancing on your portal.
We will soon have an article dedicated to load balancing.