Recherche avancée

Sur d’autres sites (3218)

• Ode to the Gravis Ultrasound

  1er août 2011, par Multimedia Mike — General

  WARNING : This post is a bunch of nostalgia. Feel free to follow along if you recall the DOS days of the early-mid 1990s.

  I finally let go of my Gravis Ultrasound MAX sound card a little while ago. It felt like the end of an era for me, even though I had scarcely used the card in recent memory.

  
  
  

  The Beginning
  What is the Gravis Ultrasound ? Only the finest PC sound card from the classic DOS days. Back in the day (very early 1990s), most consumer PC sound cards were Yamaha OPL FM synthesizers paired with a basic digital to analog converter (DAC). Gravis, a company known for game controllers, dared to break with the dominant paradigm of Sound Blaster clones and create a sound card that had 32 digital channels.
  
  I heard about the GUS sometime in 1992 through one of the dominant online services at the time, Prodigy. Through the message boards, I learned of a promotion with Electronic Arts in which customers could pre-order a GUS at a certain discount along with 2 EA games from a selected catalog (with progressive discounts when ordering more games from the list). I know I got the DOS version of PowerMonger ; I think the other was Night Shift, though that doesn’t seem to be an EA title.

  Anyway, 1992 saw many maddening delays of the GUS hardware. Finally, reports of GUS shipments began to trickle into the Prodigy message forums. Then one day in November, 1992, mine arrived. Into the 286 machine it went and a valiant attempt at software installation was made. A friend and I fought with the software late into the evening, trying to make this thing work reasonably. I remember grabbing a pair of old headphones sitting near the computer that were used for an ancient (even for the time) portable radio. That was the only means of sound reproduction we had available at that moment. And it still sounded incredible.

  After graduating to progressively superior headphones, I would later return to that original pair only to feel my ears were being physically assaulted. Strange, they sounded fine that first night I was trying to make the GUS work. I guess this was my first understanding that the degree to which one is a snobby audiophile is all a matter of hard-earned experience.

  Technology
  The GUS was powered by something called a GF1 which was supposed to use a technology called wavetable synthesis. In the early days, I thought (and I wasn’t alone in this) that this meant that the GF1 chip had a bunch of digitized instrument samples stored in the ASIC. That wasn’t it.

  However, it did feature 32 digital channels at a time when most PC audio cards had 2 (plus that Yamaha FM synthesizer). There was some hemming and hawing about how the original GUS couldn’t drive all 32 channels at a full 44.1 kHz ("CD quality") playback rate. It’s true— if 14 channels were enabled, all could be played at 44.1 kHz. Enabling more channels started progressive degradation and with all 32 channels, each was only playing at around 19 kHz. Still, from my emerging game programmer perspective, that allowed for 8-channel tracker music and 6 channels of sound effects, all at the vaunted CD level of quality.

  Games and Compatibility
  The primary reason to have a discrete sound card was for entertainment applications — ahem, games. GUS support was pretty sketchy out of the gate (ostensibly a major reason for the card’s delay). While many sound cards offered Sound Blaster emulation by basically having the same hardware as Sound Blaster cards, the GUS took a software route towards emulating the SB. To do this required a program called the Sound Blaster Operating System, or SBOS.

  Oh, how awesome it was to hear the program exclaim "SBOS installed !" And how harshly it grated on your nerves after the 200th time hearing it due to so many reboots and fiddling with options to make your games work. Also, I’ve always wondered if there’s something special about sampling an ’s’ sound — does it strain the sampling frequency range ? Perhaps the phrase was sampled at too low a bitrate because the ’s’ sounds didn’t come through very clearly, which is something you notice after hundreds of iterations when there are 3 ’s’ sounds in the phrase.

  Fortunately, SBOS became less relevant with the advent of Mega-Em, a separate emulator which intercepted calls to Roland MIDI systems and routed them to the very capable GUS. Roland-supporting games sounded beautiful.

  Eventually, more and more DOS games were released with native Gravis support, sometimes with the help of The Miles Sound System (from our friends at Rad Game Tools — you know, the people behind Smacker and Bink). The library changelog is quite the trip down PC memory lane.

  An important area where the GUS shined brightly was that of demos and music trackers. The emerging PC demo scene embraced the powerful GUS (aided, no doubt, by Gravis’ sponsorship of the community) and the coolest computer art and music of the time natively supported the card.

  Programming
  At this point in my life, I was a budding programmer in high school and was fairly intent on programming video games. So far, I had figured out how to make a few blips using a borrowed Sound Blaster card. I went to great lengths to learn how to program the Gravis Ultrasound.

  Oh you kids today, with your easy access to information at the tips of your fingers thanks to Google and the broader internet. I had to track down whatever information I could find through a combination of Prodigy message boards and local dialup BBSes and FidoNet message bases. Gravis was initially tight-lipped about programming information for its powerful card, as was de rigueur of hardware companies (something that largely persists to this day). But Gravis eventually saw an opportunity to one-up encumbent Creative Labs and released a full SDK for the Ultrasound. I wanted the SDK badly.

  So it was early-mid 1993. Gravis released an SDK. I heard that it was available on their support BBS. Their BBS with a long distance phone number. If memory serves, the SDK was only in the neighborhood of 1.5 Mbytes. That takes a long time to transfer via a 2400 baud modem at a time when long distance phone charges were still a thing and not insubstantial.

  Luckily, they also put the SDK on something called an ’FTP site’. Fortunately, about this time, I had the opportunity to get some internet access via the local university.

  Indeed, my entire motivation for initially wanting to get on the internet was to obtain special programming information. Is that nerdy enough for you ?

  I see that the GUS SDK is still available via the Gravis FTP site. The file GUSDK222.ZIP is dated 1998 and is less than a megabyte.

  Next Generation : CD Support
  So I had my original GUS by the end of 1992. That was just the first iteration of the Gravis Ultrasound. The next generation was the GUS MAX. When I was ready to get into the CD-ROM era, this was what I wanted in my computer. This is because the GUS MAX had CD-ROM support. This is odd to think about now when all optical drives have SATA interfaces and (P)ATA interfaces before that— what did CD-ROM compatibility mean back then ? I wasn’t quite sure. But in early 1995, I headed over to Computer City (R.I.P.) and bought a new GUS MAX and Sony double-speed CD-ROM drive to install in the family’s PC.

  
  
  

  About the "CD-ROM compatibility" : It seems that there were numerous competing interfaces in the early days of CD-ROM technology. The GUS MAX simply integrated 3 different CD-ROM controllers onto the audio card. This was superfluous to me since the Sony drive came with an appropriate controller card anyway, though I didn’t figure out that the extra controller card was unnecessary until after I installed it. No matter ; computers of the day were rife with expansion ports.

  
  
  The 3 different CD-ROM controllers on the GUS MAX
  

  Explaining The Difference
  It was difficult to explain the difference in quality to those who didn’t really care. Sometime during 1995, I picked up a quasi-promotional CD-ROM called "The Gravis Ultrasound Experience" from Babbage’s computer store (remember when that was a thing ?). As most PC software had been distributed on floppy discs up until this point, this CD-ROM was an embarrassment of riches. Tons of game demos, scene demos, tracker music, and all the latest GUS drivers and support software.

  Further, the CD-ROM had a number of red book CD audio tracks that illustrated the difference between Sound Blaster cards and the GUS. I remember loaning this to a tech-savvy coworker who disbelieved how awesome the GUS was. The coworker took it home, listened to it, and wholly agreed that the GUS audio sounded better than the SB audio in the comparison — and was thoroughly confused because she was hearing this audio emanating from her Sound Blaster. It was the difference between real-time and pre-rendered audio, I suppose, but I failed to convey that message. I imagine the same issue comes up even today regarding real-time video rendering vs., e.g., a pre-rendered HD cinematic posted on YouTube.

  Regrettably, I can’t find that CD-ROM anymore which leads me to believe that the coworker never gave it back. Too bad, because it was quite the treasure trove.

  Aftermath
  According to folklore I’ve heard, Gravis couldn’t keep up as the world changed to Windows and failed to deliver decent drivers. Indeed, I remember trying to keep my GUS in service under Windows 95 well into 1998 but eventually relented and installed some kind of more appropriate sound card that was better supported under Windows.

  Of course, audio output capability has been standard issue for any PC for at least 10 years and many people aren’t even aware that discrete sound cards still exist. Real-time audio rendering has become less essential as full musical tracks can be composed and compressed into PCM format and delivered with the near limitless space afforded by optical storage.

  A few years ago, it was easy to pick up old GUS cards on eBay for cheap. As of this writing, there are only a few and they’re pricy (but perhaps not selling). Maybe I was just viewing during the trough of no value a few years ago.

  Nowadays, of course, anyone interested in studying the old GUS or getting a nostalgia fix need only boot up the always-excellent DOSBox emulator which provides remarkable GUS emulation support.

