Although this does not at all deserve the name documetation yet, I hope this will help users to understand what SermonRecorder is doing for them...
The intention for developing SermonRecorder was to give churches a small, yet powerful tool to record the sermons on a PC. This process includes some special requirements:
Recordings are required for different destinations and thus different file types:
MP3 in high quality
MP3 for download (smaller in size)
WAV for further processing, etc.
files for directly recording Audio-CDs
mp3-Encoding of a 30 minutes recording can take some minutes. This can be pretty annoying after the service.
The idea was that many of these processes and requirements could easily be parallelized and automized. This was the beginning of SermonRecorder. :-)
All standard Windows sound inputs can be selected as recording source. ASIO devices are also supported, but I have not been able to test this axcept with the ASIOforAll driver, which emulates an ASIO interface.
The available interfaces are enumerated at startup and can be selected in the settings dialog. The user can detect if the right interface is set by watching if the signal meter in the main window acts on noise in the sound system.
Recordings are encoded and written to disk just-in-time, MP3 encoding is done using LAME.
There are 4 different destinations for the recording, which are written to at the same time:
mp3-High: A MP3 file in Stereo, bps can be set and is 128kbps by default.
mp3-Low: A MP3 file in Mono, bps can be set and is 32kbps by default. This is intended as size-optimized for download purposes.
WAV: A 44,1kHz, 16 bit Stereo PCM file for any use, such as postprocessing...
CD-Recording: A WAV file as the one above plus a cuesheet file, which can be used by CD burning tools to burn CDs directly.
MP3 ID3 Tags are used by default. Genre and Album can be adjusted to the user's needs in the Setup form.
The recorded files are written to temporary files in the first place, since the speaker's name and the subject may be entered during the recording and may be used in the final filename. At recording stop, all filenames are generated accordingly and the files are renamed.
If a required directory does not exist, it will be generated.
If a file already exists, the generated filename is extended, so that the files can be distinguished.
The available parameters are:
The speaker's initials in the parameter are filtered using the folowing criteria:
After these parameters in the filenames have been replaced at recording stop, a user-configurable replacer can be used to e.g. replace <space> characters by any desired character. I heard of a user who needed this in order to upload the recorded sermons to a cloud service,which didn't support space in file names.
The final file names and directories are then scanned for invalid caracters, which will be replaced by a "_".</space>
A freely configureable commandline call can be set up in the setup window, which will be executed after recording stopped.
All of the parameters above may be used, plus:
Using these parameters, it is e.g. possible to call a batch file which uploads the download mp3 file to the webserver and starts the CD burning Software automatically with the right files.