Recherche avancée

Sur d’autres sites (11074)

• Hello, I have some problems with ffmpeg.concat, there are logs

  12 mai 2022, par Matvey

  Log :

  


  [swscaler @ 0x27d3c10] [swscaler @ 0x2886fe0] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x27d3c10] [swscaler @ 0x283be10] deprecated pixel format used, make sure you did set range correctly
Output #0, avi, to '/home/pi/Desktop/VIDEOREG/2022:05:12_09:51:57:856_v1.avi':
  Metadata:
    software        : Lavf58.45.100
    ISFT            : Lavf59.20.101
  Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p(tv, bt470bg/unknown/unknown, progressive), 1080x720, q=2-31, 200 kb/s, 25 fps, 25>
    Metadata:
      encoder         : Lavc59.25.100 mpeg4
    Side data:
      cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: N/A
Output #0, avi, to '/home/pi/Desktop/VIDEOREG/2022:05:12_09:51:57:911_v3.avi':
  Metadata:
    software        : Lavf58.45.100
    ISFT            : Lavf59.20.101
  Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p(tv, bt470bg/unknown/unknown, progressive), 1080x720, q=2-31, 200 kb/s, 25 fps, 25>
    Metadata:
      encoder         : Lavc59.25.100 mpeg4
    Side data:
      cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: N/A
Output #0, avi, to '/home/pi/Desktop/VIDEOREG/2022:05:12_09:51:57:890_v2.avi':
  Metadata:
    software        : Lavf58.45.100
    ISFT            : Lavf59.20.101
  Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p(tv, bt470bg/unknown/unknown, progressive), 1080x720, q=2-31, 200 kb/s, 25 fps, 25>
    Metadata:
      encoder         : Lavc59.25.100 mpeg4
    Side data:
      cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: N/A
