If there are any subdirectories in the incoming directory (/home/dmlserv/content/loader/audio/incoming/), then trying to save a recording container will fail if there are media files to process. The only workaround to this is removal of the subdirectories.
There is a bug where derivative files are forced to lowercase in the MediaObject record, but will ingest properly if uppercase. This causes a problem when trying to play the container because the file is not found. A workaround is to always make sure Wav files and derivative files are named using lowercase only.
If the derivative file uploaded to the Variations server is truncated, the save process may cause the digitizer window to hang. This is due to the mp4creator process getting stuck and never terminating. The faulty derivative files should be replaced with newly created derivatives. If Variations is acting up as a result of this problem, a restart should clear it up.
This is due to a bug in the JRE that is included in the Variations client. There is no current plan to provide a workaround.
See the entry in Java Bug Database for more information: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6575395
This is the result of a bad update process for Quicktime 7.2. This can be fixed by downloading the Quicktime 7.2 update from Apple's website (http://www.apple.com/support/downloads/quicktime72formac.html) and rerunning the update.
Mac OSX 10.5 (Leopard) has a search embedded in the help menu of every application. This search returns links to menu items within Variations and links to non-Variations help documentation. Currently, Variations does not make use of the Mac OSX help documentation features. This results in Apple's default functionality which is to return any help documentation results in the help menu search. There is no workaround.
On Mac OSX, Apple Key-Space causes Mac Spotlight search to open and does not cause the Variations player to pause playback.
Running bin/generateAccessPage.sh from dmlserv's home directory as dmlserv will fail due to missing configuration in conf/client/dml.conf. To fix this, copy the following name/value pairs and modify for your institution from conf/server/dmlserver.xml:
<SystemProperty name="dml.z3950.Container.enabled">true</SystemProperty> <SystemProperty name="dml.z3950.Container.host">es33.uits.indiana.edu</SystemProperty> <SystemProperty name="dml.z3950.Container.port">2200</SystemProperty> <SystemProperty name="dml.z3950.Container.database">Unicorn</SystemProperty> <SystemProperty name="dml.z3950.Container.field.id.name">any</SystemProperty>
conf/client/dml.conf should then look like the following regarding these properties:
dml.z3950.Container.enabled=true dml.z3950.Container.host=es33.uits.indiana.edu dml.z3950.Container.port=2200 dml.z3950.Container.database=Unicorn dml.z3950.Container.field.id.name=any