
Recherche avancée
Autres articles (65)
-
Taille des images et des logos définissables
9 février 2011, parDans beaucoup d’endroits du site, logos et images sont redimensionnées pour correspondre aux emplacements définis par les thèmes. L’ensemble des ces tailles pouvant changer d’un thème à un autre peuvent être définies directement dans le thème et éviter ainsi à l’utilisateur de devoir les configurer manuellement après avoir changé l’apparence de son site.
Ces tailles d’images sont également disponibles dans la configuration spécifique de MediaSPIP Core. La taille maximale du logo du site en pixels, on permet (...) -
Configuration spécifique d’Apache
4 février 2011, parModules spécifiques
Pour la configuration d’Apache, il est conseillé d’activer certains modules non spécifiques à MediaSPIP, mais permettant d’améliorer les performances : mod_deflate et mod_headers pour compresser automatiquement via Apache les pages. Cf ce tutoriel ; mode_expires pour gérer correctement l’expiration des hits. Cf ce tutoriel ;
Il est également conseillé d’ajouter la prise en charge par apache du mime-type pour les fichiers WebM comme indiqué dans ce tutoriel.
Création d’un (...) -
Encodage et transformation en formats lisibles sur Internet
10 avril 2011MediaSPIP transforme et ré-encode les documents mis en ligne afin de les rendre lisibles sur Internet et automatiquement utilisables sans intervention du créateur de contenu.
Les vidéos sont automatiquement encodées dans les formats supportés par HTML5 : MP4, Ogv et WebM. La version "MP4" est également utilisée pour le lecteur flash de secours nécessaire aux anciens navigateurs.
Les documents audios sont également ré-encodés dans les deux formats utilisables par HTML5 :MP3 et Ogg. La version "MP3" (...)
Sur d’autres sites (4470)
-
FFmpeg trying to concat two like videos but the timing is off
9 avril 2022, par video487y43I am trying to concat two videos together using FFMPEG, but the output of the second video plays slow with no audio, but not only that, the time elapsed counter in the windows player counts slower as well. When I play it in VLC the timing is right but the audio is still missing.


For a better explanation of this effect please watch this video. Notice how slow the counter is




https://youtube.com/shorts/k6QD_oqTRyE?feature=share




I know the videos have to be the same type and they are both 30 fps, mp4, same size, same tbn. Here is the ffprobe results. My goal is to make compilation videos using ffmpeg since it can combine videos very fast without re-rendering them. I get the videos from tiktok. Please let me know if I can clarify this anymore. Thanks


Video 1


>Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, smpte170m/bt470bg/smpte170m, progressive), 1024x576 [SAR 1:1 DAR 16:9], 622 kb/s, 30 fps, 30 tbr, 15360 tbn (default)



Video 2


>Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 1024x576 [SAR 1:1 DAR 16:9], 760 kb/s, 30 fps, 30 tbr, 15360 tbn (default)



Output video


>Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 1024x576 [SAR 1:1 DAR 16:9], 655 kb/s, 29.92 fps, 30 tbr, 15360 tbn (default)



And here is the code during the concat process sorry for the weird format


libavutil 57. 24.101 / 57. 24.101
libavcodec 59. 25.100 / 59. 25.100
libavformat 59. 20.101 / 59. 20.101
libavdevice 59. 6.100 / 59. 6.100
libavfilter 8. 29.100 / 8. 29.100
libswscale 6. 6.100 / 6. 6.100
libswresample 4. 6.100 / 4. 6.100
libpostproc 56. 5.100 / 56. 5.100
[mov,mp4,m4a,3gp,3g2,mj2 @ 000001e74b5668c0] Auto-inserting h264_mp4toannexb bitstream filter
Input #0, concat, from 'mylist.txt':
 Duration: N/A, start: 0.000000, bitrate: 792 kb/s
 Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 1024x576 [SAR 1:1 DAR 16:9], 760 kb/s, 30 fps, 30 tbr, 15360 tbn
 Metadata:
 handler_name : VideoHandler
 vendor_id : [0][0][0][0]
 Stream #0:1(und): Audio: aac (HE-AACv2) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 32 kb/s
Metadata:
 handler_name : SoundHandler
 vendor_id : [0][0][0][0]
Output #0, mp4, to 'output.mp4':
 Metadata:
 encoder : Lavf59.20.101
 Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 1024x576 [SAR 1:1 DAR 16:9], q=2-31, 760 kb/s, 30 fps, 30 tbr, 15360 tbn
 Metadata:
 handler_name : VideoHandler
 vendor_id : [0][0][0][0]
 Stream #0:1(und): Audio: aac (HE-AACv2) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 32 kb/s
 Metadata:
 handler_name : SoundHandler
 vendor_id : [0][0][0][0]



Stream mapping:
 Stream #0:0 -> #0:0 (copy)
 Stream #0:1 -> #0:1 (copy)
Press [q] to stop, [?] for help
[mov,mp4,m4a,3gp,3g2,mj2 @ 000001e74b579400] Auto-inserting h264_mp4toannexb bitstream filter

frame= 1737 fps=0.0 q=-1.0 Lsize= 5442kB time=00:00:58.14 bitrate= 766.8kbits/s speed=1.01e+03x
video:4647kB audio:736kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 1.084181%



-
VP8 Documentation and Test Vector Contributions
14 octobre 2010, par noreply@blogger.com (John Luther)Janne Salonen of the WebM team in Oulu, Finland (formerly On2 Finland) has added a tabular description of the VP8 syntax to the VP8 Bitstream Guide. The new annex provides a concise reference of the elements in the bitstream and we hope will make implementing and testing VP8 decoders easier. The updated document and source can be downloaded from our documentation page.
We’re working on more improvements to the bitstream guide and invite other community members to help. As with the VP8 code, we gladly give attribution credit to documentation contributors and have added an AUTHORS file to the bitstream-guide Git repository.
New VP8 Test Vectors
The Oulu team has also produced some new VP8 test vectors. We analyzed a large set of WebM videos and produced two important corner use cases. The first produces the worst-case memory bandwidth (i.e., lots of global motion, all fractional motion vectors). The second produces the worst-case boolean decoder bin rate over dozens of consecutive frames. These vectors have been added to the VP8 test repository. Our team will consider other corner cases in the next batch of streams we add to the repository.
Aki Kuusela is Hantro Embedded Engineering Manager at Google.
-
lavfi/qsv : use QSVVPPContext as base context in vf_vpp_qsv/vf_overlay_qsv
9 janvier 2023, par Haihao Xianglavfi/qsv : use QSVVPPContext as base context in vf_vpp_qsv/vf_overlay_qsv
The same members between QSVVPPContext and VPPContext are removed from
VPPContext, and async_depth is moved from QSVVPPParam to QSVVPPContext
so that all QSV filters using QSVVPPContext may support async depth.In addition, we may use QSVVPPContext as base context in other QSV
filters in the future so that we may re-use functions defined in
qsvvpp.c for other QSV filters.This commit shouldn't change the functionality of vpp_qsv / overlay_qsv.
Signed-off-by : Haihao Xiang <haihao.xiang@intel.com>