Recherche avancée

Sur d’autres sites (11253)

• ffmpeg change metadata inside video file

  26 novembre 2020, par virtualsets

  Hello I have problems to change timecode insdie metadata of a video file "mov"

  


  ruta=r"E:\Brutos-sin-eliminar\inma-ruben-22-2-2020\multicam\\"
nombre=r"A019_02230134_C186.mov"
comand="ffmpeg -i " + nombre + " -ss 0 -map 0 -acodec copy -vcodec copy -timecode 01:20:10:00 -metadata:s:2:0 timecode=01:20:10:00 -metadata:s:1:0 timecode=01:20:10:00 -metadata:s:0:2 -metadata:s:0:2  timecode=01:10:10:00"+ " convert_" + nombre

os.popen(comand)


  


  I need to put muy own timecode to the file but this command not works.

  


  The console give me

  


    mov @ 00000225287fdc00] You requested a copy of the original timecode track so timecode metadata are now ignored
Output #0, mov, to 'convert_A019_02230134_C186.mov':
  Metadata:
    major_brand     : qt  
    minor_version   : 537199360
    compatible_brands: qt  
    com.blackmagic-design.camera.windowedSensor: 1
    com.apple.proapps.manufacturer: Blackmagic Design
    com.blackmagic-design.camera.uuid: 3cf1dd9e-e307-47ff-864e-5487fea3fa47
    com.blackmagic-design.camera.projectFPS: 25
    com.apple.proapps.shootingRate: 50
    com.blackmagic-design.camera.cameraType: Blackmagic Pocket Cinema Camera 4K
    com.blackmagic-design.camera.shutterAngle: 180°
    com.blackmagic-design.camera.shutterMode: Angle
    com.blackmagic-design.camera.iso: 3200
    com.blackmagic-design.camera.whiteBalanceKelvin: 3000
    com.blackmagic-design.camera.whiteBalanceTint: -44
    com.apple.proapps.customgamma: com.blackmagic-design.camera.filmlog
    com.blackmagic-design.camera.look.LUTName: Blackmagic Pocket 4K Film to Extended Video.cube
    com.blackmagic-design.camera.guides.aspectRatio: 2:1
    com.blackmagic-design.camera.guides.safeArea: 90
    com.blackmagic-design.camera.firmware: 6.6
    com.apple.proapps.clipID: A019_02230134_C186
    com.apple.proapps.reel: 19
    com.apple.proapps.scene: 1
    com.apple.proapps.shot: 99
    com.apple.proapps.isGood: 0
    com.blackmagic-design.camera.environment: interior
    com.blackmagic-design.camera.dayNight: day
    com.apple.proapps.cameraName: A
    com.blackmagic-design.camera.colorScience: Blackmagic Pocket Cinema Camera 4K, Color Science Gen 4
    com.blackmagic-design.camera.dateRecorded: 2020:02:23
    timecode        : 01:20:10:00
    encoder         : Lavf58.11.101
    Stream #0:0(eng): Video: prores (apcn / 0x6E637061), yuv422p10le(bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 122315 kb/s, 25 fps, 25 tbr, 12800 tbn, 25 tbc (default)
    Metadata:
      creation_time   : 01:10:10:00
      handler_name    : ?Apple Alias Data Handler
      encoder         : Apple ProRes 422
      timecode        : 01:10:10:00
    Stream #0:1(eng): Audio: pcm_s24le (in24 / 0x34326E69), 48000 Hz, stereo, s32 (24 bit), 2304 kb/s (default)
    Metadata:
      creation_time   : 2020-02-23T00:34:02.000000Z
      handler_name    : ?Apple Alias Data Handler
      timecode        : 01:20:10:00
    Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s (default)
    Metadata:
      creation_time   : 2020-02-23T00:34:02.000000Z
      handler_name    : ?Apple Alias Data Handler
      timecode        : 01:20:10:00
Stream mapping:
  Stream #0:0 -> #0:0 (copy)
  Stream #0:1 -> #0:1 (copy)
  Stream #0:2 -> #0:2 (copy)
Press [q] to stop, [?] for help
frame=  467 fps=0.0 q=-1.0 Lsize=  281452kB time=00:00:18.64 bitrate=123693.3kbits/s speed=71.1x    
video:278913kB audio:2531kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.002533%


  


  I dont understand why not modificate the mov file... when open the metadata it is oringinal.

  


  Reggards

  


