Tobi version 1.5 brings numerous improvements and bug fixes (as described in the change log), and ships with a robust editor for image descriptions that conform to the DIAGRAM format.
This is an intermediate release in the sense that the image description standard is still being finalised, but also because within the next few months, Tobi will enable audio narrations of the image annotations themselves (in addition to the main "book" content). The DIAGRAM format supports multiple image descriptions in order to cater for various needs (e.g. tactile picture, simple versus long text descriptions, alternative illustrations, tour/overview), and Tobi will eventually enable audio descriptions (i.e. voice recording) across the board.
This, in addition to the upcoming support for EPUB3 Media Overlays (DAISY-like text/audio synchronisation for e-books), means that 2012 will be an exciting year!
This short guide is provided to get started with image descriptions in Tobi. We also recommend this small DAISY 3 DTBOOK ("Great Painters", 600KB) as a starting point to experiment with the new editing features.
For further information about the image descriptions data model, please visit the DIAGRAM Center website.
Finally, here are a couple of screenshots showing the new user interface used to navigate images in the book content:


The main focus for this update is performance improvements. Thanks to the joint work between the Obi and Tobi projects, the common underlying Urakawa SDK library has been dramatically enhanced, and now enables much faster opening and saving of large project files. In addition, the responsiveness of the document pane in the Tobi user-interface has been greatly improved thanks to optimizations in the audio recording workflow. This results in an overall smoother recording experience, with less lag and potential delays on slower machines.
Last but not least, Tobi can now import Obi projects ("*.obi" files). This feature is based on a complex XSLT2 XML transformation, so the (free) [Saxon.NET "home edition" libraries](http://saxon.sourceforge.net) must be installed separately. This new feature means that already-existing audio-only content can be "upgraded" to full-text full-audio projects. Tobi currently only offers basic text editing (no structural modifications of the document are possible), but this is sufficient to author the text labels associated with audio phrases originally recorded from within Obi.
We are looking forward to hearing your feedback !
Regards, Daniel
Main stream publishing standards are being defined by ongoing DAISY-EPUB revision for facilitating accessible publishing in main stream, encouraging alignment of Tobi’s development path according to this transition.
The plan of development cycle is to implement the EPUB multimedia (EPUB 3) authoring work flows in Tobi, evolving it into an EPUB authoring tool. As an EPUB authoring tool, Tobi intends to cater to needs of broader audience and will be able to perform an important role of facilitating transition of DAISY membership to new EPUB 3 standards.
Along with providing support for new EPUB 3 standards, the development team will be working on implementing new features in Tobi, one of the most important being implementation of image description workflow in partnership with the DIAGRAM project. This will enable Tobi to author accessible graphics and provide access to diagrams, images and graphs to print-disabled.
Tobi team will like to hear comments, requests, feedback from existing and potential users of Tobi, in order to understand the real life expectations from the tool. We may not be able to satisfy your requests immediately but active feedback will help us define the development path of the project in long run.
Thanking all of you for your active support.
Avneesh Singh (on behalf of Tobi team)
asingh[@]daisy.org
Since Tobi v1.0 was released (only a couple of weeks ago), we published a number of application updates to fix minor bugs and to improve existing features. During this process, the Tobi forum has been the main communication channel between end-users and developers / support staff. In some cases, we even added new functionality to answer urgent needs. Normally, we would register feature requests into the project tracker for version 2.0 (i.e. "future directions"), but sometimes the well-defined scope and relatively low implementation costs justify an immediate response. - By the way, many thanks to users who are actively putting Tobi in trial mode within their respective organizations, we will continue to address your queries in a timely manner. -
It comes as no surprise that not-so-minor changes are still being made to the application, because of the low community participation in the Alpha, Beta and even Release Candidate phases of the project. Now that Tobi is gaining momentum, the feedback is flowing-in and we sometimes fix major issues that we didn't catch earlier, during our internal testing (typically, problems with computer-specific audio drivers, system-dependent errors, etc.).
Thanks to Tobi's deployment method (based on Microsoft's ClickOnce technology), we are able to "push" application updates directly to an existing end-user installation, and the payload is usually lower than 1MB (out of the 9MB full application download). Should you have decided to skip an available update (when prompted at Tobi's startup), ClickOnce will stop notifying you for an entire week. The only way to update Tobi during this period is to visit the "download" page and click on the appropriate link in the "Install and launch" section (this forces your local Tobi installation to update itself). Please note that this "limitation" is outside of our control.
Recently, we published application updates quite frequently, so we encourage you to take a look at the Tobi change-log to see what is going on. In future versions of Tobi, the ClickOnce dialog prompt will offer a direct link to the "change-log" page, or even better, it will display the description text corresponding to the update. In the meantime, please keep a bookmark of the Tobi website.
Last but not least, some of you may have been wondering about the logic behind version numbers. At the time of writing, Tobi has reached v1.3, which seems a little high given how fresh v1.0 still is ! Well, this is actually a technical mishap in our build script ... from now on we will stop incrementing the second digit for a while unless duly justified by a major feature update. Although this shouldn't create any problems per say, we apologize for the confusion it may cause.
Kind regards, Daniel
Although the current version of Tobi is primarily a DAISY 3 production tool, we aim to provide support for legacy reading systems that still depend on the DAISY 2.02 format. The recommended workflow is to run the DAISY Pipeline "DAISY 3 to DAISY 2.02" script against the fileset exported by Tobi. We recently wrote a short blog post on that subject.
It is worth noting that this Pipeline script is still in beta, so it is fair to expect some shortcomings. One known limitation listed in the "Input Requirements" section of the script documentation (i.e. "The first par of each zed smil file must be a heading") happens to be problematic in some cases when the initial DTBook XML is generated by the "Save As DAISY" addin for Microsoft Word (this production scenario has not been checked with the Open Office addin yet).
When the DTBook contains multiple docTitles ; typically, inside arbitrary levels of the XML document (which is valid as per the 2005-3 DTD ) ; the conversion to DAISY 2.02 fails. This has been discussed on the Tobi forum already. An easy workaround consists in manually replacing the docTitles inside the DTBook levels with appropriate headings (e.g. h1). Alternatively, it seems that the DTBook "fixer" Pipeline script could help, as it is successfully used internally by the Save As DAISY addins when producing full-text full-audio books.
We are currently evaluating ways to support these various edge cases. In the meantime, please let us know (via the forum) how you are getting on with DAISY 2.02 full-text full-audio production using Tobi. Many thanks for your feedback! Regards, Daniel
Dear Tobi users, the latest patch for the DAISY Pipeline includes fixes in the DAISY 3 to DAISY 2.02 "downgrader", and as a result it is strongly recommended to upgrade if you intend to produce publications that target legacy reading devices with no support for DAISY 3. Please take a look at this post on the Pipeline project blog:
http://www.daisy.org/pipeline/blog/daisy-pipeline-gui-update-patch-20100527
Regards, Daniel
Dear all,
Tobi version 1.0, the DAISY Consortium's open source multimedia production tool, is now available. Tobi produces full-text full-audio Digital Talking Books in the DAISY 3 Standard (ANSI/NISO Z39.86-2005). The DAISY Pipeline can be used to convert digital content to the DAISY 2.02 format for legacy reading devices.
Tobi's primary function is to facilitate the synchronization of text and narration, using live recording, by importing audio clips, or via the basic Text To Speech feature (TTS). Tobi provides an audio waveform editor with robust undo/redo, fast clipboard operations and the ability to author audio content at any level of the document structure.
Tobi 1.0 doesn't include an XML editor, but provides rudimentary text editing to fix minor document issues. Tobi imports DTBOOK documents that can be created using the "Save As DAISY" add-ins for Microsoft Word and Open Office, or by using conversion tools such as the DAISY Pipeline. Tobi can also import full text and audio DAISY 3 digital talking books.
Support is provided via the Tobi public forum: http://www.daisy.org/forums/tobi
Detailed information including a user manual can be found on the new Tobi project site at: http://www.daisy.org/tobi
Comments and feedback are welcome!
- 1 of 2
- ››