Mapping flite parameters onto openears parameters

Home Forums OpenEars Mapping flite parameters onto openears parameters

Viewing 2 posts - 1 through 2 (of 2 total)

  • Author
  • #1017054


    I’m moving an application that was using Flite directly to OpenEars.  I want to know what the mappings are between the floats from 0..2 that OpenEars uses and the parameters that Flite uses for these values:

    target_mean -> int_f0_target_mean

    target_stddev -> int_f0_target_stddev

    duration_stretch -> duration_stretch



    Halle Winkler

    Welcome Matt,

    Briefly, they are the float multiplication factor (0.1<->2.0) passed to FliteController as the target_mean/target_stddev/duration_stretch properties (or the default of 1.0 if those properties of FliteController are not set), multiplied by the default int_f0_target_mean/int_f0_target_stddev/duration_stretch that is stored in the voice framework. Those defaults are different in each voice.

    An example: You set FliteController.target_mean to 1.1 and you are using the voice Slt.framework which contains a default int_f0_target_mean of 170.0, so FliteController ends up sending an int_f0_target_mean of 187. i.e. it tracks 1:1 but rather than setting it directly, you manipulate the encapsulated voice default values by use of the +/- 1.0 multiplier.

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.