
Recherche avancée
Autres articles (24)
-
La file d’attente de SPIPmotion
28 novembre 2010, parUne file d’attente stockée dans la base de donnée
Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...) -
Contribute to documentation
13 avril 2011Documentation is vital to the development of improved technical capabilities.
MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
To contribute, register to the project users’ mailing (...) -
Supporting all media types
13 avril 2011, parUnlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)
Sur d’autres sites (5425)
-
Transcode H264 to AV1
17 février 2024, par CrearWe have some roadside cameras deployed and due to the supply chain issue (also the cost) we installed 1080P@H264 encoder.


I know that AV1 is significantly more efficient than H264, but transcoding H264 to AV1 may result in quality loss.


My purpose is to reduce some space while minimizing the quality loss, is there a python or FFmpeg command that can do it ? My major concern is quality loss, but if I use the same bitrate, it won’t reduce the size.


We have years of data so we can’t really look into the videos one by one to determine the optimal bitrate, sometimes when the weather is extreme, the higher dynamic in the frames results in a bigger H264 file size. I don’t want to lose those details because it can help fine-tone the detection models.


-
Revision 94d700e763 : Refactor rd loop for inter modes This commit pulls the iterative motion search
28 mai 2013, par Jingning HanChanged Paths :
Modify /vp9/encoder/vp9_rdopt.c
Refactor rd loop for inter modesThis commit pulls the iterative motion search for compound inter-
inter out from handle_inter_mode_ as a separate function. Hence,
it is applicable to 4x4/4x8/8x4 level compound inter search to be
enabled later.Also edit the rd loop for 4x4 inter block sizes for cosmetic
purpose.Change-Id : Ibc71a11cbe5a26cd52faba01026cf8446cf4d2b4
-
Fastest seek speed and decoding with ffmpeg and x265 ProRes
17 mai 2018, par Christopher JarvisI’m trying to optimize seek speed with x265. No matter what encoding settings I try, ProRes still seeks more quickly/gracefully. This makes sense since it was built for editing, but I’m sure there’s got to be something I’m missing to better improve x265.
So far, -tune fastdecode, keyint=1, maxrate and -b (to remove B Frame calculations) yield the best results, but they’re still unsatisfactory. I’ve been pouring over the docs but there’s so much jargon I just don’t understand. Perhaps another codec like VP9 / WebM would be better for this purpose ?
From what I can tell, there’s no bottleneck with CPU, read speed or RAM... or GPU for that matter. Monitoring these processes show minimal drain. Is there just an amount of decoding in a highly compressed format like x265 that can’t be circumvented ?
Thank you in advance for your help.