[mary-dev] javax / marytts on android

[Dennis Reidsma]

OK! Well, I'd be happy to help with figuring out a configurable 
alternative to the javax.sound.sampled -- I do not know so much about 
the MaryTTS innards so I wouldn't really be much of a help there...

As for the processing power: I expect this will change; also, there are 
quite a number of Android devices that are not really phones but rather 
tables -- they'll probably also get more and more processing power :)

But indeed, it also makes sense to think about making Mary "lighter"

cheers,
Dennis

On 2/13/2012 2:51 AM, Bill Cox wrote:
> Hi, Dennis.  I'm quite interested in an Android port of Mary TTS.  I
> currently listen to all my audio books using Mary TTS to generate the
> audio files in Windows or Linux, and play them in Astro Player Nova on
> my Android phone, which let's me play at a decent speed.  I also use
> Mary TTS with NVDA to read the Windows screen to me.  Currently, the
> most significant issues with Mary TTS for users who need to use it
> with a screen reader seem to be latency and efficiency.  On Android, I
> expect these issues to be worse, and unusable on platforms without an
> FPU, which still includes most Android phones, AFAIK.  I am interested
> in building a "light" version of Mary TTS, converted to fixed-point
> arithmetic, loading only hsmm modules needed for TTS, and with some
> tuning to reduce memory and CPU consumption.  This would make it more
> responsive in Windows and Linux, and I suspect make it a good synth
> for Android.  Let me know if you'd be interested in collaborating on a
> light version.
>
> Thanks,
> Bill
>
> On 2/12/12, Dennis Reidsma<d.reidsma at utwente.nl>  wrote:
>> Hi all,
>>
>> I almost finished getting MaryTTS to run on Android. There is, as far as
>> I can see, only one thing keeping me from finishing it:
>>
>> Android does not support javax.sound.sampled, which is worked pretty
>> deeply into MaryTTS.
>>
>> So, my question is: would it be conceivable that the funtionality
>> currently implemented through javax.sound.sampled gets delegated to some
>> set of interfaces, for which we can make multiple implementations? I.e.,
>> one using javax.sound.sampled (as currently done), one using some
>> android sound packages, and maybe even others such as OpenAL...
>>
>> Anyone an opinion on that?
>>
>> best regards,
>> Dennis Reidsma
>>