Recherche avancée

Sur d’autres sites (3292)

• Introducing Updates to the Funnels Feature

  29 mai 2024, par Erin

  We’ve made improvements to the Funnels feature to be more user-friendly and offer you greater flexibility. 

  &lt;script type=&quot;text/javascript&quot;&gt;<br />
       if ('function' === typeof window.playMatomoVideo){<br />
       window.playMatomoVideo(&quot;FunnelsProductUpdate2024&quot;, &quot;#FunnelsProductUpdate2024&quot;)<br />
       } else {<br />
       document.addEventListener(&quot;DOMContentLoaded&quot;, function() { window.playMatomoVideo(&quot;FunnelsProductUpdate2024&quot;, &quot;#FunnelsProductUpdate2024&quot;); });<br />
       }<br />
  &lt;/script&gt;

  Here’s what’s changing :
  

  Setting up and managing funnels is now easier than ever 

  Previously, creating funnels was tedious and required going through the Goals feature. But we’ve changed that with the introduction of a separate page to configure funnels. 

  

  Create funnels with greater flexibility—no longer tied to goals 

  Funnels is now a standalone feature, providing you with more flexibility. Before, you could only create a funnel if it was tied to a goal, in other words, the final step in the funnel had to be a goal. What’s more, you also couldn’t use goals for steps in the funnel.  

  

  Now, funnels are independent of goals, and goals can serve as steps within the funnel. This means you have the freedom to configure any combination of steps in a funnel : 

  • All steps can be goals 
  • No steps need to be goals 
  • Or some steps can be goals, some steps can be events 

  

  No matter what your customer journey looks like, funnels now offer the versatility to meet your business’s specific needs. 

  Find friction points faster with intuitive visuals 

  One of the most significant improvements is the visual upgrade of the Funnels feature. The new Funnels graph is now visually in line with industry standards and intuitive. 

  

  The new visual provides a clearer view of your drop-off and conversion rates so you can instantly find points of friction in your funnel to improve the user experience and overall conversion rate.  

  This visualisation also provides a detailed overview of the number of visitors who enter, exit, skip, or proceed at each step of your funnel by using different coloured bars for visual clarity on each step’s performance. 

  With this update, we’ve also replaced ‘backfilled visits’ with ‘skipped steps’ to avoid misinterpretation of the data. 

  New data table for more granular insights 

  Accompanying this visual improvement is a new data table, allowing for more granular insights, segment comparison, and easy data export.
  

  

  We’ve also increased Funnel analysis limits. You can now compare funnel data for 2 date periods and 6 segments (up to 12 compared datasets in total). 

  Sign up for our newsletter to receive all the latest Matomo updates. 

  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

  

• FFMPEG, How to stream video and audio into one file with volume adjustment and video cropping [closed]

  24 décembre 2024, par Unlock iPhone

  ffmpeg -i "1.mp4" -i "Knockout.mp3" -filter_complex "[0:a]volume=0.1,atempo=1.1[a] ;[1:a]volume=1[b] ;[a][b]amix=inputs=2[audio]" -filter_complex "setpts=PTS/1.1,crop='min(iw\,ih1/1)' :'min(ih\,iw1/1)" -c:v libx264 -preset ultrafast -tune fastdecode -crf 20 -c:a aac -b:a 128k -r 30 -strict experimental -shortest "Output_00001.mp4"

  


  ffmpeg -i "1.mp4" -i "Knockout.mp3" -filter_complex "[0:a]volume=0.1,atempo=1.1[a] ;[1:a]volume=1[b] ;[a][b]amix=inputs=2[audio]" -filter_complex "setpts=PTS/1.1,crop='min(iw\,ih1/1)' :'min(ih\,iw1/1)" -c:v libx264 -preset ultrafast -tune fastdecode -crf 20 -c:a aac -b:a 128k -r 30 -strict experimental -shortest "Output_00001.mp4"
ffmpeg version 2024-12-19-git-494c961379-full_build-www.gyan.dev Copyright (c) 2000-2024 the FFmpeg developers
built with gcc 14.2.0 (Rev1, Built by MSYS2 project)
configuration : —enable-gpl —enable-version3 —enable-static —disable-w32threads —disable-autodetect —enable-fontconfig —enable-iconv —enable-gnutls —enable-libxml2 —enable-gmp —enable-bzlib —enable-lzma —enable-libsnappy —enable-zlib —enable-librist —enable-libsrt —enable-libssh —enable-libzmq —enable-avisynth —enable-libbluray —enable-libcaca —enable-sdl2 —enable-libaribb24 —enable-libaribcaption —enable-libdav1d —enable-libdavs2 —enable-libopenjpeg —enable-libquirc —enable-libuavs3d —enable-libxevd —enable-libzvbi —enable-libqrencode —enable-librav1e —enable-libsvtav1 —enable-libwebp —enable-libx264 —enable-libx265 —enable-libxavs2 —enable-libxeve —enable-libxvid —enable-libaom —enable-libjxl —enable-libvpx —enable-mediafoundation —enable-libass —enable-frei0r —enable-libfreetype —enable-libfribidi —enable-libharfbuzz —enable-liblensfun —enable-libvidstab —enable-libvmaf —enable-libzimg —enable-amf —enable-cuda-llvm —enable-cuvid —enable-dxva2 —enable-d3d11va —enable-d3d12va —enable-ffnvcodec —enable-libvpl —enable-nvdec —enable-nvenc —enable-vaapi —enable-libshaderc —enable-vulkan —enable-libplacebo —enable-opencl —enable-libcdio —enable-libgme —enable-libmodplug —enable-libopenmpt —enable-libopencore-amrwb —enable-libmp3lame —enable-libshine —enable-libtheora —enable-libtwolame —enable-libvo-amrwbenc —enable-libcodec2 —enable-libilbc —enable-libgsm —enable-liblc3 —enable-libopencore-amrnb —enable-libopus —enable-libspeex —enable-libvorbis —enable-ladspa —enable-libbs2b —enable-libflite —enable-libmysofa —enable-librubberband —enable-libsoxr —enable-chromaprint
libavutil 59. 51.100 / 59. 51.100
libavcodec 61. 27.101 / 61. 27.101
libavformat 61. 9.101 / 61. 9.101
libavdevice 61. 4.100 / 61. 4.100
libavfilter 10. 6.101 / 10. 6.101
libswscale 8. 12.100 / 8. 12.100
libswresample 5. 4.100 / 5. 4.100
libpostproc 58. 4.100 / 58. 4.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '1.mp4' :
Metadata :
minor_version : 512
major_brand : isom
compatible_brands : isomiso2avc1mp41
metadata1 : TC1nO7kRGA2g5D7EvY6mVieKMGAICBrUodQ2askGrBS9jYT4Vj3PxKPaPJbSJiYW312zpE9OA+GfQsSmsg/l0YPpVbGHSS0k1WWlIhavn4vgaEjIiMMw5ES5FyQ6NBpt9K1YOSiIg6IEc4CgvXCVgyI5VVvX9u053QTky2KsdRNRA32Ui1XkoBTAB
metadata0 : ChtzZWN1cml0eS5rbGluZy5tZXRhX2VuY3J5cHQS8AGDblTacnE/fscfVL6m9on8gh3O9gP57LnH5Gi3m5WuoRauKnAkpgZgCqmDNvDCKcv7WjIn6u+WSNAu60xW9WLkiOodDgOO2LkcD3RQmNE435FJW7rzQGPQCWEORRjI73eTSQLHggb3O876An7Ho7eHOiOljlsdEkvPDRIGlAwfn5QZKj43rdvl4q6p0lL1Wjb6qGjdvX0e6QTI1dT9qdr
encoder : Lavf58.45.100
Duration : 00:00:10.04, start : 0.000000, bitrate : 16952 kb/s
Stream #0:00x1 : Video : h264 (High) (avc1 / 0x31637661), yuv420p(progressive), 1080x1920, 16948 kb/s, 24 fps, 24 tbr, 12288 tbn (default)
Metadata :
handler_name : VideoHandler
vendor_id : [0][0][0][0]
Input #1, mp3, from 'Knockout.mp3' :
Metadata :
encoder : Lavf61.5.101
Duration : 00:02:14.54, start : 0.023021, bitrate : 131 kb/s
Stream #1:0 : Audio : mp3 (mp3float), 48000 Hz, stereo, fltp, 131 kb/s
Metadata :
encoder : Lavc61.12
[fc#0 @ 0000025538b16280] Stream specifier ':a' in filtergraph description [0:a]volume=0.1,atempo=1.1[a] ;[1:a]volume=1[b] ;[a][b]amix=inputs=2[audio] matches no streams.
Error binding filtergraph inputs/outputs : Invalid argument

  


• Increased File Size When Converting MP4 to WebM using FFmpeg

  23 décembre 2024, par kimgijeong

  I am using FFmpeg to convert MP4 to WebM with the following command :

  


  ffmpeg -y -hide_banner -nostats \
-f mov,mp4,m4a,3gp,3g2,mj2 -i "http://127.0.0.1:80/lotteon-low-bitrate.mp4" \
-threads auto -f webm -acodec libopus -b:a 96.059k -vcodec libsvtav1 -preset 11 -pix_fmt yuv420p \
-vf "scale='min(-1, iw)':'min(-1,ih)':force_original_aspect_ratio=decrease,crop=trunc(iw/2)*2:trunc(ih/2)*2" \
"/usr/local/m2/m2temp/xcdrtmp/2052_1.webm"


  


  However, the output webm file size is larger than the source MP4 file. For example :

  


  


  • Source MP4 : 4.6 MB (bit rate : 994,053 bps)

    


  


  • Output WebM : 16 MB (bit rate : 3,902,037 bps)

    


  


  


  I know SVT-AV1 encoder defaults to CRF mode. Due to not specifying the bitrate explicitly, the SVT-AV1 encoder automatically sets the bit_rate. It appears that the encoder is setting it to a much higher value (3,323,104 bps), causing the increase in file size compared to the source MP4 (994,053 bps). Here are the methods i tried to reduce the WebM file size compared to the source MP4 :

  


  

  1. -b:v 994k

  


  


  I tried to match the target bitrate with the source MP4's bitrate to reduce the output size, but encountered the following error :

  


  Svt[error]: Instance 1: Force key frames is not supported for VBR mode Last message r
epeated 2 times [libsvtav1 @ 0x239dd100] Error setting encoder parameters: bad parameter (0x80001005)


  


  Looking at the official documentation, this mode change (from CRF to VBR when setting a target bitrate) appears to be expected behavior. However, the error is puzzling since I haven't set any force keyframe parameters in the FFmpeg command.

  


  

  2. svtav1-params "mbr=994k"

  


  


  The second method i tried was using the svtav1-params "mbr=994k" option to set the maxrate while maintaining CRF mode This method showed some improvement, but the output file size was still larger than the source MP4.

  


  

  • Output WebM : 5MB (bit rate : 1,209,877 bps)

  


  


  The more critical reason why we can't adopt the second method (using svtav1-params "mbr=994k") is that even for the same MP4 source file, the output file size varies slightly with each encoding.

  


  

  3. -b:v 994k -svtav1-params “rc=2:pred-struct=1”(CBR, low delay)

  


  


  The final method I tried was setting the target bitrate while using CBR (Constant Bit Rate) and low-delay mode The default value for pred-structure is 2(random access), but I had to use low-delay mode due to the following error :

  


  Svt[error]: CBR Rate control is currently not supported for SVT_AV1_PRED_RANDOM_ACCESS, use VBR mode


  


  This way was the only approach among those i tried that successfully reduced the output size.

  


  

  • Output WebM : 4.3MB (bit rate : 1,032,373 bps)

  


  


  In summary, I have three questions about this MP4 to WebM conversion issue :

  


  


  1. When setting the target bitrate with -b:v 994k, the switch to VBR mode is expected behavior. However, why does the force keyframe error occur when we haven't explicitly set any force keyframe parameters ?

     


  


  2. Why does the output WebM file size fluctuate when setting maxrate either through -maxrate or svtav1-params "mbr=994k", even when using the same MP4 source file ?

     


  


  3. Besides using -b:v 994k -svtav1-params "rc=2:pred-struct=1" (CBR with low delay), are there any other methods that can guarantee a WebM output size smaller than the source MP4 when converting from MP4 to WebM ?

     


  


  


  I am using a recent version of the SVT-AV1 codec :

  


  Svt[info]: SVT [version]:       SVT-AV1 Encoder Lib 58146ca
Svt[info]: SVT [build]  :       GCC 11.5.0 20240719 (Red Hat 11.5.0-2)   64 bit
Svt[info]: LIB Build date: Oct 28 2024 07:40:59
ffmpeg video svt-av1