Pipeline 1 Frequently Asked Questions

Pipeline 1 Frequently Asked Questions

What is DAISY Pipeline 1?

DAISY Pipeline 1 is a suite of tools designed to meet the varied and increasing production needs of the DAISY community by providing a cross-platform, customizable and extensible framework for document and DTB related transformations. It supports the migration of digital content to various formats efficiently and economically, facilitating both production and distribution of DAISY DTBs.

Who is the targeted audience?

DAISY Pipeline 1 is primarily addressed at organizations and companies involved in DAISY production. However, its use is not restricted to the DAISY membership.

Who is working on DAISY Pipeline 1?

Pipeline 1 is a collaborative project hosted by the DAISY Consortium, with numerous organizations participating and contributing to the development. Most contributions are open source, and reside at the DAISY Pipeline 1 development site.

How much does it cost?

Nothing! DAISY Pipeline 1 is free and open source software available under LGPL, the GNU Lesser General Public License, to any organization, commercial company or individual.

On which platform can I run DAISY Pipeline 1?

DAISY Pipeline 1 uses cross platform technology and is currently available for Windows (98, Me, XP), Mac OS X (PPC or Intel), and Linux.

Can I contribute?

Of course! DAISY Pipeline 1 is an open source collaborative software development project and much functionality is still needed. If you would like to join the DAISY this community please use the Contact Us Form

Where can I download DAISY Pipeline 1?

Find out full download information from the download and installation page for Pipeline 1.

How can I install DAISY Pipeline 1?

Installers are now provided for both Windows and Mac OS X. For further detailed explanation, be sure to read the installation instructions.

Do I need to install any third-party software to use the DAISY Pipeline 1?

In order to run Daisy Pipeline 1, you need to have the Java Runtime Environment (JRE) version 5 or later installed on your system.

Is DAISY Pipeline 1 compatible with screen readers?

The DAISY Pipeline 1 GUI is built on technology using Microsoft Active Accessibility (MSAA) APIs to render user interface elements accessible to assistive technology. It has been successfully tested with popular screen readers such as JAWS and Window-Eyes.

Is there a workaround for known accessibility issues?

Some scripts are available for JAWS in the code repository to improve the user experience on the DAISY Pipeline 1 GUI with this screen reader. These scripts also provide some help with the most complex controls.

Can I customize the keyboard shortcuts?

Almost all of the key bindings available in the DAISY Pipeline 1 GUI are configurable in the Keys preference dialog. This dialog is accessible via the Window ? Preferences menu bar item.

How do I access the browser in the documentation perspective?

You can press the F6 key to toggle between the documentation index and the corresponding html document.

Why isn’t the Windows installer in English?

This was an error introduced in the 20071221 release, which was fixed on January 4, 2008. Please re-download the Pipeline.

No Java virtual machine was found. What can I do?

This may come from either an incomplete Java installation, or the JVM location not being listed in your system path. If you haven’t done so already, please download a Java Runtime Environment (JRE) and install it.

Make sure your system PATH points to the installed Java runtime—on Windows, the PATH is accessible via Control Panel > System > Advanced > Environment Variables

Alternatively, you can manually specify the location of your Java runtime by adding following lines to the DAISY Pipeline.ini configuration file, located in the installation directory:



Why do I get Out Of Memory Errors while running DAISY Pipeline1?

This is a technical limitation: some Java Virtual Machines (JVM) put restrictions on the total amount of memory available on the heap. You can tell the JVM to let the heap grow to 512 MB by adding the line:


to the DAISY Pipeline.ini configuration file, located in the installation directory

Run java -X for the list of options your JVM accepts.

The message view says Unable to load script <a script name>.taskScript, what can I do ?

These unable to load warnings occur because the path to some third-party executable (Lame, Python) has not been set. These paths are configurable in the Paths preference dialog that can be reached from the Window ? Preferences menu item. For detailed explanation please refer to the installation documentation.

Why does the New Job Wizard shows the error message Unhandled script when I select some scripts?

This message is due to an error when loading the corresponding scripts. See the FAQ item above

If the problem is about a custom script you’ve added to Pipeline1, it can come from any kind of error in this custom script (for instance an incorrect parameter name).

In the documentation view, why can’t I access the browser widget with the TAB key?

TAB is normally used for moving to the next control in the GUI and Shift+TAB to the previous control. However TAB is also used to jump to the next control inside a Web browser. Once in the browser control, it is difficult to leave the browser using TAB because it will jump to the next link in the html page instead of jumping to the next Pipeline GUI control. It was therefore decided to remove the browser control from the TAB list, and to use the F6 key for toggling between the documentation index and the documentation page.

Note that the same behaviour can be experienced when browsing the CHM Help document with a topic tree view on the left pane and the corresponding html document on the right pane.

How do I export the Pipeline logs?

Pipeline 1 messages and the error log can be exported as text files on your file system. To export Pipeline 1 messages, go to the Messages View and use the Export Messages button on the view toolbar.

To export the debug log, go to the Error Log View (Window > Show View > Error Log) and use the Export Log button on the view toolbar.

Tags: Pipeline 1