Recherche avancée

Médias (1)

Mot : - Tags -/remix

Autres articles (37)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • List of compatible distributions

    26 avril 2011, par

    The table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
    If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...)

  • Sélection de projets utilisant MediaSPIP

    29 avril 2011, par

    Les exemples cités ci-dessous sont des éléments représentatifs d’usages spécifiques de MediaSPIP pour certains projets.
    Vous pensez avoir un site "remarquable" réalisé avec MediaSPIP ? Faites le nous savoir ici.
    Ferme MediaSPIP @ Infini
    L’Association Infini développe des activités d’accueil, de point d’accès internet, de formation, de conduite de projets innovants dans le domaine des Technologies de l’Information et de la Communication, et l’hébergement de sites. Elle joue en la matière un rôle unique (...)

Sur d’autres sites (8829)

  • How to use ffmpeg with laravel 5.7 on a shared hosting with limited resources/access

    29 novembre 2018, par DestinyB

    I have search through different forums and online resources on how I can use ffmpeg on my laravel 5.7 application on a shared host but have not gotten any solution. I actually installed ffmpeg on my project following the instructions from this link How to Install FFMPEG in Laravel.

    I also downloaded the binary files and save them to my local drive C :// in my system with windows 8.1 Operating System. Then I connected my binary as show bellow ;

     $ffprobe = FFMpeg\FFProbe::create([
           'ffmpeg.binaries'  => 'C:/FFmpeg/bin/ffmpeg.exe', // the path to the FFMpeg binary
           'ffprobe.binaries' => 'C:/FFmpeg/bin/ffprobe.exe', // the path to the FFProbe binary
           'timeout'          => 3600, // the timeout for the underlying process
           'ffmpeg.threads'   => 12,   // the number of threads that FFMpeg should use
       ]);

    I also did the path setting in the system environmental variables settings and everything was working great while serving the website from XAMPP Server.

    The problem I have is that I have uploaded the project to a shared host that I dont have access to check if they have the ffmpeg on the server or not and the host provider could not really give me a helpful information about that. So, I uploaded the binary files into a folder in my filemanger on the cpanel and named it "binary files". Then I changed my codes as given bellow ;

    $ffmpeg = FFMpeg\FFMpeg::create([
           'ffmpeg.binaries'  => '/home/username/binary_files/bin/ffmpeg.exe', // the path to the FFMpeg binary
           'ffprobe.binaries' => '/home/username/binary_files/bin/ffprobe.exe',  // the path to the FFProbe binary
           'timeout'          => 3600, // the timeout for the underlying process
           'ffmpeg.threads'   => 1,   // the number of threads that FFMpeg should use
       ]);

    But still I get error that Unable to load FFProbe as shown in this Image from the code

       public static function create($configuration, LoggerInterface $logger = null)
    {
       if (!$configuration instanceof ConfigurationInterface) {
           $configuration = new Configuration($configuration);
       }

       $binaries = $configuration->get('ffprobe.binaries', array('avprobe', 'ffprobe'));

       try {
           return static::load($binaries, $logger, $configuration);
       } catch (BinaryDriverExecutableNotFound $e) {
           throw new ExecutableNotFoundException('Unable to load FFProbe', $e->getCode(), $e);
       }
    }

    The major thing I am doing on my project is to convert video into proper encoded streaming video as well as automatically generate a .png or .jpg thumbnail from the video while uploading. So in case if there is an alternative other than ffmpeg to solve this or anyone that have use the ffmpeg library on a shared hosted before should help.
    Please !

  • Unable to access user selected file via NSOpenPanel in FFMPEG process in macOS app

    12 décembre 2019, par Raptor

    I am new to macOS development via SwiftUI. I’m trying to run a FFMPEG process after I selected a MP4 file via NSOpenPanel. However, the FFMPEG responded with :

    file :///Users/MyUsername/Documents/Video.mp4 : No such file or directory

    Here is my simple codes :

    import SwiftUI

    struct ContentView: View {

       @State var selectedURL: URL?

       var body: some View {
           VStack {
               if selectedURL != nil {
                   Text("Selected: \(selectedURL!.absoluteString)")
               } else {
                   Text("Nothing selected")
               }
               Button(action: {
                   let panel = NSOpenPanel()
                   panel.allowedFileTypes = ["mp4"]
                   panel.canChooseDirectories = false
                   panel.canCreateDirectories = false
                   panel.allowsMultipleSelection = false
                   let result = panel.runModal()
                   if result == .OK {
                       self.selectedURL = panel.url

                       let savePath = self.getDownloadDirectory().appendingPathComponent("video.webm")

                       self.convertVideo(inputFilePath: self.selectedURL!.absoluteString, outputFilePath: savePath.absoluteString, callback: {(s) in
                           // omit the callback at this moment
                       })
                   }
               }) {
                   Text("Select File")
               }
           }
           .frame(width: 640, height: 480)
       }

       func getDownloadDirectory() -> URL {
           let paths = FileManager.default.urls(for: .downloadsDirectory, in: .userDomainMask)
           return paths[0]
       }

       func convertVideo(inputFilePath: String, outputFilePath: String,
                        callback: @escaping (Bool) -> Void) -> (Process, DispatchWorkItem)? {
           guard let launchPath = Bundle.main.path(forResource: "ffmpeg", ofType: "") else {
               return nil
           }
           let process = Process()
           let task = DispatchWorkItem {
               process.launchPath = launchPath
               process.arguments = [
                   "-y",
                   "-i", inputFilePath,
                   "-vcodec", "vp8",
                   "-acodec", "libvorbis",
                   "-pix_fmt", "yuva420p",
                   "-metadata:s:v:0",
                   "alpha_mode=\"1\"",
                   "-auto-alt-ref", "0",
                   outputFilePath
               ]
               process.standardInput = FileHandle.nullDevice
               process.launch()
               process.terminationHandler = { process in
                   callback(process.terminationStatus == 0)
               }
           }
           DispatchQueue.global(qos: .userInitiated).async(execute: task)

           return (process, task)
       }
    }

    What did I miss to allow FFMPEG process to access my selected file ? Thanks !

  • FFmpeg does not successfully send http request to server

    20 octobre 2019, par e-ly

    I’m trying to output data from ffmpeg to my webserver, but it simply does not work when I use my domain. It works as expected when I use localhost but not when I use my domain.

    I’ve tried multiple things such as changing from a subdomain to a subdirectory using nginx, and like I said— it works when I use localhost but not when I use my domain. When I ran -v trace the logs told me that the connection was successful but the server did not receive anything, yet when I visited the same url in my browser I got a response.

    ffmpeg command :

    '-v', 'trace',                                              
    '-f', 'x11grab',
    '-s', '720x480',
    '-r', '30',
    '-i', ':100',
    '-an',
    '-c:v', 'mpeg1video',
    '-q:v', '12',
    '-bf', '0',
    '-f', 'mpegts',
    'http://stream.domain.com/'                                                                                                    

    Nginx rule :

    server {
      listen 80;
      server_name stream.domain.com;
      location / {
          proxy_pass http://localhost:9000/;
      }
    }    

    Nodejs code :

    app.post('/', (req, res) => {
       console.log('Post received', req.url, req.ip)
       res.sendStatus(200)
    })

    I expect the console of the node process to let me know that a post has been received (for debugging purposes)
    Instead, nothing is received.
    However using http://localhost:9000/ instead of http://stream.domain.com/ works as expected