Recherche avancée

Sur d’autres sites (7537)

• Introducing the Data Warehouse Connector feature

  30 janvier, par Matomo Core Team

  Matomo is built on a simple truth : your data belongs to you, and you should have complete control over it. That’s why we’re excited to launch our new Data Warehouse Connector feature for Matomo Cloud, giving you even more ways to work with your analytics data. 

  Until now, getting raw data from Matomo Cloud required APIs and custom scripts, or waiting for engineering help.  

  Our new Data Warehouse Connector feature removes those barriers. You can now access your raw, unaggregated data and schedule regular exports straight to your data warehouse. 

  The feature works with all major data warehouses including (but not limited to) : 

  • Google BigQuery 
  • Amazon Redshift 
  • Snowflake 
  • Azure Synapse Analytics 
  • Apache Hive 
  • Teradata 

  You can schedule exports, combine your Matomo data with other data sources in your data warehouse, and easily query data with SQL-like queries. 

  Direct raw data access for greater data portability 

  Waiting for engineering support can delay your work. Managing API connections and writing scripts can be time-consuming. This keeps you from focusing on what you do best—analysing data. 

  

  With the Data Warehouse Connector feature, you get direct access to your raw Matomo data without the technical setup. So, you can spend more time analysing data and finding insights that matter. 

  Bringing your data together 

  Answering business questions often requires data from multiple sources. A single customer interaction might span your CRM, web analytics, sales systems, and more. Piecing this data together manually is time-consuming—what starts as a seemingly simple question from stakeholders can turn into hours of work collecting and comparing data across different tools. 

  This feature lets you combine your Matomo data with data from other business systems in your data warehouse. Instead of switching between tools or manually comparing spreadsheets, you can analyse all your data in one place to better understand how customers interact with your business. 

  Easy, custom analysis with SQL-like queries 

  Standard, pre-built reports often don’t address the specific, detailed questions that analysts need to answer.  

  When you use the Data Warehouse Connector feature, you can use SQL-like queries in your data warehouse to do detailed, customised analysis. This flexibility allows you to explore your data in depth and uncover specific insights that aren’t possible with pre-built reports. 

  

  Here is an example of how you might use SQL-like query to compare the behaviours of paying vs. non-paying users : 

  				
                                          <xmp>SELECT  
  
  
  
  custom_dimension_value AS user_type, -- Assuming 'user_type' is stored in a custom dimension 
  
  
  
  COUNT(*) AS total_visits,  
  
  
  
  AVG(visit_total_time) AS avg_duration, 
  
  
  
  SUM(conversion.revenue) AS total_spent  
  
  
  
  FROM  
  
  
  
  `your_project.your_dataset.matomo_log_visit` AS visit 
  
  
  
  LEFT JOIN  
  
  
  
  `your_project.your_dataset.matomo_log_conversion` AS conversion  
  
  
  
  ON  
  
  
  
  visit.idvisit = conversion.idvisit  
  
  
  
  GROUP BY  
  
  
  
  custom_dimension_value; </xmp>
  
                                  
  			

  This query helps you compare metrics such as the number of visits, average session duration, and total amount spent between paying and non-paying users. It provides a full view of behavioural differences between these groups. 

  Advanced data manipulation and visualisation 

  When you need to create detailed reports or dive deep into data analysis, working within the constraints of a fixed user interface (UI) can limit your ability to draw insights. 

  Exporting your Matomo data to a data warehouse like BigQuery provides greater flexibility for in-depth manipulation and advanced visualisations, enabling you to uncover deeper insights and tailor your reports more effectively. 

  Getting started 

  To set up data warehouse exports in your Matomo : 

  1. Go to System Admin (cog icon in the top right corner) 
  2. Select ‘Export’ from the left-hand menu 
  3. Choose ‘Data Warehouse Connector’ 

  You’ll find detailed instructions in our data warehouse exports guide.  

  Please note, enabling this feature will cost an additional 10% of your current subscription. You can view the exact cost by following the steps above. 

  New to Matomo ? Start your 21-day free trial now (no credit card required), or request a demo. 

  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 : UDP to RTMP stream - issues with PES/out of range/corrupted macroblock

  15 août 2019, par MZL

  I´m trying to convert a UDP multicast transportstream video to a RTMP video stream with ffmpeg.

  The stream is generated with a Teracue ENC-300 hardware encoder. The encoder sends the stream as TS/UDP packets to the multicast IP 239.252.20.100:4444.
  ffmpeg can convert the stream, but only at a really low bitrate and/or with a lot of errors.

  My ffmpeg command looks as follows :

  ffmpeg -re -i udp://@239.252.20.100:4444?buffer_size=32000k 
  
  -b:v 900k -maxrate 1000k -bufsize 32000k -f flv 
  
  "rtmp://127.0.0.1/live/live1" -loglevel debug

  I´ve already tried some easyer code :

  ffmpeg -re -i udp://@239.252.20.100:4444 -f flv 
  
  "rtmp://127.0.0.1/live/live1" -loglevel debug

  The Teracue generates the stream with a bitrate of 1500kbps. I also tried some higher or lower bitrates. But the output of ffmpeg has only a maximum bitrate of about 400kbps. If I increase the bitrate with

  -b:v 900k

  or sometimes, when no output bitrate is set, I get a lot of error messages, especially

  PES packet size mismatch
  
  error while decoding MB X X
  
  corrupted macroblock X X

  Here is the error code :

  >[h264 @ 000002883adfe800] nal_unit_type: 6(SEI), nal_ref_idc: 0
  
  
  
  >[h264 @ 000002883adfe800] nal_unit_type: 1(Coded slice of a non-IDR picture), >nal_ref_idc: 3
  
  
  
  >[h264 @ 000002883adfe800] ct_type:1 pic_struct:0
  
  
  
  >[mpegts @ 000002883a329340] Continuity check failed for pid 192 expected 4 >got 7
  
  
  
  >[mpegts @ 000002883a329340] pid=c0 pes_code=0x1c0
  
  
  
  >    Last message repeated 1 times
  
  
  
  >[mpegts @ 000002883a329340] pid=2c pes_code=0x1e0
  
  
  
  >[NULL @ 000002883a33f7c0] ct_type:1 pic_struct:0
  
  
  
  >udp://@239.252.20.100:4444?buffer_size=32000k: corrupt decoded frame in 
  
  
  
  >stream 1
  
  
  
  >[h264 @ 000002883a35a240] nal_unit_type: 9(AUD), nal_ref_idc: 0
  
  
  
  >[h264 @ 000002883a35a240] nal_unit_type: 6(SEI), nal_ref_idc: 0
  
  
  
  >[h264 @ 000002883a35a240] nal_unit_type: 1(Coded slice of a non-IDR picture), 
  
  
  
  >nal_ref_idc: 3
  
  
  
  >[h264 @ 000002883a35a240] ct_type:1 pic_struct:0
  
  
  
  >[h264 @ 000002883a35a240] out of range intra chroma pred mode
  
  
  
  >[h264 @ 000002883a35a240] error while decoding MB 14 8
  
  
  
  >[mpegts @ 000002883a329340] Continuity check failed for pid 44 expected 2 got 
  
  >9
  
  
  
  >[mpegts @ 000002883a329340] PES packet size mismatch
  
  
  
  >[mpegts @ 000002883a329340] pid=2c pes_code=0x1e0
  
  
  
  >[NULL @ 000002883a33f7c0] ct_type:1 pic_struct:0
  
  
  
  >[h264 @ 000002883a35a240] concealing 845 DC, 845 AC, 845 MV errors in P frame
  
  
  
  >[h264 @ 000002883a38f6c0] nal_unit_type: 9(AUD), nal_ref_idc: 0
  
  
  
  >[h264 @ 000002883a38f6c0] nal_unit_type: 6(SEI), nal_ref_idc: 0
  
  
  
  >[h264 @ 000002883a38f6c0] nal_unit_type: 1(Coded slice of a non-IDR picture), >nal_ref_idc: 3
  
  
  
  >[h264 @ 000002883a38f6c0] ct_type:1 pic_struct:0
  
  
  
  >[h264 @ 000002883a38f6c0] Frame num gap 28 26
  
  
  
  >[mpegts @ 000002883a329340] Continuity check failed for pid 192 expected 9 >got 12
  
  
  
  >[mpegts @ 000002883a329340] pid=c0 pes_code=0x1c0
  
  
  
  >[mpegts @ 000002883a329340] Continuity check failed for pid 44 expected 1 got >15
  
  
  
  >[mpegts @ 000002883a329340] PES packet size mismatch
  
  
  
  >[mpegts @ 000002883a329340] pid=2c pes_code=0x1e0
  
  
  
  >[NULL @ 000002883a33f7c0] ct_type:1 pic_struct:0
  
  
  
  >udp://@239.252.20.100:4444?buffer_size=32000k: corrupt decoded frame in 
  
  >stream 1
  
  
  
  >[h264 @ 000002883adf1980] nal_unit_type: 9(AUD), nal_ref_idc: 0
  
  
  
  >[h264 @ 000002883adf1980] nal_unit_type: 6(SEI), nal_ref_idc: 0
  
  
  
  >[h264 @ 000002883adf1980] nal_unit_type: 1(Coded slice of a non-IDR picture), 
  
  
  
  >nal_ref_idc: 3
  
  
  
  >[h264 @ 000002883adf1980] ct_type:1 pic_struct:0
  
  
  
  >[h264 @ 000002883adf1980] mb_type 41 in P slice too large at 18 9
  
  
  
  >[h264 @ 000002883adf1980] error while decoding MB 18 9
  
  
  
  >[h264 @ 000002883adf1980] concealing 796 DC, 796 AC, 796 MV errors in P frame
  
  
  
  >[mpegts @ 000002883a329340] pid=c0 pes_code=0x1c0
  
  
  
  >[NULL @ 000002883a33f7c0] ct_type:1 pic_struct:0
  
  
  
  >[h264 @ 000002883adf20c0] nal_unit_type: 9(AUD), nal_ref_idc: 0
  
  
  
  >[h264 @ 000002883adf20c0] nal_unit_type: 7(SPS), nal_ref_idc: 3
  
  
  
  >[h264 @ 000002883adf20c0] nal_unit_type: 8(PPS), nal_ref_idc: 3
  
  
  
  >[h264 @ 000002883adf20c0] nal_unit_type: 6(SEI), nal_ref_idc: 0
  
  
  
  >[h264 @ 000002883adf20c0] nal_unit_type: 5(IDR), nal_ref_idc: 3
  
  
  
  >[h264 @ 000002883adf20c0] ct_type:1 pic_struct:0
  
  
  
  >[h264 @ 000002883adf20c0] corrupted macroblock 3 0 (total_coeff=-1) 
  
  
  
  >114.0kbits/s speed=   1x
  
  
  
  >[h264 @ 000002883adf20c0] error while decoding MB 3 0
  
  
  
  >[mpegts @ 000002883a329340] pid=c0 pes_code=0x1c0

  Any solutions ?

