Recherche avancée

Sur d’autres sites (5886)

• What is the best way to split a transport stream file ?

  27 mars 2016, par scaryguy

  I have a .ts file (Download files here : http://dropcanvas.com/2gmsg/1).

  I want to split this video while I expect ALL other properties remain same including pts time.

  Here is what I try to achieve this :

  ffmpeg -ss 0.000 -i sample.ts -y -c copy -t 3 splitted.ts

  Expected start time : 94678.950389
  New start time : 1.402367

  I expect the above command should only take first 3 seconds of the .ts file and all other stuff to stay same. I’ve seen copyts and copytb options from the documentation but I wasn’t able to use them.

  So how do I do this ?

  Thank you

  Here are the logs for copyts. It creates a 0 byte splitted.ts file :

  ffmpeg -ss 0:00:00 -i sample.ts -to 00:00:03 -y -c copy -copyts splitted.ts
  
  ffmpeg version 3.0 Copyright (c) 2000-2016 the FFmpeg developers
  
    built with Apple LLVM version 7.0.0 (clang-700.0.72)
  
    configuration: --prefix=/usr/local/Cellar/ffmpeg/3.0 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-opencl --enable-libx264 --enable-libmp3lame --enable-libxvid --enable-libfreetype --enable-libvorbis --enable-libvpx --enable-libass --enable-ffplay --enable-libfdk-aac --enable-libopus --enable-libx265 --enable-nonfree --enable-vda
  
    libavutil      55. 17.103 / 55. 17.103
  
    libavcodec     57. 24.102 / 57. 24.102
  
    libavformat    57. 25.100 / 57. 25.100
  
    libavdevice    57.  0.101 / 57.  0.101
  
    libavfilter     6. 31.100 /  6. 31.100
  
    libavresample   3.  0.  0 /  3.  0.  0
  
    libswscale      4.  0.100 /  4.  0.100
  
    libswresample   2.  0.101 /  2.  0.101
  
    libpostproc    54.  0.100 / 54.  0.100
  
  [NULL @ 0x7fafac02fc00] start time for stream 2 is not set in estimate_timings_from_pts
  
  Input #0, mpegts, from 'sample.ts':
  
    Duration: 00:00:10.07, start: 94678.950389, bitrate: 934 kb/s
  
    Program 1
  
      Stream #0:0[0x100]: Video: h264 (Main) ([27][0][0][0] / 0x001B), yuv420p, 854x480 [SAR 1280:1281 DAR 16:9], 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc
  
      Stream #0:1[0x101]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 44100 Hz, stereo, fltp, 140 kb/s
  
      Stream #0:2[0x102]: Data: timed_id3 (ID3  / 0x20334449)
  
  Output #0, mpegts, to 'splitted.ts':
  
    Metadata:
  
      encoder         : Lavf57.25.100
  
      Stream #0:0: Video: h264 ([27][0][0][0] / 0x001B), yuv420p, 854x480 [SAR 1280:1281 DAR 16:9], q=2-31, 29.97 fps, 29.97 tbr, 90k tbn, 90k tbc
  
      Stream #0:1: Audio: aac (LC) ([15][0][0][0] / 0x000F), 44100 Hz, stereo, 140 kb/s
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (copy)
  
    Stream #0:1 -> #0:1 (copy)
  
  Press [q] to stop, [?] for help
  
  frame=    0 fps=0.0 q=-1.0 Lsize=       0kB time=00:00:00.00 bitrate=N/A speed=   0x
  
  video:0kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
  
  Output file is empty, nothing was encoded (check -ss / -t / -frames parameters if used)

• FFMPEG no audio get recorded from RTSP stream

  22 mars 2016, par Haris

  I am trying to record rtsp stream on HLS format. I need to record both audio and video. Using below command the video and audio get recorded for some stream like a test rtsp stream from Internet rtsp ://wowzaec2demo.streamlock.net/vod/mp4:BigBuckBunny_115k.mov. Where as for my IP camera it doesn’t work, means the video get recorded but no audio on output file.

  ./ffmpeg -i rtsp://10.0.8.152:554/media/live/1/1 -acodec copy -vcodec copy -hls_list_size 65535 -hls_time 2 "./live.m3u8"

  Here is the command line output for my IP camera while start recording with above command.

  ffmpeg version 3.0 Copyright (c) 2000-2016 the FFmpeg developers
  
    built with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5)
  
    configuration: --enable-gpl --enable-libx264 --enable-libfreetype --enable-filter=drawtext --prefix=../build_Mar-20-2016
  
    libavutil      55. 17.103 / 55. 17.103
  
    libavcodec     57. 24.102 / 57. 24.102
  
    libavformat    57. 25.100 / 57. 25.100
  
    libavdevice    57.  0.101 / 57.  0.101
  
    libavfilter     6. 31.100 /  6. 31.100
  
    libswscale      4.  0.100 /  4.  0.100
  
    libswresample   2.  0.101 /  2.  0.101
  
    libpostproc    54.  0.100 / 54.  0.100
  
  Guessed Channel Layout for  Input Stream #0.1 : mono
  
  Input #0, rtsp, from 'rtsp://10.0.8.152:554/media/live/1/1':
  
    Metadata:
  
      title           : NVT
  
      comment         : From NVT
  
    Duration: N/A, start: 0.000000, bitrate: N/A
  
      Stream #0:0: Video: h264 (Baseline), yuvj420p(pc), 1280x720, 15 fps, 15 tbr, 90k tbn, 30 tbc
  
      Stream #0:1: Audio: pcm_alaw, 8000 Hz, 1 channels, s16, 64 kb/s
  
  Output #0, hls, to './live.m3u8':
  
    Metadata:
  
      title           : NVT
  
      comment         : From NVT
  
      encoder         : Lavf57.25.100
  
      Stream #0:0: Video: h264, yuvj420p, 1280x720, q=2-31, 15 fps, 15 tbr, 90k tbn, 15 tbc
  
      Stream #0:1: Audio: pcm_alaw, 8000 Hz, mono, 64 kb/s
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (copy)
  
    Stream #0:1 -> #0:1 (copy)
  
  Press [q] to stop, [?] for help
  
  [hls @ 0x33de8c0] Non-monotonous DTS in output stream 0:0; previous: 35985, current: 6000; changing to 35986. This may result in incorrect timestamps in the output file.
  
  [hls @ 0x33de8c0] Non-monotonous DTS in output stream 0:0; previous: 35986, current: 11998; changing to 35987. This may result in incorrect timestamps in the output file.
  
  [hls @ 0x33de8c0] Non-monotonous DTS in output stream 0:0; previous: 35987, current: 14998; changing to 35988. This may result in incorrect timestamps in the output file.
  
  [hls @ 0x33de8c0] Non-monotonous DTS in output stream 0:0; previous: 35988, current: 23991; changing to 35989. This may result in incorrect timestamps in the output file.
  
  [hls @ 0x33de8c0] Non-monotonous DTS in output stream 0:0; previous: 35989, current: 29990; changing to 35990. This may result in incorrect timestamps in the output file.
  
  [hls @ 0x33de8c0] Non-monotonous DTS in output stream 0:0; previous: 35990, current: 35987; changing to 35991. This may result in incorrect timestamps in the output file.
  
  frame=  114 fps= 20 q=-1.0 Lsize=N/A time=00:00:07.59 bitrate=N/A speed=1.32x    
  
  video:924kB audio:60kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
  
  Exiting normally, received signal 2.

