
Recherche avancée
Autres articles (59)
-
L’agrémenter visuellement
10 avril 2011MediaSPIP est basé sur un système de thèmes et de squelettes. Les squelettes définissent le placement des informations dans la page, définissant un usage spécifique de la plateforme, et les thèmes l’habillage graphique général.
Chacun peut proposer un nouveau thème graphique ou un squelette et le mettre à disposition de la communauté. -
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 (...) -
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
Sur d’autres sites (10971)
-
How to change frame rate of live stream using FFmpeg
4 décembre 2012, par chivI have created a streaming application, which takes video data from live source. Is there any transcoding tool which will receive stream from my streaming application and changes frame rate by transcoding the stream and re stream on another location ?
currently I'm Struggling with FFmpeg code to use in Visual Studio 2010. And I wanted to integrate FFmpeg code in my application.
Using FFmpeg.exe I'm able to transcode static files.I wont get any proper example how to transcode/change frame rate of live stream using FFmpeg. I tried,following command to re-stream on another IP.
ffmpeg -re -i "rtp://my_ip:1234" -r 60 -f rtp "trp://my_ip:4321"
-
lavc/vvc : Fix slice map construction for small subpics
22 février, par Frank Plowmanlavc/vvc : Fix slice map construction for small subpics
In the case pps_subpic_less_than_one_tile_slice is called, the
subpicture is smaller than the tile and so there are multiple
subpictures in the tile. Of course, then, not all the
subpictures can start in the top-left corner as the code before the
patch does. Patch fixes this, so each subpicture starts at the
signalled location as is specified in section 6.5.1 of H.266(V3).Signed-off-by : Frank Plowman <post@frankplowman.com>
-
Why is ffmpeg output video contrast / brightness too bright ?
24 février 2024, par danday74I have a .mov file which I run through
ffmpeg
to create HLS segments / chunks. However, when I playback the HLS video it is too bright.

For a sanity check, I ran the same .mov video file through the FlowPlayer processing pipeline and the results were the same, the output video is too bright !


I have a number of videos. Most do not have this problem but some (and only some) of the .mov files exhibit this issue.


A broken video stream reports (see below for full output) :


Stream #0:0[0x1](und): Video: hevc (Main 10) (hvc1 / 0x31637668), yuv420p10le(tv, bt2020nc/bt2020/arib-std-b67), 1920x1080, 8507 kb/s, 29.98 fps, 29.97 tbr, 600 tbn (default)



A working video stream reports (see below for full output) :


Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 3840x2160, 45457 kb/s, 29.99 fps, 29.97 tbr, 600 tbn (default)



Is this something to do with
hevc v h264
(whatever they mean) ?

Incidentally, I am using the native HTML5 video player in conjunction with hls.js to playback the videos.


How do I fix this ?


Here is my
ffmpeg
command :

ffmpeg -i "rgb.mov" \
 -v warning -preset ultrafast -g 59.96 -sc_threshold 0 \
 -map 0:0 -map 0:0 \
 -s:v:0 1920x1080 -c:v:0 libx264 -b:v:0 4521k \
 -s:v:1 1920x1080 -c:v:1 libx264 -b:v:1 7347k \
 -var_stream_map "v:0 v:1" \
 -master_pl_name master.m3u8 -f hls \
 -hls_time 6 -hls_list_size 0 -hls_playlist_type vod \
 -hls_segment_filename "hls/v%v/chunk%d.ts" "hls/v%v/index.m3u8"



And here are some screenshots showing the original video in comparison to the output video.


ORIGINAL :




OUTPUT :




