Skip to content
This repository was archived by the owner on May 15, 2024. It is now read-only.

bot

Directory actions

More options

Directory actions

More options

Latest commit

 

History

History

bot

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
scripts
scripts
 
 
utils
utils
 
 
Dockerfile
Dockerfile
 
 
Procfile
Procfile
 
 
README.md
README.md
 
 
config.py
config.py
 
 
main.py
main.py
 
 
railway.toml
railway.toml
 
 
requirements.txt
requirements.txt
 
 

README.md

Better TG Streamer Bot

Better TG Streamer Bot is a Telegram bot that facilitates video conversion to the m3u8 format.

Demo Bot: BetterTGStreamerBot

Features

  • Converts video files to m3u8 format quickly while preserving original quality and supporting multiple audio tracks.
  • Offers multi-quality, multi-audio, and subtitle encoding using H.264/AAC.
  • Allows uploads from remote URLs for encoding.
  • Displays the status of current and queued tasks.

Commands

  • /start - Show bot information.
  • /help - Provide usage instructions.
  • /convert - Convert a video to m3u8 format, maintaining original quality with multiple audio tracks.
  • /encode - Encode a video to m3u8 format with multiple quality options, audio tracks, and subtitles.
  • /remote - Upload a file from a remote URL for encoding.
  • /queue - Check the status of current and queued tasks.

Read More

Deployment Guide

Prerequisites

  • Docker installed on your system.

Steps

  1. Clone the repository and navigate to the BetterTGStreamer/bot directory.
  2. Update the required configuration variables in config.py.
  3. Build the application: 
    docker build -t tgstreamer .
  4. Run the application: 
    docker run --name tgstreamer -d tgstreamer
    Monitor your bot’s activity via: 
    docker logs -f tgstreamer

Deployment Tips

Configuration Variables

Required Variables

  • API_ID: Telegram API ID for interaction with the Telegram API.
  • API_HASH: Telegram API hash corresponding to the API_ID for authentication.
  • VIDEO_STORAGE: Telegram Channel ID for video storage.
  • LOGGER_CHANNEL: Telegram Channel ID for logging.
  • STORAGE_CHANNEL_1: Telegram Channel ID for storing m3u8 files.
  • OWNER_ID: Telegram User ID of the bot owner.
  • WEBSITE_DOMAIN: Domain name for streaming API hosting.
  • MONGO_DB_URL: MongoDB connection string for data persistence.

Bot Token Variables

  • MAIN_BOT_TOKEN: Manages user commands and interactions. Must be admin in VIDEO_STORAGE Channel
  • LOGGER_BOT_TOKEN: Sends log updates to LOGGER_CHANNEL. Must be admin in LOGGER_CHANNEL Channel
  • UPLOADER_BOTS_1: Manages uploads to STORAGE_CHANNEL_1. All of them must be admin in STORAGE_CHANNEL_1 Channel

PlayerX Config

  • PLAYERX_EMAIL: Playerx.stream account email.
  • PLAYERX_PASSWORD: Playerx.stream account password.
  • PLAYERX_API_KEY: Playerx.stream API key.

PlayerX Settings

  • Player Platform: VideoJS
  • Auto Import GDrive: Enabled
  • Multi Audio: Enabled
  • Label Audio: Language
  • Label Subtitle: Language
  • Auto Import Subtitle: Enabled
  • Encode Hardsub: Disabled

Set all other settings to default.

Optional Variables

  • STORAGE_CHANNEL_2: Secondary Telegram Channel ID for m3u8 files.
  • UPLOADER_BOTS_2: Additional bot tokens for a secondary storage channel. All of them must be admin in STORAGE_CHANNEL_2 Channel
  • MAX_ACTIVE_TASKS: Maximum number of concurrent system tasks.
  • MAX_USER_CONCURRENT_TASKS: Maximum concurrent tasks per user.
  • NO_OF_UPLOADERS: Number of concurrent uploaders per task.
  • SEGMENT_SIZE: Size in MB of each segment uploaded to Telegram.

FAQs / Useful Information

Bot Commands and Their Functions

