Recherche avancée

Médias (1)

Mot : - Tags -/école

Autres articles (23)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • Submit enhancements and plugins

    13 avril 2011

    If you have developed a new extension to add one or more useful features to MediaSPIP, let us know and its integration into the core MedisSPIP functionality will be considered.
    You can use the development discussion list to request for help with creating a plugin. As MediaSPIP is based on SPIP - or you can use the SPIP discussion list SPIP-Zone.

  • Contribute to translation

    13 avril 2011

    You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
    To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
    MediaSPIP is currently available in French and English (...)

Sur d’autres sites (4441)

  • Speed up start of a stream recording with ffmpeg

    15 janvier 2014, par neutron

    I try to record a video stream (from the web or a local webcam stream) and save it to a .mp4 / .flv file. I use FFmpeg with the version"N-59696-gc0a33c4".

    The problem isn't the recording of the stream, it is, how log it tooks to start the recording.

    This are the parameters i used to capture the stream (the stream is some random stream I found on the web) :

    ffmpeg.exe -i mmsh://live.camstreams.com/cscamscape?MSWMExt=.asf -r 25 -t 60 C:\temp\video.mp4

    And leads to this output :

    ffmpeg.exe -i mmsh://live.camstreams.com/cscams
    
cape?MSWMExt=.asf -r 25 -t 60 C:\temp\video.mp4
    
ffmpeg version N-59696-gc0a33c4 Copyright (c) 2000-2014 the FFmpeg developers
    
  built on Jan  8 2014 22:01:50 with gcc 4.8.2 (GCC)
    
  configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av
    
isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab
    
le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable-libfreetyp
    
e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena
    
ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l
    
ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp
    
eex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-aa
    
cenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavp
    
ack --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib
    
  libavutil      52. 62.100 / 52. 62.100
    
  libavcodec     55. 47.100 / 55. 47.100
    
  libavformat    55. 22.102 / 55. 22.102
    
  libavdevice    55.  5.102 / 55.  5.102
    
  libavfilter     4.  0.103 /  4.  0.103
    
  libswscale      2.  5.101 /  2.  5.101
    
  libswresample   0. 17.104 /  0. 17.104
    
  libpostproc    52.  3.100 / 52.  3.100
    
[wmv3 @ 0275db40] Extra data: 8 bits left, value: 0
    
Input #0, asf, from 'mmsh://live.camstreams.com/cscamscape?MSWMExt=.asf':
    
  Metadata:
    
    title           : Live Fish Cam
    
    WMFSDKNeeded    : 0.0.0.0000
    
    DeviceConformanceTemplate: SP
    
    WMFSDKVersion   : 11.0.5721.5275
    
    IsVBR           : 0
    
  Duration: N/A, start: 3887858.274000, bitrate: 512 kb/s
    
    Stream #0:0(eng): Video: wmv3 (Simple) (WMV3 / 0x33564D57), yuv420p, 640x360
    
, 512 kb/s, 62.50 tbr, 1k tbn, 1k tbc
    
[libx264 @ 0275e400] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
    
[libx264 @ 0275e400] profile High, level 3.0
    
[libx264 @ 0275e400] 264 - core 140 r2377 1ca7bb9 - H.264/MPEG-4 AVC codec - Cop
    
yleft 2003-2013 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deb
    
lock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 m
    
e_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chro
    
ma_qp_offset=-2 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1
    
interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1
    
 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scene
    
cut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin
    
=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
    
[wmv3 @ 0275db40] Extra data: 8 bits left, value: 0
    
Output #0, mp4, to 'C:\temp\video.mp4':
    
  Metadata:
    
    title           : Live Fish Cam
    
    WMFSDKNeeded    : 0.0.0.0000
    
    DeviceConformanceTemplate: SP
    
    WMFSDKVersion   : 11.0.5721.5275
    
    IsVBR           : 0
    
    encoder         : Lavf55.22.102
    
    Stream #0:0(eng): Video: h264 (libx264) ([33][0][0][0] / 0x0021), yuv420p, 6
    
