Last modified 7 years ago Last modified on 07/19/12 22:50:31

Known Limitations

These are known issues and limitations of AMIS version 3.0

Searching text in an online or networked book

Text search not available for online books. For online books, this is because of a lack of a package manifest for 2.02 books. for local books, the book directory is searched for html files and this is assumed to be the textual content available for searching. otherwise, we would have to process and sort a potentially large number of text references from the SMIL files.

Problems with text searching in networked books is an open, but unsolved, issue.

Seen rarely.

If you click the first page number of a chapter and start reading there, you can go forward by phrase but not backward! It will just go as far as the beginning of that page.

The ambulant log says:

prevPhrase: goto_node(<audio id="rgn_aud_0011_0022">) 
17:17:39 TRACE goto_next: time_node(par, <par id="rgn_par_0011_0001">) not active, starting after it

Which means something like this:

The document looks like

<!-- chapter 5 --> 
<par id="rgn_par_0011_0001">
        <audio id="aud1"/> 
        <audio id="rgn_aud_0011_0022"/>

<!-- page 84 --> 
        <audio id="aud2"/> 


So you're at aud2 and you want to go to the previous phrase, which is calculated correctly as audio rgn_aud_0011_0022, but it won't play that because the container par is inactive.

Section Labels

AMIS does not play section labels. It just loads the section and starts playing it when you click on it. If the label for a section is after the start of the section, then the section label will be heard only after the preceding content has played. Example:

Book layout:

Page 14
Section Three

Phrases and paragraphs... et cetera.

SMIL file:

    <par id="page_14">
       <audio src="file.mp3" clipBegin="0s" clipEnd="2s"/>
    <par id="section_three">
       <audio src="file.mp3" clipBegin="2s" clipEnd="4s"/>

NCX file:

  <navPoint id="ID0EFKAE" playOrder="4">
      <text>Section Three</text>
      <audio src="file.mp3" clipBegin="2s" clipEnd="4s" />
    <content src="file.smil#page_14" />

When you choose "Section Three", you will hear "Page 14 first", and then "Section Three".


A user may have up to 50 bookmarks for a given book. Bookmarks can only be deleted by editing the *.bmk file. Each book has its own *.bmk file, found in c:\documents and settings\all users\application data\amis\settings\bmk .

Slow Navigation

Is your SMIL file huge? Maybe the problem is the same as what is described in ticket #189.

Nokia PC Suite conflict

This bug report notified us of the problem. We were able to confirm it, and also reproduce it outside AMIS by running (and crashing) Ambulant with DirectShow? instead of FFMpeg. It appears that Nokia PC Suite conflicts with DirectX (or DirectShow?), which is unavoidably used in AMIS.

Update: it turns out that the conflict is with the "Emuzed mp3 (source) decoder" codec, and if you remove it, the problem is resolved. Here is a free filter manager for DirectX, which can be used to disable codecs.

SAPI conflict

There has been at least one case where uninstalling sapi51redist, left by an earlier beta of AMIS 3, stopped AMIS from crashing. If you have this sapi51redist package installed and you are using Windows XP or Vista, it is recommended to uninstall it by going to Add/Remove? Programs under the Control Panel.

Phrase Playback

When going to the previous phrase, sometimes a small part at the beginning of that phrase gets cut off. This is due to a bug in Ambulant (see ticket #217).

Also, problems have been observed on certain machines with phrases in the middle of large books. There are gaps in the playback (see ticket #220).

No audio speed controls in "compatibility mode"

When running in "Compatibility Mode", AMIS does not offer speed-up of audio. This applies to pre-recorded MP3s as well as TTS.

Compatibility Mode was created so that users who experience DirectX conflicts on their machine can still use AMIS. For the record, here is what Compatibility Mode is:

# Invoked by a preferences file called amisPrefsCompatibilityMode.xml # Means that self-voicing is on but uses TTS # Means that book audio is rendered through FFMpeg # Speed up (and probably slow-down, when we implement it) is disabled* # Is internally called "Safe Mode"

  • Theoretically, it is possible to have the TTS rate control available. However, since there is no timescale for FFMpeg, the speed control buttons in AMIS would have no affect on pre-recorded book audio, only on TTS-rendered things (self-voicing, text-only books). This would be quite confusing for users. To do it right, we would have to refactor the UI to have separate speed control buttons that only appeared some of the time. For now, Compatibility Mode means no timescale at all.

Problems with the Search for books dialog

There are two known issues, both related to the threading and queuing of self-voicing:

  • Can't cancel search
  • After search is complete: need to press alt+tab to resume keyboard function

Slow book loading

Because self-voicing and book-loading are both in the main thread, self-voicing slows down load time for large books significantly.

Online books unstable

Some instability has been observed with online books, especially when using restricted user accounts.

DAISY 3 display problems

Known issues that can be solved by installing java:

  • no images
  • raw xml text display
  • text displayed but fontsize and styling disabled

AMIS crashes after closing when no book was open

This can be seen on certain systems. Open AMIS, do not open a book, and close it. It might crash. If you want to reproduce this, be sure that AMIS is not automatically opening a book on startup (if it does: close that book and relaunch AMIS. Then close AMIS and see if it crashes).

Links in the text of DAISY 3 books

As described in Ticket #282, links in the body text of DAISY 3 books do not work.

Stylistic changes have no effect after 30+ times pressed

Stylistic changes, such as page contrast and font size, can be applied no more than 30 times. This is detailed in ticket #286.