• How to increase engagement and convert them into customers

  8 septembre 2020, par Joselyn Khor — Analytics Tips, Marketing

  Long gone are the days of simply tracking page views as a measure of engagement. Now it’s about engagement analysis, which is layered and provides insight for effective data-driven decisions.

  Discover how engaged people are with your website by uncovering behavioural patterns that tell you how well your site and content is or isn’t performing. This insight helps you re-evaluate, adapt and optimise your content and strategy. The more engaged they are, the more likely you’ll be able to guide them on a predetermined journey that results in more conversions ; and helps you reach the goals you’ve set for your business. 

  Why is visitor engagement important ?

  It’s vital to measure engagement if you have anything content related that plays a role in your customer’s journey. Some websites may find more value in figuring out how engaging their entire site is, while others may only want to zone in on, say, a blogging section, e-newsletters, social media channels or sign-up pages.

  In the larger scheme of things, engagement can be seen as what’s running your site. Every aspect of the buyer’s journey requires your visitors to be engaged. Whether you’re trying to attract, convert or build a loyal audience base, you need to know your content is optimised to maintain their attention and encourage them along the path to purchase, conversion or loyalty.

  How to increase engagement with Matomo

  You need to know what’s going right or wrong to eventually be able to deliver more riveting content your visitors can’t help but be drawn to. Learn how to apply Matomo’s easy-to-use features to increase engagement :

  1. The Behaviour feature
  2. Heatmaps
  3. A/B Testing
  4. Media Analytics
  5. Transitions
  6. Custom reports
  7. Other metrics to keep an eye on

  1. Look at the Behaviour feature

  It allows you to learn how visitors are responding to your content. This information is gathered by drawing insight from features such as site search, downloads, events and content interactions. Learn more

  

  Matomo’s top five ways to increase engagement with the Behaviour feature :

  Behaviour -> Pages
  Get complete insights on what pages your users engage with, what pages provide little value to your business and see the results of entry and exit pages. If important content is generating low traffic, you need to place it where it can be seen. Spend time where it matters and focus on the content that will engage with your users and see how it eventually converts them into customers.

  Behaviour -> Site search
  Site search tracks how people use your website’s internal search engine. You can see :

  • What search keywords visitors used on your website’s internal search.
  • Which of those keywords resulted in no results (what content your visitors are looking for but cannot find).
  • What pages visitors visited immediately after a search.
  • What search categories visitors use (if your website employs search categories).

  Behaviour -> Downloads
  What are users wanting to take away with them ? They could be downloading .pdfs, .zip files, ebooks, infographics or other free/paid resources. For example, if you were working for an education institution and created valuable information packs for students that you made available online in .pdf format. To see an increase in downloads meant students were finding the .pdfs and realising the need to download them. No downloads could mean the information packs weren’t being found which would be problematic.

  Behaviour -> Events
  Tracking events is a very useful way to measure the interactions your users have with your website content, which are not directly page views or downloads.

  How have Events been used effectively ? A great example comes from one of our customers, Catalyst. They wanted to capture and measure the user interaction of accordions (an area of content that expands or closes depending on how a user interacts with it) to see if people were actually getting all the information available to them on this one page. By creating an Event to record which accordion had been opened, as well as creating events for other user interactions, they were able to figure out which content got the most engagement and which got the least. Being able to see how visitors navigated through their website helped them optimise the site to ensure people were getting the relevant information they were craving.

  Behaviour -> Content interactions
  Content tracking allows you to track interaction within the content of your web page. Go beyond page views, bounce rates and average time spent on page with your content. Instead, you can analyse content interaction rates based on mouse clicking and configuring scrolling or hovering behaviours to see precisely how engaged your users are. If interaction rates are low, perhaps you need to restructure your page layout to grab your user’s attention sooner. Possibly you will get more interaction when you have more images or banner ads to other areas of your business.

  

  Watch this video to learn about the Behaviour feature

  2. Set up Heatmaps

  Effortlessly discover how your visitors truly engage with your most important web pages that impact the success of your business. Heatmaps shows you visually where your visitors try to click, move the mouse and how far down they scroll on each page.

  

  You don’t need to waste time digging for key metrics or worry about putting together tables of data to understand how your visitors are interacting with your website. Heatmaps make it easy and fast to discover where your users are paying their attention, where they have problems, where useless content is and how engaging your content is. Get insights that you cannot get from traditional reports. Learn more

  
  TRY IT FOR FREE
  

  3. Carry out A/B testing

  With A/B Testing you reduce risk in your decision-making and can test what your visitors are responding well to. 

  

  Ever had discussions with colleagues about where to place content on a landing page ? Or discussed what the call-to-action should be and assumed you were making the best decisions ? The truth is, you never know what really works the best (and what doesn’t) unless you test it. Learn more

  How to increase engagement with A/B Testing : Test, test and test. This is a surefire way to learn what content is leading your visitors on a path to conversion and what isn’t.

  4. Media Analytics

  Tells you how visitors are engaging with your video or audio content, and whether they’re leading to your desired conversions. Track :

  • How many plays your media gets and which parts they viewed
  • Finish rates
  • How your media was consumed over time
  • How media was consumed on specific days
  • Which locations your users were viewing your content from
  • Learn more

  

  How to increase engagement with Media Analytics : These metrics give a picture of how audiences are behaving when it comes to your content. By showing insights such as, how popular your media content is, how engaging it is and which days content will be most viewed, you can tailor content strategies to produce content people will actually find interesting and watch/listen.

  Matomo example : When we went through the feature video metrics on our own site to see how our videos were performing, we noticed our Acquisition video had a 95% completion rate. Even though it was longer than most videos, the stats showed us it had, by far, the most engagement. By using Media Analytics to get insights on the best and worst performing videos, we gathered useful info to help us better allocate resources effectively so that in the future, we’re producing more videos that will be watched.

  5. Investigate transitions

  See which page visitors are entering the site from and where they exit to. Transitions shows engagement on each page and whether the content is leading them to the pages you want them to be directed to.

  

  This gives you a greater understanding of user pathways. You may be assuming visitors are finding your content from one particular pathway, but figure out users are actually coming through other channels you never thought of. Through Transitions, you may discover and capitalise on new opportunities from external sites.

  How to increase engagement with Transitions : Identify clearly where users may be getting distracted to click away and where other pages are creating opportunity to click-through to conversion. 

  6. Create Custom Reports

  You can choose from over 200 dimensions and metrics to get the insights you need as well as various visualisation options. This makes understanding the data incredibly easy and you can get the insights you need instantly for faster results without the need for a developer. Learn more

  

  How to increase engagement with Custom Reports : Set custom reports to see when content is being viewed and figure out how engaged users are by looking at different hours of the day or which days of the week they’re visiting your website. For example, you could be wondering what hour of the day performed best for converting your customers. Understanding these metrics helps you figure out the best time to schedule your blog posts, pay-per-click advertising, edms or social media posts knowing that your visitors are more likely to convert at different times.

  
  TRY IT FOR FREE
  

  7. Other metrics to key an eye on …

  A good indication of a great experience and of engagement is whether your readers, viewers or listeners want to do it again and again.

  “Best” metrics are hard to determine so you’ll need to ask yourself what you want to do or what you want your site to do. How do you want your users to behave or what kind of buyer’s journey do you want them to have ?

  Want to know where to start ? Look at …

  • Bounce rate – a high bounce rate isn’t great as people aren’t finding what they’re looking for and are leaving without taking action. (This offers great opportunities as you can test to see why people are bouncing off your site and figure out what you need to change.)
  • Time on site – a long time on site is usually a good indication that people are spending time reading, navigating and being engaged with your website. 
  • Frequency of visit – how often do people come back to interact with the content on your website ? The higher the % of your visitors that come back time and time again will show how engaged they are with your content.
  • Session length/average session duration – how much time users spend on site each session
  • Pages per session – is great to show engagement because it shows visitors are happy going through your website and learn more about your business.

  Key takeaway

  Whichever stage of the buyer’s journey your visitors are in, you need to ensure your content is optimised for engagement so that visitors can easily spend time on your website.

  “Every single visit by every single visitor is no longer judged as a success or a failure at the end of 29 min (max) session in your analytics tool. Every visit is not a ‘last-visit’, rather it becomes a continuous experience leading to a win-win outcome.” – Avinash Kaushik

  As you can tell, one size does not fit all when it comes to analysing and measuring engagement, but with a toolkit of features, you can make sure you have everything you need to experiment and figure out the metrics that matter to the success of your business and website.

  Concurrently, these gentle nudges for visitors to consume more and more content encourages them along their path to purchase, conversion or loyalty. They get a more engaging website experience over time and you get happy visitors/customers who end up coming back for more.

  
  TRY IT FOR FREE
  

  Want to learn how to increase conversions with Matomo ? Look out for the final in this series : part 3 ! We’ll go through how you can boost conversions and meet your business goals with web analytics. 

