Loader software for automated imaging of optical media with Nimbie disc robot
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
dBpowerampconsolerip
doc
iromlab bumped version number Aug 29, 2018
.gitignore
LICENSE
iromlab-configure.py moved configure.py inside package Sep 5, 2017
iromlab-launch.py
package-pypi.sh set package repo to pypi Oct 25, 2017
readme.md included binaries are now installed in package directory, not the use… Jan 17, 2018
setup.cfg
setup.py added requirement of Isolyzer version 1.3.0 or more recent Jan 26, 2018

readme.md

Iromlab

What it does

Iromlab (Image and Rip Optical Media Like A Boss ) provides a simple and straightforward way to save the content of offline optical media from the KB collection. Internally it wraps around a number of widely-used software tools. Iromlab automatically detects if a carrier contains data, audio, or both. The content of data sessions is extracted and saved as an ISO image using IsoBuster. For audio sessions all tracks are ripped to WAV or FLAC format with dBpoweramp. Iromlab supports 'enhanced' audio CDs that contain both audio and data sessions. ('Mixed mode' discs, which contain 1 session that holds both audio and data tracks, are currently not supported).

ISO images are verified using Isolyzer. Audio files are checked for errors using shntool (WAV format) or flac (FLAC format).

The disc images/rips are saved in a simple batch structure. Each batch contains a batch manifest, which is a comma-delimited text file with basic information about each carriers, such as:

  • An identifier that links to a record in the KB catalogue.
  • A serial number (because carriers may span multiple volumes).
  • A carrier type code (cd-rom, dvd-rom, cd-audio or dvd-video).
  • A True/False flag that indicates the status of iromlab's imaging/ripping process.

These batches can be further processed into ingest-ready Submission Information Packages using omSipCreator.

Using Iromlab outside the KB

By default, Iromlab expects each carrier to be associated with a record in the KB catalogue by means of an identifier (PPN). This identifier is then used to fetch title information from the KB catalogue using a HTTP request. This effectively constrains the use of Iromlab to materials in the KB collection. To overcome this constraint, you can disable the PPN lookup by setting the value of enablePPNLookup in the configuration file to False. More details can be found in the setup and configuration documentation. If enablePPNLookup is disabled, the PPN data entry widget in Iromlab's data entry GUI is replaced with a Title widget, which can be used for entering a free text description of each carrier. See also the section about Processing discs that are not part of the KB collection in the User Guide.

Moreover, it would be fairly straightforward to replace the PPN lookup by some alternative identifier that is linked to another catalogue/database (especially if it can be queried using HTTP-requests).

Also, Iromlab is based on a pretty specific hardware/software setup (see sections below). However, most of the software dependencies are implemented using simple wrapper modules, so this is also something that could be modified quite easily.

Platform

MS Windows only. It may be possible to adapt the software to other platforms.

Hardware dependencies

Iromlab was created to be used in conjuction with Acronova Nimbie disc autoloaders. It has been tested with the Nimbie NB21-DVD model. It may work with other models as well.

Wrapped software

Iromlab wraps around a number of existing software tools:

  • IsoBuster (note: Iromlab needs version 4.1 or more recent!)
  • dBpoweramp, dBpoweramp Batch Ripper and Nimbie Batch Ripper Driver; all available from the dBpoweramp website. (Note: Iromlab wraps dBpoweramp's Nimbie driver binaries to control the disc loading / unloading process.)
  • cd-info - this tool is part of libcdio, the "GNU Compact Disc Input and Control Library".
  • shntool - used to verify the integrity of created WAVE files.
  • flac - used to verify the integrity of created WAVE files.

Both IsoBuster and dBpoweramp require a license, and they must be installed separately. Binaries of cd-info, shntool and flac are included in the iromlab installation, and they are automatically copied to the iromlab package directory during the setup process.

Documentation

Contributors

Written by Johan van der Knijff, except sru.py which was adapted from the KB Python API which is written by WillemJan Faber.

License

Iromlab is released under the Apache License 2.0. The KB Python API is released under the GNU GENERAL PUBLIC LICENSE. Libcdio, shntool and flac are released under the GNU GENERAL PUBLIC LICENSE. See the directories under tools for the respective license statements of these tools. dBpoweramp console rip tool: copyright Illustrate Ltd., 2017.