
Recherche avancée
Médias (1)
-
Revolution of Open-source and film making towards open film making
6 octobre 2011, par
Mis à jour : Juillet 2013
Langue : English
Type : Texte
Autres articles (40)
-
Multilang : améliorer l’interface pour les blocs multilingues
18 février 2011, parMultilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela. -
(Dés)Activation de fonctionnalités (plugins)
18 février 2011, parPour gérer l’ajout et la suppression de fonctionnalités supplémentaires (ou plugins), MediaSPIP utilise à partir de la version 0.2 SVP.
SVP permet l’activation facile de plugins depuis l’espace de configuration de MediaSPIP.
Pour y accéder, il suffit de se rendre dans l’espace de configuration puis de se rendre sur la page "Gestion des plugins".
MediaSPIP est fourni par défaut avec l’ensemble des plugins dits "compatibles", ils ont été testés et intégrés afin de fonctionner parfaitement avec chaque (...) -
Le plugin : Podcasts.
14 juillet 2010, parLe problème du podcasting est à nouveau un problème révélateur de la normalisation des transports de données sur Internet.
Deux formats intéressants existent : Celui développé par Apple, très axé sur l’utilisation d’iTunes dont la SPEC est ici ; Le format "Media RSS Module" qui est plus "libre" notamment soutenu par Yahoo et le logiciel Miro ;
Types de fichiers supportés dans les flux
Le format d’Apple n’autorise que les formats suivants dans ses flux : .mp3 audio/mpeg .m4a audio/x-m4a .mp4 (...)
Sur d’autres sites (3666)
-
error when converting .flv to .mp4 using ffmpeg
14 août 2024, par JayceI converted the 1.flv file using the tool on https://convertio.co/ and still created a normal .mp4 file. However, when I use the python code, I get the error below.


import os 
import subprocess 
 
def convert_flv_to_mp4(input_file, output_file): 
 try: 
 subprocess.run(["ffmpeg", "-i", input_file, "-c:v", "libx264", "-c:a", "aac", "-preset", "medium", "-crf", "23", output_file], check=True)
 except subprocess.CalledProcessError as e: 
 print(f"error {input_file} to {output_file}: {e}") 
 
if __name__ == "__main__": 
 input_file = r"C:\Users\vann4\OneDrive\Desktop\flv\1.flv" 
 output_file = r"C:\Users\vann4\OneDrive\Desktop\flv\1.mp4" 
 convert_flv_to_mp4(input_file, output_file) 



[flv @ 0000016342270d80] Video codec (c) is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
[flv @ 0000016342270d80] If you want to help, upload a sample of this file to https://streams.videolan.org/upload/ and contact the ffmpeg-devel mailing list. (ffmpeg-devel@ffmpeg.org)
[flv @ 0000016342270d80] Could not find codec parameters for stream 1 (Video: none ([12][0][0][0] / 0x000C), none, 1150 kb/s): unknown codec
Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options
Input #0, flv, from 'C:\Users\vann4\OneDrive\Desktop\flv\1.flv':
 Metadata:
 start_time : 1723543887483
 fp_coderate : 1150000
 sdk_version : 16.8.1.2
 old_link_info : (push-rtmp-f5-sg01.tiktokcdn.com:stage:stream-2133275252817395781)n.vn-lts55c.7qmt_34825,n.my-93iclg.4epc_3521416 
 default_bitrate : 1700
 fp_vmode : 1
 max_bitrate : 2700
 fp_amode : 0
 push_protocol : rtmpq
 fp_dispatch_expr_tag:
 e_id : 0
 stream_id : push-rtmp-f5-sg01.tiktokcdn.com:stage:stream-2133275252817395781_uhd5b
 s_id : 8
 h_id : 4
 interval : 2
 publish_time_stamp: 1723543887
 encoder : Lavf58.45.100
 min_bitrate : 1000
 link_info : n.my-93iclg.4epc_3521416,n.my-93iclg.hebn_3413106,n.sg-awn1ns.n4qb_644528,n.sg-awn1ns.kq7p_4176740,n.sg-elmss9.00jt_909,n.sg-elmss9.d4b4_59676,n.vn-6tkh26.ntnt_2987,n.vn-6tkh26.vuv7_56190
 is_hardware_encode: 1
 model : iPhone XR
 hit_node_optimize: 0
 fp_nb : 0
 ab : 0
 p_id : 0
 os_version : 17.5.1
 platform : iOS
 qId : {"newbitrate_ios_bT":1,"ByteAudioAUUnsplit+new_session_api+with_aec_sw_true+framesize_10ms":true,"rc_bwe_ios":4,"ios_70742354_2":2,"not_rc_bwe_ios":1,"ios_fix_low_enc_bit_vpaas_4":4,"default_config_bugfix":1,"newbitrate_ios_resolution_no480p":1} 
 Duration: 00:02:26.09, start: 0.000000, bitrate: 958 kb/s
 Stream #0:0: Audio: aac (HE-AAC), 44100 Hz, stereo, fltp, 64 kb/s
 Stream #0:1: Video: none ([12][0][0][0] / 0x000C), none, 1150 kb/s, 25 fps, 25 tbr, 1k tbn