• ffmpeg massive error spamming from FritzBox rtsp stream

  19 février 2019, par itzaiiro

  Im trying to offer a rtsp live TV stream via rtmp to my family, since the Fritz Box (which is offering the stream) has only 4 tuners -> at most 4 streams can be watched simultaneously.
  Im using ffmpeg to prepare the stream as dash stream and send it to my rtmp nginx. When i run ffmpeg im experiencing heavy image and audio artifacts in the final stream and error spams of doom in the console. I couldn’t find anything specific to my case on google. I read on the internet that AVM barely implemented the rtsp protocoll enough to get it to work with vlc mediaplayer.

  launch param :

  ffmpeg -i "rtsp://192.168.178.1:554/?avm=1&freq=114&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=1&pids=0,16,17,18,20,260,543,544,546,548,1621" -sn -vcodec libx264 -vprofile baseline -acodec aac -strict -2 -b:v 500k -minrate 500k -maxrate 500k -bufsize 1000k -g 60 -s 640x360 -f flv rtmp://192.168.178.15/dash/pro_sieben_low -sn -vcodec libx264 -vprofile baseline -acodec aac -strict -2 -b:v 1500k -minrate 1500k -maxrate 1500k -bufsize 3000k -g 60 -s 1280x720 -f flv rtmp://192.168.178.15/dash/pro_sieben_med -sn -vcodec libx264 -vprofile baseline -acodec aac -strict -2 -b:v 5000k -minrate 5000k -maxrate 5000k -bufsize 10000k -g 60 -s 1920x1080 -f flv rtmp://192.168.178.15/dash/pro_sieben_high

  ffmpeg output (windows) :
  stored in pastebin
  https://pastebin.com/p4HAyBi5

  Is there anyway to get this under control ? The original stream is running good with vlc, but its unwatchable after its out of ffmpeg.

  Edit :
  I was running/testing this on my windows machine, but my target for this task is a ubuntu 16.04 so here ffmpeg on target with pthread support :

  ffmpeg -i "rtsp://192.168.178.1:554/?avm=1&freq=114&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=1&pids=0,16,17,18,20,260,543,544,546,548,1621" -sn -vcodec libx264 -vprofile baseline -acodec aac -strict -2 -b:v 500k -minrate 500k -maxrate 500k -bufsize 1000k -g 60 -s 640x360 -f flv rtmp://192.168.178.15/dash/pro_sieben_low -sn -vcodec libx264 -vprofile baseline -acodec aac -strict -2 -b:v 1500k -minrate 1500k -maxrate 1500k -bufsize 3000k -g 60 -s 1280x720 -f flv rtmp://192.168.178.15/dash/pro_sieben_med -sn -vcodec libx264 -vprofile baseline -acodec aac -strict -2 -b:v 5000k -minrate 5000k -maxrate 5000k -bufsize 10000k -g 60 -s 1920x1080 -f flv rtmp://192.168.178.15/dash/pro_sieben_high
  
  ffmpeg version 2.8.15-0ubuntu0.16.04.1 Copyright (c) 2000-2018 the FFmpeg developers
  
    built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.10) 20160609
  
    configuration: --prefix=/usr --extra-version=0ubuntu0.16.04.1 --build-suffix=-ffmpeg --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --cc=cc --cxx=g++ --enable-gpl --enable-shared --disable-stripping --disable-decoder=libopenjpeg --disable-decoder=libschroedinger --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-librtmp --enable-libschroedinger --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxvid --enable-libzvbi --enable-openal --enable-opengl --enable-x11grab --enable-libdc1394 --enable-libiec61883 --enable-libzmq --enable-frei0r --enable-libx264 --enable-libopencv
  
    libavutil      54. 31.100 / 54. 31.100
  
    libavcodec     56. 60.100 / 56. 60.100
  
    libavformat    56. 40.101 / 56. 40.101
  
    libavdevice    56.  4.100 / 56.  4.100
  
    libavfilter     5. 40.101 /  5. 40.101
  
    libavresample   2.  1.  0 /  2.  1.  0
  
    libswscale      3.  1.101 /  3.  1.101
  
    libswresample   1.  2.101 /  1.  2.101
  
    libpostproc    53.  3.100 / 53.  3.100
  
  [mpeg2video @ 0x167cde0] Invalid frame dimensions 0x0.
  
      Last message repeated 10 times
  
  [rtsp @ 0x1627c20] Could not find codec parameters for stream 4 (Unknown: none ([5][0][0][0] / 0x0005)): unknown codec
  
  Consider increasing the value for the 'analyzeduration' and 'probesize' options
  
  Input #0, rtsp, from 'rtsp://192.168.178.1:554/?avm=1&freq=114&bw=8&msys=dvbc&mtype=256qam&sr=6900&specinv=1&pids=0,16,17,18,20,260,543,544,546,548,1621':
  
    Metadata:
  
      title           : SatIPServer:1 0,0,4
  
    Duration: N/A, start: 33786.528778, bitrate: N/A
  
    Program 12101
  
      Metadata:
  
        service_name    : ?▒RTL▒ Television
  
        service_provider: ?Unitymedia
  
    Program 12102
  
      Metadata:
  
        service_name    : ?SAT.1
  
        service_provider: ?Unitymedia
  
    Program 12103
  
      Metadata:
  
        service_name    : ?ProSieben
  
        service_provider: ?Unitymedia
  
      Stream #0:3: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv), 720x576 [SAR 64:45 DAR 16:9], max. 15000 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc
  
      Stream #0:2(deu): Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 192 kb/s (clean effects)
  
      Stream #0:0(deu): Audio: ac3 ([6][0][0][0] / 0x0006), 48000 Hz, 5.1(side), fltp, 384 kb/s (clean effects)
  
      Stream #0:1(deu,deu): Subtitle: dvb_teletext ([6][0][0][0] / 0x0006), 492x250
  
      Stream #0:4: Unknown: none ([5][0][0][0] / 0x0005)
  
    Program 12104
  
      Metadata:
  
        service_name    : ?VOX
  
        service_provider: ?Unitymedia
  
    Program 12105
  
      Metadata:
  
        service_name    : ?RTL2
  
        service_provider: ?Unitymedia
  
    Program 12106
  
      Metadata:
  
        service_name    : ?kabel eins
  
        service_provider: ?Unitymedia
  
    Program 12107
  
      Metadata:
  
        service_name    : ?▒S▒uper▒ RTL▒
  
        service_provider: ?Unitymedia
  
    Program 12109
  
      Metadata:
  
        service_name    : ?ntv
  
        service_provider: ?Unitymedia
  
    Program 12113
  
      Metadata:
  
        service_name    : ?ProSieben MAXX
  
        service_provider: ?Unitymedia
  
    Program 20116
  
      Metadata:
  
        service_name    : ?SIXX
  
        service_provider: ?Unitymedia
  
  [libx264 @ 0x182b140] using SAR=1/1
  
  [libx264 @ 0x182b140] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2
  
  [libx264 @ 0x182b140] profile Constrained Baseline, level 3.0
  
  [libx264 @ 0x182b140] 264 - core 148 r2643 5c65704 - H.264/MPEG-4 AVC codec - Copyleft 2003-2015 - http://www.videolan.org/x264.html - options: cabac=0 ref=3 deblock=1:0:0 analyse=0x1:0x111 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=3 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=60 keyint_min=6 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=cbr mbtree=1 bitrate=500 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 vbv_maxrate=500 vbv_bufsize=1000 nal_hrd=none filler=0 ip_ratio=1.40 aq=1:1.00
  
  [libx264 @ 0x16e03c0] using SAR=1/1
  
  [libx264 @ 0x16e03c0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2
  
  [libx264 @ 0x16e03c0] profile Constrained Baseline, level 3.1
  
  [libx264 @ 0x16e03c0] 264 - core 148 r2643 5c65704 - H.264/MPEG-4 AVC codec - Copyleft 2003-2015 - http://www.videolan.org/x264.html - options: cabac=0 ref=3 deblock=1:0:0 analyse=0x1:0x111 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=3 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=60 keyint_min=6 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=cbr mbtree=1 bitrate=1500 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 vbv_maxrate=1500 vbv_bufsize=3000 nal_hrd=none filler=0 ip_ratio=1.40 aq=1:1.00
  
  [libx264 @ 0x16cc880] using SAR=1/1
  
  [libx264 @ 0x16cc880] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2
  
  [libx264 @ 0x16cc880] profile Constrained Baseline, level 4.0
  
  [libx264 @ 0x16cc880] 264 - core 148 r2643 5c65704 - H.264/MPEG-4 AVC codec - Copyleft 2003-2015 - http://www.videolan.org/x264.html - options: cabac=0 ref=3 deblock=1:0:0 analyse=0x1:0x111 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=3 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=60 keyint_min=6 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=cbr mbtree=1 bitrate=5000 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 vbv_maxrate=5000 vbv_bufsize=10000 nal_hrd=none filler=0 ip_ratio=1.40 aq=1:1.00
  
  Output #0, flv, to 'rtmp://192.168.178.15/dash/pro_sieben_low':
  
    Metadata:
  
      title           : SatIPServer:1 0,0,4
  
      encoder         : Lavf56.40.101
  
      Stream #0:0: Video: h264 (libx264) ([7][0][0][0] / 0x0007), yuv420p, 640x360 [SAR 1:1 DAR 16:9], q=-1--1, 500 kb/s, 25 fps, 1k tbn, 25 tbc
  
      Metadata:
  
        encoder         : Lavc56.60.100 libx264
  
      Stream #0:1(deu): Audio: aac ([10][0][0][0] / 0x000A), 48000 Hz, 5.1(side), fltp, 128 kb/s (clean effects)
  
      Metadata:
  
        encoder         : Lavc56.60.100 aac
  
  Output #1, flv, to 'rtmp://192.168.178.15/dash/pro_sieben_med':
  
    Metadata:
  
      title           : SatIPServer:1 0,0,4
  
      encoder         : Lavf56.40.101
  
      Stream #1:0: Video: h264 (libx264) ([7][0][0][0] / 0x0007), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], q=-1--1, 1500 kb/s, 25 fps, 1k tbn, 25 tbc
  
      Metadata:
  
        encoder         : Lavc56.60.100 libx264
  
      Stream #1:1(deu): Audio: aac ([10][0][0][0] / 0x000A), 48000 Hz, 5.1(side), fltp, 128 kb/s (clean effects)
  
      Metadata:
  
        encoder         : Lavc56.60.100 aac
  
  Output #2, flv, to 'rtmp://192.168.178.15/dash/pro_sieben_high':
  
    Metadata:
  
      title           : SatIPServer:1 0,0,4
  
      encoder         : Lavf56.40.101
  
      Stream #2:0: Video: h264 (libx264) ([7][0][0][0] / 0x0007), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], q=-1--1, 5000 kb/s, 25 fps, 1k tbn, 25 tbc
  
      Metadata:
  
        encoder         : Lavc56.60.100 libx264
  
      Stream #2:1(deu): Audio: aac ([10][0][0][0] / 0x000A), 48000 Hz, 5.1(side), fltp, 128 kb/s (clean effects)
  
      Metadata:
  
        encoder         : Lavc56.60.100 aac
  
  Stream mapping:
  
    Stream #0:3 -> #0:0 (mpeg2video (native) -> h264 (libx264))
  
    Stream #0:0 -> #0:1 (ac3 (native) -> aac (native))
  
    Stream #0:3 -> #1:0 (mpeg2video (native) -> h264 (libx264))
  
    Stream #0:0 -> #1:1 (ac3 (native) -> aac (native))
  
    Stream #0:3 -> #2:0 (mpeg2video (native) -> h264 (libx264))
  
    Stream #0:0 -> #2:1 (ac3 (native) -> aac (native))
  
  Press [q] to stop, [?] for help
  
  RTP: missed 2137 packets.0 q=26.0 q=23.0 size=     238kB time=00:00:04.91 bitrate= 397.3kbits/s
  
  [rtsp @ 0x1627c20] PES packet size mismatch
  
  [mpeg2video @ 0x16d72c0] invalid mb type in I Frame at 0 16
  
  [mpeg2video @ 0x16d72c0] invalid mb type in I Frame at 0 17
  
  [mpeg2video @ 0x16d72c0] invalid mb type in I Frame at 0 18
  
  [mpeg2video @ 0x16d72c0] invalid mb type in I Frame at 0 19
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 0 20
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 0 21
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 0 22
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 0 23
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 17 11
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 0 24
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 0 25
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 0 26
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 0 27
  
  [mpeg2video @ 0x16d72c0] invalid mb type in I Frame at 0 31
  
  [mpeg2video @ 0x16d72c0] invalid mb type in I Frame at 0 32
  
  [mpeg2video @ 0x16d72c0] invalid mb type in I Frame at 0 33
  
  [mpeg2video @ 0x16d72c0] invalid mb type in I Frame at 0 34
  
  [mpeg2video @ 0x16d72c0] invalid mb type in I Frame at 0 35
  
  [mpeg2video @ 0x16d72c0] Warning MVs not available
  
  [mpeg2video @ 0x16d72c0] concealing 1125 DC, 1125 AC, 1125 MV errors in I frame
  
  RTP: missed 11 packets
  
  RTP: missed 37 packets
  
  [ac3 @ 0x1676bc0] exponent out-of-range
  
  [ac3 @ 0x1676bc0] error decoding the audio block
  
  [ac3 @ 0x1676bc0] frame sync error
  
  Error while decoding stream #0:0: Invalid data found when processing input
  
  [ac3 @ 0x1676bc0] exponent out-of-range
  
  [ac3 @ 0x1676bc0] error decoding the audio block
  
  RTP: missed 21 packets
  
  RTP: missed 32 packets
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 1 4
  
  [mpeg2video @ 0x16d72c0] Warning MVs not available
  
  [mpeg2video @ 0x16d72c0] concealing 1080 DC, 1080 AC, 1080 MV errors in B frame
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 21 27
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 2 26
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 0 27
  
  [mpeg2video @ 0x16d72c0] invalid cbp -1 at 2 1
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 5 2
  
  [mpeg2video @ 0x16d72c0] skip with previntra
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 2 4
  
  [mpeg2video @ 0x16d72c0] slice mismatch
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 1 6
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 3 7
  
  [mpeg2video @ 0x16d72c0] slice mismatch
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 37 9
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 1 10
  
  [mpeg2video @ 0x16d72c0] mb incr damaged
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 1 31
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 5 32
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 1 33
  
  [mpeg2video @ 0x16d72c0] mb incr damaged
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 26 35
  
  [mpeg2video @ 0x16d72c0] Warning MVs not available
  
  [mpeg2video @ 0x16d72c0] concealing 945 DC, 945 AC, 945 MV errors in B frame
  
  [rtsp @ 0x1627c20] PES packet size mismatchze=     294kB time=00:00:05.27 bitrate= 457.1kbits/s
  
  [ac3 @ 0x1676bc0] frame sync error
  
  Error while decoding stream #0:0: Invalid data found when processing input
  
  [ac3 @ 0x1676bc0] exponent out-of-range
  
  [ac3 @ 0x1676bc0] error decoding the audio block
  
  [ac3 @ 0x1676bc0] frame sync error
  
  Error while decoding stream #0:0: Invalid data found when processing input
  
  RTP: missed 38 packets25.0 q=26.0 q=22.0 size=     320kB time=00:00:11.18 bitrate= 234.3kbits/s
  
  RTP: missed 18 packets
  
  RTP: missed 9 packets
  
  RTP: missed 21 packets
  
  RTP: missed 9 packets
  
  [rtsp @ 0x1627c20] PES packet size mismatch
  
  [ac3 @ 0x1676bc0] exponent out-of-range
  
  [ac3 @ 0x1676bc0] error decoding the audio block
  
  [ac3 @ 0x1676bc0] frame sync error
  
  Error while decoding stream #0:0: Invalid data found when processing input
  
  [ac3 @ 0x1676bc0] bandwidth code = 63 > 60
  
  [ac3 @ 0x1676bc0] error decoding the audio block
  
  RTP: missed 13 packets
  
  [mpeg2video @ 0x16d72c0] mb incr damaged
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 3 6
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 1 16
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 0 17
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 5 21
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 3 27
  
  [mpeg2video @ 0x16d72c0] invalid cbp -1 at 7 32
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 8 32
  
  [mpeg2video @ 0x16d72c0] slice mismatch
  
      Last message repeated 2 times
  
  [mpeg2video @ 0x16d72c0] Warning MVs not available
  
  [mpeg2video @ 0x16d72c0] concealing 810 DC, 810 AC, 810 MV errors in P frame
  
  RTP: missed 44 packets
  
  [rtsp @ 0x1627c20] PES packet size mismatch
  
  [ac3 @ 0x1676bc0] frame sync error
  
  Error while decoding stream #0:0: Invalid data found when processing input
  
  [ac3 @ 0x1676bc0] exponent out-of-range0 size=     338kB time=00:00:11.43 bitrate= 242.2kbits/s
  
  [ac3 @ 0x1676bc0] error decoding the audio block
  
  RTP: missed 35 packets
  
      Last message repeated 1 times
  
  RTP: missed 31 packets
  
  [ac3 @ 0x1676bc0] frame sync error
  
  Error while decoding stream #0:0: Invalid data found when processing input
  
  [ac3 @ 0x1676bc0] exponent out-of-range
  
  [ac3 @ 0x1676bc0] error decoding the audio block
  
  [ac3 @ 0x1676bc0] frame sync error
  
  Error while decoding stream #0:0: Invalid data found when processing input
  
  RTP: missed 48 packets
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 5 23
  
  [mpeg2video @ 0x16d72c0] mb incr damaged
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 17 24
  
  [mpeg2video @ 0x16d72c0] slice mismatch
  
      Last message repeated 1 times
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 5 27
  
  [mpeg2video @ 0x16d72c0] skip with previntra
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 15 29
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 8 31
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 13 32
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 22 33
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 20 34
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 17 35
  
  [mpeg2video @ 0x16d72c0] Warning MVs not available
  
  [mpeg2video @ 0x16d72c0] concealing 543 DC, 543 AC, 543 MV errors in B frame
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 16 1
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 11 13
  
  [mpeg2video @ 0x16d72c0] invalid mb type in P Frame at 4 7
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 2 8
  
  [mpeg2video @ 0x16d72c0] invalid cbp 0 at 0 19
  
  [mpeg2video @ 0x16d72c0] invalid cbp 0 at 0 20
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 9 21
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 2 22
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 10 23
  
  [mpeg2video @ 0x16d72c0] slice mismatch
  
  [mpeg2video @ 0x16d72c0] invalid mb type in P Frame at 1 25
  
  [mpeg2video @ 0x16d72c0] invalid cbp 0 at 38 26
  
  [mpeg2video @ 0x16d72c0] invalid mb type in P Frame at 3 27
  
  [mpeg2video @ 0x16d72c0] invalid mb type in P Frame at 22 28
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 16 29
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 5 30
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 14 31
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 2 32
  
  [mpeg2video @ 0x16d72c0] invalid mb type in P Frame at 19 9
  
  [mpeg2video @ 0x16d72c0] invalid mb type in P Frame at 11 10
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 13 11
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 8 12
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 33 13
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 8 14
  
  [mpeg2video @ 0x16d72c0] invalid cbp -1 at 6 15
  
  [mpeg2video @ 0x16d72c0] invalid cbp -1 at 15 19
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 9 18
  
  [mpeg2video @ 0x16d72c0] mb incr damaged
  
  [mpeg2video @ 0x16d72c0] invalid cbp -1 at 15 21
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 13 21
  
  [mpeg2video @ 0x16d72c0] invalid cbp 0 at 16 22
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 5 23
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 4 24
  
  [mpeg2video @ 0x16d72c0] mb incr damaged
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 7 26
  
  [mpeg2video @ 0x16d72c0] slice mismatch
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 9 13
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 44 14
  
  [mpeg2video @ 0x16d72c0] invalid cbp 0 at 2 15
  
  [mpeg2video @ 0x16d72c0] mb incr damaged
  
      Last message repeated 1 times
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 34 18
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 15 19
  
  [mpeg2video @ 0x16d72c0] mb incr damaged
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 8 21
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 14 22
  
  [mpeg2video @ 0x16d72c0] invalid cbp -1 at 9 23
  
  [mpeg2video @ 0x16d72c0] invalid cbp 0 at 4 24
  
  [mpeg2video @ 0x16d72c0] mb incr damaged
  
  [mpeg2video @ 0x16d72c0] slice mismatch
  
      Last message repeated 1 times
  
  [mpeg2video @ 0x16d72c0] mb incr damaged
  
  [mpeg2video @ 0x16d72c0] ac-tex damaged at 25 29
  
  [mpeg2video @ 0x16d72c0] invalid cbp 0 at 14 30
  
  [mpeg2video @ 0x16d72c0] mb incr damaged
  
      Last message repeated 1 times
  
  [mpeg2video @ 0x16d72c0] 00 motion_type at 35 33
  
  [mpeg2video @ 0x16d72c0] slice mismatch
  
  [mpeg2video @ 0x16d72c0] Warning MVs not available
  
  [mpeg2video @ 0x16d72c0] concealing 1350 DC, 1350 AC, 1350 MV errors in P frame
  
  [flv @ 0x16d7c40] Failed to update header with correct duration.:00:12.12 bitrate= 241.4kbits/s
  
  [flv @ 0x16d7c40] Failed to update header with correct filesize.
  
  [flv @ 0x16df5a0] Failed to update header with correct duration.
  
  [flv @ 0x16df5a0] Failed to update header with correct filesize.
  
  [flv @ 0x16cbe00] Failed to update header with correct duration.
  
  [flv @ 0x16cbe00] Failed to update header with correct filesize.
  
  frame=  136 fps= 12 q=-1.0 Lq=-1.0 q=-1.0 size=     633kB time=00:00:13.24 bitrate= 391.8kbits/s
  
  video:7049kB audio:272kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
  
  [libx264 @ 0x182b140] frame I:4     Avg QP:19.84  size: 33269
  
  [libx264 @ 0x182b140] frame P:132   Avg QP:21.93  size:  3136
  
  [libx264 @ 0x182b140] mb I  I16..4:  6.9%  0.0% 93.1%
  
  [libx264 @ 0x182b140] mb P  I16..4:  0.1%  0.0%  0.7%  P16..4: 32.0% 11.6%  4.4%  0.0%  0.0%    skip:51.1%
  
  [libx264 @ 0x182b140] coded y,uvDC,uvAC intra: 91.1% 88.6% 67.5% inter: 14.8% 20.2% 1.5%
  
  [libx264 @ 0x182b140] i16 v,h,dc,p: 35% 15%  3% 47%
  
  [libx264 @ 0x182b140] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 31% 19%  9%  6%  7%  8%  7%  7%  7%
  
  [libx264 @ 0x182b140] i8c dc,h,v,p: 45% 20% 28%  7%
  
  [libx264 @ 0x182b140] ref P L0: 80.5% 11.2%  8.4%
  
  [libx264 @ 0x182b140] kb/s:369.61
  
  [libx264 @ 0x16e03c0] frame I:4     Avg QP:19.81  size: 77367
  
  [libx264 @ 0x16e03c0] frame P:132   Avg QP:21.64  size:  9825
  
  [libx264 @ 0x16e03c0] mb I  I16..4: 16.2%  0.0% 83.8%
  
  [libx264 @ 0x16e03c0] mb P  I16..4:  0.6%  0.0%  1.2%  P16..4: 34.1%  9.5%  2.9%  0.0%  0.0%    skip:51.8%
  
  [libx264 @ 0x16e03c0] coded y,uvDC,uvAC intra: 76.8% 77.3% 41.8% inter: 11.9% 20.4% 0.7%
  
  [libx264 @ 0x16e03c0] i16 v,h,dc,p: 38% 18%  7% 37%
  
  [libx264 @ 0x16e03c0] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 30% 22% 10%  5%  7%  7%  7%  6%  6%
  
  [libx264 @ 0x16e03c0] i8c dc,h,v,p: 47% 21% 26%  6%
  
  [libx264 @ 0x16e03c0] ref P L0: 80.8% 12.1%  7.1%
  
  [libx264 @ 0x16e03c0] kb/s:1085.42
  
  [libx264 @ 0x16cc880] frame I:4     Avg QP:15.79  size:181630
  
  [libx264 @ 0x16cc880] frame P:132   Avg QP:18.21  size: 32848
  
  [libx264 @ 0x16cc880] mb I  I16..4: 13.7%  0.0% 86.3%
  
  [libx264 @ 0x16cc880] mb P  I16..4:  1.3%  0.0%  2.7%  P16..4: 36.0% 14.2%  4.4%  0.0%  0.0%    skip:41.4%
  
  [libx264 @ 0x16cc880] coded y,uvDC,uvAC intra: 72.4% 70.6% 41.8% inter: 17.3% 24.9% 1.5%
  
  [libx264 @ 0x16cc880] i16 v,h,dc,p: 33% 21%  6% 39%
  
  [libx264 @ 0x16cc880] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 30% 23%  9%  5%  8%  7%  7%  6%  5%
  
  [libx264 @ 0x16cc880] i8c dc,h,v,p: 44% 21% 27%  8%
  
  [libx264 @ 0x16cc880] ref P L0: 80.3% 12.7%  7.0%
  
  [libx264 @ 0x16cc880] kb/s:3420.59