40x360, q=-1--1, 12800 tbn, 25 tbc
    
Stream mapping:
    
  Stream #0:0 -> #0:0 (wmv3 -> libx264)
    
Press [q] to stop, [?] for help
    
frame=  148 fps=0.0 q=28.0 size=     228kB time=00:00:03.60 bitrate= 518.3kbits/
    
frame=  151 fps=117 q=28.0 size=     236kB time=00:00:03.72 bitrate= 519.2kbits/
    
frame=  178 fps= 91 q=28.0 size=     298kB time=00:00:04.80 bitrate= 508.3kbits/
    
frame=  204 fps= 64 q=28.0 size=     347kB time=00:00:05.84 bitrate= 487.4kbits/
    
... 
    
... And so on ...

    The problem now is, that it takes around 6-10 seconds until the recording starts after I entered the command.

    Is there a way to speed up this process ?

  • Google Analytics 4 and GDPR : Everything You Need to Know

    17 mai 2022, par Erin

    Four years have passed since the European General Data Protection Regulation (GDPR, also known as DSGVO in German, and RGPD in French) took effect.

    That’s ample time to get compliant, especially for an organisation as big and innovative as Google. Or is it ? 

    If you are wondering how GDPR affects Google Analytics 4 and what the compliance status is at present, here’s the lowdown. 

    Is Google Analytics 4 GDPR Compliant ?

    No. As of mid-2022, Google Analytics 4 (GA4) isn’t fully GDPR compliant. Despite adding extra privacy-focused features, GA4 still has murky status with the European regulators. After the invalidation of the Privacy Shield framework in 2020, Google is yet to regulate EU-US data protection. At present, the company doesn’t sufficiently protect EU citizens’ and residents’ data against US surveillance laws. This is a direct breach of GDPR.

    Google Analytics and GDPR : a Complex Relationship 

    European regulators have scrutinised Google since GDPR came into effect in 2018.

    While the company took steps to prepare for GDPR provisions, it didn’t fully comply with important regulations around user data storage, transfer and security.

    The relationship between Google and EU regulators got more heated after the Court of Justice of the European Union (CJEU) invalidated the Privacy Shield — a leeway Google used for EU-US data transfers. After 2020, GDPR litigation against Google followed. 

    This post summarises the main milestones in this story and explains the consequences for Google Analytics users. 

    Google Analytics and GDPR Timeline

    2018 : Google Analytics Meets GDPR 

    In 2018, the EU adopted the General Data Protection Regulation (GDPR) — a set of privacy and data security laws, covering all member states. Every business interacting with EU citizens and/or residents had to comply.

    GDPR harmonised data protection laws across member states and put down extra provisions for what constitutes sensitive personal information (or PII). Broadly, PII includes any data about the person’s :

    • Racial or ethnic origin 
    • Employment status 
    • Religious or political beliefs
    • State of health 
    • Genetic or biometric data 
    • Financial records (such as payment method data)
    • Address and phone numbers 

    Businesses were barred from collecting this information without explicit consent (and even with it in some cases). If collected, such sensitive information is also subject to strict requirements on how it should be stored, secured, transferred and used. 

    7 Main GDPR Principles Explained 

    Article 5 of the GDPR lays out seven main GDPR principles for personal data and privacy protection : 

    • Lawfulness, fairness and transparency — data must be obtained legally, collected with consent and in adherence to laws. 
    • Purpose limitation — all personal information must be collected for specified, explicit and legal purposes. 
    • Data minimisation — companies must collect only necessary and adequate data, aligned with the stated purpose. 
    • Accuracy — data accuracy must be ensured at all times. Companies must have mechanisms to erase or correct inaccurate data without delays. 
    • Storage limitation — data must be stored only for as long as the stated purpose suggests. Though there’s no upper time limit on data storage. 
    • Integrity and confidentiality (security) — companies must take measures to ensure secure data storage and prevent unlawful or unauthorised access to it. 
    • Accountability — companies must be able to demonstrate adherence to the above principles. 

    Google claimed to have taken steps to make all of their products GDPR compliant ahead of the deadline. But in practice, this wasn’t always the case.

    In March 2018, a group of publishers admonished Google for not providing them with enough tools for GDPR compliance :

    “[Y]ou refuse to provide publishers with any specific information about how you will collect, share and use the data. Placing the full burden of obtaining new consent on the publisher is untenable without providing the publisher with the specific information needed to provide sufficient transparency or to obtain the requisite specific, granular and informed consent under the GDPR.”

    The proposed Google Analytics GDPR consent form was hard to implement and lacked customisation options. In fact, Google “makes unilateral decisions” on how the collected data is stored and used. 

    Users had no way to learn about or control all intended uses of people’s data — which made compliance with the second clause impossible. 

    Unsurprisingly, Google was among the first companies to face a GDPR lawsuit (together with Facebook). 

    By 2019, French data regulator CNIL, successfully argued that Google wasn’t sufficiently disclosing its data collection across products — and hence in breach of GDPR. After a failed appeal, Google had to pay a €50 million fine and promise to do better. 

    2019 : Google Analytics 4 Announcement 

    Throughout 2019, Google rightfully attempted to resolve some of its GDPR shortcomings across all products, Google Universal Analytics (UA) included. 

    They added a more visible consent mechanism for online tracking and provided extra compliance tips for users to follow. In the background, Google also made tech changes to its data processing mechanism to get on the good side of regulations.

    Though Google addressed some of the issues, they missed others. A 2019 independent investigation found that Google real-time-bidding (RTB) ad auctions still used EU citizens’ and residents’ data without consent, thanks to a loophole called “Push Pages”. But they managed to quickly patch this up before the allegations had made it to court. 

    In November 2019, Google released a beta version of the new product version — Google Analytics 4, due to replace Universal Analytics. 

    GA4 came with a set of new privacy-focused features for ticking GDPR boxes such as :

    • Data deletion mechanism. Users can now request to surgically extract certain data from the Analytics servers via a new interface. 
    • Shorter data retention period. You can now shorten the default retention period to 2 months by default (instead of 14 months) or add a custom limit.  
    • IP Anonymisation. GA4 doesn’t log or store IP addresses by default. 

    Google Analytics also updated its data processing terms and made changes to its privacy policy. 

    Though Google made some progress, Google Analytics 4 still has many limitations — and isn’t GDPR compliant. 

    2020 : Privacy Shield Invalidation Ruling 

    As part of the 2018 GDPR preparations, Google named its Irish entity (Google Ireland Limited) as the “data controller” legally responsible for EEA and Swiss users’ information. 

    The company announcement says : 

    Google Analytics Statement on Privacy Shield Invalidation Ruling
    Source : Google

    Initially, Google assumed that this legal change would help them ensure GDPR compliance as “legally speaking” a European entity was set in charge of European data. 

    Practically, however, EEA consumers’ data was still primarily transferred and processed in the US — where most Google data centres are located. Until 2020, such cross-border data transfers were considered legal thanks to the Privacy Shield framework. 

    But in July 2020, The EU Court of Justice ruled that this framework doesn’t provide adequate data protection to digitally transmitted data against US surveillance laws. Hence, companies like Google can no longer use it. The Swiss Federal Data Protection and Information Commissioner (FDPIC) reached the same conclusion in September 2020. 

    The invalidation of the Privacy Shield framework put Google in a tough position.

     Article 14. f of the GDPR explicitly states : 

    “The controller (the company) that intends to carry out a transfer of personal data to a recipient (Analytics solution) in a third country or an international organisation must provide its users with information on the place of processing and storage of its data”.

    Invalidation of the Privacy Shield framework prohibited Google from moving data to the US. At the same time, GDPR provisions mandated that they must disclose proper data location. 

    But Google Analytics (like many other products) had no a mechanism for : 

    • Guaranteeing intra-EU data storage 
    • Selecting a designated regional storage location 
    • Informing users about data storage location or data transfers outside of the EU 

    And these factors made Google Analytics in direct breach of GDPR — a territory, where they remain as of 2022.

    2020-2022 : Google GDPR Breaches and Fines 

    The 2020 ruling opened Google to GDPR lawsuits from country-specific data regulators.

    Google Analytics in particular was under a heavy cease-fire. 

    • Sweden first fined Google for violating GDPR for no not fulfilling its obligations to request data delisting in 2020. 
    • France rejected Google Analytics 4 IP address anonymisation function as a sufficient measure for protecting cross-border data transfers. Even with it, US intelligence services can still access user IPs and other PII. France declared Google Analytics illegal and pressed a €150 million fine. 
    • Austria also found Google Analytics GDPR non-compliant and proclaimed the service as “illegal”. The authority now seeks a fine too. 

    The Dutch Data Protection Authority and  Norwegian Data Protection Authority also found Google Analytics guilty of a GDPR breach and seek to limit Google Analytics usage. 

    New privacy controls in Google Analytics 4 do not resolve the underlying issue — unregulated, non-consensual EU-US data transfer. 

    Google Analytics GDPR non-compliance effectively opens any website tracking or analysing European visitors to legal persecution.

    In fact, this is already happening. noyb, a European privacy-focused NGO, has already filed over 100 lawsuits against European websites using Google Analytics.

    2022 : Privacy Shield 2.0. Negotiations

    Google isn’t the only US company affected by the Privacy Shield framework invalidation. The ruling puts thousands of digital companies at risk of non-compliance.

    To settle the matter, US and EU authorities started “peace talks” in spring 2022.

    European Commission President Ursula von der Leyen said that they are working with the Biden administration on the new agreement that will “enable predictable and trustworthy data flows between the EU and US, safeguarding the privacy and civil liberties.” 

    However, it’s just the beginning of a lengthy negotiation process. The matter is far from being settled and contentious issues remain as we discussed on Twitter (come say hi !).

    Matomo Tweet on EU-US Data Transfers

    For one, the US isn’t eager to modify its surveillance laws and is mostly willing to make them “proportional” to those in place in the EU. These modifications may still not satisfy CJEU — which has the power to block the agreement vetting or invalidate it once again. 

    While these matters are getting hashed out, Google Analytics users, collecting data about EU citizens and/or residents, remain on slippery grounds. As long as they use GA4, they can be subject to GDPR-related lawsuits. 

    To Sum It Up 

    • Google Analytics 4 and Google Universal Analytics are not GDPR compliant because of Privacy Shield invalidation in 2020. 
    • French and Austrian data watchdogs named Google Analytics operations “illegal”. Swedish, Dutch and Norwegian authorities also claim it’s in breach of GDPR. 
    • Any website using GA for collecting data about European citizens and/or residents can be taken to court for GDPR violations (which is already happening). 
    • Privacy Shield 2.0 Framework discussions to regulate EU-US data transfers have only begun and may take years. Even if accepted, the new framework(s) may once again be invalidated by local data regulators as has already happened in the past. 

    Time to Get a GDPR Compliant Google Analytics Alternative 

    Retaining 100% data ownership is the optimal path to GDPR compliance.

    By selecting a transparent web analytics solution that offers 100% data ownership, you can rest assured that no “behind the scenes” data collection, processing or transfers take place. 

    Unlike Google Analytics 4, Matomo offers all of the features you need to be GDPR compliant : 

    • Full data anonymisation 
    • Single-purpose data usage 
    • Easy consent and an opt-out mechanism 
    • First-party cookies usage by default 
    • Simple access to collect data 
    • Fast data removals 
    • EU-based data storage for Matomo Cloud (or storage in the country of your choice with Matomo On-Premise)

    Learn about your audiences in a privacy-centred way and protect your business against unnecessary legal exposure. 

    Start your 21-day free trial (no credit card required) to see how fully GDPR-compliant website analytics works ! 

  • FFmpeg recording works on one laptop but not the other

    30 novembre 2019, par Jason T

    The following command :

    ffmpeg -f dshow -framerate 30 -video_size 640x480 -i video="HD Pro Webcam C920" out.mp4​

    works on one laptop (with C920 LogiTech camera) (Im calling it GOOD LAPTOP). It outputs a recorded video. But it will fail on another laptop (called BAD LAPTOP) and by fail on another I mean - it doesnt output a video (see below for output).

    The suggestions are to change parameters based on the specific error that occur on BAD LAPTOP. I have tried many different suggestions but they dont seem to work. Furthermore, they dont provide much insight into the underlying cause of the problem.

    Ive used the same camera on both laptops. Im using static windows binaries downloaded from FFmpeg web-site (veranoe). Please note the versions used below were different but that doesnt appear to matter.

    Trying to diagnose. Anyone have an idea of where the problem may lie. It seems to indicate a problem at the level of the system / camera setup.

    Please note that I’ve updated BAD LAPTOP but still no dice. Also please note that Ive tried this on several systems already and it seems to run ok (i.e., produce an output video)

    BAD LAPTOP :

    $ ffmpeg -y -f dshow -framerate 30 -video_size 640x480 -t 10 -i video="HD Pro Webcam C920" out.mp4
    
