Recherche avancée

Sur d’autres sites (3319)

• slowing down a video with ffmpeg

  20 août 2014, par jeet

  I’m making a video using ffmpeg & multiple images with this command :

  ffmpeg -f image2 -i img%d.png v.mpg

  The video is made, but plays very fast. Can I slow it down a bit ? (double duration nearly)
  If possible set the speed while creation itself please.

  I also need to add an audio "a.wav" to the video being made, possibly in the same command. Is that possible ?

  Please give me the commands
  Thanks

  When I use this command, below is the error I get :

  ffmpeg -r 12 -i pic\s%d.png -i rmt.wav -shortest -r 25 v.mpg
  
  
  
  
  
  
  
  FFmpeg version SVN-r16573, Copyright (c) 2000-2009 Fabrice Bellard, et al.
  
  configuration: --extra-cflags=-fno-common --enable-memalign-hack --enable-pthreads --enable-libmp3lame --enable-libxvid --enable-libvorbis --enable-libtheora --enable-libspeex --enable-libfaac --enable-libgsm --enable-libx264 --enable-libschroedinger --enable-avisynth --enable-swscale --enable-gpl
  
  libavutil     49.12. 0 / 49.12. 0
  
  libavcodec    52.10. 0 / 52.10. 0
  
  libavformat   52.23. 1 / 52.23. 1
  
  libavdevice   52. 1. 0 / 52. 1. 0
  
  libswscale     0. 6. 1 /  0. 6. 1
  
  built on Jan 13 2009 02:57:09, gcc: 4.2.4
  
  Input #0, image2, from 'pic\s%d.png':
  
  Duration: 00:03:53.00, start: 0.000000, bitrate: N/A
  
  Stream #0.0: Video: png, rgb24, 1366x768, 12.00 tb(r)
  
  Input #1, wav, from 'rmt.wav':
  
  Duration: 00:12:16.19, bitrate: 64 kb/s
  
  Stream #1.0: Audio: pcm_u8, 8000 Hz, mono, s16, 64 kb/s
  
  Stream #0.0: Video: mpeg1video, yuv420p, 1366x768, q=2-31, 200 kb/s, 25.00 tb(c)
  
  Stream #0.1: Audio: mp2, 8000 Hz, mono, s16, 64 kb/s
  
  Stream mapping:
  
  Stream #0.0 -> #0.0
  
  Stream #1.0 -> #0.1
  
  [mp2 @ 0x1738390]Sampling rate 8000 is not allowed in mp2
  
  Error while opening codec for output stream #0.1 - maybe incorrect parameters such as bit_rate, rate, width or height

