Recherche avancée

Sur d’autres sites (2962)

• LGPD : Demystifying Brazil’s New Data Protection Law

  31 août 2023, par Erin — Privacy

  The General Personal Data Protection Law (LGPD or Lei Geral de Proteção de Dados Pessoais) is a relatively new legislation passed by the Brazilian government in 2018. The law officially took effect on September 18, 2020, but was not enforced until August 1, 2021, due to complications from the COVID-19 pandemic.

  For organisations that do business in Brazil and collect personal data, the LGPD has far-reaching implications, with 65 separate articles that outline how organisations must collect, process, disclose and erase personal data.

  In this article, you’ll learn what the LGPD is, including its contents and how a legal entity can be compliant.

  What is the LGPD ?

  The LGPD is a new data protection and privacy law passed by the Federal Brazilian Government on May 29, 2018. The purpose of the law is to unify the 40 previous Brazilian laws that regulated the processing of personal data.

  

  Many of the older laws have been either updated or removed to accommodate this change. The LGPD comprises 65 separate articles, and each covers a different area of the legislation, such as the rights of data subjects and the legal bases on which personal data may be collected. It also sets out the responsibilities of the National Data Protection Authority (ANPD), a newly created agency responsible for the guidance, supervision and enforcement of the LGPD.

  LGPD compliance is essential for organisations wishing to operate in Brazil and collect personal data for commercial purposes, whether online or offline. However, understanding the different rules and regulations and even figuring out if the LGPD applies to you can be challenging.

  Fortunately, the LGPD is relatively easy to understand and shares many similarities with the General Data Protection Regulation (GDPR), the data protection law implemented on May 25, 2018, by the European Union. This may help you better understand why the LGPD was enacted, the policies it contains and the goals it hopes to achieve. Both laws are very similar, but some items are unique to Brazil, such as what qualifies as a legal basis for collecting personal data.

  For these reasons, organisations should not apply a one-size-fits-all approach to GDPR and LGPD compliance, for they are different laws with different guiding principles and requirements.

  Who does the LGPD apply to, and who is exempt ?

  The LGPD applies to any natural person, public entity and private entity that collects, processes and stores personal data for commercial purposes within the national territory of Brazil. The same also applies to those who process the personal data of Brazilian and non-Brazilian citizens within the national territory of Brazil, even if the data processor is outside of Brazil. It also applies to those who process personal data collected from the national territory of Brazil.

  So, what does this all mean ? 

  Regardless of your location, if you conduct any personal data processing activities in Brazil or you process data that was collected from Brazil, then there is a high possibility that the LGPD applies to you. This is especially true if the data processing is for commercial purposes ; or, to be more precise, for the offering or provision of goods or services. It also means that subjects whose personal data is collected under these conditions are protected by the nine data subject rights.

  There are exceptions where the LGPD does not apply to data processors. These include if you process personal data for private or non-commercial reasons ; for artistic, journalistic and select academic purposes ; and for the purpose of state security, public safety, national defence and activities related to the investigation and prosecution of criminal offenders. Also, if the processed data originates from a country with similar data protection laws to Brazil, such as any country in the European Union (where the GDPR applies), then the LGPD will not apply to that individual or organisation.

  For these reasons, it is vital that you are familiar with the LGPD so that your data processing activities comply with the new standards. This is also important for the future, as an estimated 75% of the global population’s personal data will be protected by a privacy regulation. Getting things right now will make life easier moving forward.

  What are the nine LGPD data subject rights ?

  The LGPD has nine data subject rights. These protect the rights and freedoms of subjects, regardless of their political opinion and religious belief.

  

  These rights, listed under Article 19 of the LGPD, confirm that a data subject has the right to :

  1. Confirm the processing of their data.
  2. Access their data.
  3. Correct data that is incomplete, not accurate and out of date.
  4. Anonymize, block and delete data that is excessive, unnecessary and was not processed in compliance with the law.
  5. Move their data to a different service provider or product provider by special request.
  6. Delete or stop using personal data under certain circumstances.
  7. Gain information about who the data processor has shared the processed data with, including private and public entities.
  8. Be informed as to what the consequences may be for denying consent to the collection of personal data.
  9. Revoke consent to have their personal data processed under certain conditions.

  Many of these data subject rights are like the GDPR. For example, both the GDPR and LGPD give data subjects the right to be informed, the right to access, the right to data portability and the right to rectify false data. However, while the LGPD has nine data subject rights, the GDPR has only eight. What is the extra data subject right ? The right to gain information on who a data processor has shared your data with.

  There are other slight differences between the GDPR and LGPD with regard to data subject rights. For instance, the GDPR has a clear right to restrict certain data processing activities, such as those related to automation. The LGPD has this, too. But the subject of data collection automation is under Article 20, separate from all the data subject rights listed under Article 19.

  Under what conditions can personal data in Brazil be processed ?

  There are various conditions under which organisations can legally conduct personal data processing in Brazil. The aim of these conditions is to give data subjects confidence — that their personal data is processed for only safe, legal and ethical reasons. Also, the conditions help data processors, both individuals and organisations, determine if they have a legal basis for processing personal data in or in relation to Brazil.

  

  According to Article 7 of the LGPD, data processing may only be carried out if done :

  1. With consent by the data subject.
  2. To comply with a legal or regulatory obligation.
  3. By public authorities to assist with the execution of a public policy, one established by law or regulation.
  4. To help research entities carry out studies ; granted, when possible, subjects can anonymize their data.
  5. To carry out a contract or preliminary procedure, in particular, one related to a contract where the data subject is a party.
  6. To exercise the right of an arbitration, administration or judicial procedure.
  7. To protect the physical safety or life of someone
  8. To protect the health of someone about to undergo a procedure performed by health entities
  9. To fulfill the legitimate interests of a data processor, unless doing so would compromise a data subject’s fundamental rights and liberties.
  10. To protect one’s credit score.

  Much like the nine data subject rights, there are key differences between the LGPD and GDPR. The GDPR has six lawful bases for data processing, while the LGPD has ten. One notable addition to the LGPD is for the protection of one’s credit score, which is not covered by the GDPR. Another reason to ensure compliance with both data protection laws separately.

  LGPD vs. GDPR : How do they differ ?

  The LGPD was modeled closely on the GDPR, so it’s no surprise the two are similar. 

  Both laws ensure a high level of protection for the rights and freedoms of data subjects. They outline the legal justifications for data processing, establish the responsibilities of a data protection authority and lay out the penalties for non-compliance. That said, there are key differences between them.

  First, data subject rights ; the LGPD has nine, while the GDPR has eight. The GDPR gives data subjects the right to request a human review of automated decision-making, while the LGPD does not. Second, the legal bases for processing ; the LGPD has ten, while the GDPR has six. The four legal bases unique to the LGPD are : for protection of credit, for protection of health, for protection of life and for research entities carrying out studies.

  Both the LGPD and GDPR have different non-compliance penalties. The maximum fine for an infraction under the GDPR is up to €20 million (or 4% of the offender’s annual global revenue, whichever is higher). The maximum fine for an LGPD infraction is up to 50 million reais (around €9.2 million), or up to 2% of an offender’s revenue in Brazil, whichever is higher.

  6 steps to LGPD compliance with Matomo

  Below are steps you can follow to ensure your organisation is LGPD compliant. You’ll also learn how Matomo can help you comply quickly and easily.

  

  Let’s dive in.

  1. Appoint a DPO

  A DPO is a person, group, or organisation that communicates with data processors, data subjects, and the ANDP.

  Curiously, the LGPD lets you appoint your own DPO — even if they reside out of Brazil. So if the LGPD applies to you, you can appoint someone in your organisation to be a DPO. Just make sure that the nominated person has the understanding and capacity to perform the role’s duties.

  2. Assess your data

  Once you’re familiar with the LGPD and confirm your eligibility for LGPD compliance, take the time to assess your data. If you plan to collect data within the territory of Brazil, you’ll need to confirm the exact location of your data subjects. 

  To do this in Matomo, simply go to the previous year’s calendar. Then click on visitors, go to locations, and look for Brazil under the “Region” section. This will tell you how many of your web visitors are located in Brazil.

  

  3. Review privacy practices

  Review your existing privacy policies and practices, as there’s a good chance they’ll need to be updated to comply with the LGPD. Also, review your data sharing and third-party agreements, as you may need to communicate these new policies to partners that you rely on to deliver your services. 

  Lastly, review your procedures for tracking personal data and Personally Identifiable Information (PII). You may need to modify the type of data that you track to comply with the LGPD. You may even be tracking this data without your knowledge.

  4. Anonymize tracking data

  Data subjects under the LGPD have the right to request data anonymity. Therefore, to be LGPD compliant, your organisation must be able to accommodate for such a request.

  Fortunately, Matomo has various data anonymization techniques that help you protect your data subject’s privacy and comply with the LGPD. These techniques include the ability to anonymize previously tracked raw data, anonymize visitor IP addresses, and anonymize relevant geo-location data such as regions, cities and countries.

  

  You can find these features and more under the Anonymize data tab within the Privacy menu on the Matomo Settings page. Learn more about how to configure privacy settings in Matomo.

  5. Comply with LGPD consent laws without cookies

  By using Matomo to anonymize the data of your data subjects, this enables you to comply with LGPD consent laws and remove the need to display cookie consent banners on your website. This is made possible by the fact that Matomo is a cookieless tracking web analytics platform.

  Unlike other web analytics platforms like Google Analytics, which collect and use third-party cookies (persistent data that remains on your device, until that data expires or until you manually delete it) for their “own purposes,” Matomo is different. We use alternative means to identify web visitors, such as count the number of unique IP addresses and perform browser fingerprinting, neither of which involve the collection of personal data.

  As a result, you don’t have to display cookie consent banners on your website, and you can track your web visitors even if they disable cookies.

  6. Give users the right to opt-out

  Under the LGPD, data subjects have the right to opt-out of your data collection procedures. For this reason, make sure that your web visitors can do this on your website.

  

  You can do this in Matomo by adding an opt-out from tracking form to your website. To do this, click on the cog icon in the top menu, load the settings page, and click on the Users opt-out menu item in the Privacy section. Then follow the instructions to customise and publish the Matomo opt-out form.

  Achieve LGPD compliance with Matomo

  Like GDPR for Europe, the LGPD will impact organisations doing business in Brazil. And while they both share much of the same definitions and data subject rights, they differ on what qualifies as a legal basis for processing sensitive data. Complying with the GDPR and LGPD separately is non-negotiable and essential to avoiding maximum fines of €20 million and €9.2 million, respectively.

  

  As a web analytics platform with LGPD compliance, Matomo prioritises data privacy without compromising performance. Switch to a powerful LGPD-compliant web analytics platform that respects users’ privacy. 

  Get a 21-day free trial of Matomo today. 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 LGPD. We encourage every business and website to take data privacy seriously and discuss these issues with your lawyer if you have any concerns.

