summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2013-09-28pluginloader: Check errors on the proper fdEdward Hervey1-1/+1
Most likely a copy-paste error from the block before. If we're going to check for error/closed on the write fd... do it on the write fd
2013-09-26docs: fix spelling of "generic" in GstBaseSrc's documentation.Brendan Long1-1/+1
https://bugzilla.gnome.org/show_bug.cgi?id=708870
2013-09-26pad: only check event order when something changedWim Taymans1-18/+27
Check the event order in dataflow only when something changed instead of for each buffer.
2013-09-24Automatic update of common submoduleTim-Philipp Müller2-1/+1
From 6b03ba7 to 865aa20
2013-09-24configure: Actually use 1.3.0.1 as version to make configure happySebastian Dröge1-1/+1
2013-09-24Back to developmentSebastian Dröge1-2/+2
2013-09-24Release 1.2.0Sebastian Dröge8-28/+343
2013-09-24Update .po filesSebastian Dröge39-39/+39
2013-09-24context: Add test for the context caching in GstBinSebastian Dröge1-0/+37
https://bugzilla.gnome.org/show_bug.cgi?id=708668
2013-09-24Revert "Potential GstContext regression"Sebastian Dröge2-264/+16
This reverts commit e658379534eb4a90b654d90f1d0bdf86f37c6e31. This test commit should've never been pushed. Oops.
2013-09-24bin: Make sure to cache context types that we did not store yetSebastian Dröge1-1/+1
https://bugzilla.gnome.org/show_bug.cgi?id=708668
2013-09-24Potential GstContext regressionAlex Ashley2-16/+264
Since the refactoring of GstContext (commits qc9fa2771b508e9aaeecc700e66e958190476f, a7f5dc8b8af837f01782d1572379948ff62daab7, 690326f906dc82e41ea58b81cdb2e3e88b754, d367dc1b0d4ecb37f4d27267e03d7bf0c6c06a6, and 82d158aed3f2e8545e1e7d35085085ff58f18) I am no longer able to get a shared context for an element that is used twice in a pipeline. I used the documentation and eglglessink as my reference for implementing the GstContext logic. As the code was tied to a hardware decoder, I have ported the GstContext code to fakesink to show the problem. Using the old API a single ExampleMgr instance is created, but using the new API each element is creating its own instance.
2013-09-24collectpads: Make sure that the object lock is always taken when accessing ↵Sebastian Dröge1-1/+3
the private pad list https://bugzilla.gnome.org/show_bug.cgi?id=708636
2013-09-24collectpads: Use private pad list in set_flushing_unlockedMathieu Duponchelle1-1/+1
pads->data is the public list. It is dynamically rebuilt at each call to check_collected, in check_pads to be specific. When you add a pad and collectpads have been started, it is not added to the public list. Thus there exists a possible race where : 1) You would add a pad to collectpads while running. 2) You set collectpads to flushing before check_collected has been called again -> the pad is not set to flushing 3) the pad starts pushing data as downstream might not be prepared, in the case of adder it then returns FLOW_FLUSHING. 4) elements like demuxers, when they get a FLOW_FLUSHING, stop their tasks, never to be seen again. https://bugzilla.gnome.org/show_bug.cgi?id=708636
2013-09-23tests: handle unscheduled entries correctlyWim Taymans2-0/+29
Make the testclock return GST_CLOCK_UNSCHEDULED when an unscheduled entry is used for gst_clock_wait() or gst_clock_wait_async(). Fixes https://bugzilla.gnome.org/show_bug.cgi?id=708605
2013-09-22gst-uninstalled: Allow specifying the checkout directory by env variableEdward Hervey1-12/+23
For some rare cases, one might not be able to use the hardcoded $HOME/gst location yet would still want to use the gst-uninstalled script as-is (which has the benefit of being constantly updated). For these cases, the checkout directory can be specified with the GST_UNINSTALLED_ROOT environment variable. Ex: export GST_UNINSTALLED_ROOT=$HOME/somewhere/with/checkouts And then just call gst-uninstalled directly: $GST_UNINSTALLED_ROOT/gstreamer/gst-uninstalled
2013-09-20Automatic update of common submoduleEdward Hervey1-0/+0
From b613661 to 6b03ba7
2013-09-19Automatic update of common submoduleTim-Philipp Müller1-0/+0
From 74a6857 to b613661
2013-09-19Automatic update of common submoduleTim-Philipp Müller2-5/+7
From 12af105 to 74a6857
2013-09-19check: testclock: fix function guardsTim-Philipp Müller1-15/+29
Should be g_return_*() not g_assert(), even if it's for tests only.
2013-09-19check: testclock: don't put code with side-effects in g_assert()Tim-Philipp Müller1-2/+2
Fixes unit test failures when -DG_DISABLE_ASSERT is used. https://bugzilla.gnome.org/show_bug.cgi?id=706551
2013-09-19gstcontext: Fix return values some moreEdward Hervey1-1/+1
Return value is a boolean not a pointer
2013-09-19context: Fix return values for gst_context_has_context_type() in assertionsSebastian Dröge1-2/+2
2013-09-19Back to developmentSebastian Dröge1-1/+1
2013-09-19Release 1.1.90Sebastian Dröge9-45/+377
2013-09-19Update .po filesSebastian Dröge39-39/+39
2013-09-19context: Add convenience function gst_context_has_context_type()Sebastian Dröge4-0/+24
2013-09-19po: Update translationsSebastian Dröge39-232/+250
2013-09-18message: Implement getting the name of the context message typesSebastian Dröge1-0/+2
2013-09-18context: Fix unit test for GstContext changesSebastian Dröge4-72/+23
2013-09-18gst-launch: Update for GstContext changesSebastian Dröge1-73/+9
2013-09-18context: Update docsSebastian Dröge2-21/+8
2013-09-18bin: Implement context caching and propagation againSebastian Dröge1-1/+96
2013-09-17message/query: Simplify CONTEXT messages/queries to only contain a single typeSebastian Dröge6-216/+39
2013-09-17context: Update documentationSebastian Dröge2-24/+21
2013-09-17context: Change GstContext to contain only a single contextSebastian Dröge3-10/+34
It was unintuitive that GstContext was actually a list of different contexts. GstContext now is only a type string and a structure to contain the actual context.
2013-09-17element: Remove GstContext cachingSebastian Dröge3-44/+1
2013-09-17context: Add persistent qualifier for a contextSebastian Dröge2-4/+31
Non-persistent contexts are removed when elements go back to NULL state, persistent contexts are not. Applications most likely want to set persistent contexts.
2013-09-17query: Make CONTEXT query upstream and downstreamSebastian Dröge1-2/+2
2013-09-17event: Remove CONTEXT downstream eventSebastian Dröge4-72/+10
This is going to be implemented with an upstream query instead for consistency and simplicity.
2013-09-13gst: Stop all unused threads in GThreadPool in gst_deinit()Jonas Holmberg1-0/+1
Since the default number of max unused threads in GThreadPool has been changed from 0 to 2 it needs to be set to 0 to stop all threads or valgrind will report them as memory leaks.
2013-09-10controlbindings: fix pspec relaxation for control source propertiesRico Tzschichholz2-5/+10
The change should have been from PARAM_CONSTRUCT_ONLY to PARAM_CONSTRUCT, otherwise bindings are affected, since they look for the CONSTRUCT flag. See ec55363d
2013-09-10queue2: Only update current level if we already downloaded a rangeSebastian Dröge1-1/+2
Otherwise queue->level is NULL and dereferencing that is not a good idea in general. https://bugzilla.gnome.org/show_bug.cgi?id=707648
2013-09-09meta: Deprecate GST_META_TAG_MEMORYSebastian Dröge1-0/+3
The GQuarks are not exported by any public API
2013-09-09meta: Add a #define for memory metadataMathieu Duponchelle3-1/+11
2013-09-09basetransform: implement a default transform_meta.Mathieu Duponchelle2-5/+24
If a metadata has no dependency as shown by the tags, copy it.
2013-09-09meta: API: Add gst_meta_api_type_get_tags() to get all meta tags.Mathieu Duponchelle2-0/+24
2013-09-09tests/capsfilter: Fix memory leak and compare caps directly instead of strcmp()Sebastian Dröge1-10/+7
2013-09-09tests/capsfilter: Test caps-related queries and propertySebastian Rasmussen1-0/+155
2013-09-09Update the buffering state before stalling for more dataGustavo Noronha Silva1-0/+9
In some cases the wait for more data was happening without updating the buffering state, meaning the API user would not be able to notice it should pause the pipeline and update UI to indicate that is the case, the video would likely stutter instead. https://bugzilla.gnome.org/show_bug.cgi?id=707648
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-28 03:51:51 +0000