Features & Benefits

  • Consumes the YouTube Video Backend software, inheriting all of the benefits of the "Backend" software as well as providing a professional, polished, front-end interface for performing your video/audio downloads and conversions.
  • Implements a "TALL stack" (i.e., Tailwind CSS, Alpine.JS, and the Laravel-Livewire PHP framework) that serves as a powerful foundation on which to run downloads/conversions.
  • Employs Laravel Queues for concurrent downloads/conversions to effectively regulate the efficient allocation of limited CPU resources.
    • In fact, this queue system single-handedly reduces server load to a mere fraction of the load generated by our other conversion products!
    • Moreover, you can limit the number of simultaneous jobs in the queue in such a way that your server is never overloaded!
  • Enhances Laravel's Queue functionality with additional features via the use of Laravel Horizon.
    • Laravel Horizon provides a beautiful dashboard and code-driven configuration for Laravel Queues, which is directly integrated into the software's admin interface (see below).
    • Horizon hugely simplifies the setup of multi-server, cluster configurations to manage big traffic (see below).
    • In general, Horizon enables easy monitoring of key metrics related to your queue system such as job throughput, runtime, and job failures.
  • Leverages the power of FFmpeg (in conjunction with and in the context of the queue system) to download and convert content from all supported video/audio hosting sites to the following file formats:
    • Multiple MP3 qualities, up to 320kbps
    • MP4 and WEBM video, generally up to 720p (does not require FFmpeg!)
    • Merged video- and audio-only tracks as composite MP4 and WEBM, up to 8k HDR
  • Optionally allows for "Simulated MP3" downloads.
    • When audio-only versions of media are available from YouTube, the source audio file extension (e.g., .m4a, .aac, or .webm) is renamed to .mp3.
    • This enables MP3 generation without FFmpeg conversion and consumption, resulting in a significant savings of CPU resources!
    • Resulting MP3 files may not be playable in all audio/media players and will lack file metadata (e.g., bitrate, duration, track info, etc.).
  • Automatically caches ALL downloaded and converted files.
    • In general, files are always saved to the server first, so the caching mechanism is just an extension of that behavior. 
    • The cache ensures that the same files aren't downloaded and converted over and over again, resulting in a significant savings of resources (foremost, CPU and bandwidth) on your server!
    • You can regulate cache size by setting the maximum age of cached files, in hours, before they are purged from the cache (via a regular, scheduled task).
  • Includes 5 ready-to-consume APIs, that can each be enabled/disabled and their use restricted by IP/Domain, as needed:
    • JSON REST API that returns either MP3, MP4, or WEBM download links (see formats, above)
    • Button API that returns download buttons for either MP3, MP4, or WEBM (see formats, above)
    • Single Button API that returns a single button for downloading either one MP3 or MP4 file
    • Two Widget APIs that mimic the website interface's download section, toggle between available download formats (i.e., MP3, MP4, or WEBM), and include some or all of the following video/audio information:
      • Thumbnail image
      • Title
      • Quality
      • File size
  • Enables you to use the software for its website interface only, its API(s) only, or both!
    • A product installation can either be configured as a "Master" (with the website interface enabled) or a "Worker" (with the website interface disabled).
      • Note: For the sake of clarity, the terms "Master" and "Worker" will always be used in this context! They should not be confused with the terms "master node" and "slave node" that are used in the context of a multi-server, cluster configuration (see below).
    • In a single-server setup, a Master installation can be used:
      • For its website interface only, or
      • For both its website UI and API requests.
    • In a single-server setup, a Worker installation can only be used for API requests.
    • In any use case, a Worker can only ever perform downloads and conversions -- for itself, a Master, or another Worker. 
  • Scales effectively and seamlessly to manage more and more traffic over time.
    • If/When you've exhausted the resources of a single server (e.g., if/when you ever have so much traffic that even a single, powerful hosting plan/server cannot accommodate it), then you can easily operate the software in a cluster configuration to "balance load" equally across multiple servers (without the need for a 3rd-party load balancer like HAProxy).
      • In general, clusters consist of a "master node" (the primary server) and one or more "slave nodes" (additional servers) which function to support the "master node".
      • All incoming traffic is sent exclusively to the cluster's "master node".
      • Each cluster node hosts exactly one product installation.
    • Each product installation on each cluster node must enable cluster support (by toggling the corresponding admin setting ON).
    • A cluster will consist of multiple installations configured as either:
      • One Master and any number of Workers (to support the website interface and, optionally, API requests), or
      • Only Workers (for API requests only)
    • A cluster's "master node" can be either a Master or a Worker, while a "slave node" can only ever be a Worker.
    • Leveraging Laravel Horizon and Queues, a single, ultra-efficient, in-memory, Redis database installation on the cluster's "master node" regulates and tracks queuing across all "slave nodes".
    • Download/Conversion queuing can be disabled in the "master node" installation to free up resources on the corresponding server (to maximize its ability to handle all cluster traffic).
    • All cluster nodes' installations share and consume download links generated by the same, single YouTube Video Backend installation.
    • All "slave node" installations can use the same product license as the "master node" installation, so you don't have to keep purchasing additional licenses as the size of your cluster grows!
  • Allows any product installation (that performs downloads/conversions) to use a separate subdomain (e.g., http://cdn01.yoursite.com) for serving downloaded/converted files during browser download.
  • Eliminates traditional, public-facing, download URLs and instead encrypts download link "references", to:
    • Prevent malevolent third parties (i.e., "bots") from scraping your website and abusing your valuable server resources.
    • Mitigate DMCA takedown requests because the absence of download URLs means there are virtually no website links to report!
  • Features a sleek, user-friendly, admin interface that facilitates API key management, product license management, and product update notifications as well as:
    • Configuration of a plethora of global site settings
    • Google Analytics and Popup Ads code management
    • Language translations for default website metadata and content
    • Real-time monitoring of the queue system, via Laravel Horizon
  • Includes a convenient Installation Wizard and Config Check utility to dramatically simplify initial product setup.
  • Enables users to download/convert one or more videos while another download/conversion is in progress.
  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

How To add new Pages/Routes in MP3 Converter Pro

1) How To add a new Page like "domain.com/youtube-to-mp3" that displays the homepage? Open...

How To install MP3 Converter Pro on Plesk

Requirements # Recommended Server VPS, Cloud, or Dedicated (Get 20€ Free...

How To install MP3 Converter Pro (Update v3.0.5) on aaPanel (recommended)

Requirements # Recommended Software YouTube Video Backend Server VPS,...