For the problem video
ffmpeg -i "rgb.mov" -hide_banner
gives :

Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'rgb.mov':
 Metadata:
 major_brand : qt
 minor_version : 0
 compatible_brands: qt
 creation_time : 2021-08-03T11:23:40.000000Z
 com.apple.quicktime.location.accuracy.horizontal: 3.594173
 com.apple.quicktime.location.ISO6709: +51.5483+000.1628+000.459/
 com.apple.quicktime.make: Apple
 com.apple.quicktime.model: iPhone 12 Pro
 com.apple.quicktime.software: 14.7.1
 com.apple.quicktime.creationdate: 2021-08-03T12:23:40+0100
 Duration: 00:00:54.54, start: 0.000000, bitrate: 8730 kb/s
 Stream #0:0[0x1](und): Video: hevc (Main 10) (hvc1 / 0x31637668), yuv420p10le(tv, bt2020nc/bt2020/arib-std-b67), 1920x1080, 8507 kb/s, 29.98 fps, 29.97 tbr, 600 tbn (default)
 Metadata:
 creation_time : 2021-08-03T11:23:40.000000Z
 handler_name : Core Media Video
 vendor_id : [0][0][0][0]
 encoder : HEVC
 Side data:
 DOVI configuration record: version: 1.0, profile: 8, level: 4, rpu flag: 1, el flag: 0, bl flag: 1, compatibility id: 4
 Stream #0:1[0x2](und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 172 kb/s (default)
 Metadata:
 creation_time : 2021-08-03T11:23:40.000000Z
 handler_name : Core Media Audio
 vendor_id : [0][0][0][0]
 Stream #0:2[0x3](und): Data: none (mebx / 0x7862656D), 0 kb/s (default)
 Metadata:
 creation_time : 2021-08-03T11:23:40.000000Z
 handler_name : Core Media Metadata
 Stream #0:3[0x4](und): Data: none (mebx / 0x7862656D), 0 kb/s (default)
 Metadata:
 creation_time : 2021-08-03T11:23:40.000000Z
 handler_name : Core Media Metadata
 Stream #0:4[0x5](und): Data: none (mebx / 0x7862656D), 34 kb/s (default)
 Metadata:
 creation_time : 2021-08-03T11:23:40.000000Z
 handler_name : Core Media Metadata
At least one output file must be specified



For a working video
ffmpeg -i "rgb.mov" -hide_banner
gives :

Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'rgb.mov':
 Metadata:
 major_brand : qt
 minor_version : 0
 compatible_brands: qt
 creation_time : 2021-12-01T10:53:47.000000Z
 com.apple.quicktime.location.accuracy.horizontal: 4.785777
 com.apple.quicktime.location.ISO6709: +51.5485+000.1627+012.533/
 com.apple.quicktime.make: Apple
 com.apple.quicktime.model: iPhone 12 Pro
 com.apple.quicktime.software: 14.8.1
 com.apple.quicktime.creationdate: 2021-12-01T10:53:47+0000
 Duration: 00:00:36.35, start: 0.000000, bitrate: 45692 kb/s
 Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 3840x2160, 45457 kb/s, 29.99 fps, 29.97 tbr, 600 tbn (default)
 Metadata:
 creation_time : 2021-12-01T10:53:47.000000Z
 handler_name : Core Media Video
 vendor_id : [0][0][0][0]
 encoder : H.264
 Stream #0:1[0x2](und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 188 kb/s (default)
 Metadata:
 creation_time : 2021-12-01T10:53:47.000000Z
 handler_name : Core Media Audio
 vendor_id : [0][0][0][0]
 Stream #0:2[0x3](und): Data: none (mebx / 0x7862656D), 0 kb/s (default)
 Metadata:
 creation_time : 2021-12-01T10:53:47.000000Z
 handler_name : Core Media Metadata
 Stream #0:3[0x4](und): Data: none (mebx / 0x7862656D), 0 kb/s (default)
 Metadata:
 creation_time : 2021-12-01T10:53:47.000000Z
 handler_name : Core Media Metadata
 Stream #0:4[0x5](und): Data: none (mebx / 0x7862656D), 34 kb/s (default)
 Metadata:
 creation_time : 2021-12-01T10:53:47.000000Z
 handler_name : Core Media Metadata
At least one output file must be specified