Recherche avancée

Sur d’autres sites (9632)

• How to get your Piwik plugin translated in many languages ?

  8 septembre 2015, par Stefan Giehl — Community, Development, Plugins

  About a year ago we introduced the Piwik Marketplace to make it easy for developers to share their plugins with all Piwik users.

  As Piwik is currently available in 54 languages we would love to have as many plugins as possible available in at least a few of those languages.

  Currently most plugins on the Marketplace are only available in English and sometimes some other languages. To improve this situation, we offer plugin developers the possibility to use the power of our translators community to get their plugins translated.

  Some plugin developers are already using this service and some very popular plugins like BotTracker or CustomOptOut have already been translated in more than 10 languages !

  Getting translations for your plugin

  As long as you are developing an open source plugin hosted on Github, you may get in touch with us (translations@piwik.org) in order to get your plugin translated by the Piwik translators community.

  You will need an account on Transifex.com. If you use Transifex with a social login, please ensure to set a password in your account settings. This will be required for fetching new translations into your plugin repository.

  Importing your plugin’s strings in the translation platform

  While doing the initial setup for your plugin, we will import your english translation file (en.json) in your Github plugin repository and we will configure an auto-update for this file. Source strings on Transifex will automatically synchronise with your plugin repository. When you change any string in your en.json translation file, the updated English strings will automatically be imported in Transifex.

  How to fetch your plugins translations into your repository

  As soon as we have set up your plugin within our project Piwik on Transifex and there are new translations available, you will be able to update your plugin translations using the Piwik console. You will need a locally installed Piwik with development mode enabled, and your plugin installed. To update the translations go to the Piwik directory on your development box and execute the following command :

  ./console translations:update -u {YourTransifexUserName} -p {YourTransifexPassword} -P {YourPluginName}

  We are looking forward to seeing your Piwik plugins available in more languages ! For more information, check out our Translations plugin developer guide.

  Happy hacking,

• FFMPEG Video from images to mp4 in nvidia GPU

  16 août 2019, par M.y

  I am trying to encode a h264 .mp4 video created from .jpg images using a 1070ti nvidia cuda power, having a a crossfade transition between each image.
  I am able to render the video in GPU using the flags -c:v h264_nvenc, I see a short peak in the GPU encoding, but with a long period of computer CPU hight load, I guess preparing the transitioning images. But the image preparation it happens on cpu/ram due the -filter_complex and is quite slow.
  This works :

  ffmpeg.exe, -y, 
  
  -loop, 1, -t, 2.5, -i, 1565957420594_labeled.jpg, 
  
  -loop, 1, -t, 2.5, -i, 1565957453659_labeled.jpg, 
  
  -loop, 1, -t, 2.5, -i, 1565957487743_labeled.jpg, 
  
  -loop, 1, -t, 2.5, -i, 1565957525280_labeled.jpg, 
  
  -loop, 1, -t, 2.5, -i, 1565957587308_labeled.jpg, 
  
  -loop, 1, -t, 2.5, -i, 1565957644898_labeled.jpg, 
  
  -loop, 1, -t, 2.5, -i, 1565957859119_labeled.jpg, 
  
  -loop, 1, -t, 2.5, -i,1565959133561_labeled.jpg, 
  
  -loop, 1, -t, 2.5, -i, 1565959412948_labeled.jpg, 
  
  -loop, 1, -t, 2.5, -i, 1565959501884_labeled.jpg, 
  
  -loop, 1, -t, 2.5, -i, 1565959755432_labeled.jpg, 
  
  -loop, 1, -t, 2.5, -i, 1565959882380_labeled.jpg, 
  
  -loop, 1, -t, 2.5, -i, 1565960023185_labeled.jpg, 
  
  -loop, 1, -t, 2.5, -i, 1565960157174_labeled.jpg, 
  
  -loop, 1, -t, 2.5, -i, 1565960683303_labeled.jpg, 
  
  -loop, 1, -t, 2.5, -i, 1565961151548_labeled.jpg, 
  
  -loop, 1, -t, 2.5, -i, 1565961230278_labeled.jpg, 
  
  -loop, 1, -t, 2.5, -i, 1565961671766_labeled.jpg, 
  
  -loop, 1, -t, 2.5, -i, final.jpg, 
  
  -loop, 1, -t, 2.5, -i, final.jpg, 
  
  -c:v, h264_nvenc, -preset, fast, 
  
  -filter_complex, [1]fade=d=0.5:t=in:alpha=1,setpts=PTS-STARTPTS+0.5/TB[f0];
  
  [2]fade=d=0.5:t=in:alpha=1,setpts=PTS-STARTPTS+1.0/TB[f1];
  
  [3]fade=d=0.5:t=in:alpha=1,setpts=PTS-STARTPTS+1.5/TB[f2];
  
  [4]fade=d=0.5:t=in:alpha=1,setpts=PTS-STARTPTS+2.0/TB[f3];
  
  [5]fade=d=0.5:t=in:alpha=1,setpts=PTS-STARTPTS+2.5/TB[f4];
  
  [6]fade=d=0.5:t=in:alpha=1,setpts=PTS-STARTPTS+3.0/TB[f5];
  
  [7]fade=d=0.5:t=in:alpha=1,setpts=PTS-STARTPTS+3.5/TB[f6];
  
  [8]fade=d=0.5:t=in:alpha=1,setpts=PTS-STARTPTS+4.0/TB[f7];
  
  [9]fade=d=0.5:t=in:alpha=1,setpts=PTS-STARTPTS+4.5/TB[f8];
  
  [10]fade=d=0.5:t=in:alpha=1,setpts=PTS-STARTPTS+5.0/TB[f9];
  
  [11]fade=d=0.5:t=in:alpha=1,setpts=PTS-STARTPTS+5.5/TB[f10];
  
  [12]fade=d=0.5:t=in:alpha=1,setpts=PTS-STARTPTS+6.0/TB[f11];
  
  [13]fade=d=0.5:t=in:alpha=1,setpts=PTS-STARTPTS+6.5/TB[f12];
  
  [14]fade=d=0.5:t=in:alpha=1,setpts=PTS-STARTPTS+7.0/TB[f13];
  
  [15]fade=d=0.5:t=in:alpha=1,setpts=PTS-STARTPTS+7.5/TB[f14];
  
  [16]fade=d=0.5:t=in:alpha=1,setpts=PTS-STARTPTS+8.0/TB[f15];
  
  [17]fade=d=0.5:t=in:alpha=1,setpts=PTS-STARTPTS+8.5/TB[f16];
  
  [18]fade=d=0.5:t=in:alpha=1,setpts=PTS-STARTPTS+9.0/TB[f17];
  
  [19]fade=d=0.5:t=in:alpha=1,setpts=PTS-STARTPTS+9.5/TB[f18];
  
  [0][f0]overlay[bg1];
  
  [bg1][f1]overlay[bg2];
  
  [bg2][f2]overlay[bg3];
  
  [bg3][f3]overlay[bg4];
  
  [bg4][f4]overlay[bg5];
  
  [bg5][f5]overlay[bg6];
  
  [bg6][f6]overlay[bg7];
  
  [bg7][f7]overlay[bg8];
  
  [bg8][f8]overlay[bg9];
  
  [bg9][f9]overlay[bg10];
  
  [bg10][f10]overlay[bg11];
  
  [bg11][f11]overlay[bg12];
  
  [bg12][f12]overlay[bg13];
  
  [bg13][f13]overlay[bg14];
  
  [bg14][f14]overlay[bg15];
  
  [bg15][f15]overlay[bg16];
  
  [bg16][f16]overlay[bg17];
  
  [bg17][f17]overlay[bg18];
  
  [bg18][f18]overlay[v], 
  
  -map, [v], -movflags, +faststart, output.mp4

  I am trying to do all work in the GPU, theoretically I can encode all images in GPU memory using in each -i the flags "-hwaccel cuvid -c:v mjpeg_cuvid" I receive the following error :

  [mjpeg_cuvid @ 00000000024ef980] ignoring invalid SAR: 0/0
  
  Impossible to convert between the formats supported by the filter 'graph 0 input from stream 1:0' and the filter 'auto_scaler_0'
  
  Error reinitializing filters!
  
  Failed to inject frame into filter network: Function not implemented
  
  Error while processing the decoded data for stream #0:0

  Is there a way to load images in the GPU with the "fade" flag applied ?

  Thanks in advance !

