Age | Commit message (Collapse) | Author | Files | Lines |
|
Allows keeping the GstGLCAOpenGLLayer public but not the winsys-specific
context/display/window.
|
|
This reverts commit 94d798c3337013bd902c0fd0a66f7f6842243eeb.
cocoac headers don't need to be public as all the functionality can be
provided by the base class
|
|
Undefined symbols for architecture x86_64:
"_gst_gl_context_cocoa_get_type", referenced from:
__create_layer in libgstopengl_la-caopengllayersink.o
Might need some more in other headers, but first need to
clarify what exactly should be exported, there are some
inconsistencies (installed header files vs. funcs in docs).
|
|
Libraries in -bad are not covered by our API/ABI stability
guarantees, and to the best of our knowledge everyone using
this API has moved to the replacement APIs ages ago.
|
|
The result of gst_video_colorimetry_to_string () needs to be free'd
|
|
It causes crashes in applications because the result of
fbGetDisplay() might be in use elsewhere in the application
and Vivante doesn't seem to do any refcounting
|
|
GstGLDisplayVIVFb subclass"
This reverts commit 47fd4d391e775c11f529705bb0f457a9d25ba5e7.
This patch is incorrect. It doesn't actually compile, and causes a crash
because the viv-fb window implementation needs a native EGL handle
to pass to fbCreateWindow, but the GstGLDisplayEGL handleis actually
an EGLDisplay now (and gets cast to the wrong type)
|
|
|
|
This posed problems for the python bindings (and possibly others).
Instead, subclasses now use add_pad_template_with_gtype.
https://bugzilla.gnome.org/show_bug.cgi?id=789986
|
|
Cast to the target type before shifting (or use macro if available)
|
|
Otherwise when we stop, the necessary stop functions will not be called
and things may be leaked.
https://bugzilla.gnome.org/show_bug.cgi?id=788280
|
|
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=785679
|
|
Use new gst_element_foreach_sink_pad() from core instead.
https://bugzilla.gnome.org/show_bug.cgi?id=785679
|
|
Instead of gst_aggregator_iterate_sinkpads() which will
soon be removed.
https://bugzilla.gnome.org/show_bug.cgi?id=785679
|
|
Instead of gst_aggregator_iterate_sinkpads() which will
soon be removed.
https://bugzilla.gnome.org/show_bug.cgi?id=785679
|
|
|
|
Instead of gst_aggregator_iterate_sinkpads() which will
soon be removed.
https://bugzilla.gnome.org/show_bug.cgi?id=785679
|
|
Don't really have to do that while it's in -bad and most users
are in-tree anyway.
|
|
|
|
|
|
It is possible with GLES3
|
|
|
|
When switching bitrates we set the old streams as cancelled, but it
could also be confused with a cancel due to other reasons (as an error)
and it would lead the element to stop the pipeline mistankely. This
would happen when the stream being replaced was waiting for a manifest
update on live. Ss make it sure that we are stopping for switching
bitrates to avoid erroring out.
https://bugzilla.gnome.org/show_bug.cgi?id=789457
|
|
The value is used as GstClockTiem in the code. Adapt the hack^H^H^H^Hcode
in live-adder.
|
|
These are produced from GAP events by the base class.
https://bugzilla.gnome.org/show_bug.cgi?id=784846
|
|
Instead just take it in the chain function.
https://bugzilla.gnome.org/show_bug.cgi?id=784911
|
|
If we're adding to the tail of the queue, it's because we're converting
a gap event, so don't block there it means we're calling from the output
thread.
https://bugzilla.gnome.org/show_bug.cgi?id=784911
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=788404
|
|
Add a comment for when the state matters. Use a local var for priv in
update_time_level() to improve readability. Move the our_latency local
var below the query results checks.
|
|
|
|
Only look up klass for non serialized events/queries. For events remove
superfluous assignment for the return value in the flushing case.
|
|
We want to skip serialization for FLUSH_STOP events (apparently). We can
simplify the code to add it to the top-level conditions. There was nothing
done in the first code path if the event was FLUSH_STOP.
|
|
Just queue it like any other serialized event. This way we don't need to
check if there still are buffers in the queue.
Validated with the tests and gst-launch-1.0 pipelines.
|
|
|
|
The variable tracks wheter the queue is not empty, but num_buffers==0. That
means we have events or queries to process. Rename accordingly.
|
|
The SEGMENT_DONE event does not require any special treatment. This is
commented out in 6efc106a67.
|
|
Looks like some code was inserted afterwards.
|
|
Mention how data ends up in the queues. Document the relation of the pad
functions and the class vmethods to get events and queries.
|
|
Don't reuse the offset variables will contain a sample offset for an
intermediate time value. Instead add a segment_pos variable of type
GstClockTime for this. Use The clock-time macros to check if we got
a valid time.
|
|
This probably got shifted after some changes.
|
|
|
|
Acording to the logic this cannot happen (we already check this before). So
add a assert like we do above and remove the check. This make it clearer that
we check for the offset range.
Also remove a dead assignment since we reassign this a few lines below.
|
|
Remove wrote references to collectpads. Document the units.
|
|
The GST_EXPORT should handle it.
|
|
|
|
No need to recalc the value twice per run. Establishes that it is the same
value.
|
|
It does not fill a buffer. Rename it and add a short comment.
|
|
Don't copy the whole event struct. Set the input params when we call the
forwarding helper. Initialize the internal fields and return values in the
helper.
|
|
Avoid extra ref/unref, we have a ref and do_seek unrefs. Just return the result
as we have. This lets us remove the local var plus the label.
|