Child pages
  • Setting up and Running the MP4 Gui Encoder

This space has moved to IU's Confluence.
It is located at https://uisapp2.iu.edu/confluence-prd/display/iulV3/

Skip to end of metadata
Go to start of metadata

Setting up and Running the MP4 Gui Encoder

This convenience utility is a Java Application that wraps the command line Nero Digital Encoder (MP4).

Contents

Setting up the MP4 Gui Encoder

The MP4 Gui Encoder is a encoding tool that is used for the digitization and ingest process. Specifically the MP4 Gui Encoder is used for audio conversion from WAV formats to MP4. Currently the MP4 Gui Encoder is only supported for Windows and is installed as an additional program with the cataloger/digitizer client installation.

Installing the Nero Digital Encoder

  • Download Nero's AAC Encoder from http://www.nero.com/enu/technologies-aac-codec.html
  • Unzip the archive to your local machine
    • Extract the file to the location specified by the default configuration file:
      • The default directory is C:/Program Files/Nero/NeroDigitalAudio
      • The default encoder path is C:/Program Files/Nero/NeroDigitalAudio/win32/neroAacEnc.exe
    • Or, you can extract the file elsewhere and then edit Variations/Client/encoder.conf (see below) to change the neroAACPath.
    • Note that for 64-bit Windows, paths may need to start with C:/Program Files (x86)/ 

Testing the MP4 Encoder

All files necessary to run the gui encoder can be found in the Client directory. Included in this directory is encoder.jar which can be run from the commandline. Note that after the Variations client is installed, users should start the encoder using a shortcut either from the Start Menu or Desktop.

  • Running the Jar
    • Double click encoder.jar
      • The jar requires that encoder.conf (The configuration file) is in the same directory
      • A different encoder.conf can be specified in the jar file
    • The jar file will run similar to the example Running the Encoder

Configuration File

Location

  • Variations/Client/encoder.conf

Properties
The configuration file encoder.conf currently the following configurable items:

  • neroAACPath
    • This value should point to where you have the nero AAC encoder executable. (downloaded in the first step)

      For 64-bit Windows machines, you may need to change the Program Files directory in the path to Program Files (x86).

  • mp4creatorPath
    • This value should point to where you have the mp4creator executable. This value should be properly configured if the Variations client is installed in C:/Program Files/Variations/

      For 64-bit Windows machines, you may need to change the Program Files directory in the path to Program Files (x86).

  • bitrate.x (where x is replaced by a digit)
    • This value should be set to the bitrates that will be used at the institution. At IU, there are two set: bitrate.0=28000 and bitrate.1=192000. Note that the Nero Digitial Encoder has problems encoding at 256000 and 320000.
  • saveDirectory

    Make sure that this is set to a location where you have write privileges. On Windows 7, a user's desktop may not work.

    • This value specifies a default directory to save encoded files. If this property is not set, the default location is the directory of the wav to be encoded. The user is not given a choice of where to save files currently.
  • processingOrder
    • This property configures the order of encoding. For sequential processing, set it to "Sequential". The default is "Parallel".
  • upload.serverPath
    • This property can be set to the incoming directory Samba share on the Variations server to avoid having to copy the derivative files to the server as a separate step. Alternatively, it can be set to the relative path of the incoming directory through the Sftp mount.
  • upload.deleteLocalFile
    • If you would like the derivative files created by the encoder to be deleted upon sucessful upload to the server, set this property to true.
  • upload.type
    • Set this property to the upload protocol or comment it out if you do not wish to have the Variations Mp4 encoder attempt uploads. Valid values are "Samba" and "Sftp".
      For Sftp the following properties apply:
  • upload.sftp.hostname
    • The hostname of the sftp server
  • upload.sftp.username
    • The username to use to login to the sftp mount
  • upload.sftp.password
    • The password to use to login to the sftp mount

Logging Configuration

In Variations 6.0, debug logging was added to the encoder by default. This logging can be configured using the configuration file at Variations/Client/conf/client/encoder.lcf. The default location of the log file is Local Settings/Application Data/Variations2/encoder.log under the user's directory. In Windows 7, this default location is the same as AppData/Local/Variations2/encoder.log

Installing the MP4 Encoder

See Building the Client Installer for instructions on building digitizer client installers which create a Desktop shortcut and start menu item for the MP4 Encoder.

Running the Encoder

As of Variations 6.0 the encoder logs to Variations/Client/encoder.log.

Using the Encoder
(As mentioned before the encoder can be run with the encoder.jar file)
Make sure the bitrates have been specified in the configuration file

  • Search for a wave file to encode using the Browse button
  • Or drag and drop a file into the into the textfield
  • Click Encode
    • Encoding processes for as many bitrates as were specified should be started and individual progress bars created in the Active Encodes panel.
    • The number of active encodes is limited to the number of bitrates specified in the configuration file.
  • Use the Cancel button to stop all active encode
    • Hitting the cancel button will stop the file encoding and change the status of the Active Encodes
  • Once an encoding has finished, a Complete notice will appear next to the progress bar.

Next Steps

After you have completed the encoder configuration process, you can being building the installer at Building the Client Installer.

  • No labels