missing "--disable-index" option, in gstreamer-0.10.21

[Sameer Naik]

Hi,
I just realized that "--disable-index" compilation option (to disable indexing for seeking purposes) in on longer available in gstreamer-0.10.21, has it been removed from gstreamer? if so since when and why?

Please comment...

Regards
~Sameer

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

[Sebastian Dröge-7]

Am Montag, den 01.12.2008, 18:40 +0530 schrieb Sameer Naik:
> Hi,
> I just realized that "--disable-index" compilation option (to disable
> indexing for seeking purposes) in on longer available in
> gstreamer-0.10.21, has it been removed from gstreamer? if so since
> when and why?

It has been removed intentionally, yes. The relevant changeset was:

> 2008-07-31  Sebastian Dröge  <[hidden email]>
>
>         * configure.ac:
>         * docs/gst/gstreamer-sections.txt:
>         * docs/gst/gstreamer.types:
>         * docs/gst/gstreamer.types.in:
>         * gst/Makefile.am:
>         * gst/gst.c:
>         * gst/gstbin.c: (gst_bin_class_init), (gst_bin_set_index_func):
>         * gst/gstconfig.h.in:
>         * gst/gstelement.c: (gst_element_get_index):
>         * gst/gstregistrybinary.c: (gst_registry_binary_save_feature),
>         (gst_registry_binary_load_feature),
>         (gst_registry_binary_read_cache):
>         * gst/gstregistryxml.c: (load_feature),
>         (gst_registry_xml_read_cache), (gst_registry_xml_save_feature):
>         * plugins/Makefile.am:
>         * tools/gst-indent:
>         * tools/gst-inspect.c: (print_index_info), (print_element_list),
>         (print_plugin_features), (print_element_features):
>         * tools/gst-xmlinspect.c: (print_event_masks),
>         (print_element_info):
>         * win32/common/gstconfig.h:
>         Remove GST_DISABLE_(ENUMTYPES|INDEX|URI) everywhere.
>
>         Disabling the indexers and URI handler code will only reduce the
>         required amount of memory by a very small amount but on the other hand
>         requires much more maintaince work. Apart from that many places of
>         code are broken when disabling them.
>
>         Disabling the enum types doesn't reduce the required amount of memory
>         by more than a few bytes and makes it hard to fix bugs like #539772,
>         i.e. use the enums as GObject properties.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

[Sameer Naik]

Thanks for your prompt reply.

I read this comment made:
"Disabling the indexers and URI handler code will only reduce the required
amount of memory by a very small amount"

Is it a fact that an extremely small amount of memory is used. Does this hold
true for embedded application's where memory becomes an important parameter.
Say i am playing a 2Gb video file. won't indexing the entire file take up quite
a chunk of memory?

Secondly which version onwards was the --disable-index option removed

Regards
~Sameer

On Monday 01 December 2008 19:11:31 Sebastian Dröge wrote:

> Am Montag, den 01.12.2008, 18:40 +0530 schrieb Sameer Naik:
> > Hi,
> > I just realized that "--disable-index" compilation option (to disable
> > indexing for seeking purposes) in on longer available in
> > gstreamer-0.10.21, has it been removed from gstreamer? if so since
> > when and why?
>
> It has been removed intentionally, yes. The relevant changeset was:
> > 2008-07-31  Sebastian Dröge  <[hidden email]>
> >
> >         * configure.ac:
> >         * docs/gst/gstreamer-sections.txt:
> >         * docs/gst/gstreamer.types:
> >         * docs/gst/gstreamer.types.in:
> >         * gst/Makefile.am:
> >         * gst/gst.c:
> >         * gst/gstbin.c: (gst_bin_class_init), (gst_bin_set_index_func):
> >         * gst/gstconfig.h.in:
> >         * gst/gstelement.c: (gst_element_get_index):
> >         * gst/gstregistrybinary.c: (gst_registry_binary_save_feature),
> >         (gst_registry_binary_load_feature),
> >         (gst_registry_binary_read_cache):
> >         * gst/gstregistryxml.c: (load_feature),
> >         (gst_registry_xml_read_cache), (gst_registry_xml_save_feature):
> >         * plugins/Makefile.am:
> >         * tools/gst-indent:
> >         * tools/gst-inspect.c: (print_index_info), (print_element_list),
> >         (print_plugin_features), (print_element_features):
> >         * tools/gst-xmlinspect.c: (print_event_masks),
> >         (print_element_info):
> >         * win32/common/gstconfig.h:
> >         Remove GST_DISABLE_(ENUMTYPES|INDEX|URI) everywhere.
> >
> >         Disabling the indexers and URI handler code will only reduce the
> >         required amount of memory by a very small amount but on the other
> > hand requires much more maintaince work. Apart from that many places of
> > code are broken when disabling them.
> >
> >         Disabling the enum types doesn't reduce the required amount of
> > memory by more than a few bytes and makes it hard to fix bugs like
> > #539772, i.e. use the enums as GObject properties.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

