search for: disable_vocod

...3 to 7 are too similar to each other to save significant amount of code by eliminating some of them, but I have a feeling that generic mechanism for picking only those modes needed (either through conditional compilation or may be even with configuration perl script) would be simple than specific DISABLE_VOCODER. Another potential saving could be achieved by replacing speex_warning, speex_notification and speex_error with user-modifiable defines. The existing DISABLE_WARNING/ OVERRIDE_SPEEX_WARNING method is not efficient in reducing the code footprint because the majority of the overhead happens in the...

...ach other to save significant amount of code by eliminating some of them, >> but I have a feeling that generic mechanism for picking only those modes needed (either >> through conditional compilation or may be even with configuration perl script) would be >> simple than specific DISABLE_VOCODER. > >The problem is that there are *lots* of things like that and having an >option for everything would make the code a bit ugly. But they aren't >that hard to debug. If you don't know if a function is useful, remove it >and see what happens. If it succeeds in encoding one...

...; some of them, >>>> but I have a feeling that generic mechanism for picking only those modes >>>> needed (either >>>> through conditional compilation or may be even with configuration perl >>>> script) would be >>>> simple than specific DISABLE_VOCODER. >>> >>>The problem is that there are *lots* of things like that and having an >>>option for everything would make the code a bit ugly. But they aren't >>>that hard to debug. If you don't know if a function is useful, remove it >>>and see what...