Recherche avancée

Sur d’autres sites (8487)

• Architecture of video-based service for mobile phones

  27 juin 2015, par David Azar

  I guess this is more of a conceptual question than a technical one.

  I’m trying to figure out the best way to upload short videos to a server and also be able to download them and watch them on both Android and iOS.

  Lets focus on Android for the moment.

  I’ve done some experiments, and my results have been :

  • I’m able to compress 12-14MB video down to 500KB using FFMPEG lib with pretty good results in quality, but it takes about 12 seconds.

  • Next, im uploading those videos to my Parse backend as ParseFile to store them.

  • Finally, i can download them and watch them with no problem using a VideoView widget.

  Now, for the tests i’ve been running, these are great results. But i want to see if there is a better way to manage and scale all of this.

  My questions are :

  • Is there a better, lighter way to compress video ?

  • Is Parse the right way to go ?

  • How can i stream videos instead of downloading them and storing the on local storage before playing them ? i know this will cause my app to use significant space on disk and i dont want that.

  • How do big companies do this kind of tasks ?

  I’ve heard Amazon S3 is a cool thing for projects like this one, also Google Cloud Platform. I want to understand the best approach before building everything so i can do it the right way and also, provide the absolute best user experience for watching these videos.

• Connection randomly closes wihtout data while running a FFMPEG PHP script

  23 octobre 2022, par Victor Marinov

  I'm building a simple back-end solution for a client that allows them to upload any video in mo4 or mov format of up to about 500MB in size to a PHP back-end, which then takes the material, downsizes and compresses the it using the PHP library FFMPEG available here https://github.com/PHP-FFMpeg/PHP-FFMpeg.

  


  While the video is being processed the connection to the front-end stays open, awaiting the compression result.

  


  This may normally take up to 3-5 minutes depending on the size and duration of the video.

  


  Overall it functions as intended, but with some videos I get random resets of the connection while the video is being processed.

  


  I've added numerous error_log() lines in my script which show that the script continues running even after the connection is reset and the actual processing and compression of the video completes correctly and the file is saved in the DB and in storage.

  


  Below is a small excerpt from the code in question :

  


                          //THEN COMPRESS VIDEO THUMBNAIL
                        $format = new FFMpeg\Format\Video\X264();
                        $format->setKiloBitrate(3200);
                        error_log("BEFORE COMPRESS! ", 0);

                        //PREVENT ANY ECHO's
                        ob_start();
                        error_log("DURING COMPRESS... ", 0);
                        $video->save($format, $export_path);
                        error_log("JUST AFTER... ", 0);
                        $compress_output = ob_get_clean();

                        $resp['video_compression_result'] = 'success';
                        error_log("COMPRESS SUCCESS! ", 0);


  


  I would just like to know if any of you would have an idea why the connection might be reset on some files and not on others ? I've even tried wrapping the the $video->save() function in an output buffer to prevent any possible output which might trigger an premature output.

  


  I have increased the PHP settings for max_memory to 2G and upload_max_filze and post_max size to 500M.

  


  max_execution_time and max_input_time are both set to 1200 sec. The random reset usually comes at 1.7 or 5.4 minutes into the request and seem to depend on the file selected.

  


  I've successfully processed smaller files from the same source without issues. The only variable here appears to be the duration and size of the video. What is most puzzling to me is that the remaining code continues to run fine even after the connection is reset.

  


  If you have any clues, please let me know as this is driving me crazy for a second day in a row now and spoiling an otherwise perfectly functional solution for the client !

  


• Evolution #4417 : Augmenter la longueur du mot de passe demandé pour créer un nouvel auteur

  24 décembre 2019, par cy_altern -

  complémentairement, pour compliquer le "brut force" des mots de passes, il y aurait l’utilisation d’un algorithme de hashage de type Argon2 (cf https://fr.wikipedia.org/wiki/Argon2) qui est conçu pour imposer un coût mémoire.
  Voir https://github.com/p-h-c/phc-winner-argon2 pour les implémentations disponibles de Argon2 (PHP > 7.2 et JavaScript OK)