
Recherche avancée
Médias (1)
-
The pirate bay depuis la Belgique
1er avril 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Image
Autres articles (50)
-
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 (...) -
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir -
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 (...)
Sur d’autres sites (7451)
-
Silence h264 decoding warnings when called from OpenCV in Python
26 juillet 2018, par RaubtaubeI have the following script with which I read RTSP streams from withing Python3 using OpenCV.
cap = cv2.VideoCapture(ID)
ret, frame = cap.read()The streams are encoded using h264 and I get tons of warnings and error messages.
[h264 @ 0x7f74cc430c80] co located POCs unavailable
[h264 @ 0x7f74b4258160] error while decoding MB 38 2, bytestream -19I tried to silence them using a context manager for redirecting stdout and stderr but with no success :
class SilenceOutput(object):
def __enter__(self):
self._original_stdout = sys.stdout
self._original_stderr = sys.stderr
sys.stdout = None
sys.stderr = None
def __exit__(self, exc_type, exc_val, exc_tb):
sys.stdout = self._original_stdout
sys.stderr = self._original_stderr -
Anomalie #4402 (Fermé) : Liste de notices
12 février 2021, par cedric -je ferme ce ticket, car un ticket qui référence un wiki qui liste des patches, ça commence à ressembler à un jeu de pistes
+ depuis novembre 2019 ces notices ont été corrigée
+ maintenant proposer une PR pour chaque cas quand on tombe dessus ça sera beaucoup plus efficace -
The proper way to limit framerate when recording screen on macOS
5 juillet 2024, par jsxmacOS 14.5, FFmpeg 7.0.1. To record the screen, if I use the code from Wiki, that is,


ffmpeg -f avfoundation -i 1 output.mp4



the frame rate seems to be so high that when I press
q
to stop recording, the following message persists until my MacBook Pro starts to noise by its cooler : "[q] command received. Exiting."

My current solution is to add
-r
after-i
:

ffmpeg -f avfoundation -i 1 -r 24 output.mp4



But I heard that a more correct solution is to replace
-r
with-framerate
and to put it before instead of after-i
:



ffmpeg -f avfoundation -framerate 24 -i 1 output.mp4



Note that I used
-framerate
as an input option instead of-r 24
as an output option, so I'm telling avfoundation to record at 24fps instead of recording at the default fps and then forcing FFmpeg to drop or duplicate frames to give you the desired 24.



This doesn't work for me currently, and appears to be the same as I don't use
-r
at all.

And so, what is the proper way to fix the "too high framerate" issue when recording the screen on macOS ? Do we need
-r
or instead-framerate
, and where to put it, before or after-i
?

Just in case, here is the log of
ffmpeg -f avfoundation -i 1 output.mp4 -v verbose
:

https://github.com/jsx97/test/blob/main/ffmpeg.log