Recherche avancée

Sur d’autres sites (7547)

• FFmpeg | subtitles with ass format

  26 octobre 2018, par Praveen Tamil

  I would like to generate subtitles with dynamic font

  [Script Info]
  
  ScriptType: v4.00+
  
  PlayResX: 1280
  
  PlayResY: 720
  
  Title: WoFox
  
  
  
  [V4+ Styles]
  
  Format: Name, Fontname, Fontsize, PrimaryColour, SecondaryColour, OutlineColour, BackColour, Bold, Italic, Underline, StrikeOut, ScaleX, ScaleY, Spacing, Angle, BorderStyle, Outline, Shadow, Alignment, MarginL, MarginR, MarginV, Encoding
  
  Style: Default,Arial,30,&Hffffff,&Hffffff,&H0000FF,&H0000FF,0,0,0,0,100,100,5,0,3,1,0,3,10,10,10,1
  
  Style: Default1,/home/nodeuser8/tmp/CharmonmanRegular.ttf,40,&Hffffff,&Hffffff,&H0000FF,&H0000FF,0,0,0,0,100,100,5,0,3,1,0,3,10,10,10,1
  
  
  
  [Events]
  
  Format: Layer, Start, End, Style, Name, MarginL, MarginR, MarginV, Effect, Text
  
  Dialogue: 0,00:00:00.0,00:00:03.0,Default,,0,0,0,,My first subtitle! Click this text to edit
  
  Dialogue: 0,00:00:00.0,00:00:03.0,Default1,,0,0,0,,This box shows the amount of text that fits into one caption. As you change the style of the captions, you can preview how

  And my ffmpeg code is

  ffmpeg -i ./tmp/source.mp4 -t 5 -filter_complex "ass=filename=./tmp/subtitles.ass" ./t mp/output.mp4 -y

  But I didn’t get out expected output.

  The Console is

  [Parsed_ass_0 @ 0x58680c0] Shaper: FriBidi 1.0.5 (SIMPLE)
  
  [Parsed_ass_0 @ 0x58680c0] Using font provider fontconfig
  
  [Parsed_ass_0 @ 0x58680c0] Added subtitle file: './tmp/subtitles.ass' (3 styles, 2 events)
  
  Stream mapping:
  
    Stream #0:0 (h264) -> ass (graph 0)
  
    ass (graph 0) -> Stream #0:0 (libx264)
  
    Stream #0:1 -> #0:1 (aac (native) -> aac (native))
  
  Press [q] to stop, [?] for help
  
  [Parsed_ass_0 @ 0x5cd4180] Shaper: FriBidi 1.0.5 (SIMPLE)
  
  [Parsed_ass_0 @ 0x5cd4180] Using font provider fontconfig
  
  [Parsed_ass_0 @ 0x5cd4180] Added subtitle file: './tmp/subtitles.ass' (3  styles, 2 events)
  
  [Parsed_ass_0 @ 0x5cd4180] fontselect: (Arial, 400, 0) -> /usr/share/fonts/liberation/LiberationSans-Regular.ttf, 0, LiberationSans
  
  [Parsed_ass_0 @ 0x5cd4180] fontselect: (/home/nodeuser8/tmp/CharmonmanRegular.ttf, 400, 0) -> /usr/share/fonts/dejavu/DejaVuSans.ttf, 0, DejaVuSans
  
  [libx264 @ 0x5869880] using SAR=1/1
  
  [libx264 @ 0x5869880] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
  
  [libx264 @ 0x5869880] profile High, level 3.1, 4:2:0, 8-bit
  
  [libx264 @ 0x5869880] 264 - core 157 r2935 545de2f - H.264/MPEG-4 AVC codec - Copyleft 2003-2018 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=6 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=15 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
  
   Output #0, mp4, to './tmp/output.mp4':

  Here I’m trying to load font from /home/nodeuser8/tmp/CharmonmanRegular.ttf but ffmpeg load font from /usr/share/fonts/dejavu/DejaVuSans.ttf.

  So how to load fontfile for ass subtitles ?

