![]() Framasoft provides a search index (indexing videos from ). To enable global search, your need to specify the Search index URL of the remote search index. This way, you give the ability to your users to get results from instances that may not be federated with yours. You can enable global search, to use an external index ( ). The listening port can be changed in the PeerTube configuration file. So we recommend you to make some tests to see how many parallel lives your instance can handle before increasing limits/enabling transcoding resolutionsīear in mind that enabling live streaming will make your server listen on port 1935/TCP (and 1936/TCP if RTMPS is enabled), which is required for incoming RTMP by your streamers. It means that if your instance is streaming 10 lives, PeerTube will run 10 FFmpeg processes (high CPU/RAM usage). ![]() This setting is different than VOD transcoding, because PeerTube will transcode the live in real time. Limit parallel lives per account/on your instance.Enabling VOD transcoding is required to enable this setting Allow your users to automatically save a replay of their live.You can enable live streaming on your instance in Administration > Configuration > Live Streaming. avi and/or allow audio file uploads (PeerTube will create a video from them). If you enable transcoding, you can also allow additional files formats like. Keep in mind that a transcoding job takes a lot of CPU, requires time and create an additional video file stored on your disk storage. It allows to users that does not have a high speed Internet connection to watch the video in low quality. PeerTube can transcode the uploaded video in multiple resolutions. Moreover, the PeerTube redundancy system can be another way to help the origin instance to seed the video. This is a disadvantage that we accept, because we realized that BitTorrent client that helped to seed PeerTube files were not really used. The main drawback is that this HLS with P2P player is not compatible with WebTorrent, so you won't be able to help the swarm using your BitTorrent client. We use a widely used HLS library ( hls.js) and a clean P2P WebRTC loader ( p2p-media-loader) resulting in less bugs and an easier support. ![]() ![]() Start-up of videos is faster (especially long videos).Video resolution change is smoother (because we don't have to change the source of the tag).We don't have to store video chunks in the web browser IndexedDB (so the video is not stored on the watcher disk, which was a little bit hacky/dirty).There is a buffer system so your web browser won't download the entire video (better bandwidth management).We recommend you to enable HLS (and disable WebTorrent if you don't want to store 2 different versions of the same video resolution) because video playback is really better: So if you enable WebTorrent and HLS, the storage will be multiplied by 2. Unfortunately, we can't use the same video file for WebTorrent and HLS: we need to transcode 2 different versions of the file (a fragmented mp4 for HLS, and a raw mp4 for WebTorrent). Due to several limitations of the library leading to many bugs, we had to add HLS (with P2P) support. We have two different ways to stream the video in the PeerTube player: using WebTorrent or HLS with P2P.Īt the beginning of PeerTube, we only supported WebTorrent streaming. WebTorrent transcoding or HLS transcoding VOD transcoding Įnabling transcoding ensures that your users will have a video playback that works. Admins can configure their instance directly in the web interface using in Administration -> Configuration.Īll the fields from this web interface will override your production.yaml configuration keys.
0 Comments
Leave a Reply. |