• How to convert rtmp hevc video stream to srt av1 endpoint with ffmpeg ?

  20 juin 2024, par Lulík

  i want use ffmpeg to listen rtmp stream and send to srt endpoint.

  


  Flow : smartphone (camera) -> laptop (ffmpeg script) -> desktop (obs studio)

  


  ffmpeg script show warning message and in obs stuido i can see any video only audio.

  


  Thank you in advance.

  


  Console output while running script (error in the end is bcs i stoped sending data from phone) :

  


  ffmpeg version git-2024-06-20-8d6014d Copyright (c) 2000-2024 the FFmpeg developers
  built with gcc 12 (Debian 12.2.0-14)
  configuration: --enable-libsvtav1 --enable-libsrt
  libavutil      59. 24.100 / 59. 24.100
  libavcodec     61.  8.100 / 61.  8.100
  libavformat    61.  3.104 / 61.  3.104
  libavdevice    61.  2.100 / 61.  2.100
  libavfilter    10.  2.102 / 10.  2.102
  libswscale      8.  2.100 /  8.  2.100
  libswresample   5.  2.100 /  5.  2.100
Input #0, flv, from 'rtmp://192.168.0.194/s/streamKey':
  Duration: 00:00:00.00, start: 0.000000, bitrate: N/A
  Stream #0:0: Video: hevc (Main), yuv420p(tv, smpte170m/bt470bg/smpte170m), 1080x1920, 10240 kb/s, 30 fps, 120 tbr, 1k tbn
  Stream #0:1: Audio: aac (LC), 44100 Hz, stereo, fltp, 131 kb/s
