Sur d’autres sites (10952)

• cutting mp4 with codec copy results no audio in browser

  16 novembre 2020, par Luka

  I'm editing a video clip with ffmpeg. The original does not play in Firefox browser by itself. It does normally in Chromium. I do something like :

  


  ffmpeg -ss 00:05:10 -i INPUT.mp4 -c copy OUTPUT.mp4


  


  the resulting clip plays in Firefox but there's no audio. This happens in Firefox (82.0.3), but not in Chromium (86.0.4240.75). In chromium the sound is ok.

  


  If audio is reencoded with

  


  ffmpeg -ss 00:05:10 -i INPUT.mp4 -c:v copy -ab 360kb OUTPUT.mp4


  


  resulting clip is playing ok in Firefox.

  


  Could anyone explain what is happening here and is it possible to cut the mp4 without reencoding audio resulting in a clip that plays in Firefox too ?

  


  Some data :

  


  ffmpeg version 3.4.8-0ubuntu0.2

  


  ffprobe INPUT.mp4 :

  


  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'INPUT.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 1
    compatible_brands: iso4avc1isom
    creation_time   : 2020-11-13T18:45:37.000000Z
    com.apple.proapps.clipID: INPUT
    com.blackmagic-design.camera.dateRecorded: 2020:11:13
    com.apple.proapps.cameraName: 0
    com.blackmagic-design.camera.uuid: BDB766E79E646CBB82E3EB986EA1EA-0
  Duration: 02:01:38.00, start: 0.000000, bitrate: 6047 kb/s
    Stream #0:0(eng): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 1920x1080, 5909 kb/s, SAR 1:1 DAR 16:9, 25 fps, 25 tbr, 25 tbn, 50 tbc (default)
    Metadata:
      creation_time   : 2020-11-13T18:45:37.000000Z
      handler_name    : ?Apple Alias Data Handler
      encoder         : H264/AVC
      timecode        : 19:45:35:04
    Stream #0:1(eng): Data: none (tmcd / 0x64636D74) (default)
    Metadata:
      creation_time   : 2020-11-13T18:45:37.000000Z
      handler_name    : ?Apple Alias Data Handler
      timecode        : 19:45:35:04
    Stream #0:2(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 128 kb/s (default)
    Metadata:
      creation_time   : 2020-11-13T18:45:37.000000Z
      handler_name    : ?Apple Alias Data Handler
      timecode        : 19:45:35:04


  


  ffprobe OUTPUT.mp4

  


  


Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'OUTPUT.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2avc1mp41
    encoder         : Lavf57.83.100
  Duration: 01:34:48.02, start: -0.016000, bitrate: 6022 kb/s
    Stream #0:0(eng): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080, 5889 kb/s, SAR 1:1 DAR 16:9, 25 fps, 25 tbr, 12800 tbn, 25600 tbc (default)
    Metadata:
      handler_name    : VideoHandler
      timecode        : 19:45:35:04
    Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 127 kb/s (default)
    Metadata:
      handler_name    : SoundHandler
    Stream #0:2(eng): Data: none (tmcd / 0x64636D74)
    Metadata:
      handler_name    : TimeCodeHandler
      timecode        : 19:45:35:04


  


  ffprobe the OUTPUT.mp4 that has audio re-encoded and works in Firefox :

  


    Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2avc1mp41
    encoder         : Lavf57.83.100
  Duration: 01:34:48.04, start: 0.000000, bitrate: 6160 kb/s
    Stream #0:0(eng): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080, 5889 kb/s, SAR 1:1 DAR 16:9, 25 fps, 25 tbr, 12800 tbn, 25600 tbc (default)
    Metadata:
      handler_name    : VideoHandler
      timecode        : 19:45:35:04
    Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 265 kb/s (default)
    Metadata:
      handler_name    : SoundHandler
    Stream #0:2(eng): Data: none (tmcd / 0x64636D74)
    Metadata:
      handler_name    : TimeCodeHandler
      timecode        : 19:45:35:04


  


  EDIT :

  


  I'm providing links to original files, but a bit of warning, they are 4-5GB big each :

  


  

  1. original recording from blackmagic switcher/capture/recorder (this does not play in firefox at all, but does in Chromium)

  


  2. cut version made with -codec copy (plays in firefox but no audio. plays in chromium ok)

  


  3. cut version with re-encoded audio (plays ok in both firefox and chromium)

  


  


