dev builds
themes manual
device status forums
mailing lists
IRC bugs
dev guide

Rockbox mail archive

Subject: Re: voice build change?

Re: voice build change?

From: [IDC]Dragon <>
Date: Wed, 31 Mar 2004 08:36:33 +0200 (MEST)

> > Sorry to be such a nag today, but I don't think this is viable, because
> > then
> > the voice files are not downward compatible. If you come with a new
> > software
> > which has extra strings, it would fetch into the first voice-only
> > entries.
> How would it do that? The first voice-only entry starts at number 0x8001.
> You'd have to get a quite a large amount of new strings before you'd risk
> that.

Ah, OK, I understood you that your delimiter is just floating ontop of the
LANG_ IDs. If it's in safe distance, we have the two-table approach.

> > So, requests to speak a new ID which is not present just gives silence.
> With
> > this new separation into LANG_/VOICE_ we need two "directory" tables in
> the
> > voice file.
> No, but you need to handle a (fairly large) gap in the index numbers. But
> you would already handle gaps, don't you?

Not in this way. Currently, the ID is directly used as an offset into the
directory. It is just checked against an upper bound, which is part of the
voice file header. Non-voiced IDs have a zero directory entry. This wastes 8
bytes per such entry, on the other hand saves storing the ID itself, but the
voice file is huge anyway. I'm not searching for an ID. I could either do that,
or split into two tables.

Either way, I agree to your approach of sorting the voice-only IDs into a
way higher range. This will overcome my resistance to introduce a lot more of
them, e.g. for spelling, file types, etc.


+++ NEU bei GMX und erstmalig in Deutschland: TÜV-geprüfter Virenschutz +++
100% Virenerkennung nach Wildlist. Infos:
Received on 2004-03-31

Page template was last modified "Tue Sep 7 00:00:02 2021" The Rockbox Crew -- Privacy Policy