ffmpeg version git-2019-11-26-59d264b Copyright (c) 2000-2019 the FFmpeg developers
    
  built with gcc 9.2.1 (GCC) 20191125
    
  configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libmfx --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt --enable-amf
    
  libavutil      56. 36.100 / 56. 36.100
    
  libavcodec     58. 62.100 / 58. 62.100
    
  libavformat    58. 35.100 / 58. 35.100
    
  libavdevice    58.  9.101 / 58.  9.101
    
  libavfilter     7. 67.100 /  7. 67.100
    
  libswscale      5.  6.100 /  5.  6.100
    
  libswresample   3.  6.100 /  3.  6.100
    
  libpostproc    55.  6.100 / 55.  6.100
    
Input #0, dshow, from 'video=HD Pro Webcam C920':
    
  Duration: N/A, bitrate: N/A
    
    Stream #0:0: Video: rawvideo (YUY2 / 0x32595559), yuyv422, 640x480, 30 fps, 30 tbr, 10000k tbn, 10000k tbc
    
Stream mapping:
    
  Stream #0:0 -> #0:0 (rawvideo (native) -> h264 (libx264))
    
Press [q] to stop, [?] for help
    
video=HD Pro Webcam C920: I/O error
    
[libx264 @ 06cb7a00] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
    
