
Recherche avancée
Autres articles (20)
-
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...) -
ANNEXE : Les plugins utilisés spécifiquement pour la ferme
5 mars 2010, parLe site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)
-
Supporting all media types
13 avril 2011, parUnlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)
Sur d’autres sites (3800)
-
avformat/mov : fix "warning : variable altitude set but not used" warning
6 juin 2014, par Michael Niedermayer -
Revision 944e3e71b7 : Merge "Fixes qindex for first frame in 1-pass cq/q modes"
6 juin 2014, par Deb MukherjeeMerge "Fixes qindex for first frame in 1-pass cq/q modes"
-
Call remote cmdlet (ffmpeg) via Invoke-Command : "... not recognized as the name..."
7 décembre 2016, par sk904861I’m trying to call ffmpeg on a remote transcoding server via Powershell :
$session = new-pssession -computername transcodingserver
Invoke-Command -session $session -scriptblock { powershell ffmpeg }ffmpeg is correctly installed on the remote server and can be run there, but the remote call results in an error :
ffmpeg : The term 'ffmpeg' is not recognized as the name of a cmdlet, function, script file, or operable program.
+ CategoryInfo : NotSpecified: (ffmpeg : The te...rable program. :String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError
+ PSComputerName : transcodingserver
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ ffmpeg
+ ~~~~~~
+ CategoryInfo : ObjectNotFound: (ffmpeg:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
NotSpecified: (:) [], RemoteExceptionIt seems to me like if the machine, I run
Invoke-Command
on, tries to run ffmpeg, which is not installed there. What do you have to do, to run ffmpeg on a remote server ?