• Piwik is now Matomo – Announcement

  
  9 janvier 2018, par Matomo Core Team

  You may be surprised to read this announcement, but no stress, take a deep breath, nothing big is going to happen, it is just our name that is changing and here are the reasons why.

  

  Why are we changing from Piwik to Matomo ?

  “After an epic 10 year journey creating and perfecting the best open digital analytics solution, we felt it was a good time to refresh our brand to reflect how far we have come and to reaffirm our vision :
  To create, as a community, the leading international open source digital analytics platform, that gives every user full control of their data.”

  Matthieu Aubry, creator of Piwik

  As projects evolve, so do names. After 10 years of Piwik and the amazing achievement of building the top open source analytics software that gives every user full control of their data, we are now looking forward to the next chapter. Thus, Piwik, the community project, will now become Matomo. The only change is our name, everything else stays the same.

  This will allow users to take a fresh look at what we’ve become today and acknowledging all of the community’s hard work over the past 10 years. In addition, we also want our name to be unique, ensuring that it is not shared with any other company to remove any possible confusion or affiliations. Piwik is already used on over 1 million websites and with Matomo, we hope to reach our maximum potential.

  With the strong focus on privacy worldwide and the upcoming privacy regulations about to be legislated in Europe, it is clear that we were on the right mission from the very beginning. With the upcoming big release Matomo 4.0 planned for this year, new privacy protections will bring users the tools to be compliant with the GDPR privacy laws. And Matomo will grow in line with these regulations, with a very clear and focused vision.

  Changing our name is an exciting opportunity for us, and we hope you love the name Matomo as much as we do.

  Matomo FAQs

  So what is going to change for me ?

  Well, basically nothing, the name will change but the values stay the same : Matomo (Piwik) will continue to be free and always will be.

  Also the same people stay behind the project. We are motivated more than ever to take this project to the next level.

  Why not keep the name Piwik ?

  For a few reasons, one of which is to ensure that Matomo does not/will not share its name with any other businesses unlike Piwik. We also want to protect the Matomo brand and for it to remain the open source community project name forever.

  Where does the name Matomo come from ?

  We loved the name Piwik and were looking for something that sounded just as good ! Initially we wanted to have an acronym based on key terms, such as Free, Open Source and Privacy, but none really fit us perfectly.

  Until we found Matomo ! Easily pronounced in all languages. Short enough to remember. Concise. And best of all… Matomo means honesty in Japanese. Which aligns with one of our key values – transparency.

  We love the name Matomo and hope you do too.

  What is the vision of Matomo ?

  

  We have come a long way in those 10 years ! However, our mission statement remains the same :

  “To create, as a community, the leading international open source digital analytics platform, that gives every user full control of their data.”

  Matomo provides a range of amazing and innovative features, allowing you to get a 360 view of your visitors. These insights are invaluable to help understand behavior, keep track of goals, and increase conversion rates and revenue.

  Who will deliver Matomo professional services ?

  Any company who wishes to. The only exception is that no companies will be allowed to have the name Matomo.

  Our company providing professional services is and will remain InnoCraft.

  Where can I follow the Matomo project ?

  Our new website will be matomo.org (automatically redirected from Piwik.org)

  Follow our new Twitter : twitter.com/matomo_org

  Github : github.com/matomo-org

  Facebook : facebook.com/Matomo.org

  Linkedin : linkedin.com/company/matomo/

  If you are already following us on social media, you will be kept up to date with Matomo automatically as all social media accounts will be redirected.

  How should I pronounce Matomo ?

  If you’re wondering how to say ‘Matomo’, you can find out by clicking play :

  Where can I see a demo of Matomo ?

  On demo.matomo.org

  Where can I download Matomo first release ?

  On matomo.org/download

  (Matomo 3.3.0 will be released in the next few days)

  What is the new logo ?

  Check it out below.

  

  Matomo trademark Policy

  Matomo is an internationally registered trademark of Matthieu Aubry, Founder of Piwik (now Matomo).

  Information about how to use the name Matomo (and logo) can be found here : matomo.org/trademark/

  What are the next big steps ?

  We will keep it simple for our valued users. As it is just a name change, the only thing you will notice is that the Piwik brand will gradually be replaced on the websites you are used to seeing the name on. The first version of Matomo will be available in just a few days for download. The software version numbers stay the same : the next release after Piwik 3.2.1 will be Matomo 3.3.0.

  All our public HTTP APIs and Tracking SDKs will continue working normally. As you can imagine, there is a lot of work and complexity behind slowly updating all the SDKs and keeping backwards compatibility, so our renaming project will take a few weeks to complete.

  The Matomo trademark will later be transferred into the Matomo foundation, a non-profit that will be dedicated to promoting and ensuring access to Matomo and our related open source projects in perpetuity.

  ---

  Thank you

  Thank you for continuing to support our project, alongside our 20+ Matomo core team members and more than 500 contributors.

  Please help to spread the word about this announcement by sharing it with friends or or colleagues who may benefit from using Matomo Analytics !

  The post Piwik is now Matomo – Announcement appeared first on Analytics Platform - Matomo.

