Recherche avancée

Sur d’autres sites (11849)

• kmsgrab : Use GetFB2 if available

  5 juillet 2020, par Mark Thompson

  kmsgrab : Use GetFB2 if available
  The most useful feature here is the ability to automatically extract the
  
  framebuffer format and modifiers.  It also makes support for multi-plane
  
  framebuffers possible, though none are added to the format table in this
  
  patch.
  This requires libdrm 2.4.101 (from April 2020) to build, so it includes a
  
  configure check to allow compatibility with existing distributions.  Even
  
  with libdrm support, it still won't do anything at runtime if you are
  
  running Linux < 5.7 (before June 2020).
  

  • [DH] configure
  • [DH] libavdevice/kmsgrab.c

• Trouble with converting webm into mp3 with pydub in python

  15 août 2020, par rc_marty

  so basically I want to convert song what I downloaded from youtube in webm and convert to into mp3

  


  when I wanted export song just with song.export("neco.mp3") it didn't work too

  


  I have in workfolder ffmpeg.exe and ffprobe.exe

  


  here is the code

  


  from pydub import AudioSegment

song = AudioSegment.from_file(downloaded.webm,"webm")
print("Loaded")
song.export("neco.mp3", format="mp3", bitrate="320k")
print("Converted and saved")


  


  here is the output of the console

  


  Loaded&#xA;Traceback (most recent call last):&#xA;  File "e:/martan/projekty/Python/programek na pisnicky/songDownloader.py", line 188, in <module>&#xA;    song.export("neco.mp3", format="mp3", bitrate="320k")&#xA;  File "C:\Users\BIBRAIN\AppData\Local\Programs\Python\Python38\lib\site-packages\pydub\audio_segment.py", line 911, in export&#xA;    raise CouldntEncodeError(&#xA;pydub.exceptions.CouldntEncodeError: Encoding failed. ffmpeg/avlib returned error code: 1&#xA;&#xA;Command:[&#x27;ffmpeg&#x27;, &#x27;-y&#x27;, &#x27;-f&#x27;, &#x27;wav&#x27;, &#x27;-i&#x27;, &#x27;C:\\Users\\BIBRAIN\\AppData\\Local\\Temp\\tmpo20ooz_z&#x27;, &#x27;-b:a&#x27;, &#x27;320k&#x27;, &#x27;-f&#x27;, &#x27;mp3&#x27;, &#x27;C:\\Users\\BIBRAIN\\AppData\\Local\\Temp\\tmpiqpl57g7&#x27;]&#xA;&#xA;Output from ffmpeg/avlib:&#xA;&#xA;ffmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers&#xA;  built with gcc 10.2.1 (GCC) 20200726&#xA;  configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libsrt --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libgsm --disable-w32threads --enable-libmfx --enable-ffnvcodec --enable-cuda-llvm --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt --enable-amf&#xA;  libavutil      56. 51.100 / 56. 51.100&#xA;  libavcodec     58. 91.100 / 58. 91.100&#xA;  libavformat    58. 45.100 / 58. 45.100&#xA;  libavdevice    58. 10.100 / 58. 10.100&#xA;  libavfilter     7. 85.100 /  7. 85.100&#xA;  libswscale      5.  7.100 /  5.  7.100&#xA;  libswresample   3.  7.100 /  3.  7.100&#xA;  libpostproc    55.  7.100 / 55.  7.100&#xA;Guessed Channel Layout for Input Stream #0.0 : stereo&#xA;Input #0, wav, from &#x27;C:\Users\BIBRAIN\AppData\Local\Temp\tmpo20ooz_z&#x27;:&#xA;  Duration: 00:03:54.71, bitrate: 3072 kb/s&#xA;    Stream #0:0: Audio: pcm_s32le ([1][0][0][0] / 0x0001), 48000 Hz, stereo, s32, 3072 kb/s&#xA;Stream mapping:&#xA;  Stream #0:0 -> #0:0 (pcm_s32le (native) -> mp3 (mp3_mf))&#xA;Press [q] to stop, [?] for help&#xA;[mp3_mf @ 00000000004686c0] could not find any MFT for the given media type&#xA;[mp3_mf @ 00000000004686c0] could not create MFT&#xA;Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height&#xA;Conversion failed!&#xA;</module>

  


  I think it is something with codec but I have no idea what to do

  


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