Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=740191
|
|
The logic to compute the MaxPicNum variable was reversed. In paricular,
MaxPicNum is double MaxFrameNum only if field_pic_flag is set to 1.
https://bugzilla.gnome.org/show_bug.cgi?id=739291
|
|
If we can't get an output, we would otherwise just use it later and crash.
|
|
|
|
|
|
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=739374
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=739374
|
|
with force-aspect-ratio=true, if the width or height changed, the
viewport wasn't being updated to respect the new video width and height
until a resize occured.
|
|
|
|
Otherwise when resizing the window you will also get messages like:
class NSConcreteMapTable autoreleased with no pool in place - just leaking
class NSConcreteValue autoreleased with no pool in place - just leaking
class NSConcreteValue autoreleased with no pool in place - just leaking
class __NSCFDictionary autoreleased with no pool in place - just leaking
|
|
|
|
Default value of property postsFrameChangedNotifications is YES
but it is worth to explicitly enable it.
|
|
Need to set the ':' as the reshape method now takes one parameter.
For the story, the GstGLNSView was previously inheriting from
NSOpenGLView which has a reshape function without any parameter.
Now the GstGLNSView inherits from NSView and we re-use the reshape
function manually.
|
|
Use the reshape function after being defined. The other way
would have been to declare the reshape function in the header.
gstglwindow_cocoa.m: In function '-[GstGLNSView drawRect:]':
gstglwindow_cocoa.m:555: warning: 'GstGLNSView' may not respond to '-reshape'
gstglwindow_cocoa.m:555: warning: (Messages without a matching method signature
gstglwindow_cocoa.m:555: warning: will be assumed to return 'id' and accept
gstglwindow_cocoa.m:555: warning: '...' as arguments.)
|
|
gstglwindow_cocoa.m: In function '-[GstGLNSView drawRect:]':
gstglwindow_cocoa.m:555: warning: 'GstGLNSView' may not respond to '-reshape'
gstglwindow_cocoa.m:555: warning: (Messages without a matching method signature
gstglwindow_cocoa.m:555: warning: will be assumed to return 'id' and accept
gstglwindow_cocoa.m:555: warning: '...' as arguments.)
|
|
Memory is only freed in the TRUE clause of the if conditional. Free in the else
clause as well.
Also, consolidate g_malloc + sprintf into a g_strdup_printf().
CID #1212171
https://bugzilla.gnome.org/show_bug.cgi?id=739368
|
|
|
|
As a consequence, tsdemux won't remove its pads anymore on EOS.
Fixes the case when mpegtsbase is not able to process new packets
after EOS as the corresponding pids aren't known anymore because
the programs were removed and the pes/psi were kept, preventing the
PAT to be parsed again.
https://bugzilla.gnome.org/show_bug.cgi?id=738695
Conflicts:
gst/mpegtsdemux/mpegtsbase.c
|
|
allows GL context sharing to occur.
|
|
The part of the configure.ac that consist to check if we
can include both GL and GLES2 at the same time is failing.
Indeed, in the case NEED_GLES2=yes and NEED_OPENGL=auto,
HAVE_OPENGL variable is updated whereas it should be HAVE_GL
variable that has to be updated (HAVE_OPENGL variable is not
used in the rest of the configure.ac).
https://bugzilla.gnome.org/show_bug.cgi?id=739348
Signed-off-by: Vincent Abriou <vincent.abriou@st.com>
Reviewed-by: Benjamin GAIGNARD <benjamin.gaignard@linaro.org>
|
|
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=739277
|
|
|
|
If we don't have a complete raw audio frame we would otherwise still
ask for a 0 sized buffer from the adapter.
|
|
multi-frame mode
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=738696
|
|
Sequence-layer used for unit test have a level set to 2 which should
match the medium level, not the high.
https://bugzilla.gnome.org/show_bug.cgi?id=738230
|
|
In simple profile, level set to 0 or 2 indicate low and medium level
respectively. In main profile, level set to 0, 2 or 4 indicate low,
medium and high level respectively.
Level values are defined in Annex J.1.2 of the SMPTE 421M.
https://bugzilla.gnome.org/show_bug.cgi?id=738230
|
|
Some VC1 decoder can have different caps according to wmv format, ie
WMV3 or WVC1.
So instead of keeping the first available caps, we interserct with
current WMV format.
https://bugzilla.gnome.org/show_bug.cgi?id=738532
|
|
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=738674
|
|
profile
When stream-format is ASF or sequence-layer-raw-frame, we basically have
a raw frame so we can parse it to extract some information such the
keyframe flag. The only requirement is to have a valid sequence-header.
This commit parse the frame header and set the DELTA_UNIT buffer flag in
case the frame is not a keyframe.
https://bugzilla.gnome.org/show_bug.cgi?id=738519
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=738449
|
|
frame-layer header is represented as a sequence of 32 bit unsigned
integer serialized in little-endian byte order, so framesize is on the
first 3 bytes.
SMPTE 421M Annex L.
https://bugzilla.gnome.org/show_bug.cgi?id=738243
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=738291
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=738223
|
|
The object lock only protects the session, as we modify
the session from other threads when the bitrate property
is changed. Don't hold it much longer than for session
related things.
And we need to release the video decoder stream lock before
enqueueing a frames. It might wait for our callback to dequeue
a frame from another thread, which will then take the stream
lock too and deadlock.
|
|
It is not required on OSX apparently and was only added in 10.9.6 there.
Calculating the correct level from the configuration is not trivial, so let's
just not set a level at all here.
|
|
Check with configure for it instead of using one of the availability macros
as those wouldn't work as expected with minor versions.
|
|
|
|
Otherwise we change a value of a property when going to READY state,
which is unexpected behaviour.
|
|
|
|
|
|
Without this our GL surface would be upscaled after rendering
by Cocoa, which would reduce image quality.
|
|
The visible rect and bounds might be the same as before, but Cocoa
might've changed our viewport without us nothing. This happens if
you hide the view and show it again.
|
|
Don't update the screen until we redraw, this prevents flickering during
scrolling, clipping, resizing, etc
|
|
We have to update the GL viewport if the NSView is only partially
visible. Otherwise the content of the frame will be visibly offset.
|
|
This is only for non-Cocoa apps but previously caused a 2 second
waiting during startup for Cocoa apps. This is unacceptable.
Instead we now check a bit more extensive if something actually
runs on the GLib default main context, and if not don't even
bother waiting for something to happen from there.
|