Recherche avancée

Sur d’autres sites (5540)

• How to not process any personal data with Matomo and what it means for you

  22 avril 2018, par InnoCraft

  Disclaimer : this blog post has been written by digital analysts, not lawyers. The purpose of this article is to explain how to not process any personal data with Matomo in order to avoid going through the GDPR compliance process with Matomo analytics. This work comes from our interpretation of different sources : the official GDPR text and the UK privacy commission : ICO resources. It cannot be considered as a professional legal advice. So as GDPR, this information is subject to change. GDPR may be also known as RGPD in French, Spanish, Portuguese, Datenschutz-Grundverordnung, DS-GVO in German, Algemene verordening gegevensbescherming in Dutch, Regolamento generale sulla protezione dei dati in Italian.

  Are you looking for a way to not process any personal data with Matomo ? If the answer is yes, you are at the right place. From our understanding, if you are not processing personal data, then you shouldn’t be concerned about GDPR. Our inspiration came from this official reference :

  “The principles of data protection should therefore not apply to anonymous information, namely information which does not relate to an identified or identifiable natural person or to personal data rendered anonymous in such a manner that the data subject is not or no longer identifiable. This Regulation does not therefore concern the processing of such anonymous information, including for statistical or research purposes.“

  In this blog post we are going to see how you can configure Matomo in order to not process any personal data and what the consequences are.

  Which data is considered as personal according to GDPR ?

  From : eur-lex.europa.eu

  (1) “‘personal data’ means any information relating to an identified or identifiable natural person (‘data subject’) ; an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person ;”

  (30) “Natural persons may be associated with online identifiers provided by their devices, applications, tools and protocols, such as internet protocol addresses, cookie identifiers or other identifiers such as radio frequency identification tags. This may leave traces which, in particular when combined with unique identifiers and other information received by the servers, may be used to create profiles of the natural persons and identify them.”

  So according to your Matomo configuration, it may leave some traces within the following data :

  1. IP addresses
  2. Cookies identifiers
  3. Page URL or page titles
  4. User ID and Custom “personal” data
  5. Ecommerce order IDs
  6. Location
  7. Heatmaps & Session Recordings

  Let’s see each of them in more detail.

  1. IP addresses

  IP addresses can indirectly identify an individual. It can also give a good approximation of an individual’s location.

  IP addresses are therefore considered as personal data which means you need to anonymize them. To do so, a feature is available within Matomo, where you can anonymize the IP. We recommend you to anonymize at least the last two bytes :

  

  See our configuration guide for more information

  What are the consequences of using this feature ?

  When applying IP anonymization on two bytes, you will no longer be able to see the full IP in the UI.

  Moreover, there is a small chance that 2 different visitors with the same device and software configuration will be identified as the same visitor if the anonymised IP address is the same for both.

  2. Cookies

  It is not clear for us yet if all cookies are considered equal under GDPR. At this stage it is too early to make a definite decision.

  Did you know ? Matomo lets you optionally disable the creation of cookies by adding an extra line of code to your tracking code see below.

  

  See our configuration guide for more information

  What are the consequences of using this feature ?

  Matomo is using a few first party cookies, and the following cookies may hold personal data :

  • _pk_id : contains a visitor id used to identify unique visitors
  • _pk_ref : to identify from where they came from

  If Matomo cannot set cookies, it will use a technique called Fingerprint. It is based on several metadata such as the operating system, browser, browser plugins, IP address, browser language ; just to name a few to identify a unique visitor. As this feature is less accurate than the one using cookies, the number of visitors and visits will be affected.

  3. Page URLs and page titles

  URLs are not mentioned within the official GDPR text. However, we know that according to the different CMS you use, some of them may have URLs including personal identifiers.

  For example :

  

  As a result, you need to find a way to anonymize this data.

  There are several ways you can perform this action according to your website. If your website is adding the personal data through query parameters, you can define a rule to exclude them from Matomo.

  If the personal data are not included within query parameters, you can use the “setCustomURL” feature and write your code as follow :

  

  See our developer documentation for more information

  If you are also processing personal data within the title tag, you can use the following function : “setDocumentTitle”.

  What are the consequences of using this feature ?

  By anonymizing the URLs containing personal data, some of your  URLs will be grouped together.

  4. User ID and custom personal data

  User ID is a feature (a tracking code needs to be added) which allows you to identify the same user across different devices.

  A User ID needs a corresponding database in order to link a user across different devices, it can be an email, a username, a name, a random number… All those data are either direct or non direct online identifiers and are therefore under the scope of GDPR.

  It will be the same situation if you are using custom variables and/or custom dimensions in order to push personal data to the system.

  To continue using the User ID feature but not recording personal data, you can consider using a hash function which will anonymize/convert your actual User ID into something like “3jrj3j34434834urj33j3”.

  Alternatively, you can enable the feature “Anonymise User IDs”. This feature will be available starting in Matomo 3.5.0 :

  

  What are the consequences of using this feature ?

  Under GDPR, User ID is personal data. Anonymizing the User ID using a hash function or our built-in functionality make the User Id pseudo-anonymous, which means it can’t be easily identified to a specific user. As a result, you will still get accurate visits and unique visitors metrics, and the Visitor Profile, but without tracking the original User ID which is personal data.

  5. Ecommerce order IDs

  Order IDs are the reference number assigned to the products/services bought by your customers. As this information can be crossed with your internal database, it is considered as an online identifier and is therefore under the scope of GDPR. As for User ID, you can anonymize order IDs using our built-in functionality to Anonymise Order IDs (see section 4. about User Id).

  What are the consequences of anonymizing order ID ?

  It really depends on your former use of order IDs. If you were not using them in the past then you should not see any difference.

  6. Location

  Based on the IP address of a visitor, Matomo can detect the visitors location. Location data is problematic for privacy as this technology has become quite accurate and can detect not only the city a visitor is from, but sometimes an even more precise position of a visitor.

  

  In order to not leave any accurate traces, we strongly recommend you to enable the IP anonymization feature. Next, you need to enable the setting “Also use the anonymized IP address when enriching visits”. You find this setting directly below the IP anonymization. This is important as otherwise the full IP address will be used to geolocate a visitor.

  

  What are the consequences of anonymizing location data ?

  The more bytes you anonymize from the IP, the more anonymized your location will be. When you remove two bytes as suggested, the city and region location reports will not be as accurate. In some cases even the country may not be detected correctly anymore.

  7. Heatmaps & Session Recordings

  Heatmaps & Session Recording is a premium feature in Matomo allowing you to see where users click, hover, type and scroll. With session recordings you can then replay their actions in a video.

  Heatmaps & Session Recordings are under the scope of GDPR as they can disclose in some specific cases (for example : filling a contact form) personal data :

  

  To avoid this, Matomo will anonymize all keystrokes which a user enters into a form field unless you specifically whitelist a field. Many fields that could contain personal data, such as a credit card, phone number, email address, password, social security number, and more are always anonymized and not recorded.

  See our configuration guide for more information

  Note that a page may still show personal information within the page as part of regular content (not a form element). For example an address, or the profile page of a forum user. We have added a feature which allows you to set an HTML attribute “data-matomo-mask” to anonymize any personal content shown in the UI.

  What are the consequences of using this feature ?

  Mainly, you will not be able to see in plain text what people are entering into your forms.

  What should you do with past data ?

  Once more, we have to say that we are not lawyers. So do not take our answers as legal advice. From : ec.europa.eu/newsroom/article29/document.cfm ?doc_id=50053

  “For example, as the GDPR requires that a controller must be able to demonstrate that valid consent was obtained, all presumed consents of which no references are kept will automatically be below the consent standard of the GDPR and will need to be renewed.”

  Our interpretation is that, if you were previously relying on consent, unless you can demonstrate that valid consent was obtained, you need to get the consent back (which is almost impossible) or you need to anonymize or remove that data.

  To anonymize previously tracked data, we are actively working on a feature to do just that directly within Matomo. Alternatively, you may also set up the deletion of logs after a certain amount of time.

  We really hope you enjoyed reading this article. GDPR is still on the go and we are pretty sure you have a lot of questions about it. You probably would like to share our vision about it. So do not hesitate to ask us through our contact form to see how we are interpreting GDPR at Matomo and InnoCraft.

  The post How to not process any personal data with Matomo and what it means for you appeared first on Analytics Platform - Matomo.

