Armed with a batch of test audio prepared a few sessions ago, today I began the implementation of building the unique processes into Prism Exhilarated's Python software.

This started, suitably enough, with an update to the config file, adding in the necessary details for Xplorer's unique processes. Under the 'processes' entry, the track's two processes were added, each of which including the following details:

• A description (primarily for the console output at this time)
• The number of options
• The process's start time in the track (in milliseconds)
• An array of option filenames
• An index describing which of those files should be used for the default track

With that done I set about piping a rendition value (provided by through the command line or set to None) into the various audio construction routines. At this point though I realised the audio construction flow could use a revamp.

Previously, when triggering a track construction from the command line, the audio was unpacked first and then passed into the track construction function. This seemed like a clunky way to do this: surely unpacking audio should be done completely within the audio engine.

So I switched the flow around here, so the track construction function was called first, and unpacking audio occurred within it. As the side and album construction functions use their track construction sibling, this allowed those methods to be tidied up as well.