• CCPA vs GDPR : Understanding Their Impact on Data Analytics

  19 mars, par Alex Carmona

  With over 400 million internet users in Europe and 331 million in the US (11% of which reside in California alone), understanding the nuances of privacy laws like the General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA) is crucial for compliant and ethical consumer data collection.

  Navigating this compliance landscape can be challenging for businesses serving European and Californian markets.

  This guide explores the key differences between CCPA and GDPR, their impact on data analytics, and how to ensure your business meets these essential privacy requirements.

  What is the California Consumer Privacy Act (CCPA) ?

  The California Consumer Privacy Act (CCPA) is a data privacy law that gives California consumers control over their personal information. It applies to for-profit businesses operating in California that meet specific criteria related to revenue, data collection and sales.

  Origins and purpose

  The CCPA addresses growing concerns about data privacy and how businesses use personal information in California. The act passed in 2018 and went into effect on 1 January 2020.

  Key features

  • Grants consumers the right to know what personal information is collected
  • Provides the right to delete personal information
  • Allows consumers to opt out of the sale of their personal information
  • Prohibits discrimination against consumers who exercise their CCPA rights

  Key definitions under the CCPA framework

  • Business : A for-profit entity doing business in California and meeting one or more of these conditions :
    • Has annual gross revenues over $25 million ;
    • Buys, receives, sells or shares 50,000 or more consumers’ personal information ; or
    • Derives 50% or more of its annual revenues from selling consumers’ personal information
  • Consumer : A natural person who is a California resident
  • Personal Information : Information that could be linked to, related to or used to identify a consumer or household, such as online identifiers, IP addresses, email addresses, social security numbers, cookie identifiers and more

  What is the General Data Protection Regulation (GDPR) ?

  The General Data Protection Regulation (GDPR) is a data privacy and protection law passed by the European Union (EU). It’s one of the strongest and most influential data privacy laws worldwide and applies to all organisations that process the personal data of individuals in the EU.

  Origins and purpose

  The GDPR was passed in 2016 and went into effect on 25 May 2018. It aims to harmonise data privacy laws in Europe and give people in the European Economic Area (EEA) privacy rights and control over their data.

  Key features

  • Applies to all organisations that process the personal data of individuals in the EEA
  • Grants individuals a wide range of privacy rights over their data
  • Requires organisations to obtain explicit and informed consent for most data processing
  • Mandates appropriate security measures to protect personal data
  • Imposes significant fines and penalties for non-compliance

  Key definitions under the GDPR framework

  • Data Subject : An identified or identifiable person
  • Personal Data : Any information relating to a data subject
  • Data Controller : The entity or organisation that determines how personal data is processed and what for
  • Data Processor : The entity or organisation that processes the data on behalf of the controller

  CCPA vs. GDPR : Key similarities

  The CCPA and GDPR enhance consumer privacy rights and give individuals greater control over their data.

  Dimension	CCPA	GDPR
  Purpose	Protect consumer privacy	Protect individual data rights
  Key Rights	Right to access, delete and opt out of sale	Right to access, rectify, erase and restrict processing
  Transparency	Requires transparency around data collection and use	Requires transparency about data collection, processing and use

  CCPA vs. GDPR : Key differences

  While they have similar purposes, the CCPA and GDPR differ significantly in their scope, approach and specific requirements.

  Dimension	CCPA	GDPR
  Scope	For-profit businesses only	All organisations processing EU consumer data
  Territorial Reach	California-based natural persons	All data subjects within the EEA
  Consent	Opt-out system	Opt-in system
  Penalties	Per violation based on its intentional or negligent nature	Case-by-case based on comprehensive assessment
  Individual Rights	Narrower (relative to GDPR)	Broader (relative to CCPA)

  CCPA vs. GDPR : A multi-dimensional comparison

  The previous sections gave a broad overview of the similarities and differences between CCPA and GDPR. Let’s now examine nine key dimensions where these regulations converge or diverge and discuss their impact on data analytics.

  

  #1. Scope and territorial reach

  The GDPR has a much broader scope than the CCPA. It applies to all organisations that process the personal data of individuals in the EEA, regardless of their business model, purpose or physical location.

  The CCPA applies to medium and large for-profit businesses that derive a substantial portion of their earnings from selling Californian consumers’ personal information. It doesn’t apply to non-profits, government agencies or smaller for-profit companies.

  Impact on data analytics

  The difference in scope significantly impacts data analytics practices. Smaller businesses may not need to comply with either regulation, some may only need to follow the CCPA, while most global businesses must comply with both. This often requires different methods for collecting and processing data in California, Europe, and elsewhere.

  #2. Penalties and fines for non-compliance

  Both the CCPA and GDPR impose penalties for non-compliance, but the severity of fines differs significantly :

  CCPA	Maximum penalty
  	$2,500 per unintentional violation $7,500 per intentional violation

  “Per violation” means per violation per impacted consumer. For example, three intentional CCPA violations affecting 1,000 consumers would result in 3,000 total violations and a $22.5 million maximum penalty (3,000 × $7,500).

  

  The largest CCPA fine to date was Zoom’s $85 million settlement in 2021.

  

  In contrast, the GDPR has resulted in 2,248 fines totalling almost €6.6 billion since 2018 — €2.4 billion of which were for non-compliance.

  GDPR	Maximum penalty
  	€20 million or 4% of all revenue earned the previous year

  So far, the biggest fine imposed under the GDPR was Meta’s €1.2 billion fine in May 2023 — 15 times more than Zoom had to pay California.

  Impact on data analytics

  The significant difference in potential fines demonstrates the importance of regulatory compliance for data analytics professionals. Non-compliance can have severe financial consequences, directly affecting budget allocation and business operations.

  Businesses must ensure their data collection, storage and processing practices comply with regulations in both Europe and California.

  Choosing privacy-first, compliance-ready analytics platforms like Matomo is instrumental for mitigating non-compliance risks.

  #3. Data subject rights and consumer rights

  The CCPA and GDPR give people similar rights over their data, but their limitations and details differ.

  Rights common to the CCPA and GDPR

  • Right to Access/Know : People can access their personal information and learn what data is collected, its source, its purpose and how it’s shared
  • Right to Delete/Erasure : People can request the deletion of their personal information, with some exceptions
  • Right to Non-Discrimination : Businesses can’t discriminate against people who exercise their privacy rights

  Consumer rights unique to the CCPA

  • Right to Opt Out of Sale : Consumers can prohibit the sale of their personal information
  • Right to Notice : Businesses must inform consumers about data collection practices
  • Right to Disclosure : Consumers can request specific information collected about them

  Data subject rights unique to the GDPR

  • Right to be Informed : Broader transparency requirements encompass data retention, automated decision-making and international transfers
  • Right to Rectification : Data subjects may request the correction of inaccurate data
  • Right to Restrict Processing : Consumers may limit data use in certain situations
  • Right to Data Portability : Businesses must provide individual consumer data in a secure, portable format when requested
  • Right to Withdraw Consent : Consumers may withdraw previously granted consent to data processing

  	CCPA	GDPR
  Right to Access or Know	✓	✓
  Right to Delete or Erase	✓	✓
  Right to Non-Discrimination	✓	✓
  Right to Opt-Out	✓
  Right to Notice	✓
  Right to Disclosure	✓
  Right to be Informed		✓
  Right to Rectification		✓
  Right to Restrict Processing		✓
  Right to Data Portability		✓
  Right to Withdraw Consent		✓

  Impact on data analytics

  Data analysts must understand these rights and ensure compliance with both regulations, which could potentially require separate data handling processes for EU and California consumers.

  #4. Opt-out vs. opt-in

  The CCPA generally follows an opt-out model, while the GDPR requires explicit consent from individuals before processing their data.

  Impact on data analytics

  For CCPA compliance, businesses can collect data by default if they provide opt-out mechanisms. Failing to process opt-out requests can result in severe penalties, like Sephora’s $1.2 million fine.

  Under GDPR, organisations must obtain explicit consent before collecting any data, which can limit the amount of data available for analysis.

  #5. Parental consent

  The CCPA and GDPR have provisions regarding parental consent for processing children’s data. The CCPA requires parental consent for children under 13, while the GDPR sets the age at 16, though member states can lower it to 13.

  Impact on data analytics

  This requirement significantly impacts businesses targeting younger audiences. In Europe and the US, companies must implement different methods to verify users’ ages and obtain parental consent when necessary.

  The California Attorney General’s Office recently fined Tilting Point Media LLC $500,000 for sharing children’s data without parental consent.

  #6. Data security requirements

  Both regulations require businesses to implement adequate security measures to protect personal data. However, the GDPR has more prescriptive requirements, outlining specific security measures and emphasising a risk-based approach.

  Impact on data analytics

  Data analytics professionals must ensure that data is processed and stored securely to avoid breaches and potential fines.

  #7. International data transfers

  Both the CCPA and GDPR address international data transfers. Under the CCPA, businesses must only inform consumers about international transfers. The GDPR has stricter requirements, including ensuring adequate data protection safeguards for transfers outside the EEA.

  

  Other rules, like the Payment Services Directive 2 (PSD2), also affect international data transfers, especially in the financial industry.

  PSD2 requires strong customer authentication and secure communication channels for payment services. This adds complexity to cross-border data flows.

  Impact on data analytics

  The primary impact is on businesses serving European residents from outside Europe. Processing data within the European Union is typically advisable. Meta’s record-breaking €1.2 billion fine was specifically for transferring data from the EEA to the US without sufficient safeguards.

  Choosing the right analytics platform helps avoid these issues.

  For example, Matomo offers a free, open-source, self-hosted analytics platform you can deploy anywhere. You can also choose a managed, GDPR-compliant cloud analytics solution with all data storage and processing servers within the EU (in Germany), ensuring your data never leaves the EEA.

  #8. Enforcement mechanisms

  The California Attorney General is responsible for enforcing CCPA requirements, while in Europe, the Data Protection Authority (DPA) in each EU member state enforces GDPR requirements.

  Impact on data analytics

  Data analytics professionals should be familiar with their respective enforcement bodies and their powers to support compliance efforts and minimise the risk of fines and penalties.

  #9. Legal basis for personal data processing

  The GDPR outlines six legal grounds for processing personal data :

  • Consent
  • Contract
  • Legal obligation
  • Vital interests
  • Public task
  • Legitimate interests

  The CCPA doesn’t explicitly define lawful bases but focuses on consumer rights and transparency in general.

  Impact on data analytics

  Businesses subject to the GDPR must identify and document a valid lawful basis for each processing activity.

  Compliance rules under CCPA and GDPR

  Complying with the CCPA and GDPR requires a comprehensive approach to data privacy. Here’s a summary of the essential compliance rules for each framework :

  

  CCPA compliance rules

  • Create clear and concise privacy policies outlining data collection and use practices
  • Give consumers the right to opt-out
  • Respond to consumer requests to access, delete and correct their personal information
  • Implement reasonable security measures for consumers’ personal data protection
  • Never discriminate against consumers who exercise their CCPA rights

  GDPR compliance rules

  • Obtain explicit and informed consent for data processing activities
  • Implement technical and organisational controls to safeguard personal data
  • Designate a Data Protection Officer (DPO) if necessary
  • Perform data protection impact assessments (DPIAs) for high-risk processing activities
  • Maintain records of processing activities
  • Promptly report data breaches to supervisory authorities

  Navigating the CCPA and GDPR with confidence

  Understanding the nuances of the CCPA and GDPR is crucial for businesses operating in the US and Europe. These regulations significantly impact data collection and analytics practices.

  Implementing robust data security practices and prioritising privacy and compliance are essential to avoid severe penalties and build trust with today’s privacy-conscious consumers.

  Privacy-centric analytics platforms like Matomo enable businesses to collect, analyse and use data responsibly and transparently, extracting valuable insights while maintaining compliance with both CCPA and GDPR requirements.

  Start your 21-day free trial today !

  no credit card required