• Nginx RTMP Pull to HLS Streaming

  5 avril 2023, par Nathaniel Anderson

  I've followed this guide on setting up RTMP to HLS streaming - https://web.archive.org/web/20221205201139/https://docs.peer5.com/guides/setting-up-hls-live-streaming-server-using-nginx/

  


  RTMP streaming works just fine but for some reason I can't get HLS to link with the already existing RTMP server. I'm using OBS to stream to RTMP and it's set to be on x264 and as far as I know the default codec for audio is AAC so I'm not sure why it's not picking it up.

  


  Current Nginx.conf

  


  worker_processes  auto;
events {
    worker_connections  1024;
}

# RTMP configuration
rtmp {
    server {
        listen 1935; # Listen on standard RTMP port
        chunk_size 4000;

# Define the Application
        application show {
            live on;
            pull rtmp://localhost:1935/stream/test;
            # 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;
        }

        # RTMP video on demand for mp4 files
        application vod {
            play /mnt/mp4s;
        }

        # RTMP stream using OBS
        application stream {
            live on;
        }

    }
}

http {
    sendfile off;
    tcp_nopush on;
    aio on;
    directio 512;
    default_type application/octet-stream;

    server {
        listen 8080;

        location / {
            # Disable cache
            add_header 'Cache-Control' 'no-cache';

            # CORS setup
            add_header 'Access-Control-Allow-Origin' '*' always;
            add_header 'Access-Control-Expose-Headers' 'Content-Length';

            # allow CORS preflight requests
            if ($request_method = 'OPTIONS') {
                add_header 'Access-Control-Allow-Origin' '*';
                add_header 'Access-Control-Max-Age' 1728000;
                add_header 'Content-Type' 'text/plain charset=UTF-8';
                add_header 'Content-Length' 0;
                return 204;
            }

            types {
                application/dash+xml mpd;
                application/vnd.apple.mpegurl m3u8;
                video/mp2t ts;
            }

            root /mnt/;
        }
    }
}


  


  I've tried changing the rtmp link I have in that config too to both internal and external IP's since it can be reached. I tested watching the rtmp from another computer on the network to confirm it was functional. I wanted to avoid transcoding with ffmpeg since the server doesn't have that kind of power.