
Recherche avancée
Autres articles (46)
-
Submit enhancements and plugins
13 avril 2011If you have developed a new extension to add one or more useful features to MediaSPIP, let us know and its integration into the core MedisSPIP functionality will be considered.
You can use the development discussion list to request for help with creating a plugin. As MediaSPIP is based on SPIP - or you can use the SPIP discussion list SPIP-Zone. -
Personnaliser les catégories
21 juin 2013, parFormulaire de création d’une catégorie
Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
On peut modifier ce formulaire dans la partie :
Administration > Configuration des masques de formulaire.
Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...) -
Mise à disposition des fichiers
14 avril 2011, parPar défaut, lors de son initialisation, MediaSPIP ne permet pas aux visiteurs de télécharger les fichiers qu’ils soient originaux ou le résultat de leur transformation ou encodage. Il permet uniquement de les visualiser.
Cependant, il est possible et facile d’autoriser les visiteurs à avoir accès à ces documents et ce sous différentes formes.
Tout cela se passe dans la page de configuration du squelette. Il vous faut aller dans l’espace d’administration du canal, et choisir dans la navigation (...)
Sur d’autres sites (4199)
-
avformat/ffrtmpcrypt : Fix int-conversion warning
22 décembre 2023, par Frank Plowmanavformat/ffrtmpcrypt : Fix int-conversion warning
The gcrypt definition of `bn_new` used to use the return statement
on errors, with an AVERROR return value, regardless of the signature
of the function where the macro is used - it is called in
`dh_generate_key` and `ff_dh_init` which return pointers. As a result,
compiling with gcrypt and the ffrtmpcrypt protocol resulted in an
int-conversion warning. GCC 14 may upgrade these to errors [1].This patch fixes the problem by changing the macro to remove `AVERROR`
and instead set `bn` to null if the allocation fails. This is the
behaviour of all the other `bn_new` implementations and so the result is
already checked at all the callsites. AFAICT, this should be the only
change needed to get ffmpeg off Fedora's naughty list of projects with
warnings which may be upgraded to errors in GCC 14 [2].[1] : https://gcc.gnu.org/pipermail/gcc/2023-May/241264.html
[2] : https://www.mail-archive.com/devel@lists.fedoraproject.org/msg196024.htmlSigned-off-by : Frank Plowman <post@frankplowman.com>
Signed-off-by : Martin Storsjö <martin@martin.st> -
ffmpeg - converting one audio track of a multi-track mp4
30 décembre 2023, par Shaun.MI'm having a few mp4 with two audio tracks,
an english one in aac and a french one in dts.


Now I want to convert only the french dts to eac3 with a single ffmpeg command.


I use


ffmpeg -hide_banner -i input.mp4 ^
 -map_metadata -1 ^
 -map 0:0 -c:v copy ^
 -map 0:1 -c:a copy ^
 -map 0:2 -c:a eac3 -b:a 1536k ^
 -metadata:s:a:0 language=eng ^
 -metadata:s:a:0 title="Stereo" ^
 -metadata:s:a:1 language=fra ^
 -metadata:s:a:1 title="Stereo" ^
output.mp4



This works quite nice, but it converts both audio tracks to eac3, instead of leaving the first one untouched ...
What's wrong in the command ?


(ffmpeg version 2023-12-23-git-f5f414d9c4-full_build-www.gyan.dev under Windows 10)


-
FFmpeg Could not write header for output file #0 (incorrect codec parameters ?) : Invalid data found when processing input [closed]
29 décembre 2023, par randompersonheheI'm having trouble using FFmpeg to host an RTSP server for continuous video streaming. The command I'm using is :




ffmpeg -report -v verbose -re -stream_loop -1 -i store-aisle-detection.mp4 -c copy -f rtsp rtsp ://localhost:8888/mystream




Log :


ffmpeg started on 2023-12-29 at 15:35:47
Report written to "ffmpeg-20231229-153547.log"
Log level: 48
ffmpeg version 4.4.2-0ubuntu0.22.04.1 Copyright (c) 2000-2021 the FFmpeg developers
 built with gcc 11 (Ubuntu 11.2.0-19ubuntu1)
 configuration: --prefix=/usr --extra-version=0ubuntu0.22.04.1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --enable-pocketsphinx --enable-librsvg --enable-libmfx --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared
 libavutil 56. 70.100 / 56. 70.100
 libavcodec 58.134.100 / 58.134.100
 libavformat 58. 76.100 / 58. 76.100
 libavdevice 58. 13.100 / 58. 13.100
 libavfilter 7.110.100 / 7.110.100
 libswscale 5. 9.100 / 5. 9.100
 libswresample 3. 9.100 / 3. 9.100
 libpostproc 55. 9.100 / 55. 9.100
[h264 @ 0x560863a19240] Reinit context to 720x416, pix_fmt: yuv420p
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'store-aisle-detection.mp4':
 Metadata:
 major_brand : mp42
 minor_version : 0
 compatible_brands: mp42mp41
 creation_time : 2018-07-18T23:51:37.000000Z
 Duration: 00:01:05.49, start: 0.000000, bitrate: 1125 kb/s
 Stream #0:0(eng): Video: h264 (Main), 1 reference frame (avc1 / 0x31637661), yuv420p(tv, smpte170m, left), 720x404 (720x416), 1089 kb/s, 59.94 fps, 59.94 tbr, 60k tbn, 119.88 tbc (default)
 Metadata:
 creation_time : 2018-07-18T23:51:37.000000Z
 handler_name : ?Mainconcept Video Media Handler
 vendor_id : [0][0][0][0]
 encoder : AVC Coding
 Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 30 kb/s (default)
 Metadata:
 creation_time : 2018-07-18T23:51:37.000000Z
 handler_name : #Mainconcept MP4 Sound Media Handler
 vendor_id : [0][0][0][0]
[tcp @ 0x560863b71e80] Starting connection attempt to 127.0.0.1 port 8888
[tcp @ 0x560863b71e80] Successfully connected to 127.0.0.1 port 8888
Could not write header for output file #0 (incorrect codec parameters ?): Invalid data found when processing input
Error initializing output stream 0:1 -- 
Stream mapping:
 Stream #0:0 -> #0:0 (copy)
 Stream #0:1 -> #0:1 (copy)
 Last message repeated 1 times
[AVIOContext @ 0x560863a20300] Statistics: 135494 bytes read, 0 seeks





Can anyone help me identify and fix the problem with this command ? I want to loop the video infinitely on the RTSP server. I've tried variations with different formats (e.g., mp4 and ts), but the issue persists.


Any insights into resolving this error would be greatly appreciated.