
Advanced search
Medias (91)
-
Valkaama DVD Cover Outside
4 October 2011, by
Updated: October 2011
Language: English
Type: Picture
-
Valkaama DVD Label
4 October 2011, by
Updated: February 2013
Language: English
Type: Picture
-
Valkaama DVD Cover Inside
4 October 2011, by
Updated: October 2011
Language: English
Type: Picture
-
1,000,000
27 September 2011, by
Updated: September 2011
Language: English
Type: Audio
-
Demon Seed
26 September 2011, by
Updated: September 2011
Language: English
Type: Audio
-
The Four of Us are Dying
26 September 2011, by
Updated: September 2011
Language: English
Type: Audio
Other articles (18)
-
La sauvegarde automatique de canaux SPIP
1 April 2010, byDans le cadre de la mise en place d’une plateforme ouverte, il est important pour les hébergeurs de pouvoir disposer de sauvegardes assez régulières pour parer à tout problème éventuel.
Pour réaliser cette tâche on se base sur deux plugins SPIP : Saveauto qui permet une sauvegarde régulière de la base de donnée sous la forme d’un dump mysql (utilisable dans phpmyadmin) mes_fichiers_2 qui permet de réaliser une archive au format zip des données importantes du site (les documents, les éléments (...) -
D’autres logiciels intéressants
12 April 2011, byOn ne revendique pas d’être les seuls à faire ce que l’on fait ... et on ne revendique surtout pas d’être les meilleurs non plus ... Ce que l’on fait, on essaie juste de le faire bien, et de mieux en mieux...
La liste suivante correspond à des logiciels qui tendent peu ou prou à faire comme MediaSPIP ou que MediaSPIP tente peu ou prou à faire pareil, peu importe ...
On ne les connais pas, on ne les a pas essayé, mais vous pouvez peut être y jeter un coup d’oeil.
Videopress
Site Internet : (...) -
Encoding and processing into web-friendly formats
13 April 2011, byMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...)
On other websites (4541)
-
How to change MPEG2-ts without encoding?
27 September 2012, by BdfyI have many ts file for apple streaming ( MPEG2-TS format ). Can I change, for example PTS/PCR params for this files, using ffmpeg ?
-
Why is ffmpeg output video contrast / brightness too bright?
24 February 2024, by 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



-
How can I set a Clean Aperture on a QuickTime file in ffmpeg? [closed]
5 November 2024, by blackirishmanI am using ffmpeg to convert files to QuickTime containers. I understand that certain QuickTime files requires clap atoms, ie "This is a mandatory extension for all uncompressed Y´CbCr data formats."




Is there a way to specify a clap atom when using ffmpeg to output a QuickTime file? Otherwise would there be harm in adding a clap atom at the end of the file assuming that I updated any file length field? Lastly, assuming that there is not doubt as to the proper viewable/usable pixel dimensions of my file, is a clap even necessary?