Recherche avancée

Sur d’autres sites (7860)

• PHP unable to move uploaded file

  11 mars 2015, par Markjose

  I have been trying to create an upload.php script however the condition doesn’t seem to work and PHP can not move the uploaded file to the folder upload.

  Apache2 log output below

  PHP Warning:  move_uploaded_file(): The second argument to copy() function cannot be a directory in /var/www/html/upload.php on line 18, referer: http://192.168.0.110/stream.php
  
  
  
  PHP Warning:  move_uploaded_file(): Unable to move '/tmp/phpC34Agu' to '/var/www/html/upload/' in /var/www/html/upload.php on line 18, referer: http://192.168.0.110/stream.php

  Upload.php code

     <?php
  
  $target_path = "/var/www/html/upload/";
  
  $target = $target_path . basename($_FILES['uploadedfile']['name'][0] );
  
      if(move_uploaded_file($_FILES['uploadedfile']['tmp_name'] [0], $target_path))
  
       { 
  
      echo "The file ". basename( $_FILES['uploadefile']['name'] [0]). " has been uploaded"; 
  
     } 
  
      else {
  
   echo "Sorry, there was a problem uploading your file."; 
  
       }
  
     ?>

  I would also like php to execute this ffmpeg command directly afterwards, but i’m unsure where to insert it.

  FFMPEG command

  ffmpeg -re -i uploadedfile.name -vcodec copy -f mpegts udp://239.1.1.1:5000

  Thanks for all your help.

  Kind Regards,

  Mark Couto

• "Error opening filters !" when using fluent-ffmpeg with Node

  3 février 2015, par doremi

  I’m trying to get a basic example of html5 video streaming working in an express node app, but I keep running into ffmpeg errors that I’m unsure of how to resolve.

  The input file/stream is the sample.mp4 located here.

  Complete example :

  var ffmpeg = require('fluent-ffmpeg');
  
  var express    = require('express');
  
  var fs         = require('fs');
  
  var sampleApp  = express();
  
  var videoApp   = express();
  
  
  
  var SAMPLE_SERVER_PORT = 3000;
  
  var VIDEO_SERVER_PORT  = 5000;
  
  
  
  sampleApp.get('/:video', function (req, res) {
  
    var videoURL = 'http://localhost:' + VIDEO_SERVER_PORT + '/' + req.params.video;
  
    return res.end('<video controls="controls" src=" + videoURL +"></video>');
  
  });
  
  
  
  videoApp.get('/:video', function(req, res) {
  
  
  
    res.statusCode = 200;
  
    res.setHeader('content-type','video/mp4');
  
  
  
    var stream = fs.createReadStream('./samples/' + req.params.video);
  
  
  
    var proc = ffmpeg(stream)
  
  
  
      .format('mp4')
  
      .size('320x?')
  
      .videoBitrate('512k')
  
      .videoCodec('libx264')
  
      .fps(24)
  
      .audioBitrate('96k')
  
      .audioCodec('aac')
  
      .audioFrequency(22050)
  
      .audioChannels(2)
  
  
  
      .on('error', function(err) {
  
        console.log('an error happened: ' + err.message);
  
      })
  
  
  
      .pipe(res, { end:true });
  
  });
  
  
  
  var server = sampleApp.listen(SAMPLE_SERVER_PORT, function () {
  
    console.log('Example app listening at http://%s:%s', server.address().address, SAMPLE_SERVER_PORT);
  
  });
  
  
  
  
  
  var videoServer = videoApp.listen(VIDEO_SERVER_PORT, function () {
  
    console.log('Video Server listening at http://%s:%s', server.address().address, VIDEO_SERVER_PORT);
  
  });

  The error (via console) :

  an error happened: ffmpeg exited with code 1: Error opening filters!

  ffmpeg configuration :

  ./configure  --prefix=/usr/local --enable-gpl --enable-nonfree --enable-libass \                                                                         
  
  --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus \
  
  --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxvid --enable-libfaac --enable-libfdk-aac

  Any input would be greatly appreciated.

• Anomalie #4214 : Notices sous easyphp et php 7.3 rc3

  2 novembre 2018

  Bah…
  Tu mets : define('_BOUCLE_PROFILER', 5000);
  Ce qui indique de logguer les boucles qui mettent plus de 5s à se calculer.
  Voilà… ton log indique que la boucle des résultats de recherche de plugins met 184s à se faire.
  En fait c’est très long car elle télécharge (et met en cache) chaque logo de plugin trouvé...
  Je dirais… que… bah voilà… c’est pas un bug, c’est une feature :)