[libx264 @ 06cb7a00] profile High 4:2:2, level 3.0, 4:2:2, 8-bit
    
[libx264 @ 06cb7a00] 264 - core 158 - H.264/MPEG-4 AVC codec - Copyleft 2003-2019 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
    
Output #0, mp4, to 'out.mp4':
    
  Metadata:
    
    encoder         : Lavf58.35.100
    
    Stream #0:0: Video: h264 (libx264) (avc1 / 0x31637661), yuv422p, 640x480, q=-1--1, 30 fps, 10000k tbn, 30 tbc
    
    Metadata:
    
      encoder         : Lavc58.62.100 libx264
    
    Side data:
    
      cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: N/A
    
frame=    0 fps=0.0 q=0.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

    GOOD LAPTOP :
    ​

    $ ffmpeg -y -f dshow -framerate 30 -video_size 640x480 -t 10 -i video="Logitech HD Pro Webcam C920" out.mp4   
    
ffmpeg version N-92780-gbb586a9703 Copyright (c) 2000-2018 the FFmpeg developers                              
    
  built with gcc 8.2.1 (GCC) 20181201                                                                         
    
  configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-ico
    
nv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --en
    
able-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-lib
    
soxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx
    
264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvi
    
dstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enabl
    
e-libaom --enable-libmfx --enable-amf --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enab
    
