Recherche avancée

Sur d’autres sites (6129)

• Senior Software Engineer for Enterprise Analytics Platform

  28 janvier 2016, par Matthieu Aubry — Jobs

  We’re looking for a lead developer to work on Piwik Analytics core platform software. We have some exciting challenges to solve and need you !

  You’ll be working with both fellow employees and our open-source community. Piwik PRO staff lives in New Zealand, Europe (Poland, Germany) and in the U.S. We do the vast majority of our collaboration online.

  We are a small, flexible team, so when you come aboard, you will play an integral part in engineering. As a leader you’ll help us to prioritise work and grow our community. You’ll help to create a welcoming environment for new contributors and set an example with your development practices and communications skills. You will be working closely with our CTO to build a future for Piwik.

  Key Responsibilities

  • Strong competency coding in PHP and JavaScript.
  • Scaling existing backend system to handle ever increasing amounts of traffic and new product requirements.
  • Outstanding communication and collaboration skills.
  • Drive development and documentation of internal and external APIs (Piwik is an open platform).
  • Help make our development practices better and reduce friction from idea to deployment.
  • Mentor junior engineers and set the stage for personal growth.

  Minimum qualifications

  • 5+ years of experience in product development, security, usable interface design.
  • 5+ years experience building successful production software systems.
  • Strong competency in PHP5 and JavaScript application development.
  • Skill at writing tests and reviewing code.
  • Strong analytical skills.

  Location

  • Remote work position !
  • or you can join us in our office based in Wellington, New Zealand or in Wrocław, Poland.

  Benefits

  • Competitive salary.
  • Equity in Piwik PRO.
  • Remote work is possible.
  • Yearly meetup with the whole team abroad.
  • Be part of a successful open source company and community.
  • In our Wellington (NZ) and Wroclaw (PL) offices : snacks, coffee, nap room, Table football, Ping pong…
  • Regular events.
  • Great team of people.
  • Exciting projects.

  Learn more

  Learn more what it’s like to work on Piwik in our blog post

  About Piwik

  At Piwik and Piwik PRO we develop the leading open source web analytics platform, used by more than one million websites worldwide. Our vision is to help the world liberate their analytics data by building the best open alternative to Google Analytics.

  The Piwik platform collects, stores and processes a lot of information : hundreds of millions of data points each month. We create intuitive, simple and beautiful reports that delight our users.

  About Piwik PRO company

  At Piwik PRO we’re solving hard problems with simple solutions that make our users and customers happy. We practise agile methodology, test driven development and fast release cycles. Our backend is mostly built in modern PHP with a bit of Python. We use MySQL/MariaDB and Redis as data stores. Our frontends is built in JavaScript using AngularJS and jQuery. Our tools include Github, Travis CI, PhpStorm and Slack.

  As a Lead Software Developer for Piwik PRO, you will be writing open source code that will run on more than 200,000 servers and be used in 200+ countries and 50 languages !

  Apply online

  To apply for this position, please Apply online here. We look forward to receiving your applications !

