
Recherche avancée
Médias (2)
-
Exemple de boutons d’action pour une collection collaborative
27 février 2013, par
Mis à jour : Mars 2013
Langue : français
Type : Image
-
Exemple de boutons d’action pour une collection personnelle
27 février 2013, par
Mis à jour : Février 2013
Langue : English
Type : Image
Autres articles (13)
-
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...) -
Déploiements possibles
31 janvier 2010, parDeux types de déploiements sont envisageable dépendant de deux aspects : La méthode d’installation envisagée (en standalone ou en ferme) ; Le nombre d’encodages journaliers et la fréquentation envisagés ;
L’encodage de vidéos est un processus lourd consommant énormément de ressources système (CPU et RAM), il est nécessaire de prendre tout cela en considération. Ce système n’est donc possible que sur un ou plusieurs serveurs dédiés.
Version mono serveur
La version mono serveur consiste à n’utiliser qu’une (...) -
Configuration spécifique pour PHP5
4 février 2011, parPHP5 est obligatoire, vous pouvez l’installer en suivant ce tutoriel spécifique.
Il est recommandé dans un premier temps de désactiver le safe_mode, cependant, s’il est correctement configuré et que les binaires nécessaires sont accessibles, MediaSPIP devrait fonctionner correctement avec le safe_mode activé.
Modules spécifiques
Il est nécessaire d’installer certains modules PHP spécifiques, via le gestionnaire de paquet de votre distribution ou manuellement : php5-mysql pour la connectivité avec la (...)
Sur d’autres sites (2456)
-
inconsistent thumbnail with ffmpeg on avi, mp4
21 août 2013, par Xiongi am getting inconsistent thumbanails when i add a new video. i have video files with width and height 640x480 and 1280x720. what do i have to change ?
public void exec(string input, string output, string parametri)
{
ffmpeg = new Process();
ffmpeg.StartInfo.Arguments = " -i " + input + (parametri != null ? " " + parametri : "") + " " + output;
ffmpeg.StartInfo.FileName = "ffmpeg.exe";
ffmpeg.StartInfo.UseShellExecute = false;
ffmpeg.StartInfo.RedirectStandardOutput = true;
ffmpeg.StartInfo.RedirectStandardError = true;
ffmpeg.StartInfo.CreateNoWindow = true;
ffmpeg.Start();
ffmpeg.WaitForExit();
ffmpeg.Close();
}
public void GetThumbnail(string video, string jpg, string velicina)
{
if (velicina == null) velicina = "640x480";
exec(video, jpg, "-s " + velicina);
}
private void btnBrowseThumbnail_Click(object sender, EventArgs e)
{
string newThumbnail = Properties.Settings.Default.folderPathUserThumbnail + "CopyFiles.jpg";
GetThumbnail(txtFile.Text, newThumbnail, null);
string curFile = newThumbnail;
if (File.Exists(curFile))
txtThumbnail.Text = newThumbnail;
} -
PHP extension writing
19 octobre 2013, par Mikko Koppanen — ImagickI’ve written quite a few PHP extensions over the past years and thought that I could share some of the experience with larger community. PHP internals can be a bit scary at times and in the past I’ve scoured through a lot of extensions to find practical examples of things such as how to return objects from internal functions/methods, how to handle different types of parameters, class properties etc.
To document some of the experiences I started a project called extsample, in which I plan to add practical examples related to extension writing. There won’t be extensive written documentation outside the code, but hopefully the code itself contains enough nuggets of information to be useful. As the README says, if you need a specific example or clarification on something just open an issue in Github.
The project is still very fresh but hopefully soon it will contain more examples. Pull requests are also welcome if you have code that you want to share with others.
-
How to set RTSP transport mode to TCP using Xuggler
1er novembre 2013, par Anurag JoshiI am working with a Sanyo VCC HD2300P IP camera and trying to capture the frame from the live stream on the camera. I have another camera that provides an rtsp stream and the Xuggler code works fantastically on that. However, on the sanyo camera I get the error below
could not open stream: rtsp://admin:admin@192.168.0.3:554/VideoInput/1/h264/1
I use this stream on iSpy and VLC and am able to get the stream. Using the functionality from these 2 programs I am also able to capture a frame from the stream.
The URL for the other camera that works well is rtsp ://admin:123456@192.168.0.246/mpeg4cif. So on the face of it I don't see a reason why it should not work.Any help will be highly appreciated.
EDIT : I searched and experimented a lot. Earlier I was using the inbuilt support for Sanyo cameras in iSpy using which the camera stream was visible. However, when I tried to directly provide the URL for the H.264 stream, the stream would not work unless I changed RTSP mode to TCP. This gave me a hint that probably I need to call the IContainer.open method in a manner that uses RTSP over TCP.
Googling about it threw some possible solutions likeusing rtsp://192.168.0.3:554/VideoInput/1/h264/1?tcp
It says that this would force the stream to open on TCP. However, nothing has changed for me. I still get the same error.
EDIT2 : So essentially it boils down to how do I set the RTSP transport mode to TCP ? By default the transport mode for RTSP is UDP.
EDIT3 : I am still searching for a solution. Looks like in Xuggler 1.19 all these features were provided directly on the IContainer, IStreamCoder and IVideoSampler objects using the setProperty method which implements the IConfigurable interface. However,
setProperty("rtsp_transport", "tcp")
always returns a -ve value indicating that the setProperty command failed. This is because if we call the getPropertyNames() function on each of the IContainer, IStreamCoder and IVideoSampler objects, the list of properties returned doesn't contain a property called rtsp_transport.
At the same time, https://github.com/artclarke/xuggle-xuggler/blob/master/captive/ffmpeg/csrc/doc/protocols.texi this article suggests that it is indeed possible to set the rtsp_transport value to tcp. I am however, unable to understand it.
Please help !!