Recherche avancée

Sur d’autres sites (11192)

• Why are no dts pts written to my mp4 container

  14 mai 2019, par Kiamur

  Based on my (self-answered) question here Muxing AVPackets into mp4 file - revisited, I have to ask, what could be the reason why there are no values written for pts/dts in the resulting mp4 container.

  I examined the container file with the tool MediaInfo.
  I observe that only the very first Frame contains a value for pts in the container. After that, pts is not even shown in the mp4 file anymore, but dts is, with a value of all zeros.

  This is the output from MediaInfo for the first 3 frames :

  0000A2   slice_layer_without_partitioning (IDR) - 0 (0x0) - Frame 0 - slice_type I - frame_num 0 - DTS 00:00:00.000 - PTS 00:00:00.017 (141867 bytes)
  
  0000A2    Header (5 bytes)
  
  0000A2     zero_byte:                          0 (0x00)
  
  0000A3     start_code_prefix_one_3bytes:       1 (0x000001)
  
  0000A6     nal_ref_idc:                        3 (0x3) - (2 bits)
  
  0000A6     nal_unit_type:                      5 (0x05) - (5 bits)
  
  0000A7    slice_header (3 bytes)
  
  0000A7     first_mb_in_slice:                  0 (0x0)
  
  0000A7     slice_type:                         7 (0x07) - I
  
  0000A8     pic_parameter_set_id:               0 (0x0)
  
  0000A8     frame_num:                          0 (0x0)
  
  0000A8     idr_pic_id:                         0 (0x0)
  
  0000A8     no_output_of_prior_pics_flag:       No
  
  0000A8     long_term_reference_flag:           No
  
  0000A9     slice_qp_delta:                     -5 (0xFFFFFFFB)
  
  0000AA     disable_deblocking_filter_idc:      0 (0x0)
  
  0000AA     slice_alpha_c0_offset_div2:         0 (0x0)
  
  0000AA     slice_beta_offset_div2:             0 (0x0)
  
  0000AA    slice_data (141856 bytes)
  
  0000AA     (ToDo):                             (Data)
  
  022ACD   slice_layer_without_partitioning (IDR) - 0 (0x0) - Frame 0 - slice_type I - frame_num 0 - DTS 00:00:00.000 - PTS 00:00:00.017 - first_mb_in_slice 8040 (2248 bytes)
  
  022ACD    Header (5 bytes)
  
  022ACD     zero_byte:                          0 (0x00)
  
  022ACE     start_code_prefix_one_3bytes:       1 (0x000001)
  
  022AD1     nal_ref_idc:                        3 (0x3) - (2 bits)
  
  022AD1     nal_unit_type:                      5 (0x05) - (5 bits)
  
  022AD2    slice_header (6 bytes)
  
  022AD2     first_mb_in_slice:                  8040 (0x001F68)
  
  022AD5     slice_type:                         7 (0x07) - I
  
  022AD6     pic_parameter_set_id:               0 (0x0)
  
  022AD6     frame_num:                          0 (0x0)
  
  022AD6     idr_pic_id:                         0 (0x0)
  
  022AD6     no_output_of_prior_pics_flag:       No
  
  022AD6     long_term_reference_flag:           No
  
  022AD7     slice_qp_delta:                     -5 (0xFFFFFFFB)
  
  022AD8     disable_deblocking_filter_idc:      0 (0x0)
  
  022AD8     slice_alpha_c0_offset_div2:         0 (0x0)
  
  022AD8     slice_beta_offset_div2:             0 (0x0)
  
  022AD8    slice_data (2237 bytes)
  
  022AD8     (ToDo):                             (Data)
  
  023395  1 (36212 bytes)
  
  023395   slice_layer_without_partitioning (non-IDR) - 2 (0x2) - Frame 1 - slice_type P - frame_num 1 - DTS 00:00:00.000 (36017 bytes)
  
  023395    Header (5 bytes)
  
  023395     zero_byte:                          0 (0x00)
  
  023396     start_code_prefix_one_3bytes:       1 (0x000001)
  
  023399     nal_ref_idc:                        3 (0x3) - (2 bits)
  
  023399     nal_unit_type:                      1 (0x01) - (5 bits)
  
  02339A    slice_header (3 bytes)
  
  02339A     first_mb_in_slice:                  0 (0x0)
  
  02339A     slice_type:                         5 (0x5) - P
  
  02339A     pic_parameter_set_id:               0 (0x0)
  
  02339A     frame_num:                          1 (0x1)
  
  02339B     num_ref_idx_active_override_flag (0 bytes)
  
  02339B      num_ref_idx_active_override_flag:  Yes
  
  02339B      num_ref_idx_l0_active_minus1:      0 (0x0)
  
  02339B     ref_pic_list_modification_flag_l0:  No
  
  02339B     adaptive_ref_pic_marking_mode_flag: No
  
  02339C     cabac_init_idc:                     0 (0x0)
  
  02339C     slice_qp_delta:                     -3 (0xFFFFFFFD)
  
  02339C     disable_deblocking_filter_idc:      0 (0x0)
  
  02339C     slice_alpha_c0_offset_div2:         0 (0x0)
  
  02339D     slice_beta_offset_div2:             0 (0x0)
  
  02339D    slice_data (36012 bytes)
  
  02339D     (ToDo):                             (Data)
  
  02C046   slice_layer_without_partitioning (non-IDR) - 2 (0x2) - Frame 1 - slice_type P - frame_num 1 - DTS 00:00:00.000 - first_mb_in_slice 8040 (195 bytes)
  
  02C046    Header (5 bytes)
  
  02C046     zero_byte:                          0 (0x00)
  
  02C047     start_code_prefix_one_3bytes:       1 (0x000001)
  
  02C04A     nal_ref_idc:                        3 (0x3) - (2 bits)
  
  02C04A     nal_unit_type:                      1 (0x01) - (5 bits)
  
  02C04B    slice_header (6 bytes)
  
  02C04B     first_mb_in_slice:                  8040 (0x001F68)
  
  02C04E     slice_type:                         5 (0x5) - P
  
  02C04E     pic_parameter_set_id:               0 (0x0)
  
  02C04E     frame_num:                          1 (0x1)
  
  02C04F     num_ref_idx_active_override_flag (0 bytes)
  
  02C04F      num_ref_idx_active_override_flag:  Yes
  
  02C04F      num_ref_idx_l0_active_minus1:      0 (0x0)
  
  02C04F     ref_pic_list_modification_flag_l0:  No
  
  02C04F     adaptive_ref_pic_marking_mode_flag: No
  
  02C050     cabac_init_idc:                     0 (0x0)
  
  02C050     slice_qp_delta:                     -3 (0xFFFFFFFD)
  
  02C050     disable_deblocking_filter_idc:      0 (0x0)
  
  02C050     slice_alpha_c0_offset_div2:         0 (0x0)
  
  02C051     slice_beta_offset_div2:             0 (0x0)
  
  02C051    slice_data (190 bytes)
  
  02C051     (ToDo):                             (Data)
  
  02C109  1 (26280 bytes)
  
  02C109   slice_layer_without_partitioning (non-IDR) - 4 (0x4) - Frame 2 - slice_type P - frame_num 2 - DTS 00:00:00.000 (26157 bytes)
  
  02C109    Header (5 bytes)
  
  02C109     zero_byte:                          0 (0x00)
  
  02C10A     start_code_prefix_one_3bytes:       1 (0x000001)
  
  02C10D     nal_ref_idc:                        3 (0x3) - (2 bits)
  
  02C10D     nal_unit_type:                      1 (0x01) - (5 bits)
  
  02C10E    slice_header (3 bytes)
  
  02C10E     first_mb_in_slice:                  0 (0x0)
  
  02C10E     slice_type:                         5 (0x5) - P
  
  02C10E     pic_parameter_set_id:               0 (0x0)
  
  02C10E     frame_num:                          2 (0x2)
  
  02C10F     num_ref_idx_active_override_flag (0 bytes)
  
  02C10F      num_ref_idx_active_override_flag:  Yes
  
  02C10F      num_ref_idx_l0_active_minus1:      0 (0x0)
  
  02C10F     ref_pic_list_modification_flag_l0:  No
  
  02C10F     adaptive_ref_pic_marking_mode_flag: No
  
  02C110     cabac_init_idc:                     0 (0x0)
  
  02C110     slice_qp_delta:                     -2 (0xFFFFFFFE)
  
  02C110     disable_deblocking_filter_idc:      0 (0x0)
  
  02C110     slice_alpha_c0_offset_div2:         0 (0x0)
  
  02C111     slice_beta_offset_div2:             0 (0x0)
  
  02C111    slice_data (26152 bytes)
  
  02C111     (ToDo):                             (Data)
  
  032736   slice_layer_without_partitioning (non-IDR) - 4 (0x4) - Frame 2 - slice_type P - frame_num 2 - DTS 00:00:00.000 - first_mb_in_slice 8040 (123 bytes)
  
  032736    Header (5 bytes)
  
  032736     zero_byte:                          0 (0x00)
  
  032737     start_code_prefix_one_3bytes:       1 (0x000001)
  
  03273A     nal_ref_idc:                        3 (0x3) - (2 bits)
  
  03273A     nal_unit_type:                      1 (0x01) - (5 bits)
  
  03273B    slice_header (6 bytes)
  
  03273B     first_mb_in_slice:                  8040 (0x001F68)
  
  03273E     slice_type:                         5 (0x5) - P
  
  03273E     pic_parameter_set_id:               0 (0x0)
  
  03273E     frame_num:                          2 (0x2)
  
  03273F     num_ref_idx_active_override_flag (0 bytes)
  
  03273F      num_ref_idx_active_override_flag:  Yes
  
  03273F      num_ref_idx_l0_active_minus1:      0 (0x0)
  
  03273F     ref_pic_list_modification_flag_l0:  No
  
  03273F     adaptive_ref_pic_marking_mode_flag: No
  
  032740     cabac_init_idc:                     0 (0x0)
  
  032740     slice_qp_delta:                     -2 (0xFFFFFFFE)
  
  032740     disable_deblocking_filter_idc:      0 (0x0)
  
  032740     slice_alpha_c0_offset_div2:         0 (0x0)
  
  032741     slice_beta_offset_div2:             0 (0x0)
  
  032741    slice_data (118 bytes)
  
  032741     (ToDo):                             (Data)
  
  0327B1  1 (21125 bytes)

  It goes on like that, even though I set pts and dts. The settings may not be correct already (I do some calculations like (1 / framerate) * FrameNumber), but I would expect at least some numbers in pts and dts, when I set the according fields in the avPacket structure and write that via av_interleaved_write_frame(outFmtCtx, &avPacket) ; to the file.

  What could be wrong here ?

  Edit :

  (please see below in the comments the download to my testdata and source file)
  One thing that bugs me is the fact, if I compare the output of MediaInfo from my file and that of the muxing.c generated is, that in the header, the muxing.c generated already mentions the duration of the file as 9960 ms, whereas mine is only 40 ms.

  muxing.c also does call avformat_write_header before even one frame is drawn. Yes, I suppose that the header will be updated, when the either av_interleaved_write_frame or av_write_trailer is called, but I totally not understand the mechanics behind it.
  Maybe somebody can enlighten me with some background information of any kind.

  Additionally, I think it could be necessarry to extract some SPS and PPS from my raw data (preceding the I-slice), and give that as extra data to the avformat_write_header call. But I just cannot figure out myself if I have to do that at all and if so, how to do it.