• Ffmpeg send duration of video to client (using node-fluent-ffmpeg)

  26 mai 2013, par Vprnl

  I'm really new to the world of ffmpeg so please excuses me if this is a stupid queston.

  I'm using the module Node-fluent-ffmpeg to stream a movie and convert it from avi to webm with FFMPEG.

  So far so good (it plays the video), but I'm having trouble parsing the duration to the player. It also gives me an error even though I plays the video.

  my code is as followed :

  var stat = fs.statSync(movie);
  
  
  
  var start = 0;
  
  var end = 0;
  
  var range = req.header('Range');
  
  if (range != null) {
  
  start = parseInt(range.slice(range.indexOf('bytes=')+6,
  
    range.indexOf('-')));
  
  end = parseInt(range.slice(range.indexOf('-')+1,
  
    range.length));
  
  }
  
  if (isNaN(end) || end == 0) end = stat.size-1;
  
  if (start > end) return;
  
  
  
  var duration = (end / 1024) * 8 / 1024;
  
  
  
  res.writeHead(206, { // NOTE: a partial http response
  
      'Connection':'close',
  
      'Content-Type':'video/webm',
  
      'Content-Length':end - start,
  
      'Content-Range':'bytes '+start+'-'+end+'/'+stat.size,
  
      'Transfer-Encoding':'chunked'
  
  });
  
  
  
  var proc = new ffmpeg({ source: movie, nolog: true, priority: 1, timeout:15000})
  
      .toFormat('webm')
  
      .addOptions(['-probesize 900000', '-analyzeduration 0', '-minrate 1024k', '-maxrate 1024k', '-bufsize 1835k', '-t '+duration+' -ss'])
  
      .writeToStream(res, function(retcode, error){
  
      if (!error){
  
          console.log('file has been converted succesfully',retcode);
  
      }else{
  
          console.log('file conversion error',error);
  
      }
  
  });

  I set the header with a start and a end based on this article : http://delog.wordpress.com/2011/04/25/stream-webm-file-to-chrome-using-node-js/

  I calculate the length in seconds in the variable duration.

  The error FFmpeg is giving me is :

      file conversion error ffmpeg version N-52458-gaa96439 Copyright (c) 2000-2013 the FFmpeg developers
  
        built on Apr 24 2013 22:19:32 with gcc 4.8.0 (GCC)
  
        configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --e
  
      nable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libcaca --enable-libfreetype --enable
  
      -libgsm --enable-libilbc --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --ena
  
      ble-libopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwola
  
      me --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxavs --enabl
  
      e-libxvid --enable-zlib
  
        libavutil      52. 27.101 / 52. 27.101
  
        libavcodec     55.  6.100 / 55.  6.100
  
        libavformat    55.  3.100 / 55.  3.100
  
        libavdevice    55.  0.100 / 55.  0.100
  
        libavfilter     3. 60.101 /  3. 60.101
  
        libswscale      2.  2.100 /  2.  2.100
  
        libswresample   0. 17.102 /  0. 17.102
  
        libpostproc    52.  3.100 / 52.  3.100
  
      Input #0, avi, from 'C:/temp/test.avi':
  
        Metadata:
  
          encoder         : Nandub v1.0rc2
  
        Duration: 00:01:09.78, start: 0.000000, bitrate: 1517 kb/s
  
          Stream #0:0: Video: msmpeg4v3 (DIV3 / 0x33564944), yuv420p, 640x352, 23.98 tbr, 23.98 tbn, 23.98 tbc
  
          Stream #0:1: Audio: mp3 (U[0][0][0] / 0x0055), 48000 Hz, stereo, s16p, 222 kb/s
  
      [libvpx @ 0036db20] v1.2.0
  
      Output #0, webm, to 'pipe:1':
  
        Metadata:
  
          encoder         : Lavf55.3.100
  
          Stream #0:0: Video: vp8, yuv420p, 640x352, q=-1--1, 200 kb/s, 1k tbn, 23.98 tbc
  
          Stream #0:1: Audio: vorbis, 48000 Hz, stereo, fltp
  
      Stream mapping:
  
        Stream #0:0 -> #0:0 (msmpeg4 -> libvpx)
  
        Stream #0:1 -> #0:1 (mp3 -> libvorbis)

  The client side player (which is VideoJs) says the file is infinite/NaN in length.

  I feel like I'm pretty close to a solution but my inexperience with the subject matter prohibits me from getting it to work. If I'm unclear in any way please let me know. (I have a tendency of explaining things fuzzy.)

  Thanks in advance !

  [EDIT]

  I removed the duration bit because it has nothing to do with the issue. I checked the response header of the client and saw :

   Accept-Ranges:bytes
  
   Connection:keep-alive
  
   Content-Length:13232127
  
   Content-Range:bytes 0-13232127/13232128
  
   Content-Type:video/webm

  Why can't the client figure out the duration even though it receives it in the header ?