[mjpeg @ 0x27aaa10] mjpeg_decode_dc: bad vlc: 0:0 (0x27b7c20)trate=8122.4kbits/s speed=1.33e+04x
[mjpeg @ 0x27aaa10] error dc
[mjpeg @ 0x27aaa10] error y=18 x=37
[mjpeg @ 0x27aaa10] EOI missing, emulating
[mjpeg @ 0x29551c0] error count: 65
[mjpeg @ 0x29551c0] error y=2 x=17
###############################################


  


  My part of code for concatenation audio and video :

  


  def video_with_audio(number, filename, video):
        ms = datetime.today().strftime('%f') + '0000'
        ms = ms[:3]
        name = datetime.today().strftime('%Y:%m:%d_%H:%M:%S:')
        title_video = f'/home/pi/Desktop/VIDEOREG/{name}{ms}{number}.avi'
        print(title_video)
        os.system("ffmpeg -i " + video + " -vf setpts=PTS*2 " + title_video)
        ####################################################
        ms_1 = datetime.today().strftime('%f') + '0000'
        ms_1 = ms_1[:3]
        name_1 = datetime.today().strftime('%Y:%m:%d_%H:%M:%S:')
        title_video = f'/home/pi/Desktop/VIDEOREG/{name}{ms}{number}.avi'
        title_video_1 = f'/home/pi/Desktop/VIDEOREG/{name_1}{ms_1}{number}.avi'
        input_audio = ffmpeg.input(filename)
        input_video = ffmpeg.input(title_video)
        print(title_video_1)
        ffmpeg.concat(input_video, input_audio, v=1, a=1).output(title_video_1).run()


  


  There are slight delays during video recording, because I print information from sensors on video, can this affect the concatenation of video with audio ? (Saved video is accelerated ? that's why at the beginning I used slowing video down.)

  


• DTS Error when nesting `amix` filter in ffmpeg [closed]

  25 août 2023, par GBathie

  I am trying to create an audio file that contains multiple occurrences of other samples (think of music notes), using ffmpeg.

  


  I am using the following command :

  


  ffmpeg -f lavfi -i 'sine=frequency=87.31:sample_rate=44100' -f lavfi -i 'sine=frequency=783.99:sample_rate=44100' -filter_complex '[0]asplit=2[s0][s1];[s0]atrim=duration=0.157[s2];[s1]atrim=duration=1.157[s3];[s2][s3]amix=inputs=2[s4];[1]atrim=duration=0.165[s5];[s4][s5]amix=inputs=2[s6]' -map '[s6]' test.mp3 -y


  


  It generates two sine waves in place of notes, and builds a file containing the first note twice, and the second note once.
I then mix the result using two amix filters. I cannot use a single amix filter because, in practice, I have more notes that the maximum number of inputs that amix can take (1024).

  


  The graph looks like this :


  


  Running this commands gives me the following output, which complains about "Queue input backwards in time" :

  


  
ffmpeg version 4.2.7-0ubuntu0.1 Copyright (c) 2000-2022 the FFmpeg developers
  built with gcc 9 (Ubuntu 9.4.0-1ubuntu1~20.04.1)
  configuration: --prefix=/usr --extra-version=0ubuntu0.1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-avresample --disable-filter=resample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librsvg --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-nvenc --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared
  libavutil      56. 31.100 / 56. 31.100
  libavcodec     58. 54.100 / 58. 54.100
  libavformat    58. 29.100 / 58. 29.100
  libavdevice    58.  8.100 / 58.  8.100
  libavfilter     7. 57.100 /  7. 57.100
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  5.100 /  5.  5.100
  libswresample   3.  5.100 /  3.  5.100
  libpostproc    55.  5.100 / 55.  5.100
Input #0, lavfi, from 'sine=frequency=87.31:sample_rate=44100':
  Duration: N/A, start: 0.000000, bitrate: 705 kb/s
    Stream #0:0: Audio: pcm_s16le, 44100 Hz, mono, s16, 705 kb/s
Input #1, lavfi, from 'sine=frequency=783.99:sample_rate=44100':
  Duration: N/A, start: 0.000000, bitrate: 705 kb/s
    Stream #1:0: Audio: pcm_s16le, 44100 Hz, mono, s16, 705 kb/s
Stream mapping:
  Stream #0:0 (pcm_s16le) -> asplit
  Stream #1:0 (pcm_s16le) -> atrim
  amix -> Stream #0:0 (libmp3lame)
Press [q] to stop, [?] for help
Output #0, mp3, to 'test.mp3':
  Metadata:
    TSSE            : Lavf58.29.100
    Stream #0:0: Audio: mp3 (libmp3lame), 44100 Hz, mono, fltp (default)
    Metadata:
      encoder         : Lavc58.54.100 libmp3lame
[libmp3lame @ 0x557929fb5400] Queue input is backward in time
    Last message repeated 1 times
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854774620
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775760
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775632
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775504
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775376
[libmp3lame @ 0x557929fb5400] Queue input is backward in time
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775248
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775120
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854774992
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854774864
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775760
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775632
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775504
[libmp3lame @ 0x557929fb5400] Queue input is backward in time
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775376
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775248
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775120
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854774992
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854774864
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775760
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775632
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775504
[libmp3lame @ 0x557929fb5400] Queue input is backward in time
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775376
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775248
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775120
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854774992
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854774864
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775760
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775632
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775504
[libmp3lame @ 0x557929fb5400] Queue input is backward in time
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775376
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775248
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775120
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854774992
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854774864
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775760
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775632
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775504
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775376
[mp3 @ 0x557929fb7280] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 6959 >= -9223372036854775248
size=      10kB time=00:00:00.18 bitrate= 428.0kbits/s speed=22.2x    
video:0kB audio:9kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 2.361386%


  


  Q : What is the issue, and how can I solve it ?

  


  Note that the issue disappears if I use a single amix filter, but I cannot do this in practice.

  


• Protecting consumer privacy : How to ensure CCPA compliance

  18 août 2023, par Erin — CCPA, Privacy

  The California Consumer Privacy Act (CCPA) is a state law that enhances privacy rights and consumer protection for residents of California. 

  It grants consumers six rights, like the right to know what personal information is being collected about them by businesses and others. 

  CCPA also requires businesses to provide notice of data collection practices. Consumers can choose to opt out of the sale of their data. 

  In this article, we’ll learn more about the scope of CCPA, the penalties for non-compliance and how our web analytics tool, Matomo, can help you create a CCPA-compliant framework.

  What is the CCPA ? 

  CCPA was implemented on January 1, 2020. It ensures that businesses securely handle individuals’ personal information and respect their privacy in the digital ecosystem. 

  

  CCPA addresses the growing concerns over privacy and data protection ; 40% of US consumers share that they’re worried about digital privacy. With the increasing amount of personal information being collected and shared by businesses, there was a need to establish regulations to provide individuals with more control and transparency over their data. 

  CCPA aims to protect consumer privacy rights and promote greater accountability from businesses when handling personal information.

  Scope of CCPA 

  The scope of CCPA includes for-profit businesses that collect personal information from California residents, regardless of where you run the business from.

  It defines three thresholds that determine the inclusion criteria for businesses subject to CCPA regulations. 

  Businesses need to abide by CCPA if they meet any of the three options :

  1. Revenue threshold : Have an annual gross revenue of over $25 million.
  2. Consumer threshold : Businesses that purchase, sell or distribute the personal information of 100,000 or more consumers, households or devices.
  3. Data threshold : Businesses that earn at least half of their revenue annually from selling the personal information of California residents.

  What are the six consumer rights under the CCPA ? 

  Here’s a short description of the six consumer rights. 

  

  1. Right to know : Under this right, you can ask a business to disclose specific personal information they collect about you and the categories of sources of the information. You can also know the purpose of collection and to which third-party the business will disclose this info. This allows consumers to understand what information is being held and how it is used. You can request this info for free twice a year.
  2. Right to delete : Consumers can request the deletion of their personal information. Companies must comply with some exceptions.
  3. Right to opt-out : Consumers can deny the sale of their personal information. Companies must provide a link on their homepage for users to exercise this right. After you choose this, companies can’t sell your data unless you authorise them to do so later.
  4. Right to non-discrimination : Consumers cannot be discriminated against for exercising their CCPA rights. For instance, a company cannot charge different prices, provide a different quality of service or deny services.
  5. Right to correct : Consumers can request to correct inaccurate personal information.

  6. Right to limit use : Consumers can specify how they want the businesses to use their sensitive personal information. This includes social security numbers, financial account details, precise geolocation data or genetic data. Consumers can direct businesses to use this sensitive information only for specific purposes, such as providing the requested services.

  Penalties for CCPA non-compliance 

  52% of organisations have yet to adopt CCPA principles as of 2022. Non-compliance can attract penalties.

  

  Section 1798.155 of the CCPA states that any business that doesn’t comply with CCPA’s terms can face penalties based on the consumer’s private right to action. Consumers can directly take the company to the civil court and don’t need prosecutors’ interventions. 

  Businesses get a chance of 30 days to make amends for their actions. 

  If that’s also not possible, the business may receive a civil penalty of up to $2,500 per violation. Violations can be of any kind, even accidental. An intentional violation can attract a fine of $7,500. 

  Consumers can also initiate private lawsuits to claim damages that range from $100 to $750, or actual damages (whichever is higher), for each occurrence of their unredacted and unencrypted data being breached on a business’s server.

  CCPA vs. GDPR 

  Both CCPA and GDPR aim to enhance individuals’ control over their personal information and provide transparency about how their data is collected, used and shared. The comparison between the CCPA and GDPR is crucial in understanding the regulatory framework of data protection laws.

  Here’s how CCPA and GDPR differ :

  Scope

  • CCPA is for businesses that meet specific criteria and collect personal information from California residents. 
  • GDPR (General Data Protection Regulation) applies to businesses that process the personal data of citizens and residents of the European Union.

  Definition of personal information

  • CCPA includes personal information broadly, including identifiers such as IP addresses and households. Examples include name, email id, location and browsing history. However, it excludes HIPAA-protected medical data, clinical trial data and other personal information from government records.
  • GDPR covers any personal data relating to an identified or identifiable individual, excluding households. Examples include the phone number, email address and personal identification number. It excludes anonymous and deceased person’s data.

  

  Consent

  • Under the CCPA, consumers can opt out of the sale of their personal information.
  • GDPR states that organisations should obtain explicit consent from individuals for processing their personal data.

  Rights

  • CCPA grants the right to know what personal information is being collected and the right to request deletion of their personal information.
  • GDPR also gives individuals various rights, such as the right to access and rectify their personal data, the right to erasure (also known as the right to be forgotten) and also the right to data portability. 

  Enforcement

  • For CCPA, businesses may have to pay $7,500 for each violation. 
  • GDPR has stricter penalties for non-compliance, with fines of up to 4% of the global annual revenue of a company or €20 million, whichever is higher.

  A 5-step CCPA compliance framework 

  Here’s a simple framework you can follow to ensure compliance with CCPA. Alongside this, we’ll also share how Matomo can help. 

  Matomo is an open-source web analytics platform trusted by organisations like the United Nations, NASA and more. It provides valuable insights into website traffic, visitor behaviour and marketing effectiveness. More than 1 million websites and apps (approximately 1% of the internet !) use our solution, and it’s available in 50+ languages. Below, we’ll share how you can use Matomo to be CCPA compliant.

  1. Assess data

  First, familiarise yourself with the California Consumer Privacy Act and check your eligibility for CCPA compliance. 

  For example, as mentioned earlier, one threshold is : purchases, receives or sells the personal data of 100,000 or more individuals or households. 

  But how do you know if you have crossed 100K ? With Matomo ! 

  Go to last year’s calendar, select visitors, then go to locations and under the “Region” option, check for California. If you’ve crossed 100K visitors, you know you have to become CCPA compliant.

  

  Identify and assess the personal information you collect with Matomo.

  2. Evaluate privacy practices

  Review the current state of your privacy policies and practices. Conduct a thorough assessment of data sharing and third-party agreements. Then, update policies and procedures to align with CCPA requirements.

  For example, you can anonymise IP addresses with Matomo to ensure that user data collected for web analytics purposes cannot be used to trace back to specific individuals.

  

  If you have a consent management solution to honour user requests for data privacy, you can also integrate Matomo with it. 

  3. Communicate 

  Inform consumers about their CCPA rights and how you handle their data.

  Establish procedures for handling consumer requests and obtaining consent. For example, you can add an opt-out form on your website with Matomo. Or you can also use Matomo to disable cookies from your website.

  

  Documenting your compliance efforts, including consumer requests and how you responded to them, is a good idea. Finally, educate staff on CCPA compliance and their responsibilities to work collaboratively.

  4. Review vendor contracts

  Assessing vendor contracts allows you to determine if they include necessary data processing agreements. You can also identify if vendors are sharing personal information with third parties, which could pose a compliance risk. Verify if vendors have adequate security measures in place to protect the personal data they handle.

  That’s why you can review and update agreements to include provisions for data protection, privacy and CCPA requirements.

  Establish procedures to monitor and review vendor compliance with CCPA regularly. This may include conducting audits, requesting certifications and implementing controls to mitigate risks associated with vendors handling personal data.

  5. Engage legal counsel

  Consider consulting with legal counsel to ensure complete understanding and compliance with CCPA regulations.

  Finally, stay updated on any changes or developments related to CCPA and adjust your compliance efforts accordingly.

  Matomo and CCPA compliance 

  There’s an increasing emphasis on privacy regulations like CCPA. Matomo offers a robust solution that allows businesses to be CCPA-compliant without sacrificing the ability to track and analyse crucial data.

  You can gain in-depth insights into user behaviour and website performance — all while prioritising data protection and privacy. 

  Request a demo or sign up for a free 21-day trial to get started with our powerful CCPA-compliant web analytics platform — no credit card required. 

  Disclaimer

  We are not lawyers and don’t claim to be. The information provided here is to help give an introduction to CCPA. We encourage every business and website to take data privacy seriously and discuss these issues with your lawyer if you have any concerns.