Click to expand!

  • /convert (replied to a file): The bot downloads the specified file, converts it to m3u8 format using ffmpeg, and uploads the m3u8 and TS files to Telegram, storing the file IDs in MongoDB.

  • /encode (replied to a file): The bot uploads the file to PlayerXstream, which encodes the video into multiple qualities with multiple audio tracks and subtitles in m3u8 format. The bot sends the PlayerXstream video link to the user.

  • /remote video_link: The bot adds a video link from a remote host to PlayerXstream, which downloads and encodes the video. The bot provides the encoded video link to the user.

  • /convert playerx_video_link: The bot downloads the m3u8, TS, and SRT files from PlayerXstream and uploads them to Telegram, saving the file IDs in the database.

  • /queue: The bot operates on a queue system, adhering to maximum limits for total and per-user tasks. The /queue command displays the queue status, including the number of tasks queued and running, and the number of tasks added by the user.

Why Use Multiple Bot Tokens

Click to expand!

Utilizing multiple bot tokens distributes the workload across various bots, reducing the chances of receiving floodwait errors from Telegram's API when uploading or downloading large numbers of .ts files.

Why Use Two Storage Channels

Click to expand!

Each Telegram channel can have a maximum of 50 admins. Utilizing two channels allows up to 100 bots (50 per channel) to work simultaneously, enhancing efficiency.

How to Fix Video Streaming Slowness or Buffering Issues

Click to expand!

Issue 1: Large TS File Sizes

Cause: The TS files being streamed are too large.

Solution: Instead of using the /convert command, opt for /encode or /remote. These commands handle file sizes more efficiently. For additional details on how these commands work, refer to Bot Commands and Their Functions. If you must use the /convert command, consider reducing the SEGMENT_SIZE variable to decrease file size.

Note: Even with these adjustments, streaming in 1080p may still encounter issues due to the inherent large size and high bitrate of such files.

Issue 2: Bot Overload

Cause: The bot may be engaged in multiple tasks simultaneously—such as uploading or downloading other files—or it might be hitting Telegram's floodwait limits.

Solution: A practical approach to mitigate these problems is to increase the number of bots in operation. This spreads out the workload and reduces the likelihood of hitting usage limits, thereby improving streaming performance.

Read Further : Using More Than 100 Bots in BetterTGStreamer

Using More Than 100 Bots in BetterTGStreamer

Click to expand!

If you're experiencing high traffic for video streaming or need faster file conversion and uploads, increasing the number of bots can significantly reduce load times. The current setup allows for two channels, with a maximum of 100 bots distributed between them. To exceed this limit, you will need to add more channels, with each channel supporting up to 50 bots. Here’s how you can modify your code to accommodate this:

Expanding Capacity by Adding More Storage Channels and Bots

Step 1: Update Configuration

  • Open Config.py and introduce new variables for additional channels and bot lists. For example: 
    STORAGE_CHANNEL_3 = 'your_new_telegram_channel_id'
UPLOADER_BOTS_3 = ['list_of_bot_tokens']  # Ensure these bots are admins in STORAGE_CHANNEL_3
  • Follow the same format used for STORAGE_CHANNEL_1, STORAGE_CHANNEL_2, UPLOADER_BOTS_1, and UPLOADER_BOTS_2.

Step 2: Modify Client Initialization

  • In Client.py, import the new variables, such as UPLOADER_BOTS_3.
  • Update the start_clients function to include the new bots: 
    for token in UPLOADER_BOTS_3:
    pos += 1
    UPLOADER_CLIENTS[pos] = {
        "usage": 0,
        "token": token + "%*^3",
    }

Step 3: Adapt File Uploading Logic

  • In Uploader.py, import STORAGE_CHANNEL_3.
  • Modify the send_file function to direct files to the correct channel: 
    elif int(channel) == 3:
    data["chat_id"] = str(STORAGE_CHANNEL_3)

Note: To add additional bots and channels, replicate the steps above by incrementing the channel number (e.g., STORAGE_CHANNEL_4, UPLOADER_BOTS_4, etc.). There is no upper limit to the number of bots you can integrate; the code is designed to accommodate scalability.

Support Group

For inquiries or support, join our Telegram Support Group or email techshreyash123@gmail.com.