Can it wok on php scrip/site that uses ffmpeg to generate different video qualities like 720,1080

[Galleyr]

Hey SteelBrain & Team
Sorry I couldn't find another way to contact you, I have a php script/site hosted in Lampp/hestiaCP, that host videos uploaded, it uses ffmpeg to generate different video qualities like 720,1080, can I utilize this code to use cluster servers to reduce the load from the main server

Kind Regards

[steelbrain]

Hi @Galleyr

Thanks for writing in. The feasibility of ffmpeg-over-ip depends on a couple factors:

• Are you on a dedicated hosting solution or a shared hosting one?
• Where are the files eventually hosted? Local filesystem or a storage API service (ie s3?)
• Do you have the ability to have a shared filesystem (could be nfs, or any other kind of mount) between the video processing cluster?

If you're hosting on your own servers and have the ability to make a network mount, then this could definitely work. The way things are setup right now, you will have to add some php glue/logic to load balance between the servers but the rest should be fine.

In my local usage (mostly homelab), I was using the nfs network mount, this meant that as ffmpeg was converting videos on a remote server, the client could already start serving the partial files

[Galleyr]

Thanx for help
1- I'm using Ubuntu VPS with hestaCP on both machines, on local I'm using Ubuntu & lampp
2- For storage my script/site has the ability to change Media storage, say it can be set to store locally, remote [ ftp, s3 or wasabi] but for the remote storage, what it does is that it first uploads on local directory, processes videos using ffmpeg to generate different resolutions like 1080,720, once it completes, then uploads them to the remote storage if set.
3- Yes I have full control of all machines, I can setup NFS share
cronjob.php.txt

Also how is this different from rFFMPEG and FFMPEGoF

Kind Regards

[steelbrain]

This is helpful context! I think you can absolutely make this work! Here's how that will probably look like

• Setup a shared filesystem between the main machine (with the php application) and the pool of video conversion machines
  • If you have a separate server that handles the uploaded files, that can be the filesystem server, otherwise the php one could serve that role
  • For the shared filesystem, use something like NFS that offers block-level access on the files
• Keep the uploads in the local directory, then process the videos with the pool of workers

Let me know if this makes sense. I have to admit that ffmpeg-over-ip shines the brightest when the usecase requires live streaming of the converted output or mixing and matching machine types with different encoding capabilities (so a plex/emby/jellyfin media streaming server using a GPU from a different machine on the same network).

Since this use case is more asynchronous that you do not need to live stream the results of the conversion to clients waiting for it, it gives you a lot of freedom to innovate in your setup.

While rffmpeg is more complicated to setup than ffmpeg-over-ip, it may be worth exploring here since it has support for multiple target hosts built-in. It'll also rid you of the requirement of having a shared filesystem since it streams the contents over ssh

[Galleyr]

Thanx for the help
So how is it called the feature, for expample now for ffmpeg, it's called like
1- ffmpeg -i /home/site/upload/s5kss45s2d55.mp4 -vf scale=854:480 /home/site/upload/s5kss45s2d55_480_conveted.mp4
so is it like: ffmpeg-over-ip -i /home/site/upload/s5kss45s2d55.mp4 -vf scale=854:480 /home/site/upload/s5kss45s2d55_480_conveted.mp4 is that correct
2- Apart from being simpler, does it do same as rffmpeg/ffmpegof, I mean, in terms of functionality what is the difference

Kind Regards

[steelbrain]

Hi @Galleyr! Its been a while, but since I last wrote to you, there is no longer a need for a shared file system, meaning you can call it like a regular ffmpeg from your script.

Take it for a spin and let me know how it goes