Known Limitations

This release of Obi 1.1 has some limitations in it which are known. This list covers them. These will be removed in future releases.

GUI related performance issues in large projects

When size of project increases (about 12 to 14 hours), some performance issues related to GUI are observed. These are visible while operations like splitting / merging phrases, splitting /merging sections and phrase detection take place. It is mainly dependent on the number of sections and phrases in project and is not that much related to size of audio.

DAISY 3 Export related performance issues in large projects

While exporting a large project to DAISY 3 DTB ( more than 14 hrs), export starts consuming more time. User may have to wait for several minutes for the export to finish.

Limited phrases visible at a time

Currently Obi allows atmost 700 phrases on screen at a time, while phrases in all other sections are hidden and user explicitly needs to use F5 to make these hidden phrases visible.
This process will be made implicit in future releases so that the user does not have to bother about using F5 again and again when he wants to see the contents of a section.

Inability to select multiple items collectively

One can select only a single item at a time in Obi. This means that only a single phrase or a single section can be selected. So, operations like copy, paste, merge, delete etc. operate on a single phrase or a single section.

Inability to import a DTB into Obi

Current version of Obi is not able to import a DTB and open it in xuk project. Due to this, there is a limitation that a DAISY book created in another DAISY production tool can not be openned and editted in Obi.

Size constraints in content view limits maximum number of sections and phrases visible in project

Currently content view can show upto 208 sections and about 450 phrases in each section with default zoom level. For making more sections and phrases visible, zoom out has to be used so that the content view can accomodate them.

Pipeline-lite does not work with non western characters in file path

Pipeline-lite is not able to operate if there are non western characters in path of the file. It is recommended to keep non western characters away from the file paths on which Pipeline-lite needs to work.
For Obi 1.1, this means, DAISY 3 export folder and DAISY 2.02 export folder have to be placed at a location so that there are no non western characters in its path. This only affects validation, mp3 encoding and fileset renaming process and does not hinder normal operations of book authoring.

Error messages are not so user friendly

Error messages in message boxes when some invalid operation is done, give information. But these messages are not so user friendly, especially the exception messages.
These will be replaced with more user friendly text in future.