Stream mapping:
  Stream #0:0 -> #0:0 (hevc (native) -> av1 (libsvtav1))
  Stream #0:1 -> #0:1 (aac (native) -> mp2 (native))
Press [q] to stop, [?] for help
Svt[info]: -------------------------------------------
Svt[info]: SVT [version]:   SVT-AV1 Encoder Lib 595a874
Svt[info]: SVT [build]  :   GCC 12.2.0   64 bit
Svt[info]: LIB Build date: Jun 20 2024 14:25:08
Svt[info]: -------------------------------------------
Svt[info]: Number of logical cores available: 12
Svt[info]: Number of PPCS 76
Svt[info]: [asm level on system : up to avx2]
Svt[info]: [asm level selected : up to avx2]
Svt[info]: -------------------------------------------
Svt[info]: SVT [config]: main profile   tier (auto) level (auto)
Svt[info]: SVT [config]: width / height / fps numerator / fps denominator       : 1080 / 1920 / 120 / 1
Svt[info]: SVT [config]: bit-depth / color format                   : 8 / YUV420
Svt[info]: SVT [config]: preset / tune / pred struct                    : 10 / PSNR / random access
Svt[info]: SVT [config]: gop size / mini-gop size / key-frame type          : 641 / 16 / key frame
Svt[info]: SVT [config]: BRC mode / rate factor                     : CRF / 35 
Svt[info]: SVT [config]: AQ mode / variance boost                   : 2 / 0
Svt[info]: -------------------------------------------
Svt[warn]: Failed to set thread priority: Invalid argument
Output #0, mpegts, to 'srt://192.168.0.167:9998?mode=caller':
  Metadata:
    encoder         : Lavf61.3.104
  Stream #0:0: Video: av1, yuv420p(tv, smpte170m/bt470bg/smpte170m, progressive), 1080x1920, q=2-31, 120 fps, 90k tbn
      Metadata:
        encoder         : Lavc61.8.100 libsvtav1
  Stream #0:1: Audio: mp2, 44100 Hz, stereo, s16, 384 kb/s
      Metadata:
        encoder         : Lavc61.8.100 mp2
[mpegts @ 0x55ec921d9540] Stream 0, codec av1, is muxed as a private data stream and may not be recognized upon reading.
[in#0/flv @ 0x55ec9219cc40] Error during demuxing: Input/output error1990.7kbits/s speed=0.967x    
[out#0/mpegts @ 0x55ec922247c0] video:4431KiB audio:1138KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: 6.374870%
frame=  723 fps= 31 q=35.0 Lsize=    5923KiB time=00:00:24.12 bitrate=2011.3kbits/s speed=1.04x


  


  I send video stream from mobile app over rtmp encoded with hevc to my laptop where running script ffmpeg -f flv -listen 1 -i rtmp://192.168.0.194/s/streamKey -c:v libsvtav1 -f mpegts srt://192.168.0.167:9998?mode=caller. On the desktop i have obs with media source input srt://192.168.0.167:9998?mode=listener.

  


  When i run ffmpeg script without video codec option (-c:v libsvtav1) its working fine and in obs i can see video from my phone camera. With the option i can not see video only audio.
I clearly dont understand warning message : [mpegts @ 0x55ec921d9540] Stream 0, codec av1, is muxed as a private data stream and may not be recognized upon reading..
Do I need specify codec (av1) in obs media source or my ffmpeg script is wrong ?