
Recherche avancée
Autres articles (92)
-
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
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 (...) -
ANNEXE : Les plugins utilisés spécifiquement pour la ferme
5 mars 2010, parLe site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)
Sur d’autres sites (7483)
-
FFMPEG color key filter applied, output to a transparent HEVC mov file, speed is different
2 mars 2023, par Patrick VelliaI have an original recording that has the following ffprobe output :


Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'test.mp4':
 Metadata:
 major_brand : mp41
 minor_version : 538120216
 compatible_brands: mp41
 creation_time : 2023-02-28T19:06:41.000000Z
 firmware : H21.01.01.50.00
 Duration: 00:00:08.15, start: 0.000000, bitrate: 60160 kb/s
 Stream #0:0(eng): Video: hevc (Main) (hvc1 / 0x31637668), yuvj420p(pc, bt709), 3840x2160 [SAR 1:1 DAR 16:9], 59891 kb/s, 119.88 fps, 119.88 tbr, 120k tbn, 119.88 tbc (default)
 Metadata:
 creation_time : 2023-02-28T19:06:41.000000Z
 handler_name : GoPro H.265
 vendor_id : [0][0][0][0]
 encoder : GoPro H.265 encoder
 timecode : 19:05:32:105
 Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 189 kb/s (default)
 Metadata:
 creation_time : 2023-02-28T19:06:41.000000Z
 handler_name : GoPro AAC 
 vendor_id : [0][0][0][0]
 timecode : 19:05:32:105
 Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s (default)
 Metadata:
 creation_time : 2023-02-28T19:06:41.000000Z
 handler_name : GoPro TCD 
 timecode : 19:05:32:105
 Stream #0:3(eng): Data: bin_data (gpmd / 0x646D7067), 76 kb/s (default)
 Metadata:
 creation_time : 2023-02-28T19:06:41.000000Z
 handler_name : GoPro MET 
Unsupported codec with id 0 for input stream 2
Unsupported codec with id 100359 for input stream 3



This video is chroma keyed, so I ran the following command the key out the green and export it to a HEVC mov container (the Apple HEVC supports alpha channel via the videotoolbox codec) :


ffmpeg -i test.mp4 -vf colorkey=0x00b140:0.3:0.1 -vcodec hevc_videotoolbox -alpha_quality 0.5 -tag:v hvc1 output1.mov



which results in this ffprobe :


Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'output1.mov':
 Metadata:
 major_brand : qt 
 minor_version : 512
 compatible_brands: qt 
 encoder : Lavf58.76.100
 Duration: 00:00:08.15, start: 0.000000, bitrate: 366946 kb/s
 Stream #0:0(eng): Video: hevc (Main) (hvc1 / 0x31637668), yuv420p(tv, gbr/bt709/bt709, progressive), 3840x2160 [SAR 1:1 DAR 16:9], 367188 kb/s, 119.88 fps, 119.88 tbr, 120k tbn, 120k tbc (default)
 Metadata:
 handler_name : GoPro H.265
 vendor_id : FFMP
 encoder : Lavc58.134.100 hevc_videotoolbo
 timecode : 19:05:32:105
 Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 118 kb/s (default)
 Metadata:
 handler_name : GoPro AAC 
 vendor_id : [0][0][0][0]
 Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s
 Metadata:
 handler_name : GoPro H.265
 timecode : 19:05:32:105
Unsupported codec with id 0 for input stream 2



When the play the original video inside a web browser, it will play normally. As in, the video doesn't play in slo-mo but at "normal speed" which is what I actually want. User can slow it down and still have the frames necessary to keep the clarity when desired.


However, when I play the second video, it is unnaturally slow even at 2x the speed.


The only difference I can see above is that the export didn't include the second data stream (input 3).


This was recorded on a GoPro Hero 10. I am using FFMPEG 4.6.


Any help would be appreciated to fine tune the command.


-
Fintech Content Marketing : 10 Best Practices & Growth Strategies
24 juillet 2024, par Erin -
OCPA, FDBR and TDPSA – What you need to know about the US’s new privacy laws
22 juillet 2024, par Daniel Crough