• A Quick Start Guide to the Payment Services Directive (PSD2)

  22 novembre 2024, par Daniel Crough — Banking and Financial Services, Privacy

  In 2023, there were 266.2 billion real-time payments indicating that the demand for secure transactions has never been higher. As we move towards a more open banking system, there are a host of new payment solutions that offer convenience and efficiency, but they also present new risks.

  The Payment Services Directive 2 (PSD2) is one of many regulations established to address these concerns. PSD2 is a European Union (EU) business initiative to offer smooth payment experiences while helping customers feel safe from online threats. 

  In this post, learn what PSD2 includes, how it improves security for online payments, and how Matomo supports banks and financial institutions with PSD2 compliance.

  What is PSD2 ? 

  PSD2 is an EU directive that aims to improve the security of electronic payments across the EU. It enforces strong customer authentication and allows third-party access to consumer accounts with explicit consent. 

  Its main objectives are :

  • Strengthening security and data privacy measures around digital payments.
  • Encouraging innovation by allowing third-party providers access to banking data.
  • Improving transparency with clear communication regarding fees, terms and conditions associated with payment services.
  • Establishing a framework for sharing customer data securely through APIs for PSD2 open banking.

  Rationale behind PSD2 

  PSD2’s primary purpose is to engineer a more integrated and efficient European payment market without compromising the security of online transactions. 

  The original directive aimed to standardise payment services across EU member states, but as technology evolved, an updated version was needed.

  PSD2 is mandatory for various entities within the European Economic Area (EEA), like :

  • Banks and credit institutions
  • Electronic money institutions or digital banks like Revolut
  • Card issuing and acquiring institutions
  • Fintech companies
  • Multi-national organisations operating in the EU

  PSD2 implementation timeline

  With several important milestones, PSD2 has reshaped how payment services work in Europe. Here’s a closer look at the pivotal events that paved the way for its launch.

  • 2002 : The banking industry creates the European Payments Council (EC), which drives the Single Euro Payments Area (SEPA) initiative to include non-cash payment instruments across European regions. 
  • 2007 : PSD1 goes into effect.
  • 2013 : EC proposes PSD2 to include protocols for upcoming payment services.
  • 2015 : The Council of European Union passes PSD2 and gives member states two years to incorporate it.
  • 2018 : PSD2 goes into effect. 
  • 2019 : The final deadline for all companies within the EU to comply with PSD2’s regulations and rules for strong customer authentication. 

  PSD2 : Key components 

  PSD2 introduces several key components. Let’s take a look at each one.

  Strong Customer Authentication (SCA)

  The Regulatory Technical Standards (RTS) under PSD2 outline specific requirements for SCA. 

  SCA requires multi-factor authentication for online transactions. When customers make a payment online, they need to verify their identity using at least two of the three following elements :

  • Knowledge : Something they know (like a password, a code or a secret answer)
  • Possession : Something they have (like their phone or card)
  • Inherence : Something they are (like biometrics — fingerprints or facial features)

  

  Before SCA, banks verified an individual’s identity only using a password. This dual verification allows only authorised users to complete transactions. SCA implementation reduces fraud and increases the security of electronic payments.

  SCA implementation varies for different payment methods. Debit and credit cards use the 3D Secure (3DS) protocol. E-wallets and other local payment measures often have their own SCA-compliant steps. 

  3DS is an extra step to authenticate a customer’s identity. Most European debit and credit card companies implement it. Also, in case of fraudulent chargebacks, the issuing bank becomes liable due to 3DS, not the business. 

  However, in SCA, certain transactions are exempt : 

  • Low-risk transactions : A transaction by an issuer or an acquirer whose fraud level is below a specific threshold. If the acquirer feels that a transaction is low risk, they can request to skip SCA. 
  • Low-value transactions : Transactions under €30.
  • Trusted beneficiaries : Trusted merchants customers choose to safelist.
  • Recurring payments : Recurring transactions for a fixed amount are exempt from SCA after the first transaction.

  Third-party payment service providers (TPPs) framework

  TPPs are entities authorised to access customer banking data and initiate payments. There are three types of TPPs :

  Account Information Service Providers (AISPs)

  AISPs are services that can view customers’ account details, but only with their permission. For example, a budgeting app might use AISP services to gather transaction data from a user’s bank account, helping them monitor expenses and oversee finances. 

  Payment Initiation Service Providers (PISPs)

  PISPs enable clients to initiate payments directly from their bank accounts, bypassing the need for conventional payment options such as debit or credit cards. After the customer makes a payment, PISPs immediately contact the merchant to ensure the user can access the online services or products they bought. 

  Card-Based Payment Instruments (CBPII)

  CBPIIs refer to services that issue payment cards linked to customer accounts. 

  Requirements for TPPs

  To operate effectively under PSD2, TPPs must meet several requirements :

  Consumer consent : Customers must explicitly authorise TPPs to retrieve their financial data. This way, users can control who can view their information and for what purpose.

  Security compliance : TPPs must follow SCA and secure communication guidelines to protect users from fraud and unauthorised access.

  API availability : Banks must make their Application Programming Interfaces (APIs) accessible and allow TPPs to connect securely with the bank’s systems. This availability helps in easy integration and lets TPPs access essential data. 

  Consumer protection methods

  PSD2 implements various consumer protection measures to increase trust and transparency between consumers and financial institutions. Here’s a closer look at some of these key methods :

  • Prohibition of unjustified fees : PSD2 requires banks to clearly communicate any additional charges or fees for international transfers or account maintenance. This ensures consumers are fully aware of the actual costs and charges.
  • Timely complaint resolution : PSD2 mandates that payment service providers (PSPs) have a straightforward complaint procedure. If a customer faces any problems, the provider must respond within 15 business days. This requirement encourages consumers to engage more confidently with financial services.
  • Refund in case of unauthorised payment : Customers are entitled to a full refund for payments made without their consent.
  • Surcharge ban : Additional charges on credit and debit card payments aren’t allowed. Businesses can’t impose extra fees on these payment methods, which increases customers’ purchasing power.

  Benefits of PSD2 

  Businesses — particularly those in banking, fintech, finserv, etc. — stand to benefit from PSD2 in several ways.

  Access to customer data

  With customer consent, banks can analyse spending patterns to develop tailored financial products that match customer needs, from personalised savings accounts to more relevant loan offerings.

  Innovation and cost benefits 

  PSD2 opened payment processing up to more market competition. New payment companies bring fresh approaches to banking services, making daily transactions more efficient while driving down processing fees across the sector.

  Also, banks now work alongside payment technology providers, combining their strengths to create better services. This collaboration brings faster payment options to businesses, helping them stay competitive while reducing operational costs.

  Improved customer trust and experience

  Due to PSD2 guidelines, modern systems handle transactions quickly without compromising the safety of payment data, creating a balanced approach to digital banking.

  

  Banking customers now have more control over their financial information. Clear processes allow consumers to view and adjust their financial preferences as needed.

  Strong security standards form the foundation of these new payment systems. Payment provider platforms must adhere to strict regulations and implement additional protection measures.

  Challenges in PSD2 compliance 

  What challenges can banks and financial institutions face regarding PSD2 compliance ? Let’s examine them. 

  Resource requirements

  For many businesses, the new requirements come with a high price tag. PSD2 requires banks and fintechs to build and update their systems so that other providers can access customer data safely. For example, they must develop APIs to allow TPPs to acquire customer data. 

  Many banks still use older systems that can’t meet PSD2’s added requirements. In addition to the cost of upgrades, complying with PSD2 requires banks to devote resources to training staff and monitoring compliance.

  The significant costs required to update legacy systems and IT infrastructure while keeping services running remain challenging.

  Risks and penalties

  Organisations that fail to comply with PSD2 regulations can face significant penalties.

  Additionally, the overlapping requirements of PSD2 and other regulations, such as the General Data Protection Regulation (GDPR), can create confusion. 

  Banks need clear agreements with TPPs about who’s responsible when things go wrong. This includes handling data breaches, preventing data misuse and protecting customer information. 

  Increased competition 

  Introducing new players in the financial ecosystem, such as AISPs and PISPs, creates competition. Banks must adapt their services to stay competitive while managing compliance costs.

  PSD2 aims to protect customers but the stronger authentication requirements can make banking less convenient. Banks must balance security with user experience. Focused time, effort and continuous monitoring are needed for businesses to stay compliant and competitive.

  How Matomo can help 

  Matomo gives banks and financial institutions complete control over their data through privacy-focused web analytics, keeping collected information internal rather than being used for marketing or other purposes. 

  Its advanced security setup includes access controls, audit logs, SSL encryption, single sign-on and two-factor authentication. This creates a secure environment where sensitive data remains accessible only to authorised staff.

  While prioritizing privacy, Matomo provides tools to understand user flow and customer segments, such as session recordings, heatmaps and A/B testing.

  Financial institutions particularly benefit from several key features : 

  • Tools for obtaining explicit consent before processing personal data like this Do Not Track preference
  • Insights into how financial institutions integrate TPPs (including API usage, user engagement and potential authentication drop-off points)
  • Tracking of failed login attempts or unusual access patterns
  • IP anonymization to analyse traffic patterns and detect potential fraud

  

  PSD3 : The next step 

  In recent years, we have seen the rise of innovative payment companies and increasingly clever fraud schemes. This has prompted regulators to propose updates to payment rules.

  PSD3’s scope is to adapt to the evolving digital transformation and to better handle these fraud risks. The proposed measures : 

  • Encourage PSPs to share fraud-related information.
  • Make customers aware of the different types of fraud.
  • Strengthen customer authentication standards.
  • Provide non-bank PSPs restricted access to EU payment systems. 
  • Enact payment rules in a directly applicable regulation and harmonise and enforce the directive.

  Web analytics that respect user privacy 

  Achieving compliance with PSD2 may be a long road for some businesses. With Matomo, organisations can enjoy peace of mind knowing their data practices align with legal requirements.

  Ready to stop worrying over compliance with regulations like PSD2 and take control of your data ? Start your 21-day free trial with Matomo.

• lavf/isom : Allow reading mp3-in-isom as written by vlc.

  12 mai 2019, par Carl Eugen Hoyos

  lavf/isom : Allow reading mp3-in-isom as written by vlc.
  Reported-by : IRC user aiena
  

  • [DH] libavformat/isom.c