Recherche avancée

Sur d’autres sites (3670)

• Anomalie #3510 (Nouveau) : ajaxReload() arg en tableau Js

  24 juillet 2015, par PIerre LASZCZAK

  Bonjour,

  J’utilise un truc du genre enfin de filtrer des articles par mot_cle en ajax :
  

  $(’.formulaire_tri_par_mots’).on(’click’,’.js-visually-hidden’,function() 
          // Mettre les id_mot dans un array
  
          var id_mots = $(’input:checkbox[name="id_mot[]"]:checked’).map(function() 
  
              return this.value ;
  
          ).get() ;
          ajaxReload(’content’, 
  
              args :"id_mot":id_mots,
  
          ) ;
      ) ;
  

  
  chaque clic renvoie un tableau de valeur et les requêtes ajax générées paraissent correct :
  id_mot[]=52&id_mot[]=61&id_mot[]=74&id_mot[]=76
  les noisettes avec le critère id_mot ? se mettent bien à jour.

  par contre il me semble qu’il y a un bug dans la fonction parametre_url dans ajaxCallback.js qui me génère aussi des paramètres farfelus tel que :
  id_mot[]=52,61,74,76 autant de fois qu’il y a de mot clef...
  je me retrouve donc avec des requêtes très moches du genre :
  *id_mot[]=52,61,74,76&id_mot[]=52,61,74,76&id_mot[]=52,61,74,76*&id_mot[]=52&id_mot[]=61&id_mot[]=74&id_mot[]=76.

  J’ai supprimer les lignes 891 & 897 (mode_bourrin) dans la fonction parametre_url de ajaxCallback afin de tester et ça semble ok :

  // Ajout. Pour une variable, remplacer au même endroit,
              //else na.push(args[n]) ;// Ajout. Pour une variable, remplacer au meme endroit,
              // pour un tableau ce sera fait dans la prochaine boucle
              //else if (r[1].substring(-2) != ’[]’) 
                  //na.push(r[1]+’=’+u) ;
                  //ajouts.push(r[1]) ;
              //
              //else na.push(args[n]) ;
  

  Voilà, merci.

• Packet corrupt (stream = 0, dts = 2490755129) error in ffmpeg which creates HLS and in ffmpeg which uploads HLS to a CDN

  25 mai 2021, par Amit Maharjan

  ffmpeg command which creates the hls stream :
ffmpeg -y -v warning -i udp://225.1.2.3:2000?reuse=1&buffer_size=16777216&localaddr=127.0.0.1&overrun_nonfatal=1 -c:v:0 h264_qsv -global_quality 25 -pix_fmt nv12 -r 59.94 -filter:v:0 fps=fps=59.94,scale=768:432:force_original_aspect_ratio=decrease,pad=768:432:(ow-iw)/2:(oh-ih)/2 -vsync cfr -g 120 -c:a:0 aac -ar 48000 -b:a:0 128k -profile:v:0 high -level:v:0 3.1 -b:v:0 1000k -maxrate:v:0 1000k -bufsize:v:0 1000k -map 0:v -map 0:a -c:v:1 h264 -global_quality 25 -pix_fmt nv12 -r 24 -filter:v:1 fps=fps=24,scale=640:360:force_original_aspect_ratio=decrease,pad=640:360:(ow-iw)/2:(oh-ih)/2 -vsync cfr -g 121 -c:a:1 aac -ar 44100 -b:a:1 128k -profile:v:1 main -level:v:1 3.1 -b:v:1 800k -maxrate:v:1 800k -bufsize:v:1 800k -map 0:v -map 0:a -max_muxing_queue_size 4096 -f hls -hls_list_size 10 -hls_delete_threshold 30 -hls_flags delete_segments -hls_time 4 -master_pl_name master.m3u8 -var_stream_map " v:0,a:0,name:0 v:1,a:1,name:1" -hls_start_number_source epoch C:path_to_hls_data/436379cd-11e6-4ef0-a198-58c69b139803/%v_playlist.m3u8

  


  ffmpeg command to upload the hls stream to cdn :