le-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt                                                 
    
  libavutil      56. 25.100 / 56. 25.100                                                                      
    
  libavcodec     58. 42.104 / 58. 42.104                                                                      
    
  libavformat    58. 25.100 / 58. 25.100                                                                      
    
  libavdevice    58.  6.101 / 58.  6.101                                                                      
    
  libavfilter     7. 46.101 /  7. 46.101                                                                      
    
  libswscale      5.  4.100 /  5.  4.100                                                                      
    
  libswresample   3.  4.100 /  3.  4.100                                                                      
    
  libpostproc    55.  4.100 / 55.  4.100                                                                      
    
Input #0, dshow, from 'video=Logitech HD Pro Webcam C920':                                                    
    
  Duration: N/A, start: 35609.500000, bitrate: N/A                                                            
    
    Stream #0:0: Video: mjpeg (Baseline) (MJPG / 0x47504A4D), yuvj422p(pc, bt470bg/unknown/unknown), 640x480, 
    
30 fps, 30 tbr, 10000k tbn, 10000k tbc                                                                        
    
Stream mapping:                                                                                               
    
  Stream #0:0 -> #0:0 (mjpeg (native) -> h264 (libx264))                                                      
    
Press [q] to stop, [?] for help                                                                               
    
[libx264 @ 000001ec0b750100] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2            
    
