Michael Grüner

Oh, BTW, I had to manually edit some of the aggregator sources to add the `update_segment` method. I know these are autogenerated, but this was the only missing piece.

> > Oh, BTW, I had to manually edit some of the aggregator sources to add the `update_segment` method. I know these are autogenerated, but this was the only missing...

Changes done @sdroege please review one last time

Hey @sdroege do you mind taking a look at #78? It adds a `sink-v1_14` feature that backports the aggregator locally, as the fallback switch does.

Hi @phil-marble, currently you can set the desired logging (/var/log/) and PID (/var/run) directories during configuration. Something like: ``` ./configure --with-gstd-runstatedir=/var/run --with-gstd-logstatedir=/var/log/ ``` The default values are set to `$prefix/var/run/gstd/`...

Agreed. Marked as enhancement already.

@diegochaverri26 @rrcarlosrodriguez @jcaballeros can any of you take a look at this?

Hey @TopperBG . I can think of 3 options: 1. These logs are managed by the GStreamer debugging subsystem, so you can disable them or reduce them: ```bash gst-client debug_enable...

Indeed this looks like a bug. The “nodes” member should contain the actual list of the pipelines. I see the count is 1 but the nodes list is empty. Here’s...

For the state of the pipeline you can do a `read /pipelines/pipeline_name/state`, where `pipeline_name` is the name you gave to the pipeline.