GNOME Bugzilla – Bug 489270
Add option to disable registry caching.
Last modified: 2008-01-10 10:45:13 UTC
When user disabled Registry, many tools would not work well, such as gst-inspect, gst-launch etc, this patch is to resolve this issue. when compiling these tools, if find define GST_DISABLE_REGISTRY, these tools will use gst_registry_scan_path to scan the plugins path and register all plugins. Changed files: gst/gst.c tools/gst-inspect.c tools/gst-launch.c tools/gst-typefind.c libs/gst/check/gstcheck.c tests/examples/metadata/read-metadata.c Motorola would like to contribute Gstreamer patch to the Gstreamer open source community project. Please find attached the patch applicable for Gstreamer. For any questions, please feel free to contact (Zhao Liang "e3423c@motorola.com", Shi Ling "w20230@motorola.com").
Created attachment 97691 [details] [review] gst.c.patch
Created attachment 97692 [details] [review] gstcheck.c.patch
Created attachment 97693 [details] [review] gst-inspect.c.patch
Created attachment 97694 [details] [review] gst-launch.c.patch
Created attachment 97695 [details] [review] gst-typefind.c.patch
Created attachment 97696 [details] [review] read-metadata.c.patch
It seems you want to disable the registry *caching* with this patch, not the registry itself. This functionality should go into gst.c with a new configure option to only disable the caching. We can't go adding this code to all applications. Can you make a patch to just disable the caching? Changing to enhancement in case someone wants to try.
Hi Wim, We can do it, but if we disable registry "caching" in gstreamer core, and still want to use these tools, how do we handle? can you give some guidance?
gst_init() would just always scan the default directories instead of reading the registry cache file. Why exactly are you doing this? This should make everything slower on startup and will consume more memory.
Hi Wim, What we want is to DISABLE reading the registry cache file and scaning plugin path when gst_init(), because it will cost much time to read xml file and scan path on mobilephone. But if we use configure "--disable-registry" to disable this feature, some tools such as gst-inspect will not work, it is really a problem, so we do these patchs. Now we find another feature "binary registry" which can save time even with "registry" feature by our test.
For our use case, if we use "--disable-registry", in our app, we will load plugin libs manually, all what we do are to reduce the gst_init time. but something inconvenient is that we can not use gst-inspect etc tools, so we made these patchs. Now we are using "binary registry", it is good for our usecase, saving time and no need to load plugin lib manually.
If you are loading plugins manually and you disable the registry, tools like gst-inspect and gst-launch don't make much sense. If you are using the binary registry then they should work fine. Can you confirm and let us know if we can close that bug ? [This bug is part of Fluendo support for Motorola.]
Yes, please close this bug.