• Creating a shared library that statically includes ffmpeg

  10 octobre 2017, par El Sampsa

  I’m having hard time trying to create a shared library that has ffmpeg libraries "baked in" as static ones.

  Consider the following directory schema :

  include/
  
    my own .h files
  
    ext/
  
      ffmpeg .h files
  
  lib/
  
    libav*.a archive files (softlinks to the actual .a files)
  
    libValkka.so (my shared library)
  
  test/
  
    mytest.cpp
  
  bin/
  
    (binaries appear here)

  I’ve come a long way (see Including objects to a shared library from a C++ archive (.a) ) and the library compiles ok with this : ([STUFF] has been omitted for brevity)

  /usr/bin/c++ -fPIC -std=c++14 -pthread -Iinclude/ext -I/usr/include/libdrm -g -shared -Wl,-soname,libValkka.so -o lib/libValkka.so CMakeFiles/Valkka.dir/src/avthread.cpp.o CMakeFiles/Valkka.dir/src/opengl.cpp.o CMakeFiles/Valkka.dir/src/openglthread.cpp.o [STUFF] CMakeFiles/Valkka.dir/src/filters.cpp.o -lX11 -lGLEW -lGLU -lGL -Wl,—allow-multiple-definition -Wl,-Bsymbolic -Wl,—whole-archive -Wreorder lib/libavdevice.a lib/libavfilter.a lib/libavformat.a lib/libavcodec.a lib/libavutil.a lib/libswscale.a lib/libswresample.a -Wl,—no-whole-archive

  However, when creating executables - their source code does not use any ffmpeg api (just my own api) - with :

  c++ -std=c++14 -pthread -Iinclude -Iinclude/ext -Llib test/mytest.cpp -lValkka -g -o bin/mytest

  I get a hoard of errors about missing ffmpeg dependencies. Not everything is missing, just some weird stuff :

  lib/libValkka.so: undefined reference to `pa_stream_get_index'
  
  lib/libValkka.so: undefined reference to `deflateInit_'
  
  lib/libValkka.so: undefined reference to `pa_stream_get_state'
  
  lib/libValkka.so: undefined reference to `lzma_stream_decoder'
  
  lib/libValkka.so: undefined reference to `BZ2_bzDecompress'
  
  lib/libValkka.so: undefined reference to `vaInitialize'
  
  lib/libValkka.so: undefined reference to `pa_stream_unref'
  
  lib/libValkka.so: undefined reference to `deflateInit2_'
  
  lib/libValkka.so: undefined reference to `snd_pcm_close'
  
  ...
  
  lib/libValkka.so: undefined reference to `vaGetDisplayDRM'
  
  lib/libValkka.so: undefined reference to `vaMaxNumEntrypoints'
  
  lib/libValkka.so: undefined reference to `uncompress'
  
  lib/libValkka.so: undefined reference to `pa_stream_drop'
  
  lib/libValkka.so: undefined reference to `pa_context_connect'
  
  lib/libValkka.so: undefined reference to `FT_Get_Kerning'
  
  lib/libValkka.so: undefined reference to `ass_free_track'
  
  lib/libValkka.so: undefined reference to `pa_operation_unref'
  
  lib/libValkka.so: undefined reference to `FT_Stroker_Done'
  
  lib/libValkka.so: undefined reference to `vaTerminate'
  
  lib/libValkka.so: undefined reference to `ass_new_track'
  
  lib/libValkka.so: undefined reference to `jack_client_close'
  
  ...
  
  lib/libValkka.so: undefined reference to `xcb_xfixes_query_version'
  
  lib/libValkka.so: undefined reference to `xcb_shape_rectangles'
  
  lib/libValkka.so: undefined reference to `pa_mainloop_free'
  
  lib/libValkka.so: undefined reference to `snd_device_name_hint'
  
  lib/libValkka.so: undefined reference to `vaCreateImage'
  
  lib/libValkka.so: undefined reference to `vaBeginPicture'
  
  lib/libValkka.so: undefined reference to `DtsSetColorSpace'
  
  lib/libValkka.so: undefined reference to `vaDestroyConfig'
  
  lib/libValkka.so: undefined reference to `pa_stream_writable_size'
  
  lib/libValkka.so: undefined reference to `snd_pcm_hw_params_get_buffer_size_max'
  
  lib/libValkka.so: undefined reference to `ass_read_file'

  This is pretty frustrating, especially when I can see that those names are included in the shared library..!

  nm lib/libValkka.so | grep "vaBeginPicture"

  gives

  U vaBeginPicture

  etc. I thought it might be a problem regarding the dependency order the archive .a files, and also tried with :

  ..... -Wl,—allow-multiple-definition -Wl,-Bsymbolic -Wl,—start-group -Wl,—whole-archive -Wreorder lib/libavdevice.a lib/libavfilter.a lib/libavformat.a lib/libavcodec.a lib/libavutil.a lib/libswscale.a lib/libswresample.a -Wl,—no-whole-archive -Wl,—end-group

  But the problem persists.

  I have succesfully created a shared library that does not "bake in" those .a archives, i.e. that just depends dynamically on ffmpeg libraries, and there are no such problems.

  I am baffled.. Have I misunderstood something fundamental, forgot some annoying linked option, or both ? Help appreciated !