
Recherche avancée
Médias (1)
-
Bug de détection d’ogg
22 mars 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Video
Autres articles (83)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...) -
Le profil des utilisateurs
12 avril 2011, parChaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...)
Sur d’autres sites (9953)
-
Where to get an up to date php_ffmpeg.dll
25 avril 2015, par HeidiI have Windows 2008 R2 64 bit.
I have installed ResourceSpace 7.1.6513 which requires PHP & FFMPEG. This is not a ResourceSpace question.I have installed PHP 5.4.40 VC9 x86 non thread safe (as advised by ResourceSpace wiki & GG).
I have installed FFMPEG version N-71664-gcd69c0e (64 bit static)Now it seems that FFMPEG and PHP need to have a php_ffmpeg.dll to work in Windows.
Is that true ?If so, where do I get one that will work with my FFMPEG & PHP ? I have looked here and followed old threads, and have found random php_ffmpeg.dlls but I cannot confirm that they are compatible.
The file taht I found, I have put it c :\php\ext and updated php.ini with extension=php_ffmpeg.dll -
C++/CLI — 0xc000007b (INVALID_IMAGE_FORMAT) with /clr option on
9 mars 2015, par OverMachoGrandeI’m trying to build a C++/CLI executable to which I statically link ffmpeg (libavcodec, libavformat, libavutil & swscale). It works fine if I build it normally (without /clr, so no CLR support), it works. However, when I add CLR support, it won’t start up with a 0xc000007b. A "Hello World" C++/CLI app runs fine, though.
Supposedly the same thing happens with Boost::Threads, but since ffmpeg is pure C, I doubt it’s using Boost.
My config :
- Visual Studio 2008 Professional SP1
- Windows XP Pro SP3 (x86)
- .NET Framework 3.5 SP1
Thanks,
Robert -
Use FFMPEG to stream images from one client to another through IIS (or other) server
20 avril 2012, par eselkI'm new to FFMPEG and maybe I should post this in their forums, but you guys here seem to know everything, so here goes. I have a client app that takes screen shots and saves them as images (256 color bitmaps currently, can change if needed), it does this at a rate of about 4 fps. I currently use my own socket code written in C# to push these to my socket server (also C#) running on a Windows 2008 server. That server then sends these images out to several clients that display them as they are received and also buffers them to allow for rewind, pause, etc, like a DVR. My current format requires approx 100KB per frame, and thus only works for a very small number of clients.
I started looking at FFMPEG and the compression with MPEG1 and especially MPEG4 is amazing, and so is the quality. What I'm looking for is a basic guide, tutorial, or steps, to produce something similar to my current design, but using FFMPEG and actual video streaming. Ideally the player side could be something like Flash or anything that is easy to embed in a .NET WinForm (or a browser control I can host in the WinForm), and it would need to support buffering still so they can pause and rewind (about 5 or 10 mins, which seems like a lot, but remember this is only 4 fps and 256 color, about 1 or 2 MB per min in my testing).
I see that FFMPEG, the command-line utility, and I assume the API, even has options for posting to a server via UDP or TCP, so maybe I'll use that instead of my own socket code. Ideally my app would feed images to FFMPEG library at a rate of 4fps as they come from the screen-shot unit, and it would send these up to my IIS server (or another server ?) which would then server them to client(s) that could use them similar to a YouTube video.