ffmpeg -y -v warning -re -f hls -http_persistent 0 -i http://localhost:3000/assets/436379cd-11e6-4ef0-a198-58c69b139803/master.m3u8 -b:v:0 1000k -b:a:0 128k -c:v:0 copy -c:a:0 copy -b:v:1 800k -b:a:1 128k -c:v:1 copy -c:a:1 copy -method POST -map 0:v:0 -map 0:a:0 -map 0:v:1 -map 0:a:1 -var_stream_map " v:0,a:0,name:0 v:1,a:1,name:1" -f hls -master_pl_name master.m3u8 -hls_list_size 10 -hls_time 4 -hls_flags second_level_segment_index -master_pl_publish_rate 150 -strftime 1 -hls_segment_filename "cdn_link" "cdn_link"

  


  


  In the logs below _UploaderProcess is the ffmpeg which uploads the hls stream to cdn, _encProcess_dst is the ffmpeg which creates the hls stream

  


  


  Error logs :

  


  6961    19:42:40.241    2021-05-08  [2021-05-08T19:42:40.241 DEBUG video_encoder.js:1] - _UploaderProcess stderr: [mpegts @ 0000026eabff7c40] Packet corrupt (stream = 0, dts = 1805890264).

6960    19:42:36.204    2021-05-08  [2021-05-08T19:42:36.204 DEBUG video_encoder.js:1] - _UploaderProcess stderr: [hls @ 0000026eabfecb40] skipping 3 segments ahead, expired from playlists

