
Recherche avancée
Médias (1)
-
Rennes Emotion Map 2010-11
19 octobre 2011, par
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (52)
-
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 translation
13 avril 2011You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
MediaSPIP is currently available in French and English (...) -
Initialisation de MediaSPIP (préconfiguration)
20 février 2010, parLors de l’installation de MediaSPIP, celui-ci est préconfiguré pour les usages les plus fréquents.
Cette préconfiguration est réalisée par un plugin activé par défaut et non désactivable appelé MediaSPIP Init.
Ce plugin sert à préconfigurer de manière correcte chaque instance de MediaSPIP. Il doit donc être placé dans le dossier plugins-dist/ du site ou de la ferme pour être installé par défaut avant de pouvoir utiliser le site.
Dans un premier temps il active ou désactive des options de SPIP qui ne le (...)
Sur d’autres sites (9044)
-
Fixing a corrupted .MP4 file. which might be a 3gp file
2 juin 2020, par Tendekai MuchenjeI have a file called input.MP4 and it is corrupted. It's from a CCTV camera. I tried everything,
ffmpeg
, VLC convert, no luck. However, I usedmediainfo
andexiftool
and extracted the following info. I am wondering if someone can figure out if I can use any of this info to fix it or convert it to a usable format. I have a copy of it here on my Google Drive


mediainfo
gave me this :


General
Complete name : input.MP4
Format : MPEG-4
Format profile : 3GPP Media Release 5
Codec ID : 3gp5 (3gp5/3gp4/avc1/mp42/isom)
File size : 5.77 MiB
IsTruncated : Yes




exiftool
gave me this :


ExifTool Version Number : 10.80
File Name : input.MP4
Directory : /home/tendi/Downloads
File Size : 5.8 MB
File Modification Date/Time : 2018:07:21 19:09:03-04:00
File Access Date/Time : 2018:07:21 19:30:48-04:00
File Inode Change Date/Time : 2018:07:21 19:30:48-04:00
File Permissions : rw-rw-r--
File Type : 3GP
File Type Extension : 3gp
MIME Type : video/3gpp
Major Brand : 3GPP Media (.3GP) Release 5
Minor Version : 0.0.0
Compatible Brands : 3gp5, 3gp4, avc1, mp42, isom
Movie Data Size : 5899106
Movie Data Offset : 44




Any suggestions ?


-
Unable to find a suitable output format while cutting video
22 juillet 2018, par Java AndroidI am using below command to cut video-
String complexCommand = new String[]{"-y", "-i", yourRealPath, "-ss", "" + startMs / 1000, "-t", "" + (endMs - startMs) / 1000, "-c", "copy", filePath};
I got below error -
"ffmpeg version n3.0.1 Copyright (c) 2000-2016 the FFmpeg developers\n
built with gcc 4.8 (GCC)\n configuration : —target-os=linux
—cross-prefix=/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/bin/arm-linux-androideabi-
—arch=arm —cpu=cortex-a8 —enable-runtime-cpudetect —sysroot=/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/sysroot
—enable-pic —enable-libx264 —enable-libass —enable-libfreetype —enable-libfribidi —enable-libmp3lame —enable-fontconfig —enable-pthreads —disable-debug —disable-ffserver —enable-version3 —enable-hardcoded-tables —disable-ffplay —disable-ffprobe —enable-gpl —enable-yasm —disable-doc —disable-shared —enable-static —pkg-config=/home/vagrant/SourceCode/ffmpeg-android/ffmpeg-pkg-config —prefix=/home/vagrant/SourceCode/ffmpeg-android/build/armeabi-v7a —extra-cflags=’-I/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/include
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-strict-overflow -fstack-protector-all’ —extra-ldflags=’-L/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/lib
-Wl,-z,relro -Wl,-z,now -pie’ —extra-libs=’-lpng -lexpat -lm’ —extra-cxxflags=\n libavutil 55. 17.103 / 55. 17.103\n libavcodec 57. 24.102 / 57. 24.102\n libavformat 57. 25.100 /
57. 25.100\n libavdevice 57. 0.101 / 57. 0.101\n libavfilter 6. 31.100 / 6. 31.100\n libswscale 4. 0.100 / 4. 0.100\n libswresample 2. 0.101 / 2. 0.101\n libpostproc 54. 0.100 /
54. 0.100\nInput #0, mov,mp4,m4a,3gp,3g2,mj2, from ’/storage/emulated/0/Download/file3gpp.3gpp’ :\n Metadata :\n
major_brand : 3gp4\n minor_version : 0\n
compatible_brands : isom3gp4\n creation_time : 2018-04-09
12:04:29\n com.android.version : 7.1.1\n Duration : 00:00:04.88,
start : 0.000000, bitrate : 1425 kb/s\n Stream #0:0(eng) : Audio : aac
(LC) (mp4a / 0x6134706D), 44100 Hz, mono, fltp, 96 kb/s (default)\n
Metadata :\n creation_time : 2018-04-09 12:04:29\n
handler_name : SoundHandle\n[NULL @ 0xf622a600] Unable to find a
suitable output format for
’/storage/emulated/0/Movies/cut_video.3gpp’\n/storage/emulated/0/Movies/cut_video.3gpp :
Invalid argument\n"Why am i getting this error and how can i resolve it ?
-
Ubuntu 16.04 + OpenCV + FFMPEG + CUDA don't open default camera
20 juillet 2018, par Newton Pasqualini FilhoI am trying to work with accelerated OpenCV using my own build of FFMPEG with CUDA support for GPU video processing using Python.
My application must support any kind of video devices, including USB and IP cameras.
I have a config file parsed with
ConfigParser
that loads the camera device path, as described in OpenCV documentation we can access usb camera by index number and for IP camera we use RTSP protocol so the path could be sometimes0
orrtsp://192.168.1.2/0
.To force the use of FFMPEG behind OpenCV I am trying to open the video capture stream like bellow :
video_capture = cv.VideoCapture()
stream_opened = video_capture.open(camera_path, cv.CAP_FFMPEG)The problem is when I try to open the default USB camera
camera_path = 0
thevideo_capture.open
method always returns false, but when it is a RTSP likecamera_path = "rtsp://192.168.1.2/1"
it open the video capture stream ok.When I let OpenCV decide what backend will be used it calls to GStreammer and it opens the capture stream like this :
video_capture = cv.VideoCapture(camera_path)
I suspect that FFMPEG does not have any support for capture video from a USB camera, does it ? Is there some missing feature to my ffmpeg build ?
ffmpeg version N-91487-g1809f1c Copyright (c) 2000-2018 the FFmpeg developers
built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.10) 20160609
configuration: --prefix=/usr --pkg-config-flags=--static --enable-cuda-sdk --enable-cuvid --enable-libnpp --extra-cflags=-I/usr/local/cuda/include/ --extra-ldflags=-L/usr/local/cuda/lib64/ --nvccflags='-gencode arch=compute_61,code=sm_61 -O2' --enable-gpl --enable-libass --enable-libfdk-aac --enable-libx264 --extra-libs=-lpthread --enable-libx265 --enable-nvenc --enable-nonfree
libavutil 56. 18.102 / 56. 18.102
libavcodec 58. 21.105 / 58. 21.105
libavformat 58. 17.101 / 58. 17.101
libavdevice 58. 4.101 / 58. 4.101
libavfilter 7. 26.100 / 7. 26.100
libswscale 5. 2.100 / 5. 2.100
libswresample 3. 2.100 / 3. 2.100
libpostproc 55. 2.100 / 55. 2.100
Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...