
Recherche avancée
Autres articles (38)
-
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs -
MediaSPIP Player : problèmes potentiels
22 février 2011, parLe lecteur ne fonctionne pas sur Internet Explorer
Sur Internet Explorer (8 et 7 au moins), le plugin utilise le lecteur Flash flowplayer pour lire vidéos et son. Si le lecteur ne semble pas fonctionner, cela peut venir de la configuration du mod_deflate d’Apache.
Si dans la configuration de ce module Apache vous avez une ligne qui ressemble à la suivante, essayez de la supprimer ou de la commenter pour voir si le lecteur fonctionne correctement : /** * GeSHi (C) 2004 - 2007 Nigel McNie, (...) -
Keeping control of your media in your hands
13 avril 2011, parThe vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)
Sur d’autres sites (6801)
-
no audio after mp3 + jpg with ffmpeg
31 octobre 2019, par YongJiang ZhangI have a mp3 file. I checked. It has audio. After run command
ffmpeg -i 31.mp3 -i cover.jpg -c:a copy -s 1280x720 -pix_fmt yuv420p 31.mp4
I got 31.mp4 but it has no audio.
I use macbook pro and ffmpeg version 4.1
-
Why mp4 can not shared on Facebook or Instagram on Android ?
8 janvier 2023, par JánosThis is the file : https://t44-post-cover.s3.eu-central-1.amazonaws.com/2e3s.mp4


When I download and try share, it fails. Why ? This is the parameters was rendered. Downloading and sharing works from iPhone to Facebook on Messenger or Instagram, but not from Android phone to Facebook on Messenger or Instagram.


What parameters
ffpmpeg
need to be able to sharemp4
from Android to Facebook / Instagram ?

await new Promise<void>((resolve, reject) => {
 ffmpeg()
 .setFfmpegPath(pathToFfmpeg)
 .input(`/tmp/input_${imgId}.gif`)
 .inputFormat('gif')
 .inputFPS(30)
 .input('anullsrc')
 .inputFormat('lavfi')
 .audioCodec('aac')
 .audioChannels(2)
 .audioFilters(['apad'])
 .videoCodec('libx264')
 .videoBitrate(1000)
 .videoFilters([
 'tpad=stop_mode=clone:stop_duration=2',
 'scale=trunc(iw/2)*2:trunc(ih/2)*2:flags=lanczos,split[s0][s1];[s0]palettegen[p];[s1][p]paletteuse',
 ])
 .fps(30)
 .duration(5)
 .format('mp4')
 .outputOptions([
 '-pix_fmt yuvj420p',
 '-profile:v baseline',
 '-level 3.0',
 '-crf 17',
 '-movflags +faststart',
 '-movflags frag_keyframe+empty_moov',
 ])
 .output(`/tmp/output_${imgId}.mp4`)
 .on('end', () => {
 console.log('MP4 video generated')
 resolve()
 })
 .on('error', (e) => {
 console.log(e)
 reject()
 })
 .run()
 })
</void>


-
truehd_core : Switch to in-place modifications
6 juillet 2019, par Andreas Rheinhardttruehd_core : Switch to in-place modifications
The truehd_core bitstream filter decreases the sizes of the
major_sync_info structure (if present), of the
substream_directory and of the substreams themselves. As a consequence,
there is enough space available in front of the actual substream data
for the new header, so that one only needs to modify the header in front
of the actual data (which apart from shrinking is left untouched) and
the packet's size and buffer pointer (after having made sure that the
packet is writable).This and switching to bsf_get_packet_ref also removed the need for
having separate packets for in- and output.Even if the input is not writable, there are noticable performance
improvements : The average of 10 iterations of processing a file with 262144
runs each (inlcuding about 20 skips per iteration) went down from 5669
to 4362 decicycles. If the input is writable, it goes down to 1363
decicycles.Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>