6959    19:42:27.520    2021-05-08  [2021-05-08T19:42:27.520 DEBUG video_encoder.js:1] - _encProcess_dst stderr: [h264 @ 0000025030f09540] co located POCs unavailable
6958    19:42:27.516    2021-05-08  [2021-05-08T19:42:27.516 DEBUG video_encoder.js:1] - _encProcess_dst stderr: [h264 @ 0000025030f0a780] co located POCs unavailable
6957    19:42:27.514    2021-05-08  [2021-05-08T19:42:27.514 DEBUG video_encoder.js:1] - _encProcess_dst stderr: [h264 @ 0000025030f0c780] co located POCs unavailable
6956    19:42:27.504    2021-05-08  Error while decoding stream #0:1: Invalid data found when processing input
6955    19:42:27.504    2021-05-08  [aac @ 000002502ff97c40] Number of scalefactor bands in group (57) exceeds limit (49).
6954    19:42:27.504    2021-05-08  [2021-05-08T19:42:27.504 DEBUG video_encoder.js:1] - _encProcess_dst stderr: [aac @ 000002502ff97c40] Reserved bit set.
6953    19:42:27.503    2021-05-08  Error while decoding stream #0:1: Invalid data found when processing input
6952    19:42:27.503    2021-05-08  [2021-05-08T19:42:27.503 DEBUG video_encoder.js:1] - _encProcess_dst stderr: [aac @ 000002502ff97c40] Number of bands (50) exceeds limit (41).
6951    19:42:27.501    2021-05-08  [mpegts @ 000002502ff6cdc0] Packet corrupt (stream = 1, dts = 5313003).
6950    19:42:27.501    2021-05-08  [2021-05-08T19:42:27.501 DEBUG video_encoder.js:1] - _encProcess_dst stderr: [mpegts @ 000002502ff6cdc0] PES packet size mismatch
6949    19:42:27.498    2021-05-08  [2021-05-08T19:42:27.498 DEBUG video_encoder.js:1] - _encProcess_dst stderr: [mpegts @ 000002502ff6cdc0] Packet corrupt (stream = 0, dts = 5327196).
6948    19:42:24.201    2021-05-08  [2021-05-08T19:42:24.201 DEBUG video_encoder.js:1] - _UploaderProcess stderr: [mpegts @ 0000026eabff7c40] Packet corrupt (stream = 0, dts = 1804448823).
6947    19:42:20.193    2021-05-08  [2021-05-08T19:42:20.193 DEBUG video_encoder.js:1] - _UploaderProcess stderr: [hls @ 0000026eabfecb40] skipping 2 segments ahead, expired from playlists
6946    19:42:08.190    2021-05-08  [mpegts @ 0000026eabff7c40] Packet corrupt (stream = 0, dts = 1803007381).
6945    19:42:08.190    2021-05-08  [2021-05-08T19:42:08.190 DEBUG video_encoder.js:1] - _UploaderProcess stderr: Last message repeated 1 times
6944    19:41:48.169    2021-05-08  [2021-05-08T19:41:48.169 DEBUG video_encoder.js:1] - _UploaderProcess stderr: [hls @ 0000026eabfecb40] skipping 2 segments ahead, expired from playlists
6943    19:41:44.289    2021-05-08  [2021-05-08T19:41:44.289 DEBUG video_encoder.js:1] - _encProcess_dst stderr: [mpegts @ 000002502ff6cdc0] Packet corrupt (stream = 0, dts = 1445819).
6942    19:41:36.153    2021-05-08  [2021-05-08T19:41:36.153 DEBUG video_encoder.js:1] - _UploaderProcess stderr: [mpegts @ 0000026eabff7c40] Packet corrupt (stream = 0, dts = 1800124498).
6941    19:41:34.154    2021-05-08  [2021-05-08T19:41:34.154 DEBUG video_encoder.js:1] - _UploaderProcess stderr: [hls @ 0000026eabfecb40] skipping 2 segments ahead, expired from playlists
6940    19:41:31.565    2021-05-08  Error while decoding stream #0:1: Invalid data found when processing input
6939    19:41:31.565    2021-05-08  [2021-05-08T19:41:31.565 DEBUG video_encoder.js:1] - _encProcess_dst stderr: [aac @ 000002502ff97c40] skip_data_stream_element: Input buffer exhausted before END element found
6938    19:41:31.564    2021-05-08  Error while decoding stream #0:1: Invalid data found when processing input
6937    19:41:31.564    2021-05-08  [2021-05-08T19:41:31.564 DEBUG video_encoder.js:1] - _encProcess_dst stderr: [aac @ 000002502ff97c40] Number of bands (46) exceeds limit (41).
6936    19:41:31.498    2021-05-08  [mpegts @ 000002502ff6cdc0] Packet corrupt (stream = 1, dts = 185153643).
6935    19:41:31.498    2021-05-08  [2021-05-08T19:41:31.498 DEBUG video_encoder.js:1] - _encProcess_dst stderr: [mpegts @ 000002502ff6cdc0] PES packet size mismatch
6934    19:41:31.486    2021-05-08  [2021-05-08T19:41:31.486 DEBUG video_encoder.js:1] - _encProcess_dst stderr: [h264 @ 0000025030f0be80] co located POCs unavailable
6933    19:41:31.484    2021-05-08  [2021-05-08T19:41:31.484 DEBUG video_encoder.js:1] - _encProcess_dst stderr: [h264 @ 0000025030f0b540] co located POCs unavailable
6932    19:41:31.483    2021-05-08  [2021-05-08T19:41:31.483 DEBUG video_encoder.js:1] - _encProcess_dst stderr: [h264 @ 0000025030f0b0c0] co located POCs unavailable
6931    19:41:31.480    2021-05-08  [2021-05-08T19:41:31.480 DEBUG video_encoder.js:1] - _encProcess_dst stderr: [mpegts @ 000002502ff6cdc0] Packet corrupt (stream = 0, dts = 185167857).
6930    19:41:31.447    2021-05-08  [2021-05-08T19:41:31.447 DEBUG video_encoder.js:1] - _tspProcess_play stderr: * Warning: regulate: out of sequence PCR, maybe source was cycling, restarting regulation
6929    19:41:22.164    2021-05-08  [mpegts @ 0000026eabff7c40] Packet corrupt (stream = 0, dts = 1798863237).
6928    19:41:22.164    2021-05-08  [2021-05-08T19:41:22.164 DEBUG video_encoder.js:1] - _UploaderProcess stderr: Last message repeated 1 times
6927    19:41:02.119    2021-05-08  [2021-05-08T19:41:02.119 DEBUG video_encoder.js:1] - _UploaderProcess stderr: [hls @ 0000026eabfecb40] skipping 2 segments ahead, expired from playlists
6926    19:40:50.147    2021-05-08  [2021-05-08T19:40:50.147 DEBUG video_encoder.js:1] - _UploaderProcess stderr: [mpegts @ 0000026eabff7c40] Packet corrupt (stream = 0, dts = 1795980354).
6925    19:40:46.111    2021-05-08  [2021-05-08T19:40:46.111 DEBUG video_encoder.js:1] - _UploaderProcess stderr: [hls @ 0000026eabfecb40] skipping 2 segments ahead, expired from playlists
6924    19:40:34.099    2021-05-08  [2021-05-08T19:40:34.099 DEBUG video_encoder.js:1] - _UploaderProcess stderr: [mpegts @ 0000026eabff7c40] Packet corrupt (stream = 0, dts = 1794538913).
6923    19:40:30.074    2021-05-08  [2021-05-08T19:40:30.074 DEBUG video_encoder.js:1] - _UploaderProcess stderr: [hls @ 0000026eabfecb40] skipping 2 segments ahead, expired from playlists
6922    19:40:18.062    2021-05-08  [2021-05-08T19:40:18.062 DEBUG video_encoder.js:1] - _UploaderProcess stderr: [mpegts @ 0000026eabff7c40] Packet corrupt (stream = 0, dts = 1793097471).
6921    19:40:14.081    2021-05-08  [2021-05-08T19:40:14.081 DEBUG video_encoder.js:1] - _UploaderProcess stderr: [hls @ 0000026eabfecb40] skipping 2 segments ahead, expired from playlists
6920    19:40:02.055    2021-05-08  [mpegts @ 0000026eabff7c40] Packet corrupt (stream = 0, dts = 1791656030).
6919    19:40:02.055    2021-05-08  [2021-05-08T19:40:02.055 DEBUG video_encoder.js:1] - _UploaderProcess stderr: Last message repeated 1 times
6918    19:39:42.040    2021-05-08  [2021-05-08T19:39:42.040 DEBUG video_encoder.js:1] - _UploaderProcess stderr: [hls @ 0000026eabfecb40] skipping 2 segments ahead, expired from playlists
6917    19:39:30.017    2021-05-08  [2021-05-08T19:39:30.017 DEBUG video_encoder.js:1] - _UploaderProcess stderr: [mpegts @ 0000026eabff7c40] Packet corrupt (stream = 0, dts = 1788773147).
6916    19:39:26.014    2021-05-08  [2021-05-08T19:39:26.014 DEBUG video_encoder.js:1] - _UploaderProcess stderr: [hls @ 0000026eabfecb40] skipping 2 segments ahead, expired from playlists
6915    19:39:13.996    2021-05-08  [2021-05-08T19:39:13.996 DEBUG video_encoder.js:1] - _UploaderProcess stderr: [mpegts @ 0000026eabff7c40] Packet corrupt (stream = 0, dts = 1787331706).
6914    19:39:10.004    2021-05-08  [2021-05-08T19:39:10.004 DEBUG video_encoder.js:1] - _UploaderProcess stderr: [hls @ 0000026eabfecb40] skipping 2 segments ahead, expired from playlists
6913    19:38:58.003    2021-05-08  [2021-05-08T19:38:58.003 DEBUG video_encoder.js:1] - _UploaderProcess stderr: [mpegts @ 0000026eabff7c40] Packet corrupt (stream = 0, dts = 1785890264).


  