• How to concat videos with FFMPEG without a black frame in the middle

  21 juillet 2020, par david k

  I need to join two videos together programmatically, and FFMPEG seems to be working perfectly except it leaves a single black frame between the two joined videos.

  


  Based on this post, I'm guessing it's because the video and audio streams aren't exactly the same length (not sure why). Since I'm seeing a black flash, I'm guessing that the audio is slightly longer than the video, but I can't figure out how to remedy that. I'm fine losing a tiny piece of the audio at the end of the file.

  


  Can anyone help me "trim" the end of my audio stream so that it matches my video stream ? I need to be able to do this for many files, so I can't just hard-code a value into my command.

  


  I've attempted both of the methods that FFMPEG provides to concat, and both of them have this issue. I'd be fine with either approach, if I can get rid of the black frame.

  


  Transcode :

  


  ffmpeg -i video1.mp4 -i video2.mp4 -filter_complex \
  "[0:v][0:a][1:v][1:a] concat=n=2:v=1:a=1 [outv] [outa]" \
  -map "[outv]" -map "[outa]" output.mp4


  


  Re-wrap :

  


  ffmpeg -f concat -i files.txt -c copy output.mp4


  


  Here is the output of ffmpeg -i video1.mp4 -i video2.mp4 :

  


  ffmpeg version 4.2.2 Copyright (c) 2000-2019 the FFmpeg developers
  built with Apple clang version 11.0.0 (clang-1100.0.33.16)
  configuration: --prefix=/usr/local/Cellar/ffmpeg/4.2.2_1 --enable-shared --enable-pthreads --enable-version3 --enable-avresample --cc=clang --host-cflags='-I/Library/Java/JavaVirtualMachines/adoptopenjdk-13.0.1.jdk/Contents/Home/include -I/Library/Java/JavaVirtualMachines/adoptopenjdk-13.0.1.jdk/Contents/Home/include/darwin -fno-stack-check' --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom --enable-libbluray --enable-libmp3lame --enable-libopus --enable-librubberband --enable-libsnappy --enable-libtesseract --enable-libtheora --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librtmp --enable-libspeex --enable-libsoxr --enable-videotoolbox --disable-libjack --disable-indev=jack
  libavutil      56. 31.100 / 56. 31.100
  libavcodec     58. 54.100 / 58. 54.100
  libavformat    58. 29.100 / 58. 29.100
  libavdevice    58.  8.100 / 58.  8.100
  libavfilter     7. 57.100 /  7. 57.100
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  5.100 /  5.  5.100
  libswresample   3.  5.100 /  3.  5.100
  libpostproc    55.  5.100 / 55.  5.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'video1.mp4':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: isommp42
    creation_time   : 2020-07-20T20:43:05.000000Z
  Duration: 00:00:09.88, start: 0.000000, bitrate: 1330 kb/s
    Stream #0:0(und): Audio: aac (LC) (mp4a / 0x6134706D), 32000 Hz, mono, fltp, 53 kb/s (default)
    Metadata:
      creation_time   : 2020-07-20T20:43:05.000000Z
      handler_name    : AAC audio
    Stream #0:1(und): Video: h264 (Baseline) (avc1 / 0x31637661), yuv420p, 1280x720, 1274 kb/s, 25 fps, 25 tbr, 30k tbn, 60k tbc (default)
    Metadata:
      creation_time   : 2020-07-20T20:43:05.000000Z
      handler_name    : H.264/AVC video
      encoder         : AVC Coding
Input #1, mov,mp4,m4a,3gp,3g2,mj2, from 'video2.mp4':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: isommp42
    creation_time   : 2020-07-20T20:43:06.000000Z
  Duration: 00:00:11.68, start: 0.000000, bitrate: 1346 kb/s
    Stream #1:0(und): Audio: aac (LC) (mp4a / 0x6134706D), 32000 Hz, mono, fltp, 53 kb/s (default)
    Metadata:
      creation_time   : 2020-07-20T20:43:06.000000Z
      handler_name    : AAC audio
    Stream #1:1(und): Video: h264 (Baseline) (avc1 / 0x31637661), yuv420p, 1280x720, 1289 kb/s, 25 fps, 25 tbr, 30k tbn, 60k tbc (default)
    Metadata:
      creation_time   : 2020-07-20T20:43:06.000000Z
      handler_name    : H.264/AVC video
      encoder         : AVC Coding
At least one output file must be specified


  


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

  6 août 2020, par Matomo Core Team — Development

  We’re planning to release the first beta of Matomo 4 in a few weeks. For making it easy for Matomo users to be able to upgrade to this beta, it would be great if as many plugins on the Marketplace as possible would be already updated and compatible with Matomo 4. 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 4 helps ensure that people will be able to find and keep using your plugin. If your plugin is not compatible with Matomo 4, your plugin will be automatically deactivated. We’ll be happy to help you achieve compatibility should there be any issue.

  How do I upgrade my Matomo to Matomo 4 ?

  If you have installed your Matomo development environment through git you can simply checkout the Matomo 4 branch “4.x-dev” by executing these commands :

  • git checkout 4.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 4 ?

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

  While there were many breaking changes in Matomo 4, most of our Platform APIs remain unchanged, and almost all changes are for rarely used APIs. Often to make your plugin compatible it 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 4.

  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 I downgrade to Matomo 3 or switch between Matomo 3 and Matomo 4 ?

  To downgrade from Matomo 4 to Matomo 3 :

  • check out the “3.x-dev” branch 
  • run a composer install as usual. 
  • run the SQL statements from this downgrade guide to restore the previous MySQL schema.

  When will the final Matomo 4 release be available ?

  We estimate the final stable Matomo 4.0.0 release will be released in approx. 3 months.

  What’s new in Matomo 4 ?

  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 !