Recherche avancée

Sur d’autres sites (5565)

• Laravel php timelapse an UploadedFile video element, without saving it as a file

  24 août 2022, par The Blind Hawk

  I want to be able to change the frame rate of a video from 0.05fps to 3fps.
  
I receive the video as an Illuminate\Http\UploadedFile element, with mp4 format, how do I speed up its frame rate before sending it via email ?
  
The video is 25 minutes long, it should become 25 seconds long after changing the frame rate.
  
Is there a way to change the fps without saving the element as a File ?
  
I was planning to use the ffmpeg repository here but it requires me to save both the initial file, and the second file after changing the fps.

  
This is my code :

  


  <?php

namespace Server\Mail;

use Carbon\Carbon;
use Illuminate\Bus\Queueable;
use Illuminate\Contracts\Queue\ShouldQueue;
use Illuminate\Mail\Mailable;
use Illuminate\Queue\SerializesModels;
use Illuminate\Http\UploadedFile;

class TimeLapse extends Mailable
{
    use Queueable, SerializesModels;

    public UploadedFile $video;

    public bool $is_timelapsed;

    public string $format;

    /**
     * Create a new message instance.
     */
    public function __construct(
        UploadedFile $video, 
        bool $is_timelapsed, 
        string $format
    ){
        $this->video = $video;
        $this->is_timelapsed = $is_timelapsed;
        $this->format = $format;
    }

    private function timelapse(){
        // here I want to change $video element's fps from 0.05 to 3
    }

    /**
     * Build the message.
     *
     * @return $this
     */
    public function build()
    {
        if ( !$is_timelapsed ) { timelapse(); }

        $this->subject('message')
                    ->text('emails.timelapse');

        $this->attach($this->video, [
            'as' => 'sample'.$format,
            'mime' => 'video/'.$format,
        ]);

        return $this;
    }
}


  


• Media conversion on AWS

  27 juin 2022, par Gurmeet Singh

  I have an API written in nodeJS (/api/uploadS3) which is a PUT request and accepts a video file and a URL (AWS s3 URL in this case). Once called its task is to upload the file on the s3 URL.

  


  Now, users are uploading files to this node API in different formats (thanks to the different browsers recording videos in different formats) and I want to convert all these videos to mp4 and then store them in s3.

  


  I wanted to know what is the best approach to do this ?

  


  I have 2 solutions till now

  


  1. Convert on node server using ffmpeg -

  


  The issue with this is that ffmpeg can only execute a single operation at a time. And since I have only one server I will have to implement a queue for multiple requests which can lead to longer waiting times for users who are at the end of the queue. Apart from that, I am worried that during any ongoing video conversion if my node's traffic handling capability will be affected.

  


  Can someone help me understand what will be the effect of other requests coming to my server while video conversion is going on ? How will it impact the RAM, CPU usage and speed of processing other requests ?

  


  2. Using AWS lambda function -

  


  To avoid load on my node server I was thinking of using an AWS lambda server where my node API will upload the file to S3 in the format provided by the user. Once, done s3 will trigger a lambda function which can then take that s3 file and convert it into .mp4 using ffmpeg or AWS MediaConvert and once done it uploads the mp4 file to a new s3 path. Now I don't want the output path to be any s3 path but the path that was received by the node API in the first place.

  


  Moreover, I want the user to wait while all this happens as I have to enable other UI features based on the success or error of this upload.

  


  The query here is that, is it possible to do this using just a single API like /api/uploadS3 which —> uploads to s3 —> triggers lambda —> converts file —> uploads the mp4 version —> returns success or error.

  


  Currently, if I upload to s3 the request ends then and there. So is there a way to defer the API response until and unless all the operations have been completed ?

  


  Also, how will the lambda function access the path of the output s3 bucket which was passed to the node API ?

  


  Any other better approach will be welcomed.

  


  PS - the s3 path received by the node API is different for each user.

  


• PHP exec 'at' command doesn't work

  16 avril 2014, par Vitaly

  I'm trying to schedule video recording from live stream with 'at' command :

  exec("/usr/bin/at now +1 minute <<< \"ffmpeg -i 'http://191.235.136.144:9001/?cmd=play&file=7663&type=channel' -vcodec copy -acodec copy -t 30 -f mp4 -y /media/NASDRIVE/video_2.mp4\" 2>&1", $output, $return_var);

  Checking with 'at -l' doesn't show anything. When I run absulutely the same command in the console, everything works fine.

  I've added 'www-data ALL=NOPASSWD : ALL' to sudoers. Still getting empty 'at' queue.