[libx264 @ 000001ec0b750100] profile High 4:2:2, level 3.0, 4:2:2, 8-bit                                      
    
[libx264 @ 000001ec0b750100] 264 - core 157 r2935 545de2f - H.264/MPEG-4 AVC codec - Copyleft 2003-2018 - http
    
://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 ps
    
y_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma
    
_qp_offset=-2 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 con
    
strained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 k
    
eyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 
    
qpstep=4 ip_ratio=1.40 aq=1:1.00                                                                              
    
Output #0, mp4, to 'out.mp4':                                                                                 
    
  Metadata:                                                                                                   
    
    encoder         : Lavf58.25.100                                                                           
    
    Stream #0:0: Video: h264 (libx264) (avc1 / 0x31637661), yuvj422p(pc), 640x480, q=-1--1, 30 fps, 10000k tbn
    
, 30 tbc                                                                                                      
    
    Metadata:                                                                                                 
    
      encoder         : Lavc58.42.104 libx264                                                                 
    
    Side data:                                                                                                
    
      cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1                                            
    
frame=   62 fps= 31 q=29.0 size=       0kB time=00:00:00.10 bitrate=   3.8kbits/s dup=1 drop=0 speed=0.0495x  
    
frame=   77 fps= 30 q=29.0 size=       0kB time=00:00:00.60 bitrate=   0.6kbits/s dup=1 drop=0 speed=0.237x   
    
frame=   92 fps= 30 q=29.0 size=       0kB time=00:00:01.09 bitrate=   0.3kbits/s dup=1 drop=0 speed=0.363x   
    
frame=  107 fps= 30 q=29.0 size=       0kB time=00:00:01.59 bitrate=   0.2kbits/s dup=1 drop=0 speed=0.453x   
    
frame=  168 fps= 30 q=29.0 size=     256kB time=00:00:03.63 bitrate= 577.3kbits/s dup=1 drop=0 speed=0.654x   
    
frame=  183 fps= 30 q=29.0 size=     256kB time=00:00:04.13 bitrate= 507.5kbits/s dup=1 drop=0 speed=0.683x   
    
