Recherche avancée

Sur d’autres sites (9050)

• ffmpeg concat and preserve metadata streams

  16 décembre 2024, par Andrew

  I'm trying to concat multiple files that are the result of a GoPro Hero6 splitting movies to avoid the FAT 4GB limit. ffmpeg works great for this purpose but I need the telemetry data that is encoded in the metadata streams, and ffmpeg by default doesn't seem to preserve this. Using the ffprobe command you can see that the source videos have :

  



  Stream #0:3(eng): Data: none (gpmd / 0x646D7067), 36 kb/s (default)
Metadata:
  creation_time   : 2018-07-15T16:16:26.000000Z
  handler_name    : GoPro MET


  



  I know from research that this is the stream I need (although I'd like to be able to copy all streams). However when using ffmpeg -f concat the output is :

  



  [concat @ 0x7febb9800000] Could not find codec parameters for stream 2 (Unknown: none): unknown codec
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[concat @ 0x7febb9800000] Could not find codec parameters for stream 3 (Unknown: none): unknown codec
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[concat @ 0x7febb9800000] Could not find codec parameters for stream 4 (Unknown: none): unknown codec
Consider increasing the value for the 'analyzeduration' and 'probesize' options
Input #0, concat, from 'tmp.txt':
  Duration: N/A, start: 0.000000, bitrate: 66194 kb/s
    Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuvj420p(pc, bt709), 2704x1520 [SAR 1:1 DAR 169:95], 66005 kb/s, 59.94 fps, 59.94 tbr, 60k tbn, 119.88 tbc
    Metadata:
      creation_time   : 2018-07-15T16:08:22.000000Z
      handler_name    : GoPro AVC
      encoder         : GoPro AVC encoder
      timecode        : 16:23:48:21
    Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 189 kb/s
    Metadata:
      creation_time   : 2018-07-15T16:08:22.000000Z
      handler_name    : GoPro AAC
      timecode        : 16:23:48:21
    Stream #0:2: Unknown: none
    Stream #0:3: Unknown: none
    Stream #0:4: Unknown: none
Output #0, mp4, to 'GH0089.MP4':
  Metadata:
    encoder         : Lavf58.12.100
    Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuvj420p(pc, bt709), 2704x1520 [SAR 1:1 DAR 169:95], q=2-31, 66005 kb/s, 0.02 fps, 59.94 tbr, 60k tbn, 60k tbc
    Metadata:
      creation_time   : 2018-07-15T16:08:22.000000Z
      handler_name    : GoPro AVC
      encoder         : GoPro AVC encoder
      timecode        : 16:23:48:21
    Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 189 kb/s
    Metadata:
      creation_time   : 2018-07-15T16:08:22.000000Z
      handler_name    : GoPro AAC
      timecode        : 16:23:48:21
Stream mapping:
  Stream #0:0 -> #0:0 (copy)
  Stream #0:1 -> #0:1 (copy)
Press [q] to stop, [?] for help


  



  The warnings Could not find codec parameters are especially interesting and Stream mapping shows that only the video and audio streams are mapped. I've played around with map_metadata to no avail. I may not have the format right but it seems more likely that the issue is related to the warning as the codecs are not recognized and I would expect all streams to be mapped by default.

  



  I would expect or hope for an answer that ignore the warnings and map the unrecognized streams without attempting to understand them.

  



  Any help is appreciated.

  


• GDPR compliance for Matomo’s Premium Features like Heatmaps & Session Recording, Form Analytics, Media Analytics & co

  27 avril 2018, par InnoCraft

  The General Data Protection Regulation (EU) 2016/679, also referred to as RGPD in French, Datenschutz-Grundverordnung, DS-GVO in German, is fast-approaching. It is now less than 30 days until GDPR applies to most businesses around the world on 25th May 2018. If you haven’t heard of this new regulation yet, I recommend you check out our GDPR guide which we continue to expand regularly to get you up to speed with it.

  GDPR compliance in Matomo

  We are currently adding several new features to Matomo to get you GDPR ready. You will have for example the possibility to delete and export data for data subjects, delete and anonymize previously tracked data, anonymize the IP address and location, ask for consent, and more. A beta version with these features is already available. We will release more blog posts and user guides about these features soon and just recently published a post on how to avoid collecting personal information in the first place soon.

  If you are still using Piwik, we highly recommend you update to a recent version of Matomo as all versions of Piwik will NOT be GDPR compliant.

  GDPR compliance for premium features

  InnoCraft, the company of the makers of Matomo, are offering various premium features for your self-hosted Matomo so you can be sure to make the right decisions and continuously grow your business. These features are also available on the cloud-hosted version of Matomo.

  If you are now wondering how GDPR applies to these features, you will be happy to hear that none of them collect any personal information except for possibly Heatmaps & Session Recording and the WooCommerce integration. All of them also support all the new upcoming GDPR features like the possibility to export and delete data. It is important that you update your Matomo Premium Features to the latest version to use these features.

  Making Heatmaps & Session Recording GDPR compliant

  We have added several new features to make it easy for you to be GDPR compliant and in many cases you might not even have to do anything. Some of the changes include :

  • Keystrokes (text entered into form fields) are no longer captured by default.
  • You may enable the capturing of keystrokes, and all keystrokes will be anonymized by default.
  • You may whitelist certain form fields to be recorded in plain text. However, fields that likely contain personal or sensitive information like passwords, phone numbers, addresses, credit card details, names, email addresses, and more will be always anonymized to protect user privacy. (this has always been the case but we have now included many more fields).

  How personal information may still be recorded

  Nevertheless, Heatmaps and Session Recordings may still record personal or sensitive information if you show them as part of the regular website as plain text (and not as part of a form field). The below example shows an email address for a paypal account as well as a name and VAT information as a regular content.

  

  To anonymize such information, simply add a data-matomo-mask attribute to your website :

  <span data-matomo-mask>example@example.com</span>

  You can read more about this in the developer guide “Masking content on your website”.

  WooCommerce Integration

  The WooCommerce integration may record an Order ID when a customer purchases something on your shop. As the Order ID is an identifier which could be linked with your shop to identify an individual, it may be considered as personal information. Matomo now offers an option to automatically anonymize this Order ID so it is no longer considered as personal information. To enable this feature, log in to your Matomo and go to “Administration => Anonymize Data”.

  GDPR compliance for third party plugins on the Matomo Marketplace

  The Matomo Marketplace currently features over 80 free plugins. Over 50 of them are compatible with the latest Matomo 3.X version and most of them should support Matomo’s new GDPR features out of the box. If you are concerned by GDPR and are not sure if a third party plugin stores any personal information, we highly recommend you ask the developer of this plugin about the compliance.

  You can find a link to the plugin’s issue tracker by going to a plugin page and then clicking on “Github” on the bottom right.

  

  If you are a plugin developer, please read our developer guide “GDPR & How do I make my Matomo plugin compliant”.

  The post GDPR compliance for Matomo’s Premium Features like Heatmaps & Session Recording, Form Analytics, Media Analytics & co appeared first on Analytics Platform - Matomo.

• mp4 plays only sound but no video on ios

  5 avril 2018, par Chen

  I have a video that I get from a third party provide in my App, I want to play using react-native-video. It works fine on simulator, but on a real iphone 7 it has only sound but no video.

  After further research I found, when I try to airdrop/move via itunes the video to my iphone. It shows something like the following :

  

  I have checked the codec with ffprobe and here is the output.
  ```

  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'bad.mp4':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: mp42mp41
  
      creation_time   : 2018-03-28T21:30:13.000000Z
  
    Duration: 00:00:45.55, start: 0.000000, bitrate: 1373 kb/s
  
      Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 1920x1080 [SAR 1:1 DAR 16:9], 1042 kb/s, 29.97 fps, 29.97 tbr, 30k tbn, 59.94 tbc (default)
  
      Metadata:
  
        creation_time   : 2018-03-28T21:30:13.000000Z
  
        handler_name    : Alias Data Handler
  
        encoder         : AVC Coding
  
      Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 317 kb/s (default)
  
      Metadata:
  
        creation_time   : 2018-03-28T21:30:13.000000Z
  
        handler_name    : Alias Data Handler
  
  [STREAM]
  
  index=0
  
  codec_name=h264
  
  codec_long_name=H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
  
  profile=High
  
  codec_type=video
  
  codec_time_base=1001/60000
  
  codec_tag_string=avc1
  
  codec_tag=0x31637661
  
  width=1920
  
  height=1080
  
  coded_width=1920
  
  coded_height=1080
  
  has_b_frames=1
  
  sample_aspect_ratio=1:1
  
  display_aspect_ratio=16:9
  
  pix_fmt=yuv420p
  
  level=41
  
  color_range=tv
  
  color_space=bt709
  
  color_transfer=bt709
  
  color_primaries=bt709
  
  chroma_location=left
  
  field_order=unknown
  
  timecode=N/A
  
  refs=1
  
  is_avc=true
  
  nal_length_size=4
  
  id=N/A
  
  r_frame_rate=30000/1001
  
  avg_frame_rate=30000/1001
  
  time_base=1/30000
  
  start_pts=0
  
  start_time=0.000000
  
  duration_ts=1365364
  
  duration=45.512133
  
  bit_rate=1042237
  
  max_bit_rate=N/A
  
  bits_per_raw_sample=8
  
  nb_frames=1364
  
  nb_read_frames=N/A
  
  nb_read_packets=N/A
  
  DISPOSITION:default=1
  
  DISPOSITION:dub=0
  
  DISPOSITION:original=0
  
  DISPOSITION:comment=0
  
  DISPOSITION:lyrics=0
  
  DISPOSITION:karaoke=0
  
  DISPOSITION:forced=0
  
  DISPOSITION:hearing_impaired=0
  
  DISPOSITION:visual_impaired=0
  
  DISPOSITION:clean_effects=0
  
  DISPOSITION:attached_pic=0
  
  DISPOSITION:timed_thumbnails=0
  
  TAG:creation_time=2018-03-28T21:30:13.000000Z
  
  TAG:language=eng
  
  TAG:handler_name=Alias Data Handler
  
  TAG:encoder=AVC Coding
  
  [/STREAM]
  
  [STREAM]
  
  index=1
  
  codec_name=aac
  
  codec_long_name=AAC (Advanced Audio Coding)
  
  profile=LC
  
  codec_type=audio
  
  codec_time_base=1/48000
  
  codec_tag_string=mp4a
  
  codec_tag=0x6134706d
  
  sample_fmt=fltp
  
  sample_rate=48000
  
  channels=2
  
  channel_layout=stereo
  
  bits_per_sample=0
  
  id=N/A
  
  r_frame_rate=0/0
  
  avg_frame_rate=0/0
  
  time_base=1/48000
  
  start_pts=0
  
  start_time=0.000000
  
  duration_ts=2184582
  
  duration=45.512125
  
  bit_rate=317375
  
  max_bit_rate=458625
  
  bits_per_raw_sample=N/A
  
  nb_frames=2135
  
  nb_read_frames=N/A
  
  nb_read_packets=N/A
  
  DISPOSITION:default=1
  
  DISPOSITION:dub=0
  
  DISPOSITION:original=0
  
  DISPOSITION:comment=0
  
  DISPOSITION:lyrics=0
  
  DISPOSITION:karaoke=0
  
  DISPOSITION:forced=0
  
  DISPOSITION:hearing_impaired=0
  
  DISPOSITION:visual_impaired=0
  
  DISPOSITION:clean_effects=0
  
  DISPOSITION:attached_pic=0
  
  DISPOSITION:timed_thumbnails=0
  
  TAG:creation_time=2018-03-28T21:30:13.000000Z
  
  TAG:language=eng
  
  TAG:handler_name=Alias Data Handler
  
  [/STREAM]

  Then I tried VLC on iOS the video played without problem (it has both video and sound), except at the beginning it shows a grey pixel screen.

  

  Next, what i did was using ffmpeg to re-encode the video stream via :

  ffmpeg -i bad.mp4 -c:a copy new.mp4

  After this new.mp4 plays with no problem.
  This is really confusing as the codec does not change and both videos works with no problem on my Mac.

  I have tried to play around with the b_frames, profile level on the new video to reproduce the problem but with no luck.

  I really do not want to process every video via ffmpeg after get it from the third party. Just wondering what might be the problem with the video ?