Recherche avancée
Autres articles (35)
-
Support de tous types de médias
10 avril 2011Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)
-
Other interesting software
13 avril 2011, parWe don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
We don’t know them, we didn’t try them, but you can take a peek.
Videopress
Website : http://videopress.com/
License : GNU/GPL v2
Source code : (...) -
Keeping control of your media in your hands
13 avril 2011, parThe vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)
Sur d’autres sites (8037)
-
Crash in ffmpeg avcodec_free_context in one application but not in other
5 novembre 2017, par geekowlI am building an application in C++ on Windows 10 using Microsoft Visual Studio 2012 Professional.
I have created a wrapper library around ffmpeg (libavcodec) to encode video in H.264 format using libx264. This wrapper contains following functions :
Initialize()
Open()
EncodeFrame()
Close()
Uninitialize()I created a test application to test the wrapper library. The test application works perfectly fine.
When I use the wrapper library in my actual main application, the main application crashes in
Close()API. Inside close, it crashes inavcodec_free_context(). The difference between the main application and the test application is that the main application links with some more dependent libraries that test application does not link with.To debug the problem in the main application, I put
avcodec_free_context()in Open() after the context is allocated. The crash occurs ifavcodec_free_context()is put at a certain point as shown below.pCodecContext = avcodec_alloc_context3(pCodec);
// <---- No crash here.
pCodecContext->bit_rate = 200000;
pCodecContext->width = 320;
pCodecContext->height = 240;
.
.
.
if (pCodec->id == AV_CODEC_ID_H264)
{
av_opt_set(pCodecContext->priv_data, "preset", "slow", 0);
av_opt_set(pCodecContext->priv_data, "tune", "zerolatency", 0);
}
pCodecContext->flags |= CODEC_FLAG_GLOBAL_HEADER;
// <-- No crash here
if (avcodec_open2(pCodecContext, pCodec, NULL) < 0)
{
return -1;
}
// <-- Crash here [avcodec_free_context(&pCodecContext);]What is a correct approach to identify and resolve this problem ?
Thanks in advance.
Update
I found out that ffmpeg was built using gcc. That was causing the crash. I rebuilt ffmpeg using Visual Studio. That solved problem.
-
Crash in ffmpeg avcodec_free_context in one application but not in other
5 novembre 2017, par geekowlI am building an application in C++ on Windows 10 using Microsoft Visual Studio 2012 Professional.
I have created a wrapper library around ffmpeg (libavcodec) to encode video in H.264 format using libx264. This wrapper contains following functions :
Initialize()
Open()
EncodeFrame()
Close()
Uninitialize()I created a test application to test the wrapper library. The test application works perfectly fine.
When I use the wrapper library in my actual main application, the main application crashes in
Close()API. Inside close, it crashes inavcodec_free_context(). The difference between the main application and the test application is that the main application links with some more dependent libraries that test application does not link with.To debug the problem in the main application, I put
avcodec_free_context()in Open() after the context is allocated. The crash occurs ifavcodec_free_context()is put at a certain point as shown below.pCodecContext = avcodec_alloc_context3(pCodec);
// <---- No crash here.
pCodecContext->bit_rate = 200000;
pCodecContext->width = 320;
pCodecContext->height = 240;
.
.
.
if (pCodec->id == AV_CODEC_ID_H264)
{
av_opt_set(pCodecContext->priv_data, "preset", "slow", 0);
av_opt_set(pCodecContext->priv_data, "tune", "zerolatency", 0);
}
pCodecContext->flags |= CODEC_FLAG_GLOBAL_HEADER;
// <-- No crash here
if (avcodec_open2(pCodecContext, pCodec, NULL) < 0)
{
return -1;
}
// <-- Crash here [avcodec_free_context(&pCodecContext);]What is a correct approach to identify and resolve this problem ?
Thanks in advance.
Update
I found out that ffmpeg was built using gcc. That was causing the crash. I rebuilt ffmpeg using Visual Studio. That solved problem.
-
Showing in-video visual progress bar with FFMPEG ?
20 mai 2024, par TaapoAs OBS Studio lacks a visual indicator to show how far a video has progressed (and when you need to advance to the next scene), I was wondering if there is a command-line option (or solution) to get FFMPEG to re-encode the video and show a progress bar at the bottom of the video that shows how long the video has been playing so far.


Is there such a feature ?


Syndiquer tout le site
