Recherche avancée

Sur d’autres sites (13876)

• Cannot play local RTP stream

  24 janvier 2020, par gdogg371

  I have been struggling along with this issue now for a while, but am making good progress. I now have a 4k transport stream running using the below command line arguments for VLC :

  vlc --ffmpeg-hw --avcodec-hw=any dshow:// :dshow-vdev="Video (00 Pro Capture HDMI 4K+)" :dshow-adev="Audio (2- 00 Pro Capture HDMI 4K+)" :dshow-threads=8 :dshow-aspect-ratio=16\:9 :dshow-size="3840x2160" :dshow-pixel_format=yuv444p16le :dshow-tune=film :dshow-preset=lossless :dshow-profile=main10 show-vcodec=hevc_nvenc :dshow-fps=50 :dshow-crf=0 :dshow-acodec=mp4a :dshow-stereo-mode=5 :dshow-force-surround-sound=0 :dshow-ab=128 :dshow-samplerate=44100 :no-dshow-config :live-caching=3000 --sout "#transcode{venc=ffmpeg,vcodec=mpgv,threads=8,aspect=16:9,width=3840,height=2160,fps=50,acodec=a52,ab=1500,channels=6,samplerate=48000,soverlay}:rtp{dst=239.255.0.1,port=5004,mux=ts}"

  I can access the rtp stream on the same PC as I am running the stream from with the below :

  vlc -vvv rtp://@239.255.0.1:5004

  However, if I try the same commands on a different computer, connected via Ethernet to the same network, the client VLC session just hangs. I have included the log below with the verbosity set to debug. Can anyone spot anything in here suggesting why the stream won’t play ?

  -- logger module started --
  
  main debug: VLC media player - 3.0.8 Vetinari
  
  main debug: Copyright © 1996-2019 the VideoLAN team
  
  main debug: revision 3.0.8-0-gf350b6b5a7
  
  main debug: configured with ../extras/package/win32/../../../configure  '--enable-update-check' '--enable-lua' '--enable-faad' '--enable-flac' '--enable-theora' '--enable-avcodec' '--enable-merge-ffmpeg' '--enable-dca' '--enable-mpc' '--enable-libass' '--enable-schroedinger' '--enable-realrtsp' '--enable-live555' '--enable-dvdread' '--enable-shout' '--enable-goom' '--enable-caca' '--enable-qt' '--enable-skins2' '--enable-sse' '--enable-mmx' '--enable-libcddb' '--enable-zvbi' '--disable-telx' '--enable-nls' '--host=x86_64-w64-mingw32' '--with-breakpad=https://win.crashes.videolan.org' 'host_alias=x86_64-w64-mingw32' 'PKG_CONFIG_LIBDIR=/home/jenkins/workspace/vlc-release/windows/vlc-release-win32-x64/contrib/x86_64-w64-mingw32/lib/pkgconfig'
  
  main debug: using multimedia timers as clock source
  
  main debug:  min period: 1 ms, max period: 1000000 ms
  
  main debug: searching plug-in modules
  
  main debug: loading plugins cache file D:\VLC\plugins\plugins.dat
  
  main debug: recursively browsing `D:\VLC\plugins'
  
  main error: stale plugins cache: modified D:\VLC\plugins\access\libaccess_concat_plugin.dll
  
  main error: stale plugins cache: modified D:\VLC\plugins\access\libaccess_imem_plugin.dll
  
  ....
  
  ....
  
  ....
  
  main error: stale plugins cache: modified D:\VLC\plugins\visualization\libgoom_plugin.dll
  
  main error: stale plugins cache: modified D:\VLC\plugins\visualization\libprojectm_plugin.dll
  
  main error: stale plugins cache: modified D:\VLC\plugins\visualization\libvisual_plugin.dll
  
  main debug: plug-ins loaded: 494 modules
  
  main debug: opening config file (C:\Users\cg371\AppData\Roaming\vlc\vlcrc)
  
  main debug: looking for logger module matching "any": 2 candidates
  
  file debug: opening logfile `D:\VLC\Log.txt'
  
  main debug: using logger module "file"
  
  main debug: translation test: code is "en_GB"
  
  main debug: looking for keystore module matching "memory": 3 candidates
  
  main debug: using keystore module "memory"
  
  main debug: CPU has capabilities MMX MMXEXT SSE SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 FPU 
  
  main debug: Creating an input for 'Media Library'
  
  main debug: Input is a meta file: disabling unneeded options
  
  main debug: using timeshift granularity of 50 MiB
  
  main debug: using timeshift path: C:\Users\cg371\AppData\Local\Temp
  
  main debug: `file/directory:///C:/Users/cg371/AppData/Roaming/vlc/ml.xspf' gives access `file' demux `directory' path `/C:/Users/cg371/AppData/Roaming/vlc/ml.xspf'
  
  main debug: creating demux: access='file' demux='directory' location='/C:/Users/cg371/AppData/Roaming/vlc/ml.xspf' file='C:\Users\cg371\AppData\Roaming\vlc\ml.xspf'
  
  main debug: looking for access_demux module matching "file": 15 candidates
  
  main debug: no access_demux modules matched
  
  main debug: creating access: file:///C:/Users/cg371/AppData/Roaming/vlc/ml.xspf
  
  main debug:  (path: C:\Users\cg371\AppData\Roaming\vlc\ml.xspf)
  
  main debug: looking for access module matching "file": 26 candidates
  
  main debug: using access module "filesystem"
  
  main debug: looking for stream_filter module matching "prefetch,cache_read": 24 candidates
  
  cache_read debug: Using stream method for AStream*
  
  cache_read debug: starting pre-buffering
  
  cache_read debug: received first data after 1 ms
  
  cache_read debug: pre-buffering done 304 bytes in 0s - 296 KiB/s
  
  main debug: using stream_filter module "cache_read"
  
  main debug: looking for stream_filter module matching "any": 24 candidates
  
  playlist debug: using XSPF playlist reader
  
  main debug: using stream_filter module "playlist"
  
  main debug: stream filter added to 00000266f6927700
  
  main debug: looking for stream_filter module matching "any": 24 candidates
  
  main debug: no stream_filter modules matched
  
  main debug: looking for stream_directory module matching "any": 1 candidates
  
  main debug: no stream_directory modules matched
  
  main debug: attachment of directory-extractor failed for file:///C:/Users/cg371/AppData/Roaming/vlc/ml.xspf
  
  main debug: looking for stream_filter module matching "record": 24 candidates
  
  main debug: using stream_filter module "record"
  
  main debug: creating demux: access='file' demux='directory' location='/C:/Users/cg371/AppData/Roaming/vlc/ml.xspf' file='C:\Users\cg371\AppData\Roaming\vlc\ml.xspf'
  
  main debug: looking for demux module matching "directory": 55 candidates
  
  main debug: using demux module "directory"
  
  main debug: looking for meta reader module matching "any": 2 candidates
  
  lua debug: Trying Lua scripts in C:\Users\cg371\AppData\Roaming\vlc\lua\meta\reader
  
  lua debug: Trying Lua scripts in D:\VLC\lua\meta\reader
  
  lua debug: Trying Lua playlist script D:\VLC\lua\meta\reader\filename.luac
  
  main debug: no meta reader modules matched
  
  main debug: `file/directory:///C:/Users/cg371/AppData/Roaming/vlc/ml.xspf' successfully opened
  
  main debug: looking for xml reader module matching "any": 1 candidates
  
  main debug: using xml reader module "xml"
  
  main debug: EOF reached
  
  main debug: removing module "directory"
  
  main debug: removing module "record"
  
  main debug: removing module "playlist"
  
  main debug: removing module "cache_read"
  
  main debug: removing module "filesystem"
  
  main debug: creating audio output
  
  main debug: looking for audio output module matching "any": 6 candidates
  
  mmdevice debug: using default device
  
  mmdevice debug: display name changed: VLC media player (LibVLC 3.0.8)
  
  mmdevice debug: version 2 session control unavailable
  
  mmdevice debug: volume from -65.250000 dB to +0.000000 dB with 0.031250 dB increments
  
  main debug: using audio output module "mmdevice"
  
  main debug: keeping audio output
  
  main debug: looking for interface module matching "hotkeys,none": 16 candidates
  
  main debug: using interface module "hotkeys"
  
  main debug: looking for interface module matching "globalhotkeys,none": 16 candidates
  
  main debug: using interface module "win32"
  
  main: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
  
  main debug: looking for interface module matching "any": 16 candidates
  
  main debug: looking for extension module matching "any": 1 candidates
  
  lua debug: Opening Lua Extension module
  
  lua debug: Trying Lua scripts in C:\Users\cg371\AppData\Roaming\vlc\lua\extensions
  
  lua debug: Trying Lua scripts in D:\VLC\lua\extensions
  
  lua debug: Trying Lua playlist script D:\VLC\lua\extensions\VLSub.luac
  
  lua debug: Scanning Lua script D:\VLC\lua\extensions\VLSub.luac
  
  lua debug: Script D:\VLC\lua\extensions\VLSub.luac has the following capability flags: 0x5
  
  main debug: using extension module "lua"
  
  main debug: using interface module "qt"
  
  main debug: processing request item: null, node: Playlist, skip: 0
  
  main debug: rebuilding array of current - root Playlist
  
  main debug: rebuild done - 1 items, index -1
  
  main debug: starting playback of new item
  
  main debug: resyncing on rtp://239.255.0.1:5004
  
  main debug: rtp://239.255.0.1:5004 is at 0
  
  main debug: creating new input thread
  
  main debug: Creating an input for 'rtp://239.255.0.1:5004'
  
  main debug: requesting art for new input thread
  
  main debug: using timeshift granularity of 50 MiB
  
  main debug: using timeshift path: C:\Users\cg371\AppData\Local\Temp
  
  main debug: `rtp://@239.255.0.1:5004' gives access `rtp' demux `any' path `@239.255.0.1:5004'
  
  main debug: creating demux: access='rtp' demux='any' location='@239.255.0.1:5004' file='\\@239.255.0.1:5004'
  
  main debug: looking for access_demux module matching "rtp": 15 candidates
  
  main debug: net: opening 239.255.0.1 datagram port 5004
  
  qt debug: IM: Setting an input
  
  main debug: looking for meta fetcher module matching "any": 1 candidates
  
  lua debug: Trying Lua scripts in C:\Users\cg371\AppData\Roaming\vlc\lua\meta\fetcher
  
  lua debug: Trying Lua scripts in D:\VLC\lua\meta\fetcher
  
  main debug: no meta fetcher modules matched
  
  main debug: looking for art finder module matching "any": 2 candidates
  
  lua debug: Trying Lua scripts in C:\Users\cg371\AppData\Roaming\vlc\lua\meta\art
  
  lua debug: Trying Lua scripts in D:\VLC\lua\meta\art
  
  lua debug: Trying Lua playlist script D:\VLC\lua\meta\art\00_musicbrainz.luac
  
  lua debug: skipping script (unmatched scope) D:\VLC\lua\meta\art\00_musicbrainz.luac
  
  lua debug: Trying Lua playlist script D:\VLC\lua\meta\art\01_googleimage.luac
  
  lua debug: skipping script (unmatched scope) D:\VLC\lua\meta\art\01_googleimage.luac
  
  lua debug: Trying Lua playlist script D:\VLC\lua\meta\art\02_frenchtv.luac
  
  lua debug: skipping script (unmatched scope) D:\VLC\lua\meta\art\02_frenchtv.luac
  
  lua debug: Trying Lua playlist script D:\VLC\lua\meta\art\03_lastfm.luac
  
  main debug: using access_demux module "rtp"
  
  main debug: looking for meta reader module matching "any": 2 candidates
  
  lua debug: Trying Lua scripts in C:\Users\cg371\AppData\Roaming\vlc\lua\meta\reader
  
  lua debug: Trying Lua scripts in D:\VLC\lua\meta\reader
  
  lua debug: Trying Lua playlist script D:\VLC\lua\meta\reader\filename.luac
  
  lua debug: skipping script (unmatched scope) D:\VLC\lua\meta\art\03_lastfm.luac
  
  main debug: no art finder modules matched
  
  main debug: no meta reader modules matched
  
  main debug: `rtp://@239.255.0.1:5004' successfully opened
  
  main debug: looking for meta fetcher module matching "any": 1 candidates
  
  lua debug: Trying Lua scripts in C:\Users\cg371\AppData\Roaming\vlc\lua\meta\fetcher
  
  lua debug: Trying Lua scripts in D:\VLC\lua\meta\fetcher
  
  main debug: no meta fetcher modules matched
  
  main debug: looking for art finder module matching "any": 2 candidates
  
  lua debug: Trying Lua scripts in C:\Users\cg371\AppData\Roaming\vlc\lua\meta\art
  
  lua debug: Trying Lua scripts in D:\VLC\lua\meta\art
  
  lua debug: Trying Lua playlist script D:\VLC\lua\meta\art\00_musicbrainz.luac
  
  lua debug: Trying Lua playlist script D:\VLC\lua\meta\art\01_googleimage.luac
  
  lua debug: Trying Lua playlist script D:\VLC\lua\meta\art\02_frenchtv.luac
  
  lua debug: Trying Lua playlist script D:\VLC\lua\meta\art\03_lastfm.luac
  
  main debug: no art finder modules matched
  
  main debug: exiting
  
  main debug: exiting
  
  main debug: no exit handler
  
  main debug: removing all interfaces
  
  main debug: removing module "qt"
  
  main debug: deactivating the playlist
  
  main debug: incoming request - stopping current input
  
  main debug: removing module "rtp"
  
  main debug: dead input
  
  main debug: nothing to play
  
  main debug: removing module "mmdevice"
  
  qt debug: requesting exit...
  
  qt debug: waiting for UI thread...
  
  qt debug: IM: Deleting the input
  
  qt debug: QApp exec() finished
  
  qt debug: Video is not needed anymore
  
  qt debug: Killing extension dialog provider
  
  qt debug: ExtensionsDialogProvider is quitting...
  
  main debug: removing module "lua"
  
  main debug: removing module "win32"
  
  main debug: removing module "hotkeys"
  
  main debug: destroying
  
  main debug: saving media library to file C:\Users\cg371\AppData\Roaming\vlc\ml.xspf.tmp14968
  
  main debug: looking for playlist export module matching "export-xspf": 4 candidates
  
  main debug: using playlist export module "export"
  
  main debug: removing module "export"
  
  main debug: deleting item `Media Library'
  
  main debug: deleting item `rtp://239.255.0.1:5004'
  
  main debug: deleting item `Playlist'
  
  main debug: removing module "memory"
  
  -- logger module stopped --

• What Are Website KPIs (10 KPIs and Best Ways to Track Them)

  3 mai 2024, par Erin

  Trying to improve your website’s performance ?

  Have you ever heard the phrase, “What gets measured gets managed ?”

  To improve, you need to start crunching your numbers.

  The question is, what numbers are you supposed to track ?

  If you want to improve your conversions, then you need to track your website KPIs.

  In this guide, we’ll break down the top website KPIs you need to be tracking and how you can track them so you can double down on what’s working with your website (and ditch what’s not).

  Let’s begin.

  What are website KPIs ?

  Before we dive into website KPIs, let’s define “KPI.”

  A KPI is a key performance indicator.

  You can use this measurable metric to track progress toward a specific objective.

  A website KPI is a metric to track progress towards a specific website performance objective.

  

  Website KPIs help your business identify strengths and weaknesses on your website, activities you’re doing well (and those you’re struggling with).

  Web KPIs can give you and your team a target to reach with simple checkpoints to show you whether you’re on the right track toward your goals.

  By tracking website KPIs regularly, you can ensure your organisation performs consistently at a high level.

  Whether you’re looking to improve your traffic, leads or revenue, keeping a close eye on your website KPIs can help you reach your goals.

  10 Website KPIs to track

  If you want to improve your site’s performance, you need to track the right KPIs.

  While there are plenty of web analytics solutions on the market today, below we’ll cover KPIs that are automatically tracked in Matomo (and don’t require any configuration).

  Here are the top 10 website KPIs you need to track to improve site performance and grow your brand :

  1. Pageviews

  Website pageviews are one of the most important KPIs to track.

  What is it exactly ?

  It’s simply the number of times a specific web page has been viewed on your site in a specific time period.

  For example, your homepage might have had 327 pageviews last month, and only 252 this month. 

  This is a drop of 23%. 

  A drop in pageviews could mean your search engine optimisation or traffic campaigns are weakening. Alternatively, if you see pageviews rise, it could mean your marketing initiatives are performing well.

  High or low pageviews could also indicate potential issues on specific pages. For example, your visitors might have trouble finding specific pages if you have poor website structure.

  

  2. Average time on page

  Now that you understand pageviews, let’s talk about average time on page.

  This is simple : it’s the average amount of time your visitors spend on a particular web page on your site.

  This isn’t the average time they spend on your website but on a specific page.

  If you’re finding that you’re getting steady traffic to a specific web page, but the average time on the page is low, it may mean the content on the page needs to be updated or optimised.

  Tracking your average time on page is important, as the longer someone stays on a page, the better the experience.

  This isn’t a hard and fast rule, though. For specific types of content like knowledge base articles, you may want a shorter period of time on page to ensure someone gets their answer quickly.

  3. Bounce rate

  Bounce rate sounds fun, right ?

  Well, it’s not usually a good thing for your website.

  A bounce rate is how many users entered your website but “bounced” away without clicking through to another page.

  Your bounce rate is a key KPI that helps you determine the quality of your content and the user experience on individual pages.

  You could be getting plenty of traffic to your site, but if the majority are bouncing out before heading to new pages, it could mean that your content isn’t engaging enough for your visitors.

  Remember, like average time on page, your bounce rate isn’t a black-and-white KPI.

  A higher bounce rate may mean your site visitors got exactly what they needed and are pleased.

  But, if you have a high bounce rate on a product page or a landing page, that is a sign you need to optimise the page.

  4. Exit rate

  Bounce rate is the percentage of people who left the website after visiting one page.

  Exit rate, on the other hand, is the percentage of website visits that ended on a specific page.

  For example, you may find that a blog post you wrote has a 19% exit rate and received 1,000 visits that month. This means out of the 1,000 people who viewed this page, 190 exited after visiting it.

  On the other hand, you may find that a second blog post has 1,000 pageviews, but a 10% exit rate, with only 100 people leaving the site after visiting this page.

  What could this mean ?

  This means the second page did a better job keeping the person on your website longer. This could be because :

  • It had more engaging content, keeping the visitors’ interest high
  • It had better internal links to other relevant pieces of content
  • It had a better call to action, taking someone to another web page

  If you’re an e-commerce store and notice that your exit rate is higher on your product, cart or checkout pages, you may need to adjust those pages for better conversions.

  

  5. Average page load time

  Want to know another reason you may have a high exit rate or bounce rate on a page ?

  Your page load time.

  The average page load time is the average time it takes (in seconds) from the moment you click through to a page until it has fully rendered within your browser.

  In other words, it’s the time it takes after you click on a page for it to be fully functional.

  Your average load time is a crucial website KPI because it significantly impacts page performance and the user experience.

  How important is your page load time ?

  Nearly 53% of website visitors expect e-commerce pages to load in 3 seconds or less.

  You will likely lose visitors if your pages take too long to load.

  You could have the best content on a web page, but if it takes too long to load, your visitors will bounce, exit, or simply be frustrated.

  6. Conversions

  

  Conversions.

  It’s one of the most popular words in digital marketing circles.

  But what does it mean ?

  A conversion is simply the number of times someone takes a specific action on your website.

  For example, it could be wanting someone to :

  • Read a blog post
  • Click an external link
  • Download a PDF guide
  • Sign up to your email list
  • Comment on your blog post
  • Watch a new video you uploaded
  • Purchase a limited-edition product
  • Sign up for a free trial of your software

  To start tracking conversions, you need to first decide what your business goals are for your website.

  With Matomo, you can set up conversions easily through the Goals feature. Simply set up your website goals, and Matomo will automatically track the conversions towards that objective (as a goal completion).

  Simply choose what conversion you want to track, and you can analyse when conversions occur through the Matomo platform.

  7. Conversion rate

  

  Now that you know what a conversion is, it’s time to talk about conversion rate.

  This key website KPI will help you analyse your performance towards your goals.

  Conversion rate is simply the percentage of visitors who take a desired action, like completing a purchase, signing up for a newsletter, or filling out a form, out of the total number of visitors to your website or landing page.

  Understanding this percentage can help you plan your marketing strategy to improve your website and business performance.

  For instance, let’s say that 2% of your website visitors purchase a product on your digital storefront.

  Knowing this, you could tweak different levers to increase your sales.

  If your average order value is $50 and you get 100,000 visits monthly, you make about $100,000.

  Let’s say you want to increase your revenue.

  One option is to increase your traffic by implementing campaigns to increase different traffic sources, such as social media ads, search ads, organic social traffic, and SEO.

  If you can get your traffic to 120,000 visitors monthly, you can increase your revenue to $120,000 — an additional $20,000 monthly for the extra 20,000 visits.

  Or, if you wanted to increase revenue, you could ignore traffic growth and simply improve your website with conversion rate optimisation (CRO).

  CRO is the practice of making changes to your website or landing page to encourage more visitors to take the desired action.

  If you can get your conversion rate up to 2.5%, the calculation looks like this :

  100,000 visits x $50 average order value x 2.5% = $125,000/month.

  8. Average time spent on forms

  If you want more conversions, you need to analyse forms.

  Why ?

  Form analysis is crucial because it helps you pinpoint where users might be facing obstacles. 

  By identifying these pain points, you can refine the form’s layout and fields to enhance the user experience, leading to higher conversion rates.

  In particular, you should track the average time spent on your forms to understand which ones might be causing frustration or confusion. 

  The average time a visitor spends on a form is calculated by measuring the duration between their first interaction with a form field (such as when they focus on it) and their final interaction.

  Find out how Concrete CMS tripled their leads using Form Analytics.

  9. Play rate

  One often overlooked website KPI you need to be tracking is play rate.

  What is it exactly ?

  The percentage of visitors who click “play” on a video or audio media format on a specific web page.

  For example, if you have a video on your homepage, and 50 people watched it out of the 1,000 people who visited your website today, you have a play rate of 5%.

  Play rate lets you track whenever someone consumes a particular piece of audio or video content on your website, like a video, podcast, or audiobook.

  Not all web analytics solutions offer media analytics. However, Matomo lets you track your media like audio and video without the need for configuration, saving you time and upkeep.

  10. Actions per visit

  Another crucial website KPI is actions per visit.

  This is the average number of interactions a visitor has with your website during a single visit.

  For example, someone may visit your website, resulting in a variety of actions :

  • Downloading content
  • Clicking external links
  • Visiting a number of pages
  • Conducting specific site searches

  Actions per visit is a core KPI that indicates how engaging your website and content are.

  The higher the actions per visit, the more engaged your visitors typically are, which can help them stay longer and eventually convert to paying customers.

  Track your website KPIs with Matomo today

  Running a website is no easy task.

  There are dozens of factors to consider and manage :

  • Copy
  • Design
  • Performance
  • Tech integrations
  • And more

  But, to improve your website and grow your business, you must also dive into your web analytics by tracking key website KPIs.

  Managing these metrics can be challenging, but Matomo simplifies the process by consolidating all your core KPIs into one easy-to-use platform.

  As a privacy-friendly and GDPR-compliant web analytics solution, Matomo tracks 20-40% more data than other solutions. So you gain access to 100% accurate, unsampled insights, enabling confident decision-making.

  Join over 1 million websites that trust Matomo as their web analytics solution. Try it free for 21 days — no credit card required.

  Try Matomo for Free

  21 day free trial. No credit card required.

  
  

  Your email address
  

  Your website address
  

  Your Analytics subdomain will be .matomo.cloud (change)

  Choose your analytics subdomain
  

  .matomo.cloud

  I accept the terms and conditions and data processing agreement (DPA)

  
  Your information will be used to create an account on our cloud service. For more information please consult our privacy policy.
  
  
  

  Start improving your websites now

  

• Revision 37408 : déplacement de chaines de langue Faire refonctionner l’encodage sonore

  18 avril 2010, par kent1@… — Log

  déplacement de chaines de langue
  Faire refonctionner l’encodage sonore