[Bug 797313] wavparse: Not handling SEGMENT query

[GStreamer (GNOME Bugzilla)]

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

--- Comment #8 from Francesco Ceruti <ceppofrancy at gmail.com> ---
Thanks :-)

> With scaletempo it is expected that you get 1.0: rate will be 1.0 and
> applied_rate will be 2.0, but the segment query only gives you the rate.

mmh, okay, it's not clear to me where can I get the "applied_rate", plus I
cannot find reference of this behavior in the scaletempo documentation and it's
seems related to the wavparse element, this doesn't happen whit other decoders
(with or without scaletempo in the pipeline).

> What are you trying to do exactly with the seeking query?

I'm changing the playback position (start_position), stop_position, and
playback-rate, but using the gst_element_seek() function, that should use a
GstEvent not a GstQuery, but I don't know to much about how this works
internally.

For various reasons the seeks that change the rate and start/stop position
happens in different parts of the application, and I need to retrieve the
correct rate to avoid changing it when moving start/stop position.

Still, if it's not very reliable, I'll change how I handle the things on my
application to avoid future problems.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.