• swscale/x86/input.asm : add x86-optimized planer rgb2yuv functions

  24 novembre 2021, par Mark Reid

  swscale/x86/input.asm : add x86-optimized planer rgb2yuv functions
  sse2 only operates on 2 lanes per loop for to_y and to_uv functions, due
  
  to the lack of pmulld instruction.  Emulating pmulld with 2 pmuludq and shuffles
  
  proved too costly and made to_uv functions slower then the c implementation.
  For to_y on sse2 only float functions are generated,
  
  I was are not able outperform the c implementation on the integer pixel formats.
  For to_a on see4 only the float functions are generated.
  
  sse2 and sse4 generated nearly identical performing code on integer pixel formats,
  
  so only sse2/avx2 versions are generated.
  planar_gbrp_to_y_512_c : 1197.5
  
  planar_gbrp_to_y_512_sse4 : 444.5
  
  planar_gbrp_to_y_512_avx2 : 287.5
  
  planar_gbrap_to_y_512_c : 1204.5
  
  planar_gbrap_to_y_512_sse4 : 447.5
  
  planar_gbrap_to_y_512_avx2 : 289.5
  
  planar_gbrp9be_to_y_512_c : 1380.0
  
  planar_gbrp9be_to_y_512_sse4 : 543.5
  
  planar_gbrp9be_to_y_512_avx2 : 340.0
  
  planar_gbrp9le_to_y_512_c : 1200.5
  
  planar_gbrp9le_to_y_512_sse4 : 442.0
  
  planar_gbrp9le_to_y_512_avx2 : 282.0
  
  planar_gbrp10be_to_y_512_c : 1378.5
  
  planar_gbrp10be_to_y_512_sse4 : 544.0
  
  planar_gbrp10be_to_y_512_avx2 : 337.5
  
  planar_gbrp10le_to_y_512_c : 1200.0
  
  planar_gbrp10le_to_y_512_sse4 : 448.0
  
  planar_gbrp10le_to_y_512_avx2 : 285.5
  
  planar_gbrap10be_to_y_512_c : 1380.0
  
  planar_gbrap10be_to_y_512_sse4 : 542.0
  
  planar_gbrap10be_to_y_512_avx2 : 340.5
  
  planar_gbrap10le_to_y_512_c : 1199.0
  
  planar_gbrap10le_to_y_512_sse4 : 446.0
  
  planar_gbrap10le_to_y_512_avx2 : 289.5
  
  planar_gbrp12be_to_y_512_c : 10563.0
  
  planar_gbrp12be_to_y_512_sse4 : 542.5
  
  planar_gbrp12be_to_y_512_avx2 : 339.0
  
  planar_gbrp12le_to_y_512_c : 1201.0
  
  planar_gbrp12le_to_y_512_sse4 : 440.5
  
  planar_gbrp12le_to_y_512_avx2 : 286.0
  
  planar_gbrap12be_to_y_512_c : 1701.5
  
  planar_gbrap12be_to_y_512_sse4 : 917.0
  
  planar_gbrap12be_to_y_512_avx2 : 338.5
  
  planar_gbrap12le_to_y_512_c : 1201.0
  
  planar_gbrap12le_to_y_512_sse4 : 444.5
  
  planar_gbrap12le_to_y_512_avx2 : 288.0
  
  planar_gbrp14be_to_y_512_c : 1370.5
  
  planar_gbrp14be_to_y_512_sse4 : 545.0
  
  planar_gbrp14be_to_y_512_avx2 : 338.5
  
  planar_gbrp14le_to_y_512_c : 1199.0
  
  planar_gbrp14le_to_y_512_sse4 : 444.0
  
  planar_gbrp14le_to_y_512_avx2 : 279.5
  
  planar_gbrp16be_to_y_512_c : 1364.0
  
  planar_gbrp16be_to_y_512_sse4 : 544.5
  
  planar_gbrp16be_to_y_512_avx2 : 339.5
  
  planar_gbrp16le_to_y_512_c : 1201.0
  
  planar_gbrp16le_to_y_512_sse4 : 445.5
  
  planar_gbrp16le_to_y_512_avx2 : 280.5
  
  planar_gbrap16be_to_y_512_c : 1377.0
  
  planar_gbrap16be_to_y_512_sse4 : 545.0
  
  planar_gbrap16be_to_y_512_avx2 : 338.5
  
  planar_gbrap16le_to_y_512_c : 1201.0
  
  planar_gbrap16le_to_y_512_sse4 : 442.0
  
  planar_gbrap16le_to_y_512_avx2 : 279.0
  
  planar_gbrpf32be_to_y_512_c : 4113.0
  
  planar_gbrpf32be_to_y_512_sse2 : 2438.0
  
  planar_gbrpf32be_to_y_512_sse4 : 1068.0
  
  planar_gbrpf32be_to_y_512_avx2 : 904.5
  
  planar_gbrpf32le_to_y_512_c : 3818.5
  
  planar_gbrpf32le_to_y_512_sse2 : 2024.5
  
  planar_gbrpf32le_to_y_512_sse4 : 1241.5
  
  planar_gbrpf32le_to_y_512_avx2 : 657.0
  
  planar_gbrapf32be_to_y_512_c : 3707.0
  
  planar_gbrapf32be_to_y_512_sse2 : 2444.0
  
  planar_gbrapf32be_to_y_512_sse4 : 1077.0
  
  planar_gbrapf32be_to_y_512_avx2 : 909.0
  
  planar_gbrapf32le_to_y_512_c : 3822.0
  
  planar_gbrapf32le_to_y_512_sse2 : 2024.5
  
  planar_gbrapf32le_to_y_512_sse4 : 1176.0
  
  planar_gbrapf32le_to_y_512_avx2 : 658.5
  planar_gbrp_to_uv_512_c : 2325.8
  
  planar_gbrp_to_uv_512_sse2 : 1726.8
  
  planar_gbrp_to_uv_512_sse4 : 771.8
  
  planar_gbrp_to_uv_512_avx2 : 506.8
  
  planar_gbrap_to_uv_512_c : 2281.8
  
  planar_gbrap_to_uv_512_sse2 : 1726.3
  
  planar_gbrap_to_uv_512_sse4 : 768.3
  
  planar_gbrap_to_uv_512_avx2 : 496.3
  
  planar_gbrp9be_to_uv_512_c : 2336.8
  
  planar_gbrp9be_to_uv_512_sse2 : 1924.8
  
  planar_gbrp9be_to_uv_512_sse4 : 852.3
  
  planar_gbrp9be_to_uv_512_avx2 : 552.8
  
  planar_gbrp9le_to_uv_512_c : 2270.3
  
  planar_gbrp9le_to_uv_512_sse2 : 1512.3
  
  planar_gbrp9le_to_uv_512_sse4 : 764.3
  
  planar_gbrp9le_to_uv_512_avx2 : 491.3
  
  planar_gbrp10be_to_uv_512_c : 2281.8
  
  planar_gbrp10be_to_uv_512_sse2 : 1917.8
  
  planar_gbrp10be_to_uv_512_sse4 : 855.3
  
  planar_gbrp10be_to_uv_512_avx2 : 541.3
  
  planar_gbrp10le_to_uv_512_c : 2269.8
  
  planar_gbrp10le_to_uv_512_sse2 : 1515.3
  
  planar_gbrp10le_to_uv_512_sse4 : 759.8
  
  planar_gbrp10le_to_uv_512_avx2 : 487.8
  
  planar_gbrap10be_to_uv_512_c : 2382.3
  
  planar_gbrap10be_to_uv_512_sse2 : 1924.8
  
  planar_gbrap10be_to_uv_512_sse4 : 855.3
  
  planar_gbrap10be_to_uv_512_avx2 : 540.8
  
  planar_gbrap10le_to_uv_512_c : 2382.3
  
  planar_gbrap10le_to_uv_512_sse2 : 1512.3
  
  planar_gbrap10le_to_uv_512_sse4 : 759.3
  
  planar_gbrap10le_to_uv_512_avx2 : 484.8
  
  planar_gbrp12be_to_uv_512_c : 2283.8
  
  planar_gbrp12be_to_uv_512_sse2 : 1936.8
  
  planar_gbrp12be_to_uv_512_sse4 : 858.3
  
  planar_gbrp12be_to_uv_512_avx2 : 541.3
  
  planar_gbrp12le_to_uv_512_c : 2278.8
  
  planar_gbrp12le_to_uv_512_sse2 : 1507.3
  
  planar_gbrp12le_to_uv_512_sse4 : 760.3
  
  planar_gbrp12le_to_uv_512_avx2 : 485.8
  
  planar_gbrap12be_to_uv_512_c : 2385.3
  
  planar_gbrap12be_to_uv_512_sse2 : 1927.8
  
  planar_gbrap12be_to_uv_512_sse4 : 855.3
  
  planar_gbrap12be_to_uv_512_avx2 : 539.8
  
  planar_gbrap12le_to_uv_512_c : 2377.3
  
  planar_gbrap12le_to_uv_512_sse2 : 1516.3
  
  planar_gbrap12le_to_uv_512_sse4 : 759.3
  
  planar_gbrap12le_to_uv_512_avx2 : 484.8
  
  planar_gbrp14be_to_uv_512_c : 2283.8
  
  planar_gbrp14be_to_uv_512_sse2 : 1935.3
  
  planar_gbrp14be_to_uv_512_sse4 : 852.3
  
  planar_gbrp14be_to_uv_512_avx2 : 540.3
  
  planar_gbrp14le_to_uv_512_c : 2276.8
  
  planar_gbrp14le_to_uv_512_sse2 : 1514.8
  
  planar_gbrp14le_to_uv_512_sse4 : 762.3
  
  planar_gbrp14le_to_uv_512_avx2 : 484.8
  
  planar_gbrp16be_to_uv_512_c : 2383.3
  
  planar_gbrp16be_to_uv_512_sse2 : 1881.8
  
  planar_gbrp16be_to_uv_512_sse4 : 852.3
  
  planar_gbrp16be_to_uv_512_avx2 : 541.8
  
  planar_gbrp16le_to_uv_512_c : 2378.3
  
  planar_gbrp16le_to_uv_512_sse2 : 1476.8
  
  planar_gbrp16le_to_uv_512_sse4 : 765.3
  
  planar_gbrp16le_to_uv_512_avx2 : 485.8
  
  planar_gbrap16be_to_uv_512_c : 2382.3
  
  planar_gbrap16be_to_uv_512_sse2 : 1886.3
  
  planar_gbrap16be_to_uv_512_sse4 : 853.8
  
  planar_gbrap16be_to_uv_512_avx2 : 550.8
  
  planar_gbrap16le_to_uv_512_c : 2381.8
  
  planar_gbrap16le_to_uv_512_sse2 : 1488.3
  
  planar_gbrap16le_to_uv_512_sse4 : 765.3
  
  planar_gbrap16le_to_uv_512_avx2 : 491.8
  
  planar_gbrpf32be_to_uv_512_c : 4863.0
  
  planar_gbrpf32be_to_uv_512_sse2 : 3347.5
  
  planar_gbrpf32be_to_uv_512_sse4 : 1800.0
  
  planar_gbrpf32be_to_uv_512_avx2 : 1199.0
  
  planar_gbrpf32le_to_uv_512_c : 4725.0
  
  planar_gbrpf32le_to_uv_512_sse2 : 2753.0
  
  planar_gbrpf32le_to_uv_512_sse4 : 1474.5
  
  planar_gbrpf32le_to_uv_512_avx2 : 927.5
  
  planar_gbrapf32be_to_uv_512_c : 4859.0
  
  planar_gbrapf32be_to_uv_512_sse2 : 3269.0
  
  planar_gbrapf32be_to_uv_512_sse4 : 1802.0
  
  planar_gbrapf32be_to_uv_512_avx2 : 1201.5
  
  planar_gbrapf32le_to_uv_512_c : 6338.0
  
  planar_gbrapf32le_to_uv_512_sse2 : 2756.5
  
  planar_gbrapf32le_to_uv_512_sse4 : 1476.0
  
  planar_gbrapf32le_to_uv_512_avx2 : 908.5
  planar_gbrap_to_a_512_c : 383.3
  
  planar_gbrap_to_a_512_sse2 : 66.8
  
  planar_gbrap_to_a_512_avx2 : 43.8
  
  planar_gbrap10be_to_a_512_c : 601.8
  
  planar_gbrap10be_to_a_512_sse2 : 86.3
  
  planar_gbrap10be_to_a_512_avx2 : 34.8
  
  planar_gbrap10le_to_a_512_c : 602.3
  
  planar_gbrap10le_to_a_512_sse2 : 48.8
  
  planar_gbrap10le_to_a_512_avx2 : 31.3
  
  planar_gbrap12be_to_a_512_c : 601.8
  
  planar_gbrap12be_to_a_512_sse2 : 111.8
  
  planar_gbrap12be_to_a_512_avx2 : 41.3
  
  planar_gbrap12le_to_a_512_c : 385.8
  
  planar_gbrap12le_to_a_512_sse2 : 75.3
  
  planar_gbrap12le_to_a_512_avx2 : 39.8
  
  planar_gbrap16be_to_a_512_c : 386.8
  
  planar_gbrap16be_to_a_512_sse2 : 79.8
  
  planar_gbrap16be_to_a_512_avx2 : 31.3
  
  planar_gbrap16le_to_a_512_c : 600.3
  
  planar_gbrap16le_to_a_512_sse2 : 40.3
  
  planar_gbrap16le_to_a_512_avx2 : 30.3
  
  planar_gbrapf32be_to_a_512_c : 1148.8
  
  planar_gbrapf32be_to_a_512_sse2 : 611.3
  
  planar_gbrapf32be_to_a_512_sse4 : 234.8
  
  planar_gbrapf32be_to_a_512_avx2 : 183.3
  
  planar_gbrapf32le_to_a_512_c : 851.3
  
  planar_gbrapf32le_to_a_512_sse2 : 263.3
  
  planar_gbrapf32le_to_a_512_sse4 : 199.3
  
  planar_gbrapf32le_to_a_512_avx2 : 156.8
  Reviewed-by : Paul B Mahol <onemda@gmail.com>
  
  Signed-off-by : James Almer <jamrial@gmail.com>
  

  • [DH] libswscale/x86/input.asm
  • [DH] libswscale/x86/swscale.c
  • [DH] tests/checkasm/sw_gbrp.c

• Should H.264 bit rate be multiples of 8 ?

  31 août 2016, par Dan Sharp

  I’m working on a video platform receiving H.264 video and building an HLS stream (transmuxing the H.264 to Mpeg2 TS segments via calls to ffmpeg).

  I wanted to set the bit rate to be about 2000 kbps, but I’m wondering : does it matter if it’s 2000 or 2048 ?

  In other words, do things calculate better if the bit rate is multiples of 8, like 512 or 2024 or 2048 ?

  I don’t know enough about how the bit rate is used, either on the sending side (camera) or on the processing side (ffmpeg).

  From tests... I can’t see any noticeable difference between 2000 and 2048, but maybe one is slightly better than another for the transmuxing and segmenting ?

  I welcome any thoughts/advice.