| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Anything else requires keeping track of the GstVideoFrame mapping
across possible multiple buffers to ensure correct data pointer
usage.
|
| |
|
|
|
|
|
|
|
| |
This will deadlock if the main thread is the one who creates the GstGLContext.
All things we call from the main thread should be possible from any thread.
https://bugzilla.gnome.org/show_bug.cgi?id=751101
|
|
|
|
|
| |
We use things like CUSTOM_SUCCESS* in other places, and those are not errors
but should just be handled like OK.
|
|
|
|
|
|
|
| |
and not ERROR
Sometimes the last fragment does not exist because of rounding errors with the
durations. Just finish the stream gracefully instead of erroring out instead.
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=751778
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=751778
|
| |
|
|
|
|
| |
They may conflict with other headers.
|
|
|
|
|
|
|
| |
getcaps
Avoiding not negotiated error while negotiating as we anyway force 1/1
as output
|
|
|
|
|
| |
The client side API of the Chromium's GPU Process has asserts
in debug mode that check that output params are initialized to 0.
|
| |
|
|
|
|
|
| |
Caching and sharing to multiple element the same pool prevents
renegotiation from passthrough to not passthrough.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
multi-period streams
Segment start/time/position/base should only be modified if this is the first
time we send a segment, otherwise we will override values from the seek
segment if new streams have to be exposed as part of the seek.
Segment base should be calculated from the segment start based on the stream's
own segment, not the demuxer's segment. Both might differ slightly because of
the presentationTimeOffset.
Always add the presentationTimeOffset (relative to the period start, not
timestamp 0) to the segment start after resetting the stream's segment based
on the demuxer's segment (i.e. after seeks or stream restart). Also make sure
to keep the stream's segment up to date and not just send a new segment event
without storing the segment in the stream.
https://bugzilla.gnome.org/show_bug.cgi?id=745455
|
|
|
|
|
|
| |
And include the presentation offset in the last known position for each
stream, and just because we can also keep track of the latest known position
inside the demuxer segment.
|
|
|
|
|
|
| |
This reverts commit 5697b6b89b4b2a15c45bd47be940a17f4412ea11.
https://bugzilla.gnome.org/show_bug.cgi?id=751003
|
|
|
|
|
|
|
|
| |
thread"
This reverts commit 0bff481011cf74c59869b511393d1696b570e3d5.
It wasn't supposed to be merged and also doesn't fix the problem.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gst_adaptive_demux_stream_update_fragment_info()
It's going to return EOS if the period ended or otherwise there is just no
next fragment left. If we don't store the last return value, it will always
stay OK and gst_adaptive_demux_combine_flows() will always return OK instead
of EOS once all streams are done.
This partially switches period changes in DASH by at least trying to switch
instead of just stopping. What is still left is that after a period change
with DASH the times all start at 0 again instead of continuing.
|
|
|
|
|
|
| |
This will otherwise deadlock.
https://bugzilla.gnome.org/show_bug.cgi?id=751101
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=751228
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The problem here was that after removing the formats and
all the things we could convert, we then intersected these
caps with the template caps.
Hence if a subclass offered permissive sink templates
(eg all the possible formats videoconvert handles), but only
one output format, then at negotiation time getcaps returned
caps with the format restricted to that format, even though
we do handle conversion.
https://bugzilla.gnome.org/show_bug.cgi?id=751255
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=751165
|
|
|
|
| |
For bits that we don't parse out at the moment.
|
| |
|
|
|
|
| |
And sprinkle some more Since markers
|
|
|
|
|
|
|
| |
g_return_val_if_fail() and g_assert() are not appropriate
for checking untrusted external data.
https://bugzilla.gnome.org/show_bug.cgi?id=673925
|
|
|
|
|
|
|
|
|
|
|
| |
- add data pointer to GstJpegSegment and pass segment
to all parsing functions, rename accordingly
- shorten GstJpegMarkerCode enum type name to GstJpegMarker
- move function gtk-doc blurbs into .c file
- add since markers
- flesh out docs for SOF markers
https://bugzilla.gnome.org/show_bug.cgi?id=673925
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=673925
|
|
|
|
|
|
|
| |
Make this function private for now, since it's unclear whether
it's actually needed seeing that gst_jpeg_parse() scans too.
https://bugzilla.gnome.org/show_bug.cgi?id=673925
|
|
|
|
|
|
|
|
| |
Fix scan for next marker code when there is an odd number of filler
(0xff) bytes before the actual marker code. Also optimize the loop
to execute with fewer instructions (~10%).
This fixes parsing for Spectralfan.mov.
|
|
|
|
|
|
|
|
|
| |
The size of a marker segment is defined to be exclusive of any initial
marker code. So, fix the size for SOI, EOI and APPn segments but also
the size of any possible segment that is usually "reserved" or not
explicitly defined.
https://bugzilla.gnome.org/show_bug.cgi?id=707447
|
|
|
|
|
| |
Fix build_huffman_table() to correctly fill in the associated HUFFVAL
entries to the default Huffman tables.
|
|
|
|
|
|
| |
Signed-off-by: Gwenole Beauchesne <gwenole.beauchesne@intel.com>
https://bugzilla.gnome.org/show_bug.cgi?id=673925
|
|
|
|
|
|
|
| |
It also emits a create-context signal so that an application
can provide an external GstGLContext backend.
https://bugzilla.gnome.org/show_bug.cgi?id=750310
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=750310
|
|
|
|
| |
This reverts commit 71b8103cbd16fff9cf5a65cf517083cb794aa3b5.
|
|
|
|
| |
This reverts commit b377112ee38912d316e77b4e2102041389dc0051.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Add API for a helper object that can convert between different
stereoscopic video representations, and later do filtering
of multiple view streams.
https://bugzilla.gnome.org/show_bug.cgi?id=611157
|
|
|
|
|
|
| |
trivial patch to add proper ( while checking for if(G_UNLIKELY())
https://bugzilla.gnome.org/show_bug.cgi?id=751087
|
| |
|
| |
|
|
|
|
| |
configured caps
|
|
|
|
| |
use the in the QoS messages
|
|
|
|
| |
It is an unsigned integer so the upper bound is G_MAXUINT.
|
|
|
|
|
|
|
|
|
|
| |
Switch the increment of markersize from when it is used to when it is
returned from compute_resync_marker_size.
This also makes the CHECK_REMAINING in gst_mpeg4_parse_video_packet_header
check for the actually required number of bits now and not one too few.
https://bugzilla.gnome.org/show_bug.cgi?id=739345
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 916b954315abc2f94348ec0be3e116c19b080b54.
Clearly something else was intended, and it also makes
more sense to add the extra bit. The resync marker is
N zero bits plus a 1 bit, and the pattern/mask needs to
be run on N+1 bits too.
(Even after the rever the code doesn't do that of course, so
it still needs to be fixed differently.)
https://bugzilla.gnome.org/show_bug.cgi?id=739345
|