Recherche avancée

Sur d’autres sites (4421)

• Chrome "stalling" when streaming mp3 file from nodejs windows only

  8 octobre 2015, par Alan Hollis

  We’ve got a really annoying bug when trying to send mp3 data. We’ve got the following set up.

  Web cam producing aac -> ffmpeg convert to adts -> send to nodejs server -> ffmpeg on server converts adts to mp3 -> mp3 then streamed to browser.

  This works *perfectly" on Linux ( chrome with HTML5 and flash, firefox flash only )

  However on windows the sound just "stalls", no matter what combination we use ( browser/html5/flash ). If however we shutdown the server the sound then immediately starts to play as we expect.

  For some reason on windows based machines it’s as if the sound is being buffered "waiting" for something but we don’t know what that is.

  Any help would be greatly appreciated.

  Relevant code in node

      res.setHeader('Connection', 'Transfer-Encoding');
  
      res.setHeader('Content-Type', 'audio/mpeg');
  
      res.setHeader('Transfer-Encoding', 'chunked');
  
      res.writeHeader('206');
  
  
  
      that.eventEmitter.on('soundData', function (data) {
  
          debug("Got sound data" + data.cameraId + " " + req.params.camera_id);
  
          if (req.params.camera_id == data.cameraId) {
  
              debug("Sending data direct to browser");
  
              res.write(data.sound);
  
          }
  
      });

  Code on browser

         soundManager.setup({
  
                              url: 'http://dashboard.agricamera.co.uk/themes/agricamv2/swf/soundmanager2.swf',
  
                              useHTML5Audio: false,
  
                              onready: function () {
  
                                  that.log("Sound manager is now ready")
  
                                  var mySound = soundManager.createSound({
  
                                      url: src,
  
                                      autoLoad: true,
  
                                      autoPlay: true,
  
                                      stream: true,
  
                                  });
  
                              }
  
                          });

• A *hot* Piwik Community Meetup 2015 !

  10 août 2015, par André Bräkling — Community

  Last weekend I arrived in Germany to attend the Piwik Community Meetup 2015 and now I am in Poland.

  The meetup was HOT in every sense ! Berlin temperatures reached 35 degrees (celsius), as I finally meet in person several long-time, dedicated Piwik community contributors.

  

  Meetup preparation in Berlin, photo by M. Zawadziński, licensed under CC-BY-SA 4.0

  Pictures from the meetup preparation sessions
  

  In the first leg of my trip I was in Berlin to meet Piwik community members to prepare for the 2015 annual Piwik community meetup. These are my notes taken during the meeting at the request of one of my colleagues. I also relayed live on Framasphère, Twitter and IRC.

  

  Community discussion at the meetup, photo by D.Czajka, licensed under CC-BY-SA 4.0

  More pictures from the Piwik meetup
  

  This was harder than I expected, as I took notes with my laptop, pictures with my phone, wrote live to social media (using the Android Diaspora Native Web App), and used my laptop to relay on IRC. Going forward this requires better preparation, I was glad I had a few links and pictures ready before hand but it really requires intense focus to achieve this. I am glad presenters were patient when I requested repeating some of the ideas they shared. I am also a bit disappointed not much happened in IRC.

  Two day preparation sessions

  The discussions and session we had during the two days prior to the meetup are available here.

  We gathered in rented apartments in Berlin, this reminded me very much of similar community gatherings and perhaps of BarCamp and, at a much smaller scale, UDS sessions.

  

  Piwik Pizza !, photo by F. Rodríguez, licensed under CC-BY-SA 4.0

  A list of ideas of topics was initially submitted, we then proceeded to have scheduled sessions for open discussion. Several people shared their concern there was no possible remote participation which led to making public the Trello boards used/linked here.

  Note : The Trello links below still have action items and notes that are pending bug report / feature requests filing which should happen over the coming weeks. Most importantly, many action items will need identifying leads for different community team including Translations and Documentation, and better coordination of coming community engagement.

  Monday sessions consisted of the following subjects :

  • What are Piwik values & how to communicate them ? (see below for details)
  • How to encourage and recognize new external contributors ?
  • How could we double the Piwik userbase ?
  • How Community can organise help resources

  On Tuesday we met again to discuss the following subjects :

  • Piwik Long Term support (LTS)
  • How do Piwik.org (project) and Piwik PRO (company) sit together / are organized ? – An important part of this session was about having better communication channels and improving the new team page (bug #8520 and bug #8519, respectively)
  • Improving usability of Piwik e.g. for new users – this last session was not held has we ran out of time and prepared to go to the meetup venue.

  Some more details about individual preparation sessions

  What are Piwik values & how to communicate them ?

  The main subjects in this session were important changes proposed in the project mission and values. This was edited directly on on the wiki page on GitHub, some of the changes can be seen by comparing revisions.

  Piwik mission statement (bug #7376)

  “To create the leading Free and open source analytics platform, and to support global organisations and communities to keep full control over their data.”

  Our values

  • Openness
  • Freedom
  • Transparency
  • Data ownership
  • Privacy
  • Kaizen (改善) : continuous improvement

  This was also presented by Matthieu Aubry at the meetup and is published in the Roadmap page. Bringing more visibility and perhaps having a top page for Mission and Values was also brought up.

  Meetup agenda and notes

  The official agenda is available here.

  Many Piwik PRO employees stayed in Berlin for the meetup, and we had good participation although less than last year in Munich as my colleagues told me. Some were consultants, others staff from public organizations, universities, etc. In retrospect considering the very hot weather and summer holidays the attendance was good. I was very happy to arrive at the beautiful Kulturbrauerei and enter the air-conditioned Soda Club. T-Shirts were waiting for all attendees and free drinks (non-alcohol !) were welcome

• Python ImageIO : Too many open files

  23 avril 2016, par orbv12

  I am using imageio in python in order to open all video files in a directory and convert them to numpy arrays.

  Here is the script I am using :

    1 from __future__ import print_function
  
    2 from avi_to_numpy import *
  
    3 from os import listdir
  
    4 import numpy as np
  
    5 import imageio 
  
    6       
  
    7 class_path = '../Diving/'
  
    8 max_frames = 16
  
    9 stride = 8
  
   10 videos = [vid for vid in listdir(class_path)]
  
   11 train = []
  
   12 
  
   13 for vid in videos:
  
   14     print(str.format('Loading {}...', vid), end="")
  
   15     filename = class_path + vid
  
   16     reader = imageio.get_reader(filename, 'ffmpeg')
  
   17     frames = []
  
   18     
  
   19     for i, im in enumerate(reader):
  
   20         if len(frames) == max_frames:
  
   21             break
  
   22         
  
   23         if i % stride == 0:
  
   24             frames.append(im)
  
   25     
  
   26     reader.close()
  
   27     train.append(np.array(frames))
  
   28     print('done')        
  
   29 
  
   30 
  
   31 print(len(train))

  Eventually this script crashes with the following error output :

  Traceback (most recent call last):
  
    File "load_class_test.py", line 16, in <module>
  
      reader = imageio.get_reader(filename, 'ffmpeg')
  
    File "/usr/local/lib/python2.7/site-packages/imageio/core/functions.py", line 111, in get_reader
  
      return format.get_reader(request)
  
    File "/usr/local/lib/python2.7/site-packages/imageio/core/format.py", line 158, in get_reader
  
      return self.Reader(self, request)
  
    File "/usr/local/lib/python2.7/site-packages/imageio/core/format.py", line 207, in __init__
  
      self._open(**self.request.kwargs.copy())
  
    File "/usr/local/lib/python2.7/site-packages/imageio/plugins/ffmpeg.py", line 260, in _open
  
      self._initialize()
  
    File "/usr/local/lib/python2.7/site-packages/imageio/plugins/ffmpeg.py", line 326, in _initialize
  
      stdout=sp.PIPE, stderr=sp.PIPE)
  
    File "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 710, in __init__
  
      errread, errwrite)
  
    File "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 1223, in _execute_child
  
      errpipe_read, errpipe_write = self.pipe_cloexec()
  
    File "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 1175, in pipe_cloexec
  
      r, w = os.pipe()
  
  OSError: [Errno 24] Too many open files
  
  </module>

  I am closing the Reader object from imageio. It seems as if the files opened by ffmpeg are not being closed properly.

  Is there an obvious step I am missing here ? Am I closing the files properly ?

  EDIT : Found temporary solution. Opened a new issue on github.

  I was able to resolve the issue by uncommenting the following lines of code from ’imageio/plugins/ffmpeg.py’ :

  381         def _close_streams(self):
  
  382             for std in (self._proc.stdin,
  
  383                         self._proc.stdout,
  
  384                         self._proc.stderr):
  
  385                 try:
  
  386                     std.close()
  
  387                 except Exception:  # pragma: no cover
  
  388                     pass

  I then added a call to the above function in _close(self) :

  271         def _close(self):
  
  272             self._terminate(0.05)  # Short timeout
  
  273             self._close_streams()
  
  274             self._proc = None

  I am not sure what the side effects of doing this are, but it provides a solution for me.

  Here is the link to the issue : https://github.com/imageio/imageio/issues/145