• Merge and Concat Multiple Audio and Video files using FFMPEG

  20 décembre 2018, par mattgi

  I have a script at present that results in several audio-only and video-only files.

  My goal is to take these and then concat each video clip whilst merging in the audio-clips.

  I thought this would be easy but I have not been able to find a good example to work from.

  FFMPEG.org suggests that the movie/amovie input syntax could be the best option.. but am craving more doco. FFMPEG’s information on the topic is @
  https://www.ffmpeg.org/ffmpeg-filters.html#Examples-124. It suggests that to "...Concatenate two parts, handling audio and video separately" we should be able to use the "(a)movie sources" and includes this example :

  movie=part1.mp4, scale=512:288 [v1] ; amovie=part1.mp4 [a1] ;
  
  movie=part2.mp4, scale=512:288 [v2] ; amovie=part2.mp4 [a2] ;
  
  [v1] [v2] concat [outv] ; [a1] [a2] concat=v=0:a=1 [outa]

  I have tried this myself without any success :

  -f lavfi
  
  -i amovie=/clips/1-0.mp3 [a0];
  
     movie=/clips/1-1-overlayed.mp4 [v1];
  
     amovie=/clips/1-2.mp3 [a2];
  
     movie=/clips/1-3-overlayed.mp4 [v3];
  
     amovie=/clips/1-4.mp3 [a4];
  
     movie=/clips/1-5-overlayed.mp4 [v5];
  
     [v1] [v3] [v5] concat=n=3 "[outv]" ; [a0] [a2] [a4] concat=n=3:v=0:a=1 "[outa]"
  
  -map "[outv]"
  
  -map "[outa]"
  
  output.mp4

  gives :

  "[outa]": Invalid argument

  Any ideas on how to get this working ? (doesn’t have to use the same movie/amovie constructs, my main requirement is that I have an array of items and need to produce a video from them, that is a concat of each video, and a merge of each audio.

  ...

  When I use regular concat, I get this error :

  [mp3 @ 0x7fd200003a00] Estimating duration from bitrate, this may be inaccurate
  
  Input #0, mp3, from '/clips/1-0.mp3':
  
    Duration: 00:00:04.27, start: 0.000000, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #1, mov,mp4,m4a,3gp,3g2,mj2, from '/clips/1-1-overlayed.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.20.100
  
    Duration: 00:00:04.28, start: 0.000000, bitrate: 28 kb/s
  
      Stream #1:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 3:4 DAR 4:3], 24 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
  [mp3 @ 0x7fd20080ac00] Estimating duration from bitrate, this may be inaccurate
  
  Input #2, mp3, from '/clips/1-2.mp3':
  
    Duration: 00:00:14.38, start: 0.000000, bitrate: 32 kb/s
  
      Stream #2:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #3, mov,mp4,m4a,3gp,3g2,mj2, from '/clips/1-3-overlayed.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.20.100
  
    Duration: 00:00:14.36, start: 0.000000, bitrate: 530 kb/s
  
      Stream #3:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1920x1080, 528 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
  [mp3 @ 0x7fd20100d200] Estimating duration from bitrate, this may be inaccurate
  
  Input #4, mp3, from '/clips/1-4.mp3':
  
    Duration: 00:00:02.78, start: 0.000000, bitrate: 32 kb/s
  
      Stream #4:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #5, mov,mp4,m4a,3gp,3g2,mj2, from '/clips/1-5-overlayed.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.20.100
  
    Duration: 00:00:02.80, start: 0.000000, bitrate: 34 kb/s
  
      Stream #5:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 3:4 DAR 4:3], 29 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
  Stream specifier ':a' in filtergraph description [0:a][1:v][2:a][3:v][4:a][5:v]concat=n=3:v=1:a=1[v][a] matches no streams.

  The input (via NodeJS wrapper) looks like this :

  FFmpeg {
  
    options:
  
     [ '-hide_banner',
  
       '-y',
  
       '-i',
  
       '/clips/1-0.mp3',
  
       '-i',
  
       '/clips/1-1-overlayed.mp4',
  
       '-i',
  
       '/clips/1-2.mp3',
  
       '-i',
  
       '/clips/1-3-overlayed.mp4',
  
       '-i',
  
       '/clips/1-4.mp3',
  
       '-i',
  
       '/clips/1-5-overlayed.mp4',
  
       '-filter_complex',
  
       '[0:a][1:v][2:a][3:v][4:a][5:v]concat=n=3:v=1:a=1[v][a]',
  
       '-map',
  
       '[v]',
  
       '-map',
  
       '[a]',
  
       '/projects/1.mp4' ],
  
    outputFilename: '' }

• To all Matomo plugin developers : Matomo 5 is coming, make your plugin compatible now

  5 mai 2023, par Matomo Core Team — Development

  We’re planning to release the first beta of Matomo 5 in a few weeks. For making it easy for Matomo users to be able to upgrade to this beta, it would be great to have as many plugins on the Marketplace as possible already updated and compatible with Matomo 5. Then many users would be able to upgrade to the first beta without any issues.

  Presumably, as you put your plugin on our Marketplace, you want people to use it. Making your plugin compatible with Matomo 5 helps ensure that people will be able to find and keep using your plugin. If your plugin is not compatible with Matomo 5, your plugin will be automatically deactivated in Matomo 5 instances. We’ll be happy to help you achieve compatibility should there be any issue.

  How do I upgrade my Matomo instance to Matomo 5 ?

  If you have installed your Matomo development environment through git, you can simply checkout the Matomo 5 branch “5.x-dev” and install its dependencies by executing these commands :

  • git checkout 5.x-dev
  • composer install

  Alternatively, you can also download the latest version directly from GitHub as a zip file and run composer install afterwards.

  How do I upgrade my plugin to Matomo 5 ?

  • We recommend you create a new branch for your plugin that supports Matomo 5. For example a branch named “5.x-dev“. This way you will be able to make changes to your plugin for Matomo 4 and Matomo 5 and release separate versions.
  • Check out our migration guide from Matomo 4 to Matomo 5 and make sure to review the list of all breaking changes.
  • Release a new version of your plugin in GitHub as usual.

  While there are some breaking changes in Matomo 5, most of our Platform APIs remain unchanged, and almost all changes are for rarely used APIs. Quite often, making your plugin compatible with Matomo 5 will just be a matter of adjusting the “plugin.json” file (as mentioned in the migration guide).

  You can find all developer documentation on our developer zone which has already been updated for Matomo 5.

  How do I know my plugin changes were released successfully ?

  If you have configured an email address within your “plugin.json” file, then you will receive a confirmation or an error email within a few minutes. Alternatively, you can also check out your plugin page on the Marketplace directly. If the plugin release was successful, you will see additional links below the download button showing which versions your plugin is compatible with.

  

  How can switch between Matomo 4 and Matomo 5 or downgrade to Matomo 4 ?

  To downgrade from Matomo 5 to Matomo 4 in your Matomo development environment :

  • check out the “4.x-dev” branch 
  • run “composer install” as usual

  When will the final Matomo 5 release be available ?

  We estimate the final stable Matomo 5.0.0 release will be released in approx. 2-3 months.

  What is new in Matomo 5 ?

  We don’t have a summary of the changes available just yet but you can see all closed issues within this release here.

  Any questions or need help ?

  If you have any questions, or experience any problems during the migration, don’t hesitate to get in touch with us. We’ll be happy to help get your plugin compatible and the update published. If you find any undocumented breaking change or find any step during the migration process not clear, please let us know as well.

  Thank you for contributing a plugin to the Marketplace and making Matomo better. We really appreciate your work !