
Recherche avancée
Médias (29)
-
#7 Ambience
16 octobre 2011, par
Mis à jour : Juin 2015
Langue : English
Type : Audio
-
#6 Teaser Music
16 octobre 2011, par
Mis à jour : Février 2013
Langue : English
Type : Audio
-
#5 End Title
16 octobre 2011, par
Mis à jour : Février 2013
Langue : English
Type : Audio
-
#3 The Safest Place
16 octobre 2011, par
Mis à jour : Février 2013
Langue : English
Type : Audio
-
#4 Emo Creates
15 octobre 2011, par
Mis à jour : Février 2013
Langue : English
Type : Audio
-
#2 Typewriter Dance
15 octobre 2011, par
Mis à jour : Février 2013
Langue : English
Type : Audio
Autres articles (111)
-
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...) -
Support audio et vidéo HTML5
10 avril 2011MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...) -
De l’upload à la vidéo finale [version standalone]
31 janvier 2010, parLe chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
Upload et récupération d’informations de la vidéo source
Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)
Sur d’autres sites (10508)
-
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



-
How can I set a Clean Aperture on a QuickTime file in ffmpeg ? [closed]
5 novembre 2024, par 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 ?


-
Can I record a video without using UIImagePickerController ?
24 mai 2016, par SUKIYAKICan I record a video without using UIImagePickerController ?
Of course without needing to jailbreak or anything else that would cause the App Store to reject the app.I think there is a way to access video device not using UIImagePickerController because these camera applications can record video and work on iPhone 2G/3G which utilizes ffmpeg :
I pick this code up by googling.
AVFormatParameters formatParams;
AVInputFormat *iformat;
formatParams.device = "/dev/video0";
formatParams.channel = 0;
formatParams.standard = "ntsc";
formatParams.width = 640;
formatParams.height = 480;
formatParams.frame_rate = 29;
formatParams.frame_rate_base = 1;
filename = "";
iformat = av_find_input_format("video4linux");
av_open_input_file(&ffmpegFormatContext,
filename, iformat, 0, &formatParams);This code tell me how to open camera device, but I don’t know device path of iPhone.
How do iVideoCamera and iVidCam record video ?