Recherche avancée

Sur d’autres sites (8396)

• ffmpeg - Audio Issues with TS File

  5 décembre 2020, par MeaningOfLife

  I am new to the world of ffmpeg, so I apologize in advance if this is a stupid question or request.

  


  I'm in the process of trying to convert a .ts file to a h264/mp4. I was able to successfully convert the video, however whenever I go to play the output file, the audio is weird. Most of the audio is only coming through the left channel. I noticed that the audio has multiple channels - 6 to be exact. And there are two audio streams as well. I'm assuming that this has something to do with it, but I am not sure what exactly to put in the command line to fix it.

  


  I was hoping there would be a way to copy the video stream from the mp4 I had already made with ffmpeg, and then replace the audio from that mp4 with the audio from the source ts file - preferably mixed down into regular stereo audio. It is quite a big file, so I would like to not have to convert the video stream again if I don't have to.

  


  Here is the media information from the source video.

  


  General
ID : 1 (0x1)
Complete name : D:\88th Annual Christmas in Rockefeller Center.ts
Format : MPEG-TS
File size : 9.80 GiB
Duration : 2 h 7 min
Overall bit rate mode : Variable
Overall bit rate : 11.0 Mb/s
Law rating : None

Video
ID : 101 (0x65)
Menu ID : 1 (0x1)
Format : MPEG Video
Format version : Version 2
Format profile : Main@High
Format settings : BVOP
Format settings, BVOP : Yes
Format settings, Matrix : Default
Format settings, GOP : Variable
Format settings, picture structure : Frame
Codec ID : 2
Duration : 2 h 7 min
Bit rate mode : Variable
Bit rate : 9 851 kb/s
Maximum bit rate : 80.0 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Active Format Description : Full frame 16:9 image
Frame rate : 29.970 (30000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan order : Top Field First
Compression mode : Lossy
Bits/(Pixel*Frame) : 0.159
Time code of first frame : 00:00:00;00
Time code source : Group of pictures header
Stream size : 8.80 GiB (90%)

Audio #1
ID : 102 (0x66)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : 129
Duration : 2 h 7 min
Bit rate mode : Constant
Bit rate : 384 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Delay relative to video : 32 ms
Stream size : 351 MiB (3%)
Language : English
Service kind : Complete Main

Audio #2
ID : 7543 (0x1D77)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : 129
Duration : 2 h 7 min
Bit rate mode : Constant
Bit rate : 192 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Delay relative to video : 11 ms
Stream size : 176 MiB (2%)
Language : Spanish
Service kind : Complete Main

Text #1
ID : 101 (0x65)-CC1
Menu ID : 1 (0x1)
Format : EIA-608
Muxing mode : A/53 / DTVCC Transport
Muxing mode, more info : Muxed in Video #1
Duration : 2 h 7 min
Bit rate mode : Constant
Stream size : 0.00 Byte (0%)
CaptionServiceName : CC1

Text #2
ID : 101 (0x65)-1
Menu ID : 1 (0x1)
Format : EIA-708
Muxing mode : A/53 / DTVCC Transport
Muxing mode, more info : Muxed in Video #1
Duration : 2 h 7 min
Bit rate mode : Constant
Stream size : 0.00 Byte (0%)


  


• Matomo Celebrates 15 Years of Building an Open-Source & Transparent Web Analytics Solution

  30 juin 2022, par Matthieu Aubry — About, Community
  &lt;script type=&quot;text/javascript&quot;&gt;<br />
       if ('function' === typeof window.playMatomoVideo){<br />
       window.playMatomoVideo(&quot;brand&quot;, &quot;#brand&quot;)<br />
       } else {<br />
       document.addEventListener(&quot;DOMContentLoaded&quot;, function() { window.playMatomoVideo(&quot;brand&quot;, &quot;#brand&quot;); });<br />
       }<br />
  &lt;/script&gt;

  Fifteen years ago, I realised that people (myself included) were increasingly integrating the internet into their everyday lives, and it was clear that it would only expand in the future. It was an exciting new world, but the amount of personal data shared online, level of tracking and lack of security was a growing concern. Google Analytics was just launched then and was already gaining huge traction – so data from millions of websites started flowing into Google’s database, creating what was then the biggest centralised database about people worldwide and their actions online.

  So as a young engineering student, I decided we needed to build an open source and transparent solution that could help make the internet more secure and private while still providing organisations with powerful insights. I aimed to create a win-win solution for businesses and their digital consumers.

  And in 2007, I started developing Matomo with the help from Scott Switzer and Jennifer Langdon (who offered me an internship and support).   

  All thanks to the Matomo Community

  We have reached significant milestones and made major changes over the last 15 years, but we wouldn’t be where we are today without the Matomo Community.

  So I would like to celebrate and thank the hundreds of volunteer developers who have donated their time to develop Matomo, the thousands of contributors who provided feedback to improve Matomo, the countless supportive forum members, our passionate team of 40 at Matomo, the numerous translators who have translated Matomo and the 1.5 million websites that choose Matomo as their analytics platform.

  

  Matomo has been a community effort built on the shoulders of many, and we will continue to work for you. 

  So let’s look at some milestones we have achieved over the last 15 years.

  Looking back on milestones in our timeline

  2007

  • Birth of Matomo
  • First alpha version released

  2008

  • Release first public 0.1.0 version

  2009

  • 50,000 websites use Matomo

  2010

  • Matomo first stable 1.0.0 released
  • Mobile app launched

  2011

  • Released Ecommerce Analytics, Custom Variables, First Party Cookies

  • Released Privacy control features (first of many privacy features to come !)

  2012

  • Released Log Analytics feature
  • 1 Million Downloads !
  • 300,000 websites worldwide use Matomo

  2013

  • Matomo is now available in 50 languages !
  • Matomo brand redesign

  2016

  • Released Roll-Up Reporting Premium Feature, Users Flow Premium Feature, White Label Premium Feature, A/B Testing Premium Feature, Media Analytics Premium Feature, Funnels Premium Feature and Activity Log Premium Feature 
  • On-Premise Premium Plugins now available on the Marketplace

  2017

  • Launched Matomo Cloud service 
  • Released Multi Channel Conversion Attribution Premium Feature, Custom Reports Premium Feature, Login Saml Premium Feature, WooCommerceAnalytics Premium Feature and Heatmap & Session Recording Premium Feature 

  2018

  • Piwik renamed to Matomo
  • New Matomo logo and Matomo.org website re-launch
  • Launch of Matomo Tag Manager
  • 10,000 stars on Github
  • GDPR comes into effect, and Matomo released new product features and published several new guides
  • 17 Matomo features videos published online
  • Reached thousands of paying customers, making the project sustainable and financially independent

  2019

  • 700,000 websites worldwide use Matomo
  • Google Analytics importer released

  2020

  • Matomo For WordPress goes live on the WP Marketplace !
  • Released Paid Advertising Performance Premium feature
  • 100 million On-Premise Plugins downloads on the marketplace (since the beginning)

  2021

  • 1,000,000 websites worldwide use Matomo
  • including 30,000 active Matomo for WordPress installations
  • Released SEO Web Vitals, Advertising Conversion Export and Tracking Spam Prevention feature

  2022

  • Released WP Statistics to Matomo importer

  Our efforts continue

  While we’ve seen incredible growth over the years, our work doesn’t stop there. In fact, we’re only just getting started.

  Today over 55% of the internet continues to use privacy-threatening web analytics solutions, while 1.5% uses Matomo. So there are still great strides to be made to create a more private internet, and joining the Matomo Community is one way to support this movement.

  There are many ways to get involved too, such as :

  • Submitting feature requests
  • Developing for Matomo 
  • Leaving Matomo a review on sites like Capterra, TrustRadius, G2 Crowd, alternativeTo, SaaSworthy, Siftery, Open Hub
  • Translating Matomo
  • Joining our Security Bug Bounty Programme
  • Sharing Matomo with your peers
  • Talking about Matomo on social platforms

  So what comes next for Matomo ?

  The future of Matomo is approachable, powerful and flexible. We’re strengthening the customers’ voice, expanding our resources internally (we’re continuously hiring !) and conducting rigorous customer research to craft a tool that balances usability and functionality.

  I look forward to the next 15 years and seeing what the future holds for Matomo and our community.

• Troll spirit

  15 juin 2013, par Mans — Law and liberty

  Last week’s announcements from the White House of steps being taken to begin fighting back against patent trolls, along with legislation passed in Vermont for the same purpose, are worthy of praise. Whether they prove effective or not, they are a sign of the problem finally having been recognised by the highest authorities. That said, only one aspect of the issue is addressed, that of non-practising entities or trolls. Little effort is being made to stymie troll-like behaviour from otherwise legitimate actors. While a stake is driven through the heart of the troll, its spirit remains free to roam the corporate world, and like a demon of darkness it possesses companies, compelling them to engage in the very practices we seek to eradicate.

  The demon

  The most damaging, when wielded by a troll, are those patents with vague or overly broad claims. These can easily be asserted against large numbers of alleged infringers, many of which likely choose to settle out of court rather than risk an expensive litigation process with uncertain outcome. Such negotiations are frequently subject to non-disclosure agreements prohibiting publication of details in any deals, or even the existence thereof. As a result, an accused has no way of assessing a fair price for a licence (assuming the patent is in fact valid), and the patent holder can thus extract from each would-be infringer precisely as much as they are willing or able to pay to avoid a lawsuit.

  At the root of this problem is the ease with which applications for the patents in question are granted. Given the volume of patent applications, it is hardly reasonable to demand a hugely more extensive examination process than currently takes place (although some improvements here are no doubt possible) ; after all, a speedy decision is in the best interest of all parties. The solution must evidently be found elsewhere.

  The exorcism

  An obvious cure to the problem is the abolishment of the patent system. As this is clearly not feasible today, more practical, albeit less effective, remedies must be sought. A few ideas follow.

  Make patent validity all or nothing

  Change the rules such that any claim being found invalid cancels the patent its entirety. With the full patent at stake in this manner, companies would be discouraged from gambling on frivolous claims and encouraged to conduct a more thorough background investigation before filing.

  Maintain a registry of licences

  Require that all patent licence agreements be filed in an open, easily searchable registry. This would hopefully increase fairness in licensing deals.

  Mandate reimbursement of licence fees for invalidated patents

  If a patent is challenged and found invalid, require that the owner reimburse any licence fees previously collected for the patent in question. Apart from being morally right, this could act as a deterrent to over-charging. The amount requested for a licence would likely be balanced against the risk of being made to pay it all back later, resulting in lower licence fees for low-confidence patents.

  These suggestions, alone or together, will not completely eradicate the problems of patent abuse. They are but small steps towards a more thorough overhaul of a system increasingly ill-suited to the nature and pace of modern technological development.