Recherche avancée

Sur d’autres sites (7577)

• To all Matomo plugin developers : Matomo 4 is coming, make your plugin compatible now

  6 août 2020, par Matomo Core Team — Development

  We’re planning to release the first beta of Matomo 4 in a few weeks. For making it easy for Matomo users to be able to upgrade to this beta, it would be great if as many plugins on the Marketplace as possible would be already updated and compatible with Matomo 4. Then many users would be able to upgrade to the first beta without any issues.

  Presumably, as you put your plugin on our Marketplace, you want people to use it. Making your plugin compatible with Matomo 4 helps ensure that people will be able to find and keep using your plugin. If your plugin is not compatible with Matomo 4, your plugin will be automatically deactivated. We’ll be happy to help you achieve compatibility should there be any issue.

  How do I upgrade my Matomo to Matomo 4 ?

  If you have installed your Matomo development environment through git you can simply checkout the Matomo 4 branch “4.x-dev” by executing these commands :

  • git checkout 4.x-dev 
  • composer install

  Alternatively, you can also download the latest version directly from GitHub as a zip file and run composer install afterwards. 

  How do I upgrade my plugin to Matomo 4 ?

  • We recommend you create a new branch for your plugin that supports Matomo 4. For example a branch named “4.x-dev“. This way you will be able to make changes to your plugin for Matomo 3 and Matomo 4 and release separate versions.
  • Check out our migration guide from Matomo 3 to Matomo 4 and the list of all breaking changes.
  • Release a new version of your plugin in GitHub as usual.

  While there were many breaking changes in Matomo 4, most of our Platform APIs remain unchanged, and almost all changes are for rarely used APIs. Often to make your plugin compatible it will just be a matter of adjusting the “plugin.json” file (as mentioned in the migration guide).

  You can find all developer documentation on our developer zone which has already been updated for Matomo 4.

  How do I know my plugin changes were released successfully ?

  If you have configured an email address within your “plugin.json” file, then you will receive a confirmation or an error email within a few minutes. Alternatively, you can also check out your plugin page on the Marketplace directly. If the plugin release was successful, you will see additional links below the download button showing which versions your plugin is compatible with.

  

  How can I downgrade to Matomo 3 or switch between Matomo 3 and Matomo 4 ?

  To downgrade from Matomo 4 to Matomo 3 :

  • check out the “3.x-dev” branch 
  • run a composer install as usual. 
  • run the SQL statements from this downgrade guide to restore the previous MySQL schema.

  When will the final Matomo 4 release be available ?

  We estimate the final stable Matomo 4.0.0 release will be released in approx. 3 months.

  What’s new in Matomo 4 ?

  We don’t have a summary of the changes available just yet but you can see all closed issues within this release here.

  Any questions or need help ? 

  If you have any questions, or experience any problems during the migration don’t hesitate to get in touch with us. We’ll be happy to help get your plugin compatible and the update published. If you find any undocumented breaking change or find any step during the migration process not clear, please let us know as well.

  Thank you for contributing a plugin to the Marketplace and making Matomo better. We really appreciate your work !

• Nodejs couldn't find the ffmpeg module for some reason

  29 décembre 2020, par Chawchawchaw

  I need to display the live streaming vidoe(rtsp) on a website(http, vue framework) with nodejs and vue framework.

  


  I've looked it up a lot and got the basic logic of what they are and how it works.
So I'm planning on to convert rtsp to hls with nodejs using socket.io and display it on a web.(let me know if there's more efficient way way to do it)

  


  The thing is, for some reason, when I try to develop it in my backend(nodejs), node just keep sends me an error that FFMpeg module wasn't found. It's been over a week.. please help.

  


  Btw, all works with ffmpeg cmd(window powerShell).

  


  How I set up(ffmpeg) :

  


  


  1. downloaded ffmpeg from https://ffmpeg.org/

     


  


  2. added to system path : C :\Users\Marie\Desktop\ffmpeg-4.3.1-2020-11-19-full_build\bin

     


  


  3. tested with window powerShell and converted rstp to m3u8 :

     


     ffmpeg -i 'rtsp ://ip.ip.ip/media/video1' -hls_time 3 -hls_wrap 10 'C :\Users\Marie\Desktop\tmp\hls/streaming.m3u8'

     


  


  


  below is a screen shot of no. 3 result


  


  ---

  


  how I set up(nodejs)

  


  

  1. npm i ffmpeg fluent-ffmpeg rtsp-ffmpeg

  


  2. I've just copied and pasted the example working code and changed rtsp link to mine. e.g : (https://www.npmjs.com/package/rtsp-ffmpeg)

  


  


  => didn't work out, error says can't find ffmpeg module

  


  

  3. set up path manually e.g.) ffmpeg.setFfmpegPath(path)

  


  


  => didn't work out. error says can't find ffmpeg module

  


  ...
I've seriously tried almost everything like delete, re-install ffmpeg, changed path, added path manyally, .. Please help....

  


  Edited :
package.json

  


  {
  "name": "streaming",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "start": "node app.js"
  },
  "author": "",
  "license": "ISC",
  "dependencies": {
    "express": "^4.17.1",
    "ffmpeg": "0.0.4",
    "fluent-ffmpeg": "^2.1.2",
    "jsmpeg": "^1.0.0",
    "node-media-server": "^2.2.4",
    "node-onvif": "^0.1.7",
    "node-rtsp-stream": "0.0.9",
    "rtsp-ffmpeg": "0.0.15",
    "socket.io": "^3.0.4",
    "ws": "^7.4.1"
  }
}


  


  app.js

  


  const Stream = require('node-rtsp-stream')