[Sebastian Dröge-7]

Am Montag, den 01.12.2008, 19:58 +0530 schrieb Sameer Naik:

> Thanks for your prompt reply.
>
> I read this comment made:
> "Disabling the indexers and URI handler code will only reduce the required
> amount of memory by a very small amount"
>
> Is it a fact that an extremely small amount of memory is used. Does this hold
> true for embedded application's where memory becomes an important parameter.
> Say i am playing a 2Gb video file. won't indexing the entire file take up quite
> a chunk of memory?

Sure but this wasn't controlled by this configure parameter. It just
disabled the GstIndex type which provides a generic index to be used by
the application.

Almost all elements that use indexes are not using GstIndex internally
(or are not supporting GstIndex at all) because custom indexes are often
much more efficient memory and time wise.

If you want to prevent elements from creating a file index at all you
need to change a lot of code anyway. There never was a configure
parameter for disabling this (and for many file formats you will loose
the ability to seek).

> Secondly which version onwards was the --disable-index option removed

0.10.21 and later. 0.10.20 still had it

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

[Stefan Sauer]

hi,

Sameer Naik schrieb:

> Thanks for your prompt reply.
>
> I read this comment made:
> "Disabling the indexers and URI handler code will only reduce the required
> amount of memory by a very small amount"
>
> Is it a fact that an extremely small amount of memory is used. Does this hold
> true for embedded application's where memory becomes an important parameter.
> Say i am playing a 2Gb video file. won't indexing the entire file take up quite
> a chunk of memory?
>  

I am on a embedded system as well. There are a couple of thing that we
can improve on the 0.11 timeframe regarding the structure of the
gstreamer core library. But keeping to many things optional also puts a
lot of hassle into maintenance. Regarding the index feture, it will
probably be used by more plugins in the future and thus it became less
attractive to allow disabling it.
> Secondly which version onwards was the --disable-index option removed
>  
Have a look at the ChangeLog.

Stefan

> Regards
> ~Sameer
>
> On Monday 01 December 2008 19:11:31 Sebastian Dröge wrote:
>  
>> Am Montag, den 01.12.2008, 18:40 +0530 schrieb Sameer Naik:
>>    
>>> Hi,
>>> I just realized that "--disable-index" compilation option (to disable
>>> indexing for seeking purposes) in on longer available in
>>> gstreamer-0.10.21, has it been removed from gstreamer? if so since
>>> when and why?
>>>      
>> It has been removed intentionally, yes. The relevant changeset was:
>>    
>>> 2008-07-31  Sebastian Dröge  <[hidden email]>
>>>
>>>         * configure.ac:
>>>         * docs/gst/gstreamer-sections.txt:
>>>         * docs/gst/gstreamer.types:
>>>         * docs/gst/gstreamer.types.in:
>>>         * gst/Makefile.am:
>>>         * gst/gst.c:
>>>         * gst/gstbin.c: (gst_bin_class_init), (gst_bin_set_index_func):
>>>         * gst/gstconfig.h.in:
>>>         * gst/gstelement.c: (gst_element_get_index):
>>>         * gst/gstregistrybinary.c: (gst_registry_binary_save_feature),
>>>         (gst_registry_binary_load_feature),
>>>         (gst_registry_binary_read_cache):
>>>         * gst/gstregistryxml.c: (load_feature),
>>>         (gst_registry_xml_read_cache), (gst_registry_xml_save_feature):
>>>         * plugins/Makefile.am:
>>>         * tools/gst-indent:
>>>         * tools/gst-inspect.c: (print_index_info), (print_element_list),
>>>         (print_plugin_features), (print_element_features):
>>>         * tools/gst-xmlinspect.c: (print_event_masks),
>>>         (print_element_info):
>>>         * win32/common/gstconfig.h:
>>>         Remove GST_DISABLE_(ENUMTYPES|INDEX|URI) everywhere.
>>>
>>>         Disabling the indexers and URI handler code will only reduce the
>>>         required amount of memory by a very small amount but on the other
>>> hand requires much more maintaince work. Apart from that many places of
>>> code are broken when disabling them.
>>>
>>>         Disabling the enum types doesn't reduce the required amount of
>>> memory by more than a few bytes and makes it hard to fix bugs like
>>> #539772, i.e. use the enums as GObject properties.
>>>      
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
>  

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel