Recherche avancée

Sur d’autres sites (11322)

• Revision e8b133c79c : Factor inverse transform functions into vpx_dsp This commit moves the module in

  31 juillet 2015, par Jingning Han

  Changed Paths :
   Modify /test/idct8x8_test.cc

  
   Delete /vp9/common/arm/neon/vp9_idct16x16_1_add_neon.c

  
   Delete /vp9/common/arm/neon/vp9_idct16x16_1_add_neon_asm.asm

  
   Delete /vp9/common/arm/neon/vp9_idct16x16_add_neon.c

  
   Delete /vp9/common/arm/neon/vp9_idct16x16_add_neon_asm.asm

  
   Delete /vp9/common/arm/neon/vp9_idct16x16_neon.c

  
   Delete /vp9/common/arm/neon/vp9_idct32x32_1_add_neon.c

  
   Delete /vp9/common/arm/neon/vp9_idct32x32_1_add_neon_asm.asm

  
   Delete /vp9/common/arm/neon/vp9_idct32x32_add_neon.c

  
   Delete /vp9/common/arm/neon/vp9_idct32x32_add_neon_asm.asm

  
   Delete /vp9/common/arm/neon/vp9_idct4x4_1_add_neon.c

  
   Delete /vp9/common/arm/neon/vp9_idct4x4_1_add_neon_asm.asm

  
   Delete /vp9/common/arm/neon/vp9_idct4x4_add_neon.c

  
   Delete /vp9/common/arm/neon/vp9_idct4x4_add_neon_asm.asm

  
   Delete /vp9/common/arm/neon/vp9_idct8x8_1_add_neon.c

  
   Delete /vp9/common/arm/neon/vp9_idct8x8_1_add_neon_asm.asm

  
   Delete /vp9/common/arm/neon/vp9_idct8x8_add_neon.c

  
   Delete /vp9/common/arm/neon/vp9_idct8x8_add_neon_asm.asm

  
   Modify /vp9/common/vp9_idct.c

  
   Modify /vp9/common/vp9_idct.h

  
   Modify /vp9/common/vp9_rtcd_defs.pl

  
   Modify /vp9/common/x86/vp9_idct_intrin_sse2.c

  
   Delete /vp9/common/x86/vp9_idct_intrin_sse2.h

  
   Delete /vp9/common/x86/vp9_idct_sse2.asm

  
   Delete /vp9/common/x86/vp9_idct_ssse3_x86_64.asm

  
   Modify /vp9/encoder/x86/vp9_dct_ssse3.c

  
   Modify /vp9/vp9_common.mk

  
   Add /vpx_dsp/arm/idct16x16_1_add_neon.asm
  (from /vp9/common/arm/neon/vp9_idct16x16_1_add_neon_asm.asm
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
   Add /vpx_dsp/arm/idct16x16_1_add_neon.c
  (from /vp9/common/arm/neon/vp9_idct16x16_1_add_neon.c
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
   Add /vpx_dsp/arm/idct16x16_add_neon.asm
  (from /vp9/common/arm/neon/vp9_idct16x16_add_neon_asm.asm
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
   Add /vpx_dsp/arm/idct16x16_add_neon.c
  (from /vp9/common/arm/neon/vp9_idct16x16_add_neon.c
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
   Add /vpx_dsp/arm/idct16x16_neon.c
  (from /vp9/common/arm/neon/vp9_idct16x16_neon.c
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
   Add /vpx_dsp/arm/idct32x32_1_add_neon.asm
  (from /vp9/common/arm/neon/vp9_idct32x32_1_add_neon_asm.asm
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
   Add /vpx_dsp/arm/idct32x32_1_add_neon.c
  (from /vp9/common/arm/neon/vp9_idct32x32_1_add_neon.c
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
   Add /vpx_dsp/arm/idct32x32_add_neon.asm
  (from /vp9/common/arm/neon/vp9_idct32x32_add_neon_asm.asm
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
   Add /vpx_dsp/arm/idct32x32_add_neon.c
  (from /vp9/common/arm/neon/vp9_idct32x32_add_neon.c
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
   Add /vpx_dsp/arm/idct4x4_1_add_neon.asm
  (from /vp9/common/arm/neon/vp9_idct4x4_1_add_neon_asm.asm
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
   Add /vpx_dsp/arm/idct4x4_1_add_neon.c
  (from /vp9/common/arm/neon/vp9_idct4x4_1_add_neon.c
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
   Add /vpx_dsp/arm/idct4x4_add_neon.asm
  (from /vp9/common/arm/neon/vp9_idct4x4_add_neon_asm.asm
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
   Add /vpx_dsp/arm/idct4x4_add_neon.c
  (from /vp9/common/arm/neon/vp9_idct4x4_add_neon.c
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
   Add /vpx_dsp/arm/idct8x8_1_add_neon.asm
  (from /vp9/common/arm/neon/vp9_idct8x8_1_add_neon_asm.asm
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
   Add /vpx_dsp/arm/idct8x8_1_add_neon.c
  (from /vp9/common/arm/neon/vp9_idct8x8_1_add_neon.c
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
   Add /vpx_dsp/arm/idct8x8_add_neon.asm
  (from /vp9/common/arm/neon/vp9_idct8x8_add_neon_asm.asm
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
   Add /vpx_dsp/arm/idct8x8_add_neon.c
  (from /vp9/common/arm/neon/vp9_idct8x8_add_neon.c
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
   Add /vpx_dsp/inv_txfm.c
  (from /vp9/common/vp9_idct.c
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
   Add /vpx_dsp/inv_txfm.h

  
   Modify /vpx_dsp/vpx_dsp.mk

  
   Modify /vpx_dsp/vpx_dsp_rtcd_defs.pl

  
   Add /vpx_dsp/x86/inv_txfm_sse2.asm
  (from /vp9/common/x86/vp9_idct_sse2.asm
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
   Add /vpx_dsp/x86/inv_txfm_sse2.c
  (from /vp9/common/x86/vp9_idct_intrin_sse2.c
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
   Add /vpx_dsp/x86/inv_txfm_sse2.h
  (from /vp9/common/x86/vp9_idct_intrin_sse2.h
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
   Add /vpx_dsp/x86/inv_txfm_ssse3_x86_64.asm
  (from /vp9/common/x86/vp9_idct_ssse3_x86_64.asm
  :7f8dd35329fcec4f32eba6f56ada69224e30f238)
  
  Factor inverse transform functions into vpx_dsp

  This commit moves the module inverse transform functions from vp9
  to vpx_dsp folder. The hybrid transform wrapper functions stay in
  the vp9 folder, since it involves codec-specific data structures.

  Change-Id : Ib066367c953d3d024c73ba65157bbd70a95c9ef8

• 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

• Raspberry Pi Camera Module - Stream to LAN

  20 août 2015, par user3096434

  have a little problem with the setup of my RasPi camera infrastructure. Basically I have a RPi 2 which shall act as a MontionEye server from now on and 2 Pi B+ with camera modules.

  Previously, when I had only one camera in my network, I used the following command to stream the output from RPi B+ camera module to Youtube in full HD. So far, this command works flawless :

  raspivid -n -vf -hf -t 0 -w 1920 -h 1080 -fps 30 -b 3750000 -g 50 -o - | b ffmpeg -ar 8000 -ac 2 -acodec pcm_s16le -f s16le -ac 2 -i /dev/zero -f h264 -i - -vcodec copy -acodec aac -ab 64k -g 50 -strict experimental -f flv $RTMP_URL/$STREAM_KEY 

  Now I have a 2nd RPi with a camera module and figured it might be the time for a change towards motioneye, as I then can view both/all camera’s in my network within the same software. I have motioneye installed on my RPi 2 and the software is running correctly.

  I have a little problem when it comes to access the data stream from the RPi B+ camera on my local network.

  Basically I cannot seem to figure out how to change the ffmpeg portion of the above mentioned command, in a way so it will stream the data to localhost (Or the RPi2 IP where motioneye runs - which one to use ?) instead of Youtube or any other videohoster.

  I wonder, if changing the following part is a correct assumption :

  Instead of using variables to define Youtube URL and key

  -f flv $RTMP_URL/$STREAM_KEY 

  And change this to

  -f flv 10.1.1.11:8080 

  Will I then be able to add this RPi B+ video stream to my RPi 2 motioneye server, by using motioneye ’add network camera’ function ?

  From my understanding I should be able to enter the following details into motioneye ’add network camera’wizard :

  Camera type: network camera
  
  RTSP-URL: 10.1.1.11:8080
  
  User: Pi
  
  Pass: [my pwd]
  
  Camera: [my ffmpeg stream shall show here]

  Thanks in advance !

  Uhm, and then... How do I forwarded the video stream from a given camera connected to motioneye ? Like from motioneye to youtube (or similar), without re-encoding the stream ?

  Like the command shown above streams directly to youtube. But I want to have it in a way, that video is streamed to local network/motioneye server, and from there I can decide which camera’s stream and when I want to send the videostream to youtube ?

  How would a RPi professional realize this ?

  The command above explained : Takes full HD video with 30 fps from Pi camera module and hardware encodes it on GPU with 3.75mbit/s. Then I streamcopy the video (no re-encoding) and add some audio, so that the stream complies with youtube rules (yes, no live stream without audio). Audio is taken from virtual SB16 /dev/zero at low sampling rate then encoded to 32k AAC and sent to youtube. Works fine xD.

  Just when I have like 3 or more of these RPi cams the youtube stream approach ain’t feasible anymore, as my DSL upstream is limited (10 mbit/s=. Thus I need motioneye server and some magic, so I can watch f.e. all 3 camera’s videostream and then motioneye server can select and streamcopy the video from the Pi’s cam I choose and send it to youtube, as the original command did.

  Any help, tips, links to similar projects highly appreciated.

  Again, many thanks in advance, and even more thanks just cause you read until here.

  —mx