Recherche avancée

Sur d’autres sites (4316)

• 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 !

• Issue with downloading read-only recordings on Teams [closed]

  26 août 2023, par Ankit

  I have been following this guidance to download read-only Microsoft Teams recordings until last month (early July'23) successfully. But now when I am trying the same steps and everything, I am getting some error (given below for reference).

  


  The code that I am trying in CMD -

  


  ffmpeg -i "PASTE_YOUR_COPIED_REQUEST_URL_HERE" -codec copy NAME_OF_DOWNLOADFILE.mp4


  


  The error that I am getting now -

  


  [tls @ <some number="number">] Error in the pull function.&#xA;[tls @ <some number="number">] IO error: Error number -10054 occurred&#xA;[in#0 @ <some number="number">] Error opening input: Error number -10054 occurred&#xA;Error opening input file &#xA;Error opening input files: Error number -10054 occurred&#xA;</some></some></some>

  


  I am running Windows 10 Enterprise 64-bit version.

  


  ---

  


  I have tried the following things, but they didn't help -

  


  

  1. Tried downloading inherently downloadable recordings (that are un-protected, non view-only videos)

  


  2. Removing some parts of the URL as highlighted/suggested by some Reddit users

  


  3. Tried different browsers (Edge and Chrome)

  


  4. Tried refreshing my ffmpeg folder with latest version

  


  5. Tried running the command in cmd with 'Run as Administrator' option

  


  


  Please suggest how shall I download read-only Teams recording using either ffmpeg or some other tool ?

  


• How to play HDR10 videos using ffplay and ffmpeg ?

  6 janvier 2023, par befandy

  I'm trying to play on Windows a HDR10 video. My display support 10 bits HDR content.
The command that I'm using to play the HDR10 video is the following.
ffplay -sws_flags print_info -i video.mp4

  


  But the output looks washed out.

  


  the log are the following :

  


  ffplay version 2022-03-28-git-5ee198f9aa-full_build-www.gyan.dev Copyright (c) 2003-2022 the FFmpeg developers built with gcc 11.2.0 (Rev7, Built by MSYS2 project) configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-bzlib --enable-lzma --enable-libsnappy --enable-zlib --enable-librist --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libdav1d --enable-libdavs2 --enable-libuavs3d --enable-libzvbi --enable-librav1e --enable-libsvtav1 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxvid --enable-libaom --enable-libopenjpeg --enable-libvpx --enable-mediafoundation --enable-libass --enable-frei0r --enable-libfreetype --enable-libfribidi --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec --enable-nvenc --enable-d3d11va --enable-dxva2 --enable-libmfx --enable-libshaderc --enable-vulkan --enable-libplacebo --enable-opencl --enable-libcdio --enable-libgme --enable-libmodplug --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libshine --enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libilbc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-ladspa --enable-libbs2b --enable-libflite --enable-libmysofa --enable-librubberband --enable-libsoxr --enable-chromaprint libavutil      57. 24.101 / 57. 24.101 libavcodec     59. 25.100 / 59. 25.100 libavformat    59. 20.101 / 59. 20.101 libavdevice    59.  6.100 / 59.  6.100 libavfilter     8. 29.100 /  8. 29.100 libswscale      6.  6.100 /  6.  6.100 libswresample   4.  6.100 /  4.  6.100 libpostproc    56.  5.100 / 56.  5.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'video.mp4':=0/0 Metadata: major_brand     : isom minor_version   : 512 compatible_brands: isomiso2mp41 encoder         : Lavf58.29.100 Duration: 00:00:08.78, start: 0.000000, bitrate: 159424 kb/s Stream #0:0[0x1](und): Video: hevc (Main 10) (hev1 / 0x31766568), yuv420p10le(tv, bt2020nc/bt2020/smpte2084, progressive), 3840x2160 [SAR 1:1 DAR 16:9], 159427 kb/s, 60 fps, 60 tbr, 15360 tbn (default) Metadata: handler_name    : VideoHandler vendor_id       : [0][0][0][0] [swscaler @ 000001d62a81d000] [swscaler @ 000001d622aebf80] bicubic scaler, from yuv420p10le to yuv420p using MMXEXT [swscaler @ 000001d62a81d000] [swscaler @ 000001d622aebf80] using unscaled yuv420p10le -> yuv420p special converter [swscaler @ 000001d62a81d000] [swscaler @ 000001d635638600] bicubic scaler, from yuv420p10le to yuv420p using MMXEXT [swscaler @ 000001d62a81d000] [swscaler @ 000001d635638600] using unscaled yuv420p10le -> yuv420p special converter [swscaler @ 000001d62a81d000] [swscaler @ 000001d635661d80] bicubic scaler, from yuv420p10le to yuv420p using MMXEXT [swscaler @ 000001d62a81d000] [swscaler @ 000001d635661d80] using unscaled yuv420p10le -> yuv420p special converter [swscaler @ 000001d62a81d000] [swscaler @ 000001d63567df80] bicubic scaler, from yuv420p10le to yuv420p using MMXEXT [swscaler @ 000001d62a81d000] [swscaler @ 000001d63567df80] using unscaled yuv420p10le -> yuv420p special converter [swscaler @ 000001d62a81d000] [swscaler @ 000001d6356bbf80] bicubic scaler, from yuv420p10le to yuv420p using MMXEXT 3.44 M-V:  0.204 fd=  91 aq=    0KB vq=15552KB sq=    0B f=0/0

  


  With the help of '-sws_flags print_info' flag we can see that there is a downscaling happening from 10 bits to 8 bits "yuv420p10le -> yuv420p"

  


  I have try to play the video using VLC and it is working fine on my display : colour are vivid and display bright.

  


  I have also try to decode first the video and then past metadata directly to ffplay as follow.
Decoding to yuv format with : ffmpeg -i video.mp4 video.yuv
Then play yuv file : ffplay -framerate 60 -video_size 3840x2160 -pixel_format yuv420p10le -color_range tv -color_trc smpte2084 -color_primaries bt2020 -colorspace bt2020nc -i video.yuv

  


  But the result is the same washed out color and "yuv420p10le -> yuv420p" conversion

  


  Is there a way to play a HDR video (encoded or decoded stream) with ffplay ?