[vist#0:1/none @ 0000016343d38c00] Decoding requested, but no decoder found for: none
Error opening output file C:\Users\vann4\OneDrive\Desktop\flv\1.mp4.
Error opening output files: Invalid argument
error C:\Users\vann4\OneDrive\Desktop\flv\1.flv to C:\Users\vann4\OneDrive\Desktop\flv\1.mp4: Command '['ffmpeg', '-i', 'C:\\Users\\vann4\\OneDrive\\Desktop\\flv\\1.flv', '-c:v', 'libx264', '-c:a', 'aac', '-preset', 'medium', '-crf', '23', 'C:\\Users\\vann4\\OneDrive\\Desktop\\flv\\1.mp4']' returned non-zero exit status 4294967274.



I tried converting the .mp4 file to .avi and it's completely normal.


hope everyone can help me. Thanks for reading


-
ffmpeg crashes on crossfades between 3 clips if 2 clips coming from same input file [closed]
14 avril 2020, par ErikI observed that ffmpeg 4.2.2 (macOS) crashes in particular cases of crossfades between clips, if one clip comes from file
1.dv
, and two clips are cut out of file2.dv
, as shown below :


ffmpeg -f lavfi -i color=black:size=720x576:duration=11:rate=25 -i 1.dv -i 2.dv -filter_complex "\
 [1:v]trim=5:10,setpts=expr=PTS-STARTPTS,yadif,fade=alpha=1:d=2:st=3:type=out,setpts=expr=PTS-STARTPTS,fifo[s5];\
 [2:v]split=2[s7][s8];\
 [s7]trim=5:10,setpts=expr=PTS-STARTPTS,yadif,fade=alpha=1:d=2:type=in,fade=alpha=1:d=2:st=6:type=out,setpts=expr=PTS-STARTPTS+(3/TB),fifo[s15];\
 [s8]trim=12:17,setpts=expr=PTS-STARTPTS,yadif,fade=alpha=1:d=2:type=in,setpts=expr=PTS-STARTPTS+(6/TB),fifo[s22];\
 [0:v][s5]overlay=eof_action=repeat[s6];\
 [s6][s15]overlay=eof_action=repeat[s16];\
 [s16][s22]overlay=eof_action=repeat[s24];\
 [1:a]atrim=5:10,asetpts=expr=PTS-STARTPTS[s26];\
 [2:a]asplit=2[s27][s28];\
 [s27]atrim=5:10,asetpts=expr=PTS-STARTPTS[s30];\
 [s28]atrim=12:17,asetpts=expr=PTS-STARTPTS[s33];\
 [s26][s30]acrossfade=d=2[s31];\
 [s31][s33]acrossfade=d=2[s36]" \
 -map "[s24]" -map "[s36]" -ab 128k -acodec aac -crf 23 -movflags faststart -preset medium -tune film -vcodec libx264 -aspect 1024:576 out.mp4 -y




The order makes a difference : if the two clips from
2.dv
are used first and then the clip from1.dv
is appended, everything works fine. Also, if all clips are coming from different files.


ffmpeg 3.4.6 (ubuntu 18.04) shows no issues in any case.



A self-compiled ffmpeg version N-97322-gb1699f4 (commit 2020-04-13) works with short clips as above, but crashes if one of the two clips taken from
2.dv
is getting longer. In my tests 1500 frames (64 sec) is OK, 1700 (68 sec) leads to a segmentation fault. That is, if you replace in the command line above :


- 

[s7]trim=5:10...
->[s7]trim=0:68
and accordingly[s27]atrim=5:10...
->[s27]atrim=0:68







Interestingly, the length of the clip taken from
1.dv
does not play a role.


The ffmpeg output shows about 20 times :



frame= 0 fps=0.0 q=0.0 size= 0kB time=00:00:00.00 bitrate=N/A speed= 0x 




before it continues (seg fault case) :



frame= 4 fps=0.3 q=0.0 size= 0kB time=00:00:00.00 bitrate=N/A speed= 0x 
frame= 24 fps=1.6 q=0.0 size= 0kB time=00:00:00.00 bitrate=N/A speed= 0x 
frame= 25 fps=1.5 q=0.0 size= 0kB time=00:00:00.00 bitrate=N/A speed= 0x 
frame= 34 fps=1.9 q=0.0 size= 0kB time=00:00:00.00 bitrate=N/A speed= 0x 
frame= 36 fps=2.0 q=0.0 size= 0kB time=00:00:00.00 bitrate=N/A speed= 0x 
frame= 39 fps=2.1 q=0.0 size= 0kB time=00:00:00.00 bitrate=N/A speed= 0x 
frame= 40 fps=2.0 q=0.0 size= 0kB time=00:00:00.00 bitrate=N/A speed= 0x 
frame= 40 fps=2.0 q=0.0 size= 0kB time=00:00:00.00 bitrate=N/A speed= 0x 
frame= 40 fps=1.9 q=0.0 size= 0kB time=00:00:00.00 bitrate=N/A speed= 0x 





success case :



frame= 5 fps=0.4 q=0.0 size= 0kB time=00:00:00.00 bitrate=N/A speed= 0x 
frame= 42 fps=3.2 q=28.0 size= 0kB time=00:00:00.00 bitrate=N/A speed= 0x 
frame= 53 fps=3.9 q=28.0 size= 0kB time=00:00:00.36 bitrate= 2.9kbits/s speed=0.0264x 
frame= 65 fps=4.6 q=28.0 size= 0kB time=00:00:00.84 bitrate= 1.2kbits/s speed=0.0594x 
... 




Slightly older versions included in the newest MacOS builds from zeranoe.com (git-2020-04-13-59e3a9a) and evermeet.cx (N-97308-g14dd0a9057-tessus, from 2020-04-12) are working nicely - also on my production cases (longer clips).



Any feedback would be appreciated !


-
ffmpeg - extract timecode start metadata from tmcd track to a drawtext filter
3 mars 2015, par mwjbI have a Quicktime file with a timecode track. I’m encoding it to a new video codec and would like to burnin the timecode from timecode track. Setting the timecode manually isn’t an option as this will be used for many files with unique starting timecodes.
This is the current work-in-progress ffmpeg command. Obviously I need to find a way to extract the metadate:timecode value and have this start the timecode count instead of the manual entry seen below :
ffmpeg -i infile.mov -y -c:v mjpeg -qscale:v 4 -vendor ap10 -pix_fmt yuvj422p -s 1280x720 -vf drawtext="fontfile=thefont.ttf: timecode='01\:00\:00\:00': rate=24: fontsize=40: fontcolor=white: boxcolor=black: box=1: x=1700: y=80" outfile.mov
The Timecode metadata is there in the Stream #0:1 track, as read by ffmpeg :
ffmpeg version 2.5.2 Copyright (c) 2000-2014 the FFmpeg developers
built on Jan 1 2015 20:24:48 with llvm-gcc 4.2.1 (LLVM build 2336.11.00)
configuration: --prefix=/Volumes/tempdisk/sw --as=yasm --enable-gpl --enable-pthreads --disable-ffplay --disable-ffserver --disable-shared --enable-static --enable-libvpx --disable-decoder=libvpx --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libx265 --enable-libxvid --enable-zlib --enable-avfilter --enable-fontconfig --enable-libfreetype --enable-libass --enable-libutvideo --enable-filters --enable-postproc --enable-runtime-cpudetect
libavutil 54. 15.100 / 54. 15.100
libavcodec 56. 13.100 / 56. 13.100
libavformat 56. 15.102 / 56. 15.102
libavdevice 56. 3.100 / 56. 3.100
libavfilter 5. 2.103 / 5. 2.103
libswscale 3. 1.101 / 3. 1.101
libswresample 1. 1.100 / 1. 1.100
libpostproc 53. 3.100 / 53. 3.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'infile.mov':
Metadata:
major_brand : qt
minor_version : 537199360
compatible_brands: qt
creation_time : 2015-03-02 22:06:00
timecode : 06:00:00:00
Duration: 00:20:00.00, start: 0.000000, bitrate: 36175 kb/s
Stream #0:0(eng): Video: dnxhd (AVdn / 0x6E645641), yuv422p, 1920x1080, 36175 kb/s, 24 fps, 24 tbr, 24k tbn, 24k tbc (default)
Metadata:
creation_time : 2015-03-02 22:06:00
handler_name : Apple Alias Data Handler
encoder : Avid DNxHD Codec
Stream #0:1(eng): Data: none (tmcd / 0x64636D74) (default)
Metadata:
creation_time : 2015-03-02 22:06:58
handler_name : Apple Alias Data Handler
timecode : 06:00:00:00I came across this post ffmpeg and timecode from movie metadata which appeared to be on the same sort of track as I’m on. Would certainly appreciate some guidance on this. Many Thanks.