Is it possible for compiled chapter.wav files to be more intuitive and resolved programmatically?
E.g. an oral MAST event has completed Mark 1 for the language group San Chi. San Chi's 3 letter group is MLC. The file is stored /mlc/ulb/mrk/01. Perhaps auto-generate the file: mlc_mrk-01.wav?
That way, we don't have 30 files all called "chapter.wav."
Is it possible for compiled chapter.wav files to be more intuitive and resolved programmatically?
E.g. an oral MAST event has completed Mark 1 for the language group San Chi. San Chi's 3 letter group is MLC. The file is stored /mlc/ulb/mrk/01. Perhaps auto-generate the file: mlc_mrk-01.wav?
That way, we don't have 30 files all called "chapter.wav."