Hello, this time I want to present an HLS video transmission system.
Our system includes the following notable features:
Custom Vast Advertising System: You can integrate third-party ads through Vast technology or use our own advertising system directly in the script.
Encrypted HLS Encoding: HLS chunks are encrypted, ensuring that even if someone manages to obtain a chunk, they will not be able to read it due to the strong security measures in place.
Player with Reinforced Security:
1.Our player is designed with several layers of security to protect your content:
Only allow authorized domains.
2.Precautions have been taken to avoid viewing the source code or using the browser inspector to extract the actual link.
3.Browser extensions that might try to obtain the actual HLS link to track the location of videos are blocked.
Multi-Server Compatibility: If you run out of space on one server, you can add more servers, either VPS or dedicated servers.
Additionally, our system offers the flexibility to upload videos locally or remotely.
Note: When referring to servers, we are referring to virtual private servers (VPS) or dedicated servers.
Note: Please overlook the simple design; My strength lies in programming, not design.
If you would like to see a demo of our player, please feel free to contact me.
Support for remote upload by url
https://example.com/video/FileName.mp4
Google Drive: https://drive.google.com/file/d/VIDEO ID/view
https://mega.nz/file/*
https://my.mail.ru/video/embed/*
https://streamwish.to/e/*
https://www.yourupload.com/embed/*
For MP4 videos With the H264 Codec and without multi-quality you can convert the video to HLS without consuming much CPU resources.
CPU Requirements for Encoding to HLS with H.264 (MP4)
When using the copy function in ffmpeg to convert an MP4 file with H.264 codec to HLS, there is no re-encoding of the video or audio. This process is mostly I/O-bound (reliant on disk reads and writes) and does not require much CPU or RAM.
Suggested minimum specs:
CPU: 4 cores (any modern generation, such as an Intel i3 or Ryzen 3)
RAM: 4 GB
Disk: SSD recommended for faster processing (enough space for the source file and the generated HLS segments).
GPU: Not required.
This is sufficient because using copy keeps the original codec data and does not involve intensive CPU usage for compression.
=================================================================
CPU Requirements for Multi-Quality Encoding and Different Codec (without H.264)
Encoding to multiple qualities and using a different codec (e.g. VP9, AV1) is CPU and RAM intensive. This process is compute-bound, and can significantly benefit from a modern GPU that supports hardware encoding if available.
Suggested specs for high load:
CPU: High-end processor with multiple cores and threads.
Example: Ryzen 9 5950X (16 cores, 32 threads) or Intel i9-12900K.
Alternatively, use servers with Xeon processors (e.g. Intel Xeon E5-2699 v4) for concurrent tasks.
RAM: 16 GB or more (will depend on the number of simultaneous resolutions).
GPU (optional): Recommended if hardware encoding is supported.
NVIDIA: RTX 3000 or higher (NVENC).
AMD: Modern GPUs with HEVC/VCE hardware support.
Disk: At least a 1TB SSD for working with large volumes of temporary data.
Example of multi-quality configurations:
Input: 1080p60.
Outputs: 1080p30, 720p30, 480p30, 360p30.
This type of encoding consumes massive resources because each output must be independently re-encoded with the desired codec. Additionally, codecs like AV1 are especially demanding and may require specialized hardware or even more powerful configurations.
You can optionally pay $50 to purchase the php embed hls, with this you can have the player separate from the streamingembed HLS, but the streamingEmbed HLS of $350 is required as this is just an add-on.
Price: 150$
Telegram: masterchip95
After purchase you will receive an email for direct contact to carry out the installation.
