Recherche avancée

Sur d’autres sites (6018)

• fate/subtitles : Add JACOsub remuxing test

  24 septembre 2021, par Andreas Rheinhardt

  fate/subtitles : Add JACOsub remuxing test
  This muxer was untested up until now ; had it been tested, it would
  
  have been obvious that it has been broken for years.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
  

  • [DH] tests/fate/subtitles.mak
  • [DH] tests/ref/fate/sub-jacosub-remux

• Convert fla and swf to mp4 video

  4 mai 2021, par Max Williams

  I have an .fla file and a .swf file which were intended to make a Flash Video some years ago.

  


  I want to make an mp4. i tried simply passing the swf into ffmpeg, and the resulting mp4 file had the audio but no video. If I use the fla and the swf, would I get video too ? I don't know how Flash worked wrt the different file types.

  


  EDIT : as asked for, the output from doing just the swf and from using both as the input :

  


  swf alone :

  


  $ ffmpeg -i input.swf  output.mp4
ffmpeg version git-2018-05-03-0f0d468 Copyright (c) 2000-2018 the FFmpeg developers
  built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04.4)
  configuration: --enable-gpl --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-librtmp --enable-libtheora --enable-libvorbis --enable-libx264 --enable-nonfree --enable-version3
  libavutil      56. 18.100 / 56. 18.100
  libavcodec     58. 19.100 / 58. 19.100
  libavformat    58. 13.100 / 58. 13.100
  libavdevice    58.  4.100 / 58.  4.100
  libavfilter     7. 21.100 /  7. 21.100
  libswscale      5.  2.100 /  5.  2.100
  libswresample   3.  2.100 /  3.  2.100
  libpostproc    55.  2.100 / 55.  2.100
[swf @ 0x22483c0] SWF compressed file detected
[swf @ 0x22483c0] Estimating duration from bitrate, this may be inaccurate
Input #0, swf, from 'input.swf':
  Duration: 00:00:51.87, bitrate: 112 kb/s
    Stream #0:0: Audio: mp3, 44100 Hz, mono, fltp, 112 kb/s
File 'output.mp4' already exists. Overwrite ? [y/N] y
Stream mapping:
  Stream #0:0 -> #0:0 (mp3 (mp3float) -> aac (native))
Press [q] to stop, [?] for help
Output #0, mp4, to 'output.mp4':
  Metadata:
    encoder         : Lavf58.13.100
    Stream #0:0: Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, mono, fltp, 69 kb/s
    Metadata:
      encoder         : Lavc58.19.100 aac
[swf @ 0x22483c0] New audio stream 0:1 at pos:226047 and DTS:0s
[swf @ 0x22483c0] New audio stream 0:2 at pos:234457 and DTS:0s
[swf @ 0x22483c0] New audio stream 0:3 at pos:245057 and DTS:0s
[swf @ 0x22483c0] New audio stream 0:4 at pos:255657 and DTS:0s
[swf @ 0x22483c0] New audio stream 0:5 at pos:270637 and DTS:0s
[swf @ 0x22483c0] New audio stream 0:6 at pos:281967 and DTS:0s
[swf @ 0x22483c0] New audio stream 0:7 at pos:290742 and DTS:0s
[swf @ 0x22483c0] New audio stream 0:8 at pos:300612 and DTS:0s
[swf @ 0x22483c0] New audio stream 0:9 at pos:309022 and DTS:0s
[swf @ 0x22483c0] New audio stream 0:10 at pos:463819 and DTS:0s
[swf @ 0x22483c0] New audio stream 0:11 at pos:696822 and DTS:0s
[swf @ 0x22483c0] New audio stream 0:12 at pos:709202 and DTS:0s
[swf @ 0x22483c0] New audio stream 0:13 at pos:735377 and DTS:0s
[swf @ 0x22483c0] New audio stream 0:14 at pos:745561 and DTS:0s
size=     265kB time=00:00:31.04 bitrate=  69.8kbits/s speed= 109x    
video:0kB audio:259kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 2.325915%
[aac @ 0x22a06c0] Qavg: 1972.990



  


  both :

  


  $ ffmpeg -i input.fla -i input.swf output.mp4
ffmpeg version git-2018-05-03-0f0d468 Copyright (c) 2000-2018 the FFmpeg developers
  built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04.4)
  configuration: --enable-gpl --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-librtmp --enable-libtheora --enable-libvorbis --enable-libx264 --enable-nonfree --enable-version3
  libavutil      56. 18.100 / 56. 18.100
  libavcodec     58. 19.100 / 58. 19.100
  libavformat    58. 13.100 / 58. 13.100
  libavdevice    58.  4.100 / 58.  4.100
  libavfilter     7. 21.100 /  7. 21.100
  libswscale      5.  2.100 /  5.  2.100
  libswresample   3.  2.100 /  3.  2.100
  libpostproc    55.  2.100 / 55.  2.100
input.fla: Invalid data found when processing input


  


• Matomo to end support for Internet Explorer 11

  21 septembre 2021, par Matomo Core Team — Community

  A lot of the Matomo user interface is built on top of a programming framework called “Angular.js”. The support for this framework will end very soon, meaning we have to migrate the Matomo user interface to an alternative framework. The Matomo development team has chosen this new framework to be “Vue.js 3”.

  Unfortunately, Vue.js does not support Internet Explorer 11 (IE 11). Therefore, we have to drop the support for IE 11. Many other popular services like Microsoft and WordPress recently did the same. This is happening because IE 11 was released about 8 years ago and is now used by less than 0.5% of the internet. 

  When will this change happen ?

  Our next release (Matomo 4.5) will still support IE 11. It will show a notification in the user interface if you are using Internet Explorer to make you aware of this upcoming change. 

  When Matomo 4.6 is released around November 2021, then IE 11 will no longer be supported.

  What does “end support” mean ?

  The Matomo user interface will work less and less over time for people using IE 11 as a browser. While Matomo 4.6 might still mostly work with IE 11, once we migrate more of the user interface the functionality will stop working completely. It’s possible that even Matomo 4.6 will no longer be functional with IE 11 at all.

  What should I do now ?

  If you are impacted by this, then we strongly recommend that you switch to a more modern browser. Preferably a privacy-friendly browser like Mozilla Firefox or Brave. But any modern browser including Microsoft Edge, Safari and Google Chrome will work just fine.

  If you can’t use a different browser and you are using Matomo On-Premise, then you can install and configure this new plugin which lets you only receive Matomo core updates that are compatible with IE 11. This will prevent you from accidentally upgrading to a Matomo core release that doesn’t work with IE 11, and you can still receive critical security updates and bug fixes until February 2022.

  Will this affect the Matomo JavaScript tracker ?

  No, all visitors using IE 11 will still be tracked and Matomo tracker will support the same browsers as before. Meaning also some older versions of Internet Explorer are still supported.

  Have any questions about this ?

  Get in touch with us