
Recherche avancée
Autres articles (11)
-
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 (...) -
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...) -
Contribute to a better visual interface
13 avril 2011MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.
Sur d’autres sites (2825)
-
Make new VDPAU easier to use by adding context to callback.
7 août 2013, par Reimar DöffingerMake new VDPAU easier to use by adding context to callback.
Using VDPAU correctly means checking for preemption
and possibly regenerating the context all the time.
With the current API there is no context or other
user-defined pointer and thus this in not possible
during decoding unless using some hack like global
variables.
The need to reinitialize both surfaces and even function
pointers makes handling preemption even more difficult.
This patch introduces a new render2 function that gets
both the AVCodecContext and AVFrame in addition,
in both the user can store additional opaque data.
This allows even advanced approaches like keeping a
"generation counter" for the surfaces so they can be
regenerated on the fly and efficiently.
In addition, the function has a return value that will
be passed through all the way instead of being silently
ignored as for the current render function.
Unfortunately the HWAccel API has no way of providing
API/ABI compatibility, so a currently disallowed
state (render pointer being NULL) is used to extend it.Signed-off-by : Reimar Döffinger <Reimar.Doeffinger@gmx.de>
-
ffmpeg.exe - Entry Point Not Found
8 février 2018, par Mikkel BachmannI know there’s a lot of "Entry point not found" posts ; But i find that they don’t fit on my problem.
When i try to run ffmpeg i get this error message :
but the catch is that i only get the message is i run ffmpeg from my server application or from the folder where the server application is located
e:\StreamServer2\
If i run from an other folder eg.e:\StreamServer2.BAK\
there are no problem.
the same goes for when i run the StreamServer located inStreamServer2.BAK
The
ffmpeg.exe
is a copy of the same file.I have tried to delete ffmpeg.exe and copy a new to the folder. As i assumed that it was ffmpeg.exe that was damaged when we moved the server to our new data center. but that did not make any difference.
I am running ffmpeg with thise parameters :
ffmpeg.exe -analyzeduration 0 -fpsprobesize 0 -rtsp_transport tcp -i rtsp://addrOnIpCam -g 52 -movflags frag_keyframe+empty_moov -b:v 64k -q 5 test.avi
and from server application :
ffmpeg.exe -analyzeduration 0 -fpsprobesize 0 -rtsp_transport tcp -i rtsp://addrOnIpCam -g 52 -movflags frag_keyframe+empty_moov -b:v 64k -q 5 -an -
-
hw_base_encode : Free pictures on close
15 octobre 2024, par David Rosca