[Bug 648220] New: Regression: videoscale fails to negotiate for PAR transformation

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=648220
  GStreamer | gstreamer (core) | git

           Summary: Regression: videoscale fails to negotiate for PAR
                    transformation
    Classification: Platform
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: blocker
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: mail at renestadler.de
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


Such a pipeline used to work:

videotestsrc !
'video/x-raw-yuv,format=(fourcc)UYVY,width=352,height=288,framerate=(fraction)30/1,pixel-aspect-ratio=(fraction)1/1'
! videoscale !
'video/x-raw-yuv,format=(fourcc)UYVY,width=352,height=288,framerate=(fraction)30/1,pixel-aspect-ratio=(fraction)12/11'
! fakesink

This converts from PAR 1/1 to 12/11 (all other caps fields are identical). With
latest everything, this now gives:

ERROR: from element /GstPipeline:pipeline0/GstVideoTestSrc:videotestsrc0:
Internal data flow error.
Additional debug info:
gstbasesrc.c(2582): gst_base_src_loop ():
/GstPipeline:pipeline0/GstVideoTestSrc:videotestsrc0:
streaming task paused, reason not-negotiated (-4)

It works again if I revert this core commit:

commit 83597767b169dd6c39a07b6144a650c1f098825a
Author: Thiago Santos <thiago.sousa.santos at collabora.co.uk>
Date:   Mon Feb 14 18:05:09 2011 -0300

    basetransform: Be smarter with pad allocs

    Avoid doing unnecessary pad-allocs when on passthrough mode.
    If multiple basetransform elements are on a pipeline, they
    would do a pad-alloc for each received buffer, each element
    would do this, so we would have lots of pad allocs on the
    pipeline for a single buffer being pushed through it.

    This patch attempts to reduce this amount by avoiding
    doing pad-allocs if the element has already done it
    after the last pushed buffer. So it will only be allowed
    to do a new pad-alloc after it has pushed a buffer, so we get
    1x1 pad-alloc and buffer ratio

    https://bugzilla.gnome.org/show_bug.cgi?id=642373

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.