// let path = 'C:/Users/Marie/Desktop/ffmpeg-4.3.1-2020-11-19-full_build/bin/ffmpeg.exe'
// let path = 'C:/Users/Marie/Desktop/ffmpeg-4.3.1-2020-11-19-full_build/bin/'
let path = 'C:/Users/Marie/Desktop/ffmpeg-4.3.1-2020-11-19-full_build/bin'
const ffmpeg = require('fluent-ffmpeg')

ffmpeg.setFfmpegPath(path)

stream = new Stream({
  name: 'name',
  streamUrl: 'rtsp://ip.ip.ip.ip/media/video1',
  wsPort: 9999,
  ffmpegOptions: { // options ffmpeg flags
    '-stats': '', // an option with no neccessary value uses a blank string
    '-r': 30 // options with required values specify the value after the key
  }
})


  


  Error : spawn ffmpeg ENOENT

  


  app.js (for another test)

  


  const app = require( 'express' )(),
    server = require( 'http' ).Server( app ),
    io = require( 'socket.io' )( server ),
    rtsp = require( 'rtsp-ffmpeg' )

process.env.FFMPEG_PATH = 'C:/Users/Marie/Desktop/ffmpeg-4.3.1-2020-11-19-full_build/bin/ffmpeg.exe'
// console.log( rtsp.FFMpeg )

server.listen( 6147 )
var uri = 'rtsp://ip.ip.ip.ip/media/video1',
    stream = new rtsp.FFMpeg( { input: uri } )
io.on( 'connection', function ( socket )
{
    var pipeStream = function ( data )
    {
        socket.emit( 'data', data.toString( 'base64' ) )
    }
    stream.on( 'data', pipeStream )
    socket.on( 'disconnect', function ()
    {
        stream.removeListener( 'data', pipeStream )
    } )
} )
app.get( '/', function ( req, res )
{
    res.sendFile( __dirname + '/index.html' )
} )


  


  error :
FMpeg executable wasn't found. Install this package and check FFMpeg.cmd property

  


  nodejs version = 10.16.3

  


• FFMPEG Screen Flashing Green

  18 novembre 2022, par Devin Dixon

  I have this problem where my ffmpeg videos are flicking green. Example of the video is here :
https://www.glitch.fun/streams/31fea7e0-7523-4365-9780-31deee9e472c/watchrecording/efb841c0-4b87-4482-b165-990880a66f63

  


  My ffmpeg command is this :

  


  /usr/bin/ffmpeg -vaapi_device /dev/dri/renderD128 -y -v info -f x11grab -draw_mouse 0 -r 60 -s 1920x1080 -thread_queue_size 14000 -i :0.0+0,0 -f alsa -thread_queue_size 14000 -i plug:bsnoop -acodec aac -strict -2 -ar 44100 -b:a 128k -af aresample=async=1 -c:v h264_vaapi -vf format=nv12|vaapi,hwupload -preset medium -maxrate 14000k -bufsize 14000k -pix_fmt yuv420p -r 60 -crf 25 -g 120 -tune zerolatency -f flv rtmp://ingest.bingewave.com/live/[output_to_livestream] -pix_fmt yuv420p -r 60 -b:v 15000k -maxrate 15000k -bufsize 15000k -c:v h264_vaapi -vf format=nv12|vaapi,hwupload -preset medium -keyint_min 24 -level 3.0 -g 120 -tune zerolatency -f flv rtmp://127.0.0.1:1935/live/[output_to_recording]


  


  The reason why my fps and bitrate is so high and preset is so medium is because Glitch is an open source esports platform, and those kinds of settings are required for streaming of game graphics
The command has two outputs :

  


  

  • rtmp ://[output_to_livestream] goes to a livestream where users watch live

  


  • rtmp ://127.0.0.1:1935/live/[output to recording] goes a goes to a file

  


  


  And the output to the recording is captured by nginx and saved to a file as such :

  


  rtmp {
    server {
        listen 1935;
        chunk_size 4096;

        application live {
            live on;
            #Set this to "record off" if you don't want to save a copy of your broadcasts
            record all;
            # The directory in which the recordings will be stored.
            record_path /var/www/html/recordings;
            record_unique on;
            record_suffix -%d-%b-%y-%T.flv;
            on_record_done http://127.0.0.1:3000/recorded;
            # Turn on HLS
            exec /usr/bin/ffmpeg -vaapi_device /dev/dri/renderD128 -i rtmp://127.0.0.1:1935/live/$name -c:v copy -c:a copy -f flv rtmp://127.0.0.1/show/$name;
        }

        application show {
            live on;
            # Turn on HLS
            hls on;
            hls_path /mnt/hls/;
            hls_fragment 3;
            hls_playlist_length 60;
            # disable consuming the stream from nginx as rtmp
            deny play all;
        }
    }
}


  


  So the part that goes to the live is fine, no green flickering at all. But the part that goes to the recording is one that goes the above issue :

  


  -pix_fmt yuv420p -r 60 -b:v 15000k -maxrate 15000k -bufsize 15000k -c:v h264_vaapi -vf format=nv12|vaapi,hwupload -preset medium -keyint_min 24 -level 3.0 -g 120 -tune zerolatency -f flv rtmp://127.0.0.1:1935/live/[output_to_recording]


  


  I
s there something I need to be changing here ?