• Use data to develop impactful video content

  28 septembre 2021, par Ben Erskine — Analytics Tips, Plugins

  Creating impactful video content is at the heart of what you do. How you really engage with your audience, change behaviours and influence customers to complete your digital goals. But how do you create truly impactful marketing content ? By testing, trialling, analysing and ultimately tweaking and reacting to data-informed insights that gear your content to your audience (rather than simply producing great content and shooting arrows in the dark).

  Whether you want to know how many plays your video has, finish rates, how your video is consumed over time, how video was consumed on specific days or even which locations users are viewing your video content. Media Analytics will gather all of your video data in one place and provide answers to all of these questions (and much more).

  

  What is impactful video content ?

  Impactful video content grabs your audience’s attention, keeps their attention and promotes them to take measurable action. Be that time spent on your website, goal completion or brand engagement (including following, commenting or sharing on social). Maybe you’ve developed video content, had some really great results, but not consistently, nor every time and it can be difficult to identify what exactly it is that engages and entices each and every time. And we all want to find where that lovely sweet spot is for your audience.

  Embedded video on your website can be a marketing piece that talks about the benefits of your product. Or can be educational or informative that support the brand and overall impression of the brand. And at the very best entertaining at the same time. 

  84% of people say that they’ve been convinced to buy a product or service by watching a brand’s video. Building trust, knowledge and engagement are simply quicker with video. Viewers interact more, and are engaged longer with video, they are more likely to take in the message and trust what they are seeing through educational, informative or even entertaining video marketing content than solely through reading content on a website. And even better they take action, complete goals on your website and engage with your brand (potentially long term).

  It is not only necessary to have embedded video content on your website, it needs to deliver all the elements of a well functioning website, creating the very best user experience is essential to keeping your viewers engaged. This includes ensuring the video is quick to load, on-brand, expected (in format and tone) and easy to use and/or find. Ensuring that your video content is all of these things can mean that your website users will stick around longer on your website, spend more time exploring (and reading) your website and ultimately complete more of your goals. With a great user experience, your users, in turn, are more likely to come back again to your website and trust your brand. 

  All great reasons to create impactful video content that supports your website and brand ! And to analyse data around this behaviour to repeat (or better) the video content that really hits the mark.

  

  Let’s talk stats

  In terms of video marketing, there are stats to support that viewers retain 95% of a message when they view it in a video format. The psychology behind this should be fairly obvious. It is easier (and quicker) for humans to consume video and watch someone explain something than it is to read and take action. Simply look at the rise of YouTube for explanatory and instructional video content !

  And how about the 87% of marketers that report a positive ROI on using video in their marketing ? This number has steadily increased since 2015 and matches the increase in video views over the years. This should be enough to demonstrate that video marketing is the way forward, however it needs to be the right type of video to create impact and engagement.

  Do you need more reasons to consider honing and refining your video content for your audience ? And riding this wave of impactful video marketing success ?

  

  But, how do we do that ?

  So, how do you make content that consistently converts your audience to engaged customers ? The answer is in the numbers. The data. Collecting data on each and every piece of media that is produced and put out into the world. Measuring everything, from where it is viewed, how it is viewed, how much of it is viewed and what is your viewer’s action after the fact.

  While Vimeo and YouTube have their own video analytics they are each to their own, meaning a lot more work for you to combine and analyse your data before forming insights that are useful. 

  Your data is collected by external parties, and is owned and used by these platforms, for their own means. Using Web Analytics from Matomo to collect and collate media data can mean your robust data insights are all in one place. And you own the data, keeping your data private, clean and easy to digest. 

  Once your data is across a single platform, your time can be spent on analysing the data (rather than collating) and discovering those super valuable insights. Additionally, these insights can be collated and reported, in one place, and used to inform future digital and video marketing planning. Working with the data and alongside creative teams to produce video that talks to your audience in an impactful way.

  The more data that is collected the deeper the insights. Saving time and money across a single platform and with data-backed insights to inform decisions that can influence the time (and money) spent producing video content that truly hits the mark with your audience. No more wasted investment and firing into the dark without knowledge. 

  Interrogating the ideal length of your video media means it is more likely to be viewed to the end. Or understanding the play rate on your website of any video. How often is the video played ? And which is played more often ? Constant tweaking and updating of your video content planning can be informed by data-driven human-centric insights. By consistently tracking your media, analysing and forming insights you can build upon past work, and create a fuller picture of who your audience is and how they will engage with future video content. Understanding your media over time can lead to informed decisions that can impact the video content and the level of investment to deliver ROI that means something.

  

  Wrap Up

  Media Analytics puts you at the heart of video engagement. No more guessing at what your audience wants to see, how long or when. Make every piece of video content have the impact you want (and need) to drive engagement, goal completion and customer conversion. Create a user experience that keeps your users on your website for longer. Delivering on all of those delicious digital marketing goals and speaking the language of key stakeholders throughout the business. Back your digital marketing, with truly impactful content, and above all else deliver to your audience content that keeps them engaged and coming back for more.

  Don’t just take our word for it ! Take a look at what Matomo can offer you with streamlined and insightful Media Analytics, all in one place. And go forth and create impactful content, that matters.

  Next steps :

  Check out our detailed user guide to Media Analytics

  Or, if you have questions, see our helpful Video & Audio Analytics FAQ’s