diff options
| author | Nicolas Dufresne <nicolas.dufresne@collabora.co.uk> | 2015-01-18 11:07:43 -0500 |
|---|---|---|
| committer | Nicolas Dufresne <nicolas.dufresne@collabora.co.uk> | 2015-01-18 11:07:43 -0500 |
| commit | acc9529a36ab7eef38539cce9ab7d11658df1fd4 (patch) | |
| tree | 17aafa0f2708313851ec5d90d4a132a8d88b1106 | |
| parent | ad43a4de43c6ad9400c1f0b9d9b7e2b9c479f734 (diff) | |
x264enc: Don't set an allocation maximum
There is no reason x264enc should enforce a maximum allocation size.
The maximum is normally set by buffer pool which cannot grow, but we
don't offer a buffer pool. This would lead to stall when used with
element that don't implement allocation query.
Related to: https://bugzilla.gnome.org/show_bug.cgi?id=738302
| -rw-r--r-- | ext/x264/gstx264enc.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/ext/x264/gstx264enc.c b/ext/x264/gstx264enc.c index a5a1e41f..dd37c702 100644 --- a/ext/x264/gstx264enc.c +++ b/ext/x264/gstx264enc.c @@ -1932,8 +1932,7 @@ gst_x264_enc_propose_allocation (GstVideoEncoder * encoder, GstQuery * query) info = &self->input_state->info; num_buffers = x264_encoder_maximum_delayed_frames (self->x264enc) + 1; - gst_query_add_allocation_pool (query, NULL, info->size, num_buffers, - num_buffers); + gst_query_add_allocation_pool (query, NULL, info->size, num_buffers, 0); return GST_VIDEO_ENCODER_CLASS (parent_class)->propose_allocation (encoder, query); |