
Recherche avancée
Autres articles (35)
-
La file d’attente de SPIPmotion
28 novembre 2010, parUne file d’attente stockée dans la base de donnée
Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...) -
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 (...) -
Contribute to documentation
13 avril 2011Documentation is vital to the development of improved technical capabilities.
MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
To contribute, register to the project users’ mailing (...)
Sur d’autres sites (5055)
-
python3 openCV VideoCapture only black image (Raspbian Stretch)
21 juin 2018, par PrimuSI have a little python function that analyzes a video, chunks it into one image per second and gives me the most dominant color for that image. (Code can be found here : https://github.com/primus852/python-movie-barcode)
This works great on my Windows testing environment. However, on my Rasbian Stretch Raspberry Pi Setup it only produces a black image, as the source seems to be black.
I compiled OpenCV (3.4.1) myself with this great article : https://www.pyimagesearch.com/2017/09/04/raspbian-stretch-install-opencv-3-python-on-your-raspberry-pi/, and it worked perfectly fine. I am using
python3
and avirtualenv
.I tried adding the ffmpeg package :
apt install ffmpeg
, to no avail.2 ideas
- I compiled the openCV source without support for mkv/mp4/similar ? If so, how would I check that and can I just "re-compile" the whole package ?
- I am missing codecs, where would I be able to check that ?
The crucial code (I think) is this :
cap = cv2.VideoCapture(full_path)
are there other options that do not break the majority of my code ? I read aboutskvideo.io
fromscikit-video
but that does not seem to work with my code...I am new to python, any hint is appreciated
// EDIT, I think it is not a duplicate because I pass the I get no error that the capture cannot be opened and :
OpenCV FFMPEG support :
python -c "import cv2; print(cv2.getBuildInformation())" | grep -i ffmpeg
- returns :
FFMPEG: YES
- returns :
FFMPEG Codec :
ffmpeg -codecs | grep -i avc
(file is using AVC)- returns :
DEV.LS h264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (decoders: h264 h264_mmal h264_vdpau ) (encoders: libx264 libx264rgb h264_omx h264_vaapi )
- returns :
File PATH
It exists and the path is correct...
Any other ideas ? Could it possibly the
virtualenv
?//EDIT2
Tried with an AVI file
works...
-
Unable to find a suitable output format for 'pipe :' pipe: : Invalid argument
22 août 2017, par MahiWhen I run this command :
raspivid -n -vf -hf -t 0 -w 960 -h 540 -fps 25 -b 500000 -o - |
ffmpeg -i - -vcodec copy -an -metadata title="Streaming from raspberry pi camera" \
-f flv $RTMP_URL/$STREAM_KEYit returns :
[NULL @ 0x3414410] Unable to find a suitable output format for 'pipe:'
pipe:: Invalid argumentHow should I tweak my command line ?
-
Specifying input duration of .aac with ffmpeg
28 septembre 2020, par JademaloI had an error with an mp4 recording, and after recovering the video and audio streams I've still got an issue. The aac audio file is 160kb/s CBR. However, ffmpeg returns this when trying to work with it ;


[aac @ 000001187e6944c0] Estimating duration from bitrate, this may be inaccurate
Input #0, aac, from 'result.aac':
 Duration: 00:38:41.01, bitrate: 174 kb/s
 Stream #0:0: Audio: aac (LC), 44100 Hz, stereo, fltp, 174 kb/s



That duration and bitrate is totally wrong. It should be 42 minutes long, and it definitely has a bitrate of 160 kb/s.


This results in the audio being very inconsistently timed, as well as having all sorts of other issues. It's very weird.


Is there any way I can specify that the input is 160 cbr to try and wrangle it back into a usable file ?