
Recherche avancée
Médias (1)
-
SWFUpload Process
6 septembre 2011, par
Mis à jour : Septembre 2011
Langue : français
Type : Texte
Autres articles (97)
-
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
Multilang : améliorer l’interface pour les blocs multilingues
18 février 2011, parMultilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela. -
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
Sur d’autres sites (9110)
-
Can not open a video file in OpenCV
31 octobre 2017, par mansI have a video file that encoded in h264 and save in mkv format (*.mkv).
I can pen file in VLC and play it, but I want to open it in OpenCV and extract each frame of the video.I have this code :
std::string fileName = "D:/Temp/video.mkv";
cv::VideoCapture capture(fileName);
capture.set(CV_CAP_PROP_FOURCC, CV_FOURCC('H', '2', '6', '4'));
if (!capture.isOpened())
{
//error!
std::cout << "Can not load video";
}
else
{
double prevtimestamp = 0;
cv::Mat frame;
while (1)
{
capture.grab();
double timestamp = capture.get(CV_CAP_PROP_POS_MSEC);
}
}when I run this code, I am getting message that the file can not be open.
My questions :
- Is there anything wrong with this code ?
- Do I need FFMPEG on the path so OpenCV can open h264 videos ?
- How can I get more information why OpenCV can not open the file ?
-
lavc/aacpsdsp : fix clobber on RISC-V LP64D/ILP32D
6 octobre 2022, par Rémi Denis-Courmontlavc/aacpsdsp : fix clobber on RISC-V LP64D/ILP32D
Although the DSP function only uses single precision from RISC-V F, the
caller may leave double precision values in the spilled registers if the
calling convention supports double precision hardware floats. Then, we
need to save and restore FS registers as double precision.Conversely, we do not need to save anything at all if an integer calling
convention is in use. However we can assume that single precision floats
are supported, since the Zve32f extension implies the F extension.
So for the sake of simplicity, we always save at least single precision
values.In theory, we should even save quadruple precision values if the LP64Q
ABI is in use. I have yet to see a compiler that supports it though. -
Anomalie #2076 : Surcharge des fichiers de langues
10 mai 2011, par Guy Cesarodoublon avec #2075, pb de double clic.