frame=  198 fps= 30 q=29.0 size=     256kB time=00:00:04.63 bitrate= 452.7kbits/s dup=1 drop=0 speed=0.706x   
    
frame=  213 fps= 30 q=29.0 size=     512kB time=00:00:05.13 bitrate= 817.1kbits/s dup=1 drop=0 speed=0.727x   
    
frame=  228 fps= 30 q=29.0 size=     512kB time=00:00:05.63 bitrate= 744.6kbits/s dup=1 drop=0 speed=0.744x   
    
frame=  243 fps= 30 q=29.0 size=     512kB time=00:00:06.13 bitrate= 683.9kbits/s dup=1 drop=0 speed=0.759x   
    
frame=  259 fps= 30 q=29.0 size=     512kB time=00:00:06.66 bitrate= 629.2kbits/s dup=1 drop=0 speed=0.777x   
    
frame=  274 fps= 30 q=29.0 size=     512kB time=00:00:07.16 bitrate= 585.3kbits/s dup=1 drop=0 speed=0.789x   
    
frame=  289 fps= 30 q=29.0 size=     512kB time=00:00:07.66 bitrate= 547.1kbits/s dup=1 drop=0 speed=0.799x   
    
frame=  301 fps= 30 q=-1.0 Lsize=     973kB time=00:00:09.93 bitrate= 802.7kbits/s dup=1 drop=0 speed=0.975x  
    

    
video:969kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.445649%            
    
[libx264 @ 000001ec0b750100] frame I:4     Avg QP:24.23  size: 13237                                          
    
[libx264 @ 000001ec0b750100] frame P:77    Avg QP:24.67  size:  7807                                          
    
[libx264 @ 000001ec0b750100] frame B:220   Avg QP:26.09  size:  1534                                          
    
[libx264 @ 000001ec0b750100] consecutive B-frames:  2.3%  0.7%  0.0% 97.0%                                    
    
[libx264 @ 000001ec0b750100] mb I  I16..4: 19.6% 70.5%  9.9%                                                  
    
[libx264 @ 000001ec0b750100] mb P  I16..4:  3.6%  3.3%  0.3%  P16..4: 54.9% 11.7%  9.5%  0.0%  0.0%    skip:16
    
.8%                                                                                                           
    
[libx264 @ 000001ec0b750100] mb B  I16..4:  0.1%  0.2%  0.0%  B16..8: 28.2%  1.1%  0.2%  direct: 7.9%  skip:62
    
.2%  L0:51.0% L1:45.9% BI: 3.1%                                                                               
    
[libx264 @ 000001ec0b750100] 8x8 transform intra:56.1% inter:69.3%                                            
    
[libx264 @ 000001ec0b750100] coded y,uvDC,uvAC intra: 35.2% 85.0% 30.8% inter: 9.3% 38.8% 1.5%                
    
[libx264 @ 000001ec0b750100] i16 v,h,dc,p: 32% 34%  8% 27%                                                    
    
[libx264 @ 000001ec0b750100] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 33% 18% 28%  2%  3%  5%  3%  5%  3%               
    
[libx264 @ 000001ec0b750100] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 40% 19%  8%  3%  6% 11%  4%  6%  3%               
    
[libx264 @ 000001ec0b750100] i8c dc,h,v,p: 48% 16% 31%  5%                                                    
    
[libx264 @ 000001ec0b750100] Weighted P-Frames: Y:3.9% UV:1.3%                                                
    
[libx264 @ 000001ec0b750100] ref P L0: 39.0%  6.6% 38.0% 16.3%  0.1%                                          
    
[libx264 @ 000001ec0b750100] ref B L0: 61.8% 30.3%  7.9%                                                      
    
[libx264 @ 000001ec0b750100] ref B L1: 84.4% 15.6%                                                            
    
[libx264 @ 000001ec0b750100] kb/s:790.62                

Navigation