Encoding format string

[Thibault Saunier]

Hi,

The default video track restriction caps are: `video/x-
raw,framerate=30/1,width=1280,height=720` meaning that all clips will
go through that state, you should set them to what you want, like

```
ges-launch-1.0 --video-cap="video/x-
raw(ANY),framerate=24/1,width=4096,height=2160" ...
```

You probably do not need to set those caps in the encoding profile once
you set the tracks restriction caps.

Cheers,

- Thibault

On Thu, 2022-12-01 at 16:32 -0800, amindfv--- via gstreamer-devel
wrote:
> Hi Thibault, sure - thanks.
> 
> I've just re-run the code; attached is one .dot file that exhibits
> the problems mentioned in the previous email.
> 
> This is the command that created it:
> 
>     GST_DEBUG_DUMP_DOT_DIR=/tmp ges-launch-1.0 --track-types=video
> +clip /foo/foo.MOV inpoint=16.0 duration=2.0 +clip /foo/bar.MOV
> inpoint=15.0 duration=3.0 --outputuri file:///foo/dotdotdot.mp4 --
> format 'video/quicktime,variant=iso:video/x-
> raw(ANY),framerate=24/1,width=4096,height=2160->video/x-h264|element-
> properties,target-bitrate=200000'
> 
> Thanks,
> Tom
> 
> On Thu, Dec 01, 2022 at 10:14:32AM -0300, Thibault Saunier via
> gstreamer-devel wrote:
> > Hi,
> > 
> > Could you share the .dot (or svg) file?
> > 
> > Regards,
> > 
> > - Thibault
> > 
> > On Wed, 2022-11-30 at 19:54 -0800, amindfv--- via gstreamer-devel
> > wrote:
> > > On Wed, Oct 26, 2022 at 01:18:28AM -0700,
> > > amindfv at mailbox.org wrote:
> > > > Hi Eslam - thank you very much for the information about
> > > > GST_DEBUG_DUMP_DOT_DIR. I'd never used it before, and it's
> > > > given me
> > > > a ton of insight about what's going on (though unfortunately I
> > > > still haven't fixed the issue).
> > > > 
> > > > A few things I notice from the pipeline, as rendered in the
> > > > .dot
> > > > files:
> > > > 
> > > >   - At some point in the pipeline, a GstVideoConvert element
> > > > has a
> > > > sink pad with format I420_10LE (good), but its source pad has
> > > > format I420 (not good)
> > > >   - Later in the same pipeline, a GstVideoRate element has a
> > > > sink
> > > > pad with framerate 24/1, but source pad with framerate 30/1
> > > > (also
> > > > not good). Later, in the GstEncodeBin, the framerate is
> > > > converted
> > > > back to 24/1.
> > > >   - In some .dot files, a GESSmartMixer (inside a NleOperation)
> > > > downgrades the geometry from 4K to 1280x720 (definitely not
> > > > good).
> > > > Not sure what it means but the "interlace-mode: progressive"
> > > > label
> > > > also disappears.
> > > > 
> > > > This is after explicitly adding a framerate to my encoding
> > > > profile,
> > > > as in:
> > > > 
> > > >    ges-launch-1.0 [...] --format
> > > > 'video/quicktime,variant=iso:video/x-
> > > > raw(ANY),framerate=24/1,width=4096,height=2160->video/x-
> > > > h264|element-properties,target-bitrate=200000'
> > > > 
> > > 
> > > 
> > > Just to follow up here, does anyone have an explanation for why
> > > this
> > > occurred? It seems so deeply wrong to me that GES would silently
> > > downgrade video geometry and change framerate in the middle of a
> > > pipeline (i.e. go 4K 24fps -> 720p 30 fps -> 4K 24fps) without a
> > > really good reason.
> > > 
> > > Thanks,
> > > Tom
> >