
Recherche avancée
Médias (2)
-
SPIP - plugins - embed code - Exemple
2 septembre 2013, par
Mis à jour : Septembre 2013
Langue : français
Type : Image
-
Publier une image simplement
13 avril 2011, par ,
Mis à jour : Février 2012
Langue : français
Type : Video
Autres articles (111)
-
Ajouter des informations spécifiques aux utilisateurs et autres modifications de comportement liées aux auteurs
12 avril 2011, parLa manière la plus simple d’ajouter des informations aux auteurs est d’installer le plugin Inscription3. Il permet également de modifier certains comportements liés aux utilisateurs (référez-vous à sa documentation pour plus d’informations).
Il est également possible d’ajouter des champs aux auteurs en installant les plugins champs extras 2 et Interface pour champs extras. -
Emballe médias : à quoi cela sert ?
4 février 2011, parCe plugin vise à gérer des sites de mise en ligne de documents de tous types.
Il crée des "médias", à savoir : un "média" est un article au sens SPIP créé automatiquement lors du téléversement d’un document qu’il soit audio, vidéo, image ou textuel ; un seul document ne peut être lié à un article dit "média" ; -
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 (10248)
-
avfilter/af_amix : Fix double-free of AVFilterChannelLayouts on error
7 août 2020, par Andreas Rheinhardtavfilter/af_amix : Fix double-free of AVFilterChannelLayouts on error
The query_formats function of the amix filter tries to allocate a list
of channel layouts which are attached to more permanent objects
(an AVFilter's links) for storage afterwards on success. If attaching
a list to a link succeeds, the link becomes one of the common owners
of the list. Yet if a list has been successfully attached to links (or if
there were no links to attach it to in which case
ff_set_common_channel_layouts() already frees the list) and an error
happens lateron, the list was manually freed, which is wrong, because
the list has either already been freed or it is owned by its links in
which case these links' pointers to their list will become dangling and
there will be double-frees/uses-after-free when these links are cleaned
up automatically.This commit fixes this by removing the custom freeing code ; this is made
possible by using the list in ff_set_common_channel_layouts() directly
after its allocation (without anything that can fail in between).Notice that ff_set_common_channel_layouts() is buggy itself which can
lead to double-frees on error. This is not fixed in this commit.Reviewed-by : Nicolas George <george@nsup.org>
Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com> -
Cross origin issue in html 5 player
2 septembre 2020, par Danish Abdul HamidHey Guys i am new this field i encoded video through ffmpeg and for packaging used bento 4 for output single file in ts below the command i used


mp4hls —hls-version 4 —output-single-file —segment-duration 6 input_7000kb.mp4 input_5000kb.mp4 input_3500kb.mp4


and this is output file http://stream.simpaisa.com/output/master.m3u8 when i open this url in html 5 player its showing error "not allowed by Access-Control-Allow-Headers in preflight response" but in android and vlc this url is working. server already have .htaccess file for cross origin allow .


when i used this command mp4hls —hls-version 4 input_7000kb.mp4 input_5000kb.mp4 input_3500kb.mp4


the output file is http://stream.simpaisa.com/new/output/master.m3u8 and this file is working in html 5 player no cross origin issue


Please tell me whats the issue


this is .htaccess file configuration


Header set Access-Control-Allow-Origin "*"
Header set Access-Control-Allow-Credentials "true"
Header set Access-Control-Allow-Methods "GET,HEAD,OPTIONS,POST,PUT"
Header set Access-Control-Allow-Headers "Access-Control-Allow-Headers, Origin,Accept, X-Requested-With, Content-Type, Access-Control-Request-Method, Access-Control-Request-Headers"
RewriteEngine On


RewriteCond %REQUEST_FILENAME !-f
RewriteRule ^(.*)$ index.php [QSA,L]


-
FFMPEG with -vf yadif on progressive file produces incorrect 'Original Frame Rate' metadata double
28 septembre 2020, par hedgehog90I've got an ffmpeg command that I often use, I incorporate the yadif argument for content that may or may not be interlaced :


ffmpeg -i input.mkv -c copy -c:v hevc_nvenc -c:a:0 aac -b:a 192k -vf yadif=mode=1:deint=1 output.mkv


This means if input.mkv is an interlaced video, I get double the frame rate and the footage is deinterlaced, and if it's progressive it remains so and the frame rate doesn't change, exactly as I want it.


However, I've just noticed in Mediainfo that progressive videos processed by this command, it adds this mysterious "Original Frame Rate" tag (I assume it's just metadata)




It doesn't appear to affect playback in VLC or MPV, however it is recognized in MPV as 'framerate (Specified)'...


How do I prevent ffmpeg from generating this tag when using the yadif filter ?