• ffmpeg to convert mov to flv

  27 octobre 2014, par jeet

  I’m trying to convert a mov video to flv, but keep getting these errors below.
  There are 2 commands I used, both are below.

  ffmpeg -y -i video.mov -deinterlace -acodec copy -r 25 -qmin 3 -qmax 6 video.flv
  
  
  
  
  
  FFmpeg version SVN-r16573, Copyright (c) 2000-2009 Fabrice Bellard, et al.
  
  configuration: --extra-cflags=-fno-common --enable-memalign-hack --enable-pthreads --enable-libmp3lame --enable-libxvid --enable-libvorbis --enable-libtheora --enable-libspeex --enable-libfaac --enable-libgsm --enable-libx264 --enable-libschroedinger --enable-avisynth --enable-swscale --enable-gpl
  
  libavutil     49.12. 0 / 49.12. 0
  
  libavcodec    52.10. 0 / 52.10. 0
  
  libavformat   52.23. 1 / 52.23. 1
  
  libavdevice   52. 1. 0 / 52. 1. 0
  
  libswscale     0. 6. 1 /  0. 6. 1
  
  built on Jan 13 2009 02:57:09, gcc: 4.2.4
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'vid\video.mov':
  
  Duration: 00:03:16.00, start: 0.000000, bitrate: 398 kb/s
  
  Stream #0.0(eng): Video: mpeg4, yuv420p, 800x600 [PAR 1:1 DAR 4:3], 30.00 tb(r)
  
  Stream #0.1(eng): Audio: pcm_u8, 8000 Hz, mono, s16, 64 kb/s
  
  Output #0, flv, to 'vid\video.flv':
  
  Stream #0.0(eng): Video: flv, yuv420p, 800x600 [PAR 1:1 DAR 4:3], q=3-6, 200 kb/s, 25.00 tb(c)
  
  Stream #0.1(eng): Audio: pcm_u8, 8000 Hz, mono, s16, 64 kb/s
  
  Stream mapping:
  
  Stream #0.0 -> #0.0
  
  Stream #0.1 -> #0.1
  
  [NULL @ 0x1714390]codec not compatible with flv
  
  Could not write header for output file #0 (incorrect codec parameters ?)

  Second command :

  ffmpeg -y -i video.mov -deinterlace -ar 44100 -r 25 -qmin 3 -qmax 6 video.flv

  Audio resampler only works with 16 bits per sample, patch welcome.

  With a newer version of ffmpeg :

  ffmpeg version N-49610-gc2dd5a1 Copyright (c) 2000-2013 the FFmpeg developers
  
  built on Feb  5 2013 13:20:59 with gcc 4.7.2 (GCC)
  
  configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-libass --enable-libbluray --enable-libcaca --enable-libfreetype --enable-libgsm --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib
  
    libavutil      52. 17.101 / 52. 17.101
  
    libavcodec     54. 91.100 / 54. 91.100
  
    libavformat    54. 61.104 / 54. 61.104
  
    libavdevice    54.  3.103 / 54.  3.103
  
    libavfilter     3. 35.101 /  3. 35.101
  
    libswscale      2.  2.100 /  2.  2.100
  
    libswresample   0. 17.102 /  0. 17.102
  
    libpostproc    52.  2.100 / 52.  2.100
  
  Guessed Channel Layout for  Input Stream #0.1 : mono
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'vid\video.mov':
  
    Metadata:
  
      major_brand     : qt  
  
      minor_version   : 512
  
      compatible_brands: qt  
  
      creation_time   : 1970-01-01 00:00:00
  
    Duration: 00:02:50.39, start: 0.000000, bitrate: 370 kb/s
  
      Stream #0:0(eng): Video: mpeg4 (Simple Profile) (mp4v / 0x7634706D), yuv420p, 1366x768 [SAR 1:1 DAR 683:384], 308 kb/s, 11.50 fps, 11.50 tbr, 23 tbn, 23 tbc
  
      Metadata:
  
        creation_time   : 1970-01-01 00:00:00
  
        handler_name    : DataHandler
  
      Stream #0:1(eng): Audio: pcm_u8 (raw  / 0x20776172), 8000 Hz, mono, u8, 64 kb/s
  
      Metadata:
  
        creation_time   : 1970-01-01 00:00:00
  
        handler_name    : DataHandler
  
  [flv @ 026347a0] FLV does not support sample rate 8000, choose from (44100, 22050, 11025)
  
  Output #0, flv, to 'vid\video.flv':
  
    Metadata:
  
      major_brand     : qt  
  
      minor_version   : 512
  
  compatible_brands: qt  
  
      encoder         : Lavf54.61.104
  
      Stream #0:0(eng): Video: flv1 ([2][0][0][0] / 0x0002), yuv420p, 1366x768 [SAR 1:1 DAR 683:384], q=2-31, 200 kb/s, 1k tbn, 11.50 tbc
  
      Metadata:
  
        creation_time   : 1970-01-01 00:00:00
  
        handler_name    : DataHandler
  
      Stream #0:1(eng): Audio: mp3 ([2][0][0][0] / 0x0002), 8000 Hz, mono, s16p
  
      Metadata:
  
        creation_time   : 1970-01-01 00:00:00
  
        handler_name    : DataHandler
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (mpeg4 -> flv)
  
    Stream #0:1 -> #0:1 (pcm_u8 -> libmp3lame)
  
  Could not write header for output file #0 (incorrect codec parameters ?): Invalid data found when processing input

  1 more thing please :
  If I use this newer version of ffmpeg to create a video with the below command, I get a video with a very hazy display.
  It’s like a few black dots on a blank screen :

  ffmpeg -i img%d.png -i audio.wav -acodec copy output.mov

  what could be the reason for this display ?