• Google Analytics Now Illegal in Austria ; Other EU Member States Expected to Follow

  18 janvier 2022, par Erin — Privacy

  Breaking news : The Austrian Data Protection Authority (“Datenschutzbehörde” or “DSB” or “DPA”) has ruled that Austrian website providers using Google Analytics are in violation of the GDPR. 

  This ruling stems from a decision made in 2020 by the Court of Justice of the European Union (CJEU) that stated that cloud services hosted in the US are incapable of complying with the GDPR and EU privacy laws. The decision was made because of the US surveillance laws requiring US providers (like Google or Facebook) to provide personal data to US authorities. 

  The 2020 ruling, known as “Schrems II”, marked the ending of the Privacy Shield, a framework that allowed for EU data to be transferred to US companies that became certified. 

  The tech industry was sent into a frenzy following this decision, but many US and EU companies decided to ignore the case. The choice to ignore is what landed one Austrian business in the DPA’s line of fire, damaging the brand’s reputation and possibly resulting in a hefty fine of up to €20 million or 4% of the organisation’s global turnover. 

  About the Austrian DPA’s Model Case 

  In this specific case, noyb (the European Center for Digital Rights) found that IP addresses (which are classified as personal data by the GDPR) and other identifiers were sent to the US in cookie data as a result of the organisation using Google Analytics. 

  This model case led to the DPA’s decision to rule that Austrian website providers using Google Analytics are in violation of GDPR. It is believed that other EU Member States will soon follow in this decision as well.

  "We expect similar decisions to now drop gradually in most EU member states. We have filed 101 complaints in almost all Member States and the authorities coordinated the response. A similar decision was also issued by the European Data Protection Supervisor last week."

  What does this mean if you are using Google Analytics ?

  If there is one thing to learn from this case, it is that ignoring these court rulings and continuing to use Google Analytics is not a viable option. 

  If you are operating a website in Austria, or your website services Austrian citizens, you should remove Google Analytics from your website immediately. 

  For businesses in other EU Member States, it is also highly recommended that you take action before noyb and local data protection authorities start targeting more businesses. 

  "Instead of actually adapting services to be GDPR compliant, US companies have tried to simply add some text to their privacy policies and ignore the Court of Justice. Many EU companies have followed the lead instead of switching to legal options."

  Removing Google Analytics from your site doesn’t mean that you need to give up website analytics altogether though. There are a variety of Google Analytics alternatives available today. Matomo in particular is a powerful open-source web analytics platform that gives you 100% data ownership and GDPR compliance. 

  

  Matomo is one of the best Google Analytics alternatives offering privacy by design on our Cloud, On-Premise and Matomo for WordPress. So you can get the insights you need while remaining compliant. As the GDPR continues to evolve, you can rest assured that Matomo will be at the forefront of these changes. 

  In addition, all Google Analytics data can be imported into Matomo so no historical data is lost. To make your migration as seamless as possible, we’ve put together a guide to migrating from Google Analytics to Matomo. 

  Ready to begin your journey to GDPR compliance ? Check out our live demo and start your 21-day free trial now – no credit card required.

  If you are interested in learning more about GDPR compliance and Matomo, check out our GDPR resources below :    

  • GDPR Manager user guide
  • How to fill in the information asset registration when using Matomo
  • How to make Matomo GDPR compliant in 12 easy steps
  • How to not process any personal data with Matomo and what it means for you
  • PII, personal data and GDPR. Discover what this means for your privacy
  • How should I write my privacy notice for Matomo Analytics under GDPR
  • Lawful basis for processing personal data under GDPR with Matomo
  • How to complete your privacy policy with Matomo Analytics under GDPR
  • GDPR compliance for Premium Features
  • How to get your Matomo plugin ready for GDPR
  • Subprocessors on Matomo Cloud (subprocessors not applicable to On-Premise)
  • Privacy in Matomo

  What does this mean if you are using Matomo ? 

  Our users can rest assured that Matomo remains in compliance with GDPR as all data is stored in the EU (Matomo Cloud) or in any country of your choice (Matomo On-Premise). With Matomo you’re able to continue analysing your website and not worry about GDPR.

  Final thoughts

  For EU businesses operating websites, now is the time to act. While Google pushes out false narratives to try and convince users that it is safe to continue using Google Analytics, it’s clear from these court rulings that the data protection authorities across the EU disagree with Google’s narrative.

  The fines, reputational damage and stresses mounting from using Google Analytics are imminent. Find an alternative to Google Analytics as this problem is not going away. 

  Getting started with Matomo is easy. Make the switch today and start your free 21-day trial – no credit card required. 