• Using Unicast RTSP URIs via ffmpeg

  6 août 2019, par Chris Marshall

  I’m fairly new to ffmpeg, so I’d certainly appreciate being given an "M" to "RTFM." The ffmpeg docs are...not-so-easy...to navigate, but I’m trying.

  The goal is to develop a compiled server that incorporates ffmpeg, but first, I need to get it working via CLI.

  I have a standard AXIS Surveillance camera (AXIS M5525-E), set up as an ONVIF device (but that isn’t really relevant to this issue).

  When I query it, I get the following URI as its video streaming URI :

  rtsp://192.168.4.12/onvif-media/media.amp?profile=profile_1_jpeg&streamtype=unicast

  The IP is local to a sandboxed network.

  I add the authentication parameters to it, like so :

  rtsp://<login>:<password>@192.168.4.12/onvif-media/media.amp?profile=profile_1_jpeg&amp;streamtype=unicast
  
  </password></login>

  (Yeah, I know that’s not secure, but this is just for testing and feasibility study. The whole damn sandbox is an insecure mess).

  Now, if I use VLC to open the URI, it works great (of course). Looking at it with a packet analyzer, I see the following negotiation between the device and my computer (at .2 - Clipped for brevity) :

  Id = 11
  
  Source = 192.168.4.12
  
  Destination = 192.168.4.2
  
  Captured Length = 82
  
  Packet Length = 82
  
  Protocol = TCP
  
  Date Received = 2019-08-06 12:18:37 +0000
  
  Time Delta = 1.342024087905884
  
  Information = 554 -> 53755 ([ECN, ACK, SYN], Seq=696764098, Ack=3139240483, Win=28960)
  
                      °
  
                      °
  
                      °
  
  Id = 48
  
  Source = 192.168.4.12
  
  Destination = 192.168.4.2
  
  Captured Length = 366
  
  Packet Length = 366
  
  Protocol = TCP
  
  Date Received = 2019-08-06 12:18:38 +0000
  
  Time Delta = 2.09382700920105
  
  Information = 554 -> 53755 ([ACK, PUSH], Seq=696765606, Ack=3139242268, Win=1073)

  Followed immediately by UDP stream packets.

  If, however, I feed the same URI to ffmpeg :

  ffmpeg -i rtsp://<login>:<password>@192.168.4.12/onvif-media/media.amp?profile=profile_1_jpeg&amp;streamtype=unicast -c:v libx264 -crf 21 -preset veryfast -g 30 -sc_threshold 0 -f hls -hls_time 4 /Volumes/Development/webroot/fftest/stream.m3u8
  
  </password></login>

  I get nothing. No negotiation at all between the device and my computer.

  After that, if I then remove the &streamtype=unicast argument, I get a negotiation, and a stream :

  Id = 10
  
  Source = 192.168.4.12
  
  Destination = 192.168.4.2
  
  Captured Length = 82
  
  Packet Length = 82
  
  Protocol = TCP
  
  Date Received = 2019-08-06 10:37:48 +0000
  
  Time Delta = 3.047425985336304
  
  Information = 554 -> 49606 ([ECN, ACK, SYN], Seq=457514925, Ack=2138974173, Win=28960)
  
                      °
  
                      °
  
                      °
  
  Id = 31
  
  Source = 192.168.4.12
  
  Destination = 192.168.4.2
  
  Captured Length = 345
  
  Packet Length = 345
  
  Protocol = TCP
  
  Date Received = 2019-08-06 10:37:49 +0000
  
  Time Delta = 3.840152025222778
  
  Information = 554 -> 49606 ([ACK, PUSH], Seq=457516393, Ack=2138975704, Win=1039)

  I will, of course, be continuing to work out why this is [not] happening, and will post any solutions that I find, but, like I said, I’m fairly new to this, so it’s entirely possible that I’m missing some basic stuff, and would appreciate any guidance.

  Thanks !