Recherche avancée

Sur d’autres sites (10597)

• Improve LPC order guess

  3 décembre 2014, par Martijn van Beurden

  Improve LPC order guess
  The recent compression preset retuning improved upon most material
  
  but it the few tracks that show regression are usually classical
  
  music. This patch improves compression by improving the LPC order
  
  guess, of which classical music benefits most.
  Improvement is 0.007% on average but up to 0.1%. I haven’t seen
  
  regressions for any of my test samples.
  Signed-off-by : Erik de Castro Lopo <erikd@mega-nerd.com>
  

  • [DH] src/libFLAC/lpc.c

• Revision 8fd3f9a2fb : Enable non-rd mode coding on key frame, for speed 6. For key frame at speed 6 :

  12 novembre 2014, par Marco

  Changed Paths :
   Modify /test/vp9_avg_test.cc

  
   Modify /vp9/common/vp9_rtcd_defs.pl

  
   Modify /vp9/encoder/vp9_avg.c

  
   Modify /vp9/encoder/vp9_encodeframe.c

  
   Modify /vp9/encoder/vp9_speed_features.c

  
   Modify /vp9/encoder/x86/vp9_avg_intrin_sse2.c

  
  
  Enable non-rd mode coding on key frame, for speed 6.

  For key frame at speed 6 : enable the non-rd mode selection in speed setting
  and use the (non-rd) variance_based partition.

  Adjust some logic/thresholds in variance partition selection for key frame only
  (no change to delta frames),
  mainly to bias to selecting smaller prediction blocks, and also set max tx size
  of 16x16.

  Loss in key frame quality ( 0.6-0.7dB) compared to rd coding,
  but speeds up key frame encoding by at least 6x.
  Average PNSR/SSIM metrics over RTC clips go down by 1-2% for speed 6.

  Change-Id : Ie4845e0127e876337b9c105aa37e93b286193405

• Use deck.js as a remote presentation tool

  8 janvier 2014, par silvia

  deck.js is one of the new HTML5-based presentation tools. It’s simple to use, in particular for your basic, every-day presentation needs. You can also create more complex slides with animations etc. if you know your HTML and CSS.

  Yesterday at linux.conf.au (LCA), I gave a presentation using deck.js. But I didn’t give it from the lectern in the room in Perth where LCA is being held – instead I gave it from the comfort of my home office at the other end of the country.

  I used my laptop with in-built webcam and my Chrome browser to give this presentation. Beforehand, I had uploaded the presentation to a Web server and shared the link with the organiser of my speaker track, who was on site in Perth and had set up his laptop in the same fashion as myself. His screen was projecting the Chrome tab in which my slides were loaded and he had hooked up the audio output of his laptop to the room speaker system. His camera was pointed at the audience so I could see their reaction.

  I loaded a slide master URL :
  http://html5videoguide.net/presentations/lca_2014_webrtc/?master
  and the room loaded the URL without query string :
  http://html5videoguide.net/presentations/lca_2014_webrtc/.

  Then I gave my talk exactly as I would if I was in the same room. Yes, it felt exactly as though I was there, including nervousness and audience feedback.

  How did we do that ? WebRTC (Web Real-time Communication) to the rescue, of course !

  We used one of the modules of the rtc.io project called rtc-glue to add the video conferencing functionality and the slide navigation to deck.js. It was actually really really simple !

  Here are the few things we added to deck.js to make it work :

  • Code added to index.html to make the video connection work :

    <meta name="rtc-signalhost" content="http://rtc.io/switchboard/">
    
    <meta name="rtc-room" content="lca2014">
    
    ...
    
    <video id="localV" rtc-capture="camera" muted></video>
    
    <video id="peerV" rtc-peer rtc-stream="localV"></video>
    
    ...
    
    <script src="glue.js"></script>
    
    <script>
    
    glue.config.iceServers = [{ url: 'stun:stun.l.google.com:19302' }];
    
    </script>

    The iceServers config is required to punch through firewalls – you may also need a TURN server. Note that you need a signalling server – in our case we used http://rtc.io/switchboard/, which runs the code from rtc-switchboard.

  • Added glue.js library to deck.js :

    Downloaded from https://raw.github.com/rtc-io/rtc-glue/master/dist/glue.js into the source directory of deck.js.

  • Code added to index.html to synchronize slide navigation :

    glue.events.once('connected', function(signaller) {
    
      if (location.search.slice(1) !== '') {
    
        $(document).bind('deck.change', function(evt, from, to) {
    
          signaller.send('/slide', {
    
            idx: to,
    
            sender: signaller.id
    
          });
    
        });
    
      }
    
      signaller.on('slide', function(data) {
    
        console.log('received notification to change to slide: ', data.idx);
    
        $.deck('go', data.idx);
    
      });
    
    });

    This simply registers a callback on the slide master end to send a slide position message to the room end, and a callback on the room end that initiates the slide navigation.

  And that’s it !

  You can find my slide deck on GitHub.

  Feel free to write your own slides in this manner – I would love to have more users of this approach. It should also be fairly simple to extend this to share pointer positions, so you can actually use the mouse pointer to point to things on your slides remotely. Would love to hear your experiences !

  Note that the slides are actually a talk about the rtc.io project, so if you want to find out more about these modules and what other things you can do, read the slide deck or watch the talk when it has been published by LCA.

  Many thanks to Damon Oehlman for his help in getting this working.

  BTW : somebody should really fix that print style sheet for deck.js – I’m only ever getting the one slide that is currently showing.