• ffmpeg transcoding stop after few seconds

  9 avril 2018, par Salem F

  Hi i’m trying to do this over week now with no success ,
  What’s i’m trying to do is transcoding video from live streaming source and downscale it with FFmpeg , but every time I start transcoding it broadcasting fro 11 Sec and stop . here last command I tried

    ffmpeg  -re  -i 'http://source.com/1034.ts' -preset ultrafast http://localhost:2052/feed1.ffm

  I tried to download the .ts file with IDM and it finish downloading the file on the exact 12 Sec that FFmpeg stop trans coding on it .

  does that means that FFmpeg download that file as one segment and not continued reading the source video As what video players does usually . BTW I tried with source with VLC player and it didn’t stop playing the the same source video .

  Edit :- I decide to pass FFmpeg command via FFserver config file ffserver.conf

  Launch ffmpeg -i 'http://source.com/1.ts' -copyinkf -codec copy   

  The stream works fine for a while but after testing couple sources I notice it’s struggle to trans-coding HD videos .

  I guess the issue with my VPS KVM server being very limited CPU and RAM ( 128MB only ) ! Since I tried using ultrafast preset but din’t solve the issue , another thing , I notice when I enable AVOptionVideo crf setting on ffserver.conf trans-coding runs bit smoothly without frame-rate dropping .
  Las my server uses Xeon L5520 CPU which is outdated CPU specially I gout 1/4 power of V single core (if they count HT it will be 1/8 of the real core ) :(

  Edit 2 :-

  # vlc -I dummy 'https://source.com/1034.ts' --sout '#standard{access=http,mux=flv,dst=localhost:2052}'
  
  VLC media player 2.2.8 Weatherwax (revision 2.2.7-14-g3cc1d8cba9)
  
  [09d3fdf0] pulse audio output error: PulseAudio server connection failure: Connection refused
  
  [09d279c0] core interface error: no suitable interface module
  
  [09c9b8f8] core libvlc error: interface "globalhotkeys,none" initialization failed
  
  [09d279c0] dbus interface error: Failed to connect to the D-Bus session daemon: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
  
  [09d279c0] core interface error: no suitable interface module
  
  [09c9b8f8] core libvlc error: interface "dbus,none" initialization failed
  
  [09d279c0] dummy interface: using the dummy interface module...
  
  [b5e04ae0] access_output_http access out: Consider passing --http-host=IP on the command line instead.
  
  [b5e38ab8] ts demux: MPEG-4 descriptor not found for pid 0x101 type 0xf
  
  [b5e90ae0] packetizer_mpeg4audio decoder: AAC channels: 2 samplerate: 48000
  
  [flv @ 0xb5e33b40] dimensions not set
  
  [b5e06360] avformat mux error: could not write header: Invalid argument
  
  [b5e88ef0] core decoder error: cannot continue streaming due to errors
  
  [b5e90ae0] core decoder error: cannot continue streaming due to errors

  Here output with -loglevel verbose

  :~# ffmpeg -i http://source.com/1.ts -copyinkf -codec copy  -loglevel verbose  http://127.0.0.1:8090/feed1.ffm
  
  ffmpeg version 2.6.9 Copyright (c) 2000-2016 the FFmpeg developers
  
    built with gcc 4.9.2 (Debian 4.9.2-10)
  
    configuration: --prefix=/usr --extra-cflags='-g -O2 -fstack-protector-strong -Wformat -Werror=format-security ' --extra-ldflags='-Wl,-z,relro' --cc='ccache cc' --enable-shared --enable-libmp3lame --enable-gpl --enable-nonfree --enable-libvorbis --enable-pthreads --enable-libfaac --enable-libxvid --enable-postproc --enable-x11grab --enable-libgsm --enable-libtheora --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libx264 --enable-libspeex --enable-nonfree --disable-stripping --enable-libvpx --enable-libschroedinger --disable-encoder=libschroedinger --enable-version3 --enable-libopenjpeg --enable-librtmp --enable-avfilter --enable-libfreetype --enable-libvo-aacenc --disable-decoder=amrnb --enable-libvo-amrwbenc --enable-libaacplus --libdir=/usr/lib/i386-linux-gnu --disable-vda --enable-libbluray --enable-libcdio --enable-gnutls --enable-frei0r --enable-openssl --enable-libass --enable-libopus --enable-fontconfig --enable-libpulse --disable-mips32r2 --disable-mipsdspr1 --disable-mipsdspr2 --enable-libvidstab --enable-libzvbi --enable-avresample --disable-htmlpages --disable-podpages --enable-libutvideo --enable-libfdk-aac --enable-libx265 --enable-libiec61883 --enable-vaapi --enable-libdc1394 --disable-altivec --shlibdir=/usr/lib/i386-linux-gnu
  
    libavutil      54. 20.100 / 54. 20.100
  
    libavcodec     56. 26.100 / 56. 26.100
  
    libavformat    56. 25.101 / 56. 25.101
  
    libavdevice    56.  4.100 / 56.  4.100
  
    libavfilter     5. 11.102 /  5. 11.102
  
    libavresample   2.  1.  0 /  2.  1.  0
  
    libswscale      3.  1.101 /  3.  1.101
  
    libswresample   1.  1.100 /  1.  1.100
  
    libpostproc    53.  3.100 / 53.  3.100
  
  Invalid UE golomb code
  
      Last message repeated 2 times
  
  Input #0, mpegts, from 'http://source.com/1.ts':
  
    Duration: N/A, start: 30472.768167, bitrate: N/A
  
    Program 1
  
      Metadata:
  
        service_name    : Service01
  
        service_provider: FFmpeg
  
      Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p, 960x540 (960x544) [SAR 1:1 DAR 16:9], 50 fps, 50 tbr, 90k tbn, 100 tbc
  
      Stream #0:1[0x101]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 48000 Hz, stereo, fltp, 105 kb/s
  
  [graph 0 input from stream 0:1 @ 0x971f2c0] tb:1/48000 samplefmt:fltp samplerate:48000 chlayout:0x3
  
  [audio format for output stream 0:0 @ 0x9844de0] auto-inserting filter 'auto-inserted resampler 0' between the filter 'Parsed_anull_0' and the filter 'audio format for output stream 0:0'
  
  [auto-inserted resampler 0 @ 0x97115e0] ch:2 chl:stereo fmt:fltp r:48000Hz -> ch:1 chl:mono fmt:fltp r:22050Hz
  
  [graph 1 input from stream 0:0 @ 0x96f5d00] w:960 h:540 pixfmt:yuv420p tb:1/90000 fr:50/1 sar:1/1 sws_param:flags=2
  
  [scaler for output stream 0:1 @ 0x96f5e80] w:352 h:240 flags:'0x4' interl:0
  
  [scaler for output stream 0:1 @ 0x96f5e80] w:960 h:540 fmt:yuv420p sar:1/1 -> w:352 h:240 fmt:yuv420p sar:40/33 flags:0x4
  
  Output #0, ffm, to 'http://127.0.0.1:8090/feed1.ffm':
  
    Metadata:
  
      creation_time   : now
  
      encoder         : Lavf56.25.101
  
      Stream #0:0: Audio: wmav2, 22050 Hz, mono, fltp, 64 kb/s
  
      Metadata:
  
        encoder         : Lavc56.26.100 wmav2
  
      Stream #0:1: Video: msmpeg4v3 (msmpeg4), yuv420p, 352x240 [SAR 40:33 DAR 16:9], q=2-31, 256 kb/s, 50 fps, 1000k tbn, 15 tbc
  
      Metadata:
  
        encoder         : Lavc56.26.100 msmpeg4
  
  Stream mapping:
  
    Stream #0:1 -> #0:0 (aac (native) -> wmav2 (native))
  
    Stream #0:0 -> #0:1 (h264 (native) -> msmpeg4v3 (msmpeg4))
  
  Press [q] to stop, [?] for help
  
  Invalid UE golomb code
  
  *** dropping frame 3 from stream 1 at ts 1
  
      Last message repeated 1 times
  
  [msmpeg4 @ 0x970f060] warning, clipping 1 dct coefficients to -127..127
  
  *** dropping frame 4 from stream 1 at ts 2
  
      Last message repeated 1 times
  
  *** dropping frame 5 from stream 1 at ts 3
  
      Last message repeated 1 times
  
  *** dropping frame 5 from stream 1 at ts 4
  
  *** dropping frame 6 from stream 1 at ts 4
  
      Last message repeated 1 times
  
  *** dropping frame 7 from stream 1 at ts 5
  
      Last message repeated 1 times
  
  [msmpeg4 @ 0x970f060] warning, clipping 1 dct coefficients to -127..127
  
  *** dropping frame 8 from stream 1 at ts 6
  
      Last message repeated 1 times
  
  *** dropping frame 8 from stream 1 at ts 7
  
  *** dropping frame 9 from stream 1 at ts 7
  
      Last message repeated 1 times
  
  *** dropping frame 10 from stream 1 at ts 8
  
      Last message repeated 1 times
  
  *** dropping frame 11 from stream 1 at ts 9
  
      Last message repeated 1 times
  
  *** dropping frame 11 from stream 1 at ts 10
  
  *** dropping frame 12 from stream 1 at ts 10
  
      Last message repeated 1 times
  
  *** dropping frame 13 from stream 1 at ts 11
  
      Last message repeated 1 times
  
  *** dropping frame 14 from stream 1 at ts 12
  
      Last message repeated 1 times
  
  *** dropping frame 14 from stream 1 at ts 13
  
  *** dropping frame 15 from stream 1 at ts 13
  
      Last message repeated 1 times
  
  *** dropping frame 16 from stream 1 at ts 14
  
      Last message repeated 1 times
  
  *** dropping frame 17 from stream 1 at ts 15
  
      Last message repeated 1 times
  
  *** dropping frame 17 from stream 1 at ts 16
  
  *** dropping frame 18 from stream 1 at ts 16
  
      Last message repeated 1 times
  
  *** dropping frame 19 from stream 1 at ts 17
  
      Last message repeated 1 times
  
  *** dropping frame 20 from stream 1 at ts 18me=00:00:01.33 bitrate= 270.3kbits/s dup=0 drop=39
  
      Last message repeated 1 times
  
  *** dropping frame 20 from stream 1 at ts 19
  
  *** dropping frame 21 from stream 1 at ts 19
  
      Last message repeated 1 times
  
  *** dropping frame 22 from stream 1 at ts 20
  
      Last message repeated 1 times
  
  *** dropping frame 23 from stream 1 at ts 21
  
      Last message repeated 1 times
  
  *** dropping frame 23 from stream 1 at ts 22
  
  *** dropping frame 24 from stream 1 at ts 22
  
      Last message repeated 1 times
  
  *** dropping frame 25 from stream 1 at ts 23
  
      Last message repeated 1 times
  
  *** dropping frame 26 from stream 1 at ts 24
  
      Last message repeated 1 times
  
  *** dropping frame 26 from stream 1 at ts 25
  
  *** dropping frame 27 from stream 1 at ts 25
  
      Last message repeated 1 times
  
  *** dropping frame 28 from stream 1 at ts 26
  
      Last message repeated 1 times
  
  *** dropping frame 29 from stream 1 at ts 27
  
      Last message repeated 1 times
  
  *** dropping frame 29 from stream 1 at ts 28
  
  *** dropping frame 30 from stream 1 at ts 28
  
      Last message repeated 1 times
  
  *** dropping frame 31 from stream 1 at ts 29
  
      Last message repeated 1 times
  
  *** dropping frame 32 from stream 1 at ts 30
  
      Last message repeated 1 times
  
  *** dropping frame 32 from stream 1 at ts 31
  
  *** dropping frame 33 from stream 1 at ts 31
  
      Last message repeated 1 times
  
  *** dropping frame 34 from stream 1 at ts 32
  
      Last message repeated 1 times
  
  *** dropping frame 34 from stream 1 at ts 33
  
  *** dropping frame 35 from stream 1 at ts 33
  
  *** dropping frame 35 from stream 1 at ts 34
  
  *** dropping frame 36 from stream 1 at ts 34
  
      Last message repeated 1 times
  
  *** dropping frame 37 from stream 1 at ts 35
  
      Last message repeated 1 times
  
  Invalid UE golomb code
  
  *** dropping frame 38 from stream 1 at ts 36
  
      Last message repeated 1 times
  
  *** dropping frame 38 from stream 1 at ts 37
  
  *** dropping frame 39 from stream 1 at ts 37
  
      Last message repeated 1 times
  
  *** dropping frame 40 from stream 1 at ts 38
  
      Last message repeated 1 times
  
  *** dropping frame 41 from stream 1 at ts 39me=00:00:02.73 bitrate= 311.7kbits/s dup=0 drop=88
  
      Last message repeated 1 times
  
  *** dropping frame 41 from stream 1 at ts 40
  
  *** dropping frame 42 from stream 1 at ts 40
  
      Last message repeated 1 times
  
  *** dropping frame 43 from stream 1 at ts 41
  
      Last message repeated 1 times
  
  *** dropping frame 44 from stream 1 at ts 42
  
      Last message repeated 1 times
  
  *** dropping frame 44 from stream 1 at ts 43
  
  *** dropping frame 45 from stream 1 at ts 43
  
      Last message repeated 1 times
  
  *** dropping frame 46 from stream 1 at ts 44
  
      Last message repeated 1 times
  
  *** dropping frame 47 from stream 1 at ts 45
  
      Last message repeated 1 times
  
  *** dropping frame 47 from stream 1 at ts 46
  
  *** dropping frame 48 from stream 1 at ts 46
  
      Last message repeated 1 times
  
  *** dropping frame 49 from stream 1 at ts 47
  
      Last message repeated 1 times
  
  *** dropping frame 50 from stream 1 at ts 48
  
      Last message repeated 1 times
  
  *** dropping frame 50 from stream 1 at ts 49
  
  *** dropping frame 51 from stream 1 at ts 49
  
      Last message repeated 1 times
  
  *** dropping frame 52 from stream 1 at ts 50
  
      Last message repeated 1 times
  
  *** dropping frame 53 from stream 1 at ts 51
  
      Last message repeated 1 times
  
  [h264 @ 0x9844a00] error while decoding MB 58 12, bytestream -5
  
  [h264 @ 0x9844a00] concealing 1311 DC, 1311 AC, 1311 MV errors in B frame
  
  *** dropping frame 53 from stream 1 at ts 52
  
  No more output streams to write to, finishing.
  
  frame=   55 fps= 42 q=4.3 Lsize=     152kB time=00:00:03.66 bitrate= 339.6kbits/s dup=0 drop=119
  
  video:116kB audio:26kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 6.760316%
  
  Input file #0 (http://source.com/1.ts):
  
    Input stream #0:0 (video): 174 packets read (220322 bytes); 174 frames decoded;
  
    Input stream #0:1 (audio): 156 packets read (36657 bytes); 156 frames decoded (159744 samples);
  
    Total: 330 packets (256979 bytes) demuxed
  
  Output file #0 (http://127.0.0.1:8090/feed1.ffm):
  
    Output stream #0:0 (audio): 72 frames encoded (73383 samples); 72 packets muxed (26712 bytes);
  
    Output stream #0:1 (video): 55 frames encoded; 55 packets muxed (119080 bytes);
  
    Total: 127 packets (145792 bytes) muxed

  Here input url file info After i download it to my PC with IDM

  General
  
  ID                             : 1 (0x1)
  
  Complete name                  : D:\1.ts
  
  Format                         : MPEG-TS
  
  File size                      : 256 KiB
  
  Duration                       : 2 s 520 ms
  
  Overall bit rate mode          : Variable
  
  Overall bit rate               : 788 kb/s
  
  
  
  Video
  
  ID                             : 256 (0x100)
  
  Menu ID                        : 1 (0x1)
  
  Format                         : AVC
  
  Format/Info                    : Advanced Video Codec
  
  Format profile                 : High@L3.1
  
  Format settings, CABAC         : Yes
  
  Format settings, RefFrames     : 2 frames
  
  Codec ID                       : 27
  
  Duration                       : 2 s 680 ms
  
  Width                          : 960 pixels
  
  Height                         : 540 pixels
  
  Display aspect ratio           : 16:9
  
  Frame rate                     : 50.000 FPS
  
  Color space                    : YUV
  
  Chroma subsampling             : 4:2:0
  
  Bit depth                      : 8 bits
  
  Scan type                      : Progressive
  
  
  
  Audio
  
  ID                             : 257 (0x101)
  
  Menu ID                        : 1 (0x1)
  
  Format                         : AAC
  
  Format/Info                    : Advanced Audio Codec
  
  Format version                 : Version 4
  
  Format profile                 : LC
  
  Muxing mode                    : ADTS
  
  Codec ID                       : 15
  
  Duration                       : 2 s 69 ms
  
  Bit rate mode                  : Variable
  
  Channel(s)                     : 2 channels
  
  Channel positions              : Front: L R
  
  Sampling rate                  : 48.0 kHz
  
  Frame rate                     : 46.875 FPS (1024 SPF)
  
  Compression mode               : Lossy
  
  Delay relative to video        : -12 ms
  
  
  
  Menu
  
  ID                             : 4096 (0x1000)
  
  Menu ID                        : 1 (0x1)
  
  Duration                       : 2 s 520 ms
  
  List                           : 256 (0x100) (AVC) / 257 (0x101) (AAC)
  
  Service name                   : Service01
  
  Service provider               : FFmpeg
  
  Service type                   : digital television