1. 15 Feb, 2017 1 commit
  2. 22 Sep, 2016 1 commit
  3. 22 Jun, 2016 1 commit
    • Wim Taymans's avatar
      video-converter: fix interlaced scaling some more · 5e752f4e
      Wim Taymans authored
      Fix problem with the line cache where it would forget the first line in
      the cache in some cases.
      Keep as much backlog as we have taps. This generally works better and we
      could do even better by calculating the overlap in all taps.
      Allocated enough lines for the line cache.
      Use only half the number of taps for the interlaced lines because we
      only have half the number of lines.
      The pixel shift should be relative to the new output pixel size so scale
      it.
      Fixes: https://bugzilla.gnome.org/show_bug.cgi?id=767921
      5e752f4e
  4. 01 Jun, 2016 1 commit
  5. 15 Jul, 2015 1 commit
    • Wim Taymans's avatar
      video: improve logging · 14083178
      Wim Taymans authored
      Add logging categories for most video objects.
      Remove some useless debug lines in video-info and videotestsrc.
      Add a performance debug line in the video scaler.
      14083178
  6. 07 Jul, 2015 1 commit
    • Tobias Mueller's avatar
      GstVideoScaler: Initialised scaling functions to get rid of compiler messages · 190c7f19
      Tobias Mueller authored
      E.g.
      
      video-scaler.c: In function 'gst_video_scaler_horizontal':
      video-scaler.c:1332:3: error: 'func' may be used uninitialized in this function [-Werror=maybe-uninitialized]
         func (scale, src, dest, dest_offset, width, n_elems);
         ^
      
      video-scaler.c: In function 'gst_video_scaler_vertical':
      video-scaler.c:1373:3: error: 'func' may be used uninitialized in this function [-Werror=maybe-uninitialized]
         func (scale, src_lines, dest, dest_offset, width, n_elems);
         ^
      
      GCC's analyses seem to be correct, for the simple fact that if you pass
      get_functions a known format, but no hscale or vscale, it'll return
      True without having done anything.
      Some callers check for the scale values to be not NULL, but then
      hscale->resampler.max_taps could return 0.
      A different approach to the one presented in this patch is to check
      for those max_taps, too, before calling get_functions.
      
      Fixes https://bugzilla.gnome.org/show_bug.cgi?id=752051
      190c7f19
  7. 29 Jun, 2015 1 commit
  8. 17 Jun, 2015 1 commit
  9. 16 Jun, 2015 1 commit
  10. 12 Jun, 2015 3 commits
  11. 18 May, 2015 2 commits
  12. 04 May, 2015 1 commit
  13. 21 Apr, 2015 2 commits
  14. 12 Mar, 2015 1 commit
  15. 04 Mar, 2015 1 commit
  16. 02 Mar, 2015 1 commit
    • Wim Taymans's avatar
      video-converter: v-resample enough pixels · b2a7ac27
      Wim Taymans authored
      When we are using the fast linear resampler, use the ->inc to calculate
      the first and last pixel we need so that we can do vertical resampling
      on the right amount of pixels.
      b2a7ac27
  17. 25 Feb, 2015 3 commits
  18. 11 Feb, 2015 1 commit
    • Wim Taymans's avatar
      video-scaler: add 2d scaler · cdd86d02
      Wim Taymans authored
      Make a convenience function that combines 2 scalers to perform a 2d
      scale. This removes quite a bit of overhead in method calls when doing a
      typical scale and it also can reuse a piece of unused memory in the
      vertical scaler.
      Use the 2d scaler in video-converter and remove the other scalers and
      temp memory.
      cdd86d02
  19. 10 Feb, 2015 3 commits
    • Wim Taymans's avatar
      video-scaler: Small performance tweaks · 43139706
      Wim Taymans authored
      Small performance tweaks for RGB and friends.
      Add, but ifdef out, alternative nearest neighbour scaling, it is slower
      than the current table based version.
      Use memcpy instead of orc_memcpy because it is measurably faster.
      Fix YUY2 and friends vertical scaling.
      43139706
    • Sebastian Dröge's avatar
      video-scaler: Guard against (impossible) bits!=16 && bits!=8 case to fix... · 13643870
      Sebastian Dröge authored
      video-scaler: Guard against (impossible) bits!=16 && bits!=8 case to fix compiler warning with clang
      
      video-scaler.c:1331:14: error: variable 'func' is used uninitialized whenever 'if' condition is false
            [-Werror,-Wsometimes-uninitialized]
        } else if (bits == 16) {
                   ^~~~~~~~~~
      video-scaler.c:1348:3: note: uninitialized use occurs here
        func (scale, src_lines, dest, dest_offset, width, n_elems);
        ^~~~
      video-scaler.c:1331:10: note: remove the 'if' if its condition is always true
        } else if (bits == 16) {
               ^~~~~~~~~~~~~~~~
      video-scaler.c:1260:27: note: initialize the variable 'func' to silence this warning
        GstVideoScalerVFunc func;
                                ^
                                 = NULL
      13643870
    • Luis de Bethencourt's avatar
      video-converter: bits variable always set · 4fb00958
      Luis de Bethencourt authored
      In function gst_video_scaler_vertical() the bits variable is always
      set to either 8 or 16 in every possible format. No need to initialize it.
      
      If the format isn't valid it goes to no_func, so there is no need to
      handle the case of bits not being 8 or 16.
      
      CID #1268401
      4fb00958
  20. 06 Feb, 2015 1 commit
  21. 04 Feb, 2015 2 commits
  22. 28 Jan, 2015 2 commits
  23. 27 Jan, 2015 1 commit
  24. 07 Jan, 2015 1 commit
  25. 02 Dec, 2014 1 commit
  26. 25 Nov, 2014 2 commits
  27. 21 Nov, 2014 1 commit
  28. 19 Nov, 2014 2 commits