Recherche avancée
Autres articles (35)
-
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 (...) -
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir -
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP 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 (...)
Sur d’autres sites (6469)
-
I need to implement video compression for files that exceed 5 MB in size
27 septembre 2024, par KAVYA PI need to implement video compression for files that exceed 5 MB in size. I have tried several packages for this purpose, but they either do not work as expected or have significant security vulnerabilities. It's crucial for me to find a reliable and secure solution for compressing videos that meet this file size requirement. If you have any recommendations for libraries or tools that effectively handle video compression without compromising security, please let me know.


const handleFileChange = async (
 event: React.ChangeEvent<htmlinputelement>
 ) => {
 const file = event.target.files?.[0];
 if (file) {
 const isImage = file.type.startsWith('image/');
 const MAX_FILE_SIZE = isImage ? 2 * 1024 * 1024 : 5 * 1024 * 1024; // 2 MB for images, 5 MB for videos

 if (file.size > MAX_FILE_SIZE) {
 if (isImage) {
 alert('Image file size exceeds 2 MB. Compressing the file...');
 try {
 const compressedFile = await imageCompression(file, {
 maxSizeMB: 2,
 maxWidthOrHeight: 1920,
 useWebWorker: true,
 });
 onSelectFile({
 ...event,
 target: {
 ...event.target,
 files: [compressedFile] as unknown as FileList,
 },
 });
 } catch (error) {
 console.error('Error compressing the image:', error);
 }
 } else {
 alert('Video file size exceeds 5 MB. Please choose a smaller video.');
 }
 } else {
 onSelectFile(event); // Proceed with the file selection
 }
 }
 };
</htmlinputelement>

-
h264 : eliminate ff_h264_set_parameter_from_sps()
6 avril 2015, par Anton Khirnovh264 : eliminate ff_h264_set_parameter_from_sps()
That function currently does two things — reinitializing the DSP
contexts and setting low_delay based on the SPS values.The former more appropriately belongs in h264_slice_header_init(), while
the latter only really makes sense in decode_slice_header().The third call to ff_h264_set_parameter_from_sps(), done immediately
after parsing a new SPS, appears to serve no useful purpose, so it is
just dropped.Also, drop now unneeded H264Context.cur_chroma_format_idc.
-
Revert "lavfi : always check av_expr_parse_and_eval() return value"
2 mai 2015, par Anton Khirnov
Syndiquer tout le site
