GithubHelp home page GithubHelp logo

daisy / amis Goto Github PK

View Code? Open in Web Editor NEW
6.0 6.0 2.0 448.26 MB

AMIS (Adaptive Multimedia Information System)

Home Page: http://daisy.org/amis

C 1.03% Shell 0.03% Perl 0.05% CSS 0.37% XSLT 2.93% JavaScript 1.59% C++ 88.33% Objective-C 0.10% C# 0.04% Python 1.65% Batchfile 0.30% NSIS 1.42% Makefile 0.04% Clarion 0.17% HTML 1.95%

amis's People

Contributors

danielweck avatar marisademeglio avatar tddpirate avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

amis's Issues

Clean-up source code

Make sure C++ code style conventions are followed. Add logging, remove trace wherever not necessary. Remove unused source code.

timescale does not slow down to 1x

Press speed-up 3 or more times and see that pressing slow-down as many times as possible does not return the speed back to 1.0. Tested on XP in debug mode.

Fix relative text searching

AmisCore needs to be able to have only SearchNext and SearchPrevious as public text searching functions. The initial search (SearchFullText) to establish criteria and position needs to be absorbed into the other functions.

crash with pipeline-generated zed books

AMIS seems to crash after playing a pipeline-generated book (zed book with mp3s) for a short time. The error given isn't traceable through the call stack but looks something like "HEAP xxxxxx modified after it was freed".

playback broken when clicking a link in the browser widget (book content)

  1. Open the AMIS help file (i.e. the Pipeline-generated audio-only one)
  2. click on a URL (i.e. the AMIS website) => the embedded browser displays the page correctly
  3. click on an item of the TOC (left pane) => the browser widget is stuck with the webpage, it's impossible to get back to normal book playback

audio node gets skipped

Here is the recipe:

  1. Open the book at http://amisproject.org/temp/Skill_with_People_shortened.zip
  2. Go to the pages tab
  3. Choose page 2
  4. The next thing you will hear will be the phrase after the page 2 announcement. You never hear "page 2" itself.

What seems to be happening:

  1. The audio file seek times are correct.
  2. Ambulant does indeed try to go to the correct node.
  3. You can even hear it play a little snippet of the correct part of the audio file if you are stepping through the code.
  4. Then it tries to seek forward to the next node's start time. This is why the phrase after "page 2" is heard, but never "page 2" itself.

search for books dialog bug

steps:

  1. enter a search path
  2. press enter
  3. AMIS tries to automatically load from the list

it should be

  1. enter a search path
  2. press enter
  3. browse the list with the arrow keys
  4. press enter again to choose your selection

Somehow, the first "enter" keypress is getting passed through.

bug on closing help contents

Recipe:

  1. Help->Contents
  2. Then open another book from disk
  3. AMIS gets very confused

What's happening is that when the help contents are closed, AMIS tries to load your most recently-read book. However, when you try to open a book yourself, or if you didn't have a book open before you opened help, then weird stuff happens.

next/previous page controls

even if a book has pages, the next/previous page controls aren't highlighted as soon as the book is opened. this was observed with a save-as-daisy generated book.

thai encoding support

Note that AMIS has no trouble supporting Thai encoding; however, to make sure it works, an alias to TIS-620 must be added to the registry.

The installer should prompt the user to ask if they want to make this change.

AMIS is very slow when going to a SMIL ID

  1. Download readhowyouwant's Alice in Wonderland book
  2. Click a section or choose a link (far down = slower)
  3. Watch it hang

The problem is that ambulant's goto_node function is very slow when dealing with large numbers of nodes. Currently investigating this.

Pressing previous phrase too quickly makes AMIS hang

Steps to reproduce:

  1. Build AMIS in release or debug mode
  2. Open "Mountains_skip"
  3. Go to the chapter "...and getting down"
  4. Press "previous phrase" (left arrow) three times fast

The last message in the ambulant debug logfile (or output window) will be inside goto_node (or in one of the functions it calls).

Remember settings

* Page style
* Text style
* Font size
* Sidebar width
* Basic or Default view
* Volumes
* Speed 
* window size and position
* reading options (per-book)

Re-add commands used only by Jaws scripts

  • implement (these commands are always available)
    • ID_AMIS_FOCUS_ON_SIDEBAR
    • ID_AMIS_TOGGLE_AUDIO_SELFVOICING_PLAYBACK
  • implement (available when a book is open)
    • ID_AMIS_FOCUS_ON_TEXT
    • ID_AMIS_RESET_HIGHLIGHT_COLORS
    • ID_AMIS_TOGGLE_AUDIO_CONTENT_PLAYBACK

Write help contents

Prepare the following as full-text, full-audio books:

  • Help contents (including a short intro about AMIS)
  • Keyboard shortcuts (should be auto-generated from localization db)

Basic support for text-only books

In order to read books with TTS, it is necessary to disable audio element rendering. However, under ordinary circumstances, Ambulant would speed through the book. We want it to stop at each phrase.

Another thing we want is to have Ambulant skip audio nodes in case TTS rendering is taking over. There are situations in which the user would prefer to use TTS instead of the book's pre-recorded audio.

self-voicing and ambulant volumes are different

There are 2 audio preferences saved in amisPrefs.xml: tts-volume-pct and audio-volume-pct. The latter, audio-volume-pct, is used to save the state of both the self-voicing and ambulant book playback volumes. However, the effect of this setting is different on each audio player -- a value of, say, 55 in the amisPrefs file results in the book playback volume being reasonable and the self-voicing audio playback being barely heard.

Timescale broken on Vista

Timescale audio does not work on Vista Home Premium SP1. Neither the self-voicing nor the book audio could be made faster. This OS uses DirectX 10.

timescale crash under vista

Noticed in both Vista HP and Ultimate:

Press Speed-up four times
It works
Press speed-down four times
After each time, it works.
Then it crashes soon after the fourth press.

In fact, for Vista Ultimate, you only need to press three times up, three times down, then it crashes.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.