• Your Essential SOC 2 Compliance Checklist

  11 mars, par Daniel Crough — Privacy, Security

  With cloud-hosted applications becoming the norm, organisations face increasing data security and compliance challenges. SOC 2 (System and Organisation Controls 2) provides a structured framework for addressing these challenges. Established by the American Institute of Certified Public Accountants (AICPA), SOC 2 has become a critical standard for demonstrating trustworthiness to clients and partners.

  A well-structured SOC 2 compliance checklist serves as your roadmap to successful audits and effective security practices. In this post, we’ll walk through the essential steps to achieve SOC 2 compliance and explain how proper analytics practices play a crucial role in maintaining this important certification.

  Download SOC2 Checklist

  

  What is SOC 2 compliance ?

  SOC 2 compliance applies to service organisations that handle sensitive customer data. While not mandatory, this certification builds significant trust with customers and partners.

  According to the AICPA, “SOC 2 reports are intended to meet the needs of a broad range of users that need detailed information and assurance about the controls at a service organisation relevant to security, availability, and processing integrity of the systems the service organisation uses to process users’ data and the confidentiality and privacy of the information processed by these systems.“

  At its core, SOC 2 helps organisations protect customer data through five fundamental principles : security, availability, processing integrity, confidentiality, and privacy.

  Think of it as a seal of approval that tells customers, “We take data protection seriously, and here’s the evidence.”

  Companies undergo SOC 2 audits to evaluate their compliance with these standards. During these audits, independent auditors assess internal controls over data security, availability, processing integrity, confidentiality, and privacy.

  What is a SOC 2 compliance checklist ?

  A SOC 2 compliance checklist is a comprehensive guide that outlines all the necessary steps and controls an organisation needs to implement to achieve SOC 2 certification. It covers essential areas including :

  • Security policies and procedures
  • Access control measures
  • Risk assessment protocols
  • Incident response plans
  • Disaster recovery procedures
  • Vendor management practices
  • Data encryption standards
  • Network security controls

  SOC 2 compliance checklist benefits

  A structured SOC 2 compliance checklist offers several significant advantages :

  Preparedness

  Preparing for a SOC 2 examination involves many complex elements. A checklist provides a clear, structured path, breaking the process into manageable tasks that ensure nothing is overlooked.

  Resource optimisation

  A comprehensive checklist reduces time spent identifying requirements, minimises costly mistakes and oversights, and enables more precise budget planning for the compliance process.

  Better team alignment

  A SOC 2 checklist establishes clear responsibilities for team members and maintains consistent understanding across all departments, helping align internal processes with industry standards.

  Risk reduction

  Following a SOC 2 compliance checklist significantly reduces the risk of compliance violations. Systematically reviewing internal controls provides opportunities to catch security gaps early, mitigating the risk of data breaches and unauthorised access.

  Audit readiness

  A well-maintained checklist simplifies audit preparation, reduces stress during the audit process, and accelerates the certification timeline.

  Business growth

  A successful SOC 2 audit demonstrates your organisation’s commitment to data security, which can be decisive in winning new business, especially with enterprise clients who require this certification from their vendors.

  Challenges in implementing SOC 2

  Implementing SOC 2 presents several significant challenges :

  Time-intensive documentation

  Maintaining accurate records throughout the SOC 2 compliance process requires diligence and attention to detail. Many organisations struggle to compile comprehensive documentation of all controls, policies and procedures, leading to delays and increased costs.

  Incorrect scoping of the audit

  Misjudging the scope can result in unnecessary expenses and extended timelines. Including too many systems complicates the process and diverts resources from critical areas.

  Maintaining ongoing compliance

  After achieving initial compliance, continuous monitoring becomes essential but is often neglected. Regular internal control audits can be overwhelming, especially for smaller organisations without dedicated compliance teams.

  Resource constraints

  Many organisations lack sufficient resources to dedicate to compliance efforts. This limitation can lead to staff burnout or reliance on expensive external consultants.

  Employee resistance

  Staff members may view new security protocols as unnecessary hurdles. Employees who aren’t adequately trained on SOC 2 requirements might inadvertently compromise compliance efforts through improper data handling.

  Analytics and SOC 2 compliance : A critical relationship

  One often overlooked aspect of SOC 2 compliance is the handling of analytics data. User behaviour data collection directly impacts multiple Trust Service Criteria, particularly privacy and confidentiality.

  Why analytics matters for SOC 2

  Standard analytics platforms often collect significant amounts of personal data, creating potential compliance risks :

  1. Privacy concerns : Many analytics tools collect personal information without proper consent mechanisms
  2. Data ownership issues : When analytics data is processed on third-party servers, maintaining control becomes challenging
  3. Confidentiality risks : Analytics data might be shared with advertising networks or other third parties
  4. Processing integrity questions : When data is transformed or aggregated by third parties, verification becomes difficult

  How Matomo supports SOC 2 compliance

  

  Matomo’s privacy-first analytics approach directly addresses these concerns :

  1. Complete data ownership : With Matomo, all analytics data remains under your control, either on your own servers or in a dedicated cloud instance
  2. Consent management : Built-in tools for managing user consent align with privacy requirements
  3. Data minimisation : Configurable anonymisation features help reduce collection of sensitive personal data
  4. Transparency : Clear documentation of data flows supports audit requirements
  5. Configurable data retention : Set automated data deletion schedules to comply with your policies

  By implementing Matomo as part of your SOC 2 compliance strategy, you address key requirements while maintaining the valuable insights your organisation needs for growth.

  Conclusion

  A SOC 2 compliance checklist helps organisations meet critical security and privacy standards. By taking a methodical approach to compliance and implementing privacy-respecting analytics, you can build trust with customers while protecting sensitive data.

  Start your 21-day free trial — no credit card needed.