Importing audio already recorded?

Please forgive me for I am new to this program, and have not found a thread on this yet.

I have Bible passages already recorded (as one .wav file per chapter), edited and with a marker at the beginning of each verse. These have been loaded to MegaVoice players.

I’ve been using Adobe Audition to edit these files.

Is it possible to import the audio I’ve already recorded and put inside the HearThis database? If so is there documentation how to do this?

Thank you for the help : )
John

The SAB Help menu has links to Help PDFs with instructions.
People usually convert to MP3 (or smaller 3GP) for SAB.
We use MP3 saved as 64 kbps constant compression.
We use the Audacity program with Lame Encoder installed to convert WAV to MP3.
https://www.audacityteam.org/download
https://lame.buanzo.org/Lame_v3.99.3_for_Windows.exe

I think MikeB is talking about how you could get your existing recordings into SAB. But if I understand your question correctly, you’re wondering about splitting up your chapter-level WAV files into smaller WAV file clips (one per “block” in HearThis - where a block is typically a single sentence). There is no automated process that I know of to help you do this. If it’s a relatively small amount of audio, with some patience, you could use audio editing software (such as Audition or Audacity) to split it up manually. (There might be a somewhat more automated way to split it wherever you have marked verse breaks, but unfortunately this will probably not correspond perfectly to sentence breaks.)

It’s also possible that you could come up with an approach using Aeneas to identify alignment between the text and audio, and then apply some process that would split it up. I certainly think that would be technically possible, but I don’t know of any single software solution that currently exists to achieve it. I will consult with my local Aeneas expert when I get a chance to see if he has any more concrete ideas.

If you do come up with an approach, I think I can tell you how to name the files and where to put them so that HearThis can see them. (Even that can get a little complicated, because of the settings in HearThis that allow you to skip recording of section heads or other fields that you don’t want to record.
Unless you come up with a good automated approach, if it’s a lot of recorded material, you might be better off to live with the hassle of having stuff in HearThis appear to be unrecorded, and manually copying in the recorded chapters into the correct folder structure after publishing from HearThis.

I’m not sure I’ve been very much help, but please reach back out if you need to. (We might need to establish a live connection outside of the forum to more fully understand your specific needs.)

Thank you MikeB and Tom for your help.

While I currently only have about 10 chapters recorded, I am looking to help other missionaries record Bible and other audio in their different tribal languages. I have a system where I am able to have someone read a chapter, then I edit it following the text, and end up with one .wav file per chapter. I have a nice shotgun mic and record to a MixPre6, giving me a lot more control over the audio quality. It’s not too much work to select each verse, save as a new file (Audition: Shift Option C on Mac), save as a .wav file, move to the next verse.

I like the HearThis workflow for the missionaries to record more after I’m done, a very good solution for them. So it would be nice to have HearThis configured for them when I leave so they can continue to add to what’s been done already on their own.

I would be interested in the file naming / structure, at least, to see how that is set up.

Thanks again.
John

When you say, “it’s not to much work,” did you mean, “it is too much work”? We aren’t going to be able to provide a way to do import at this time. For one thing, there is no one working full-time on HearThis development. (I do support it and do bug fixes and small enhancements from time to time, but it is just on e of the products I work on.) Additionally, your workflow is not really in scope for the intended use of HearThis. I’m not saying you can’t or shouldn’t do it, just that you’ll kind of be on your own for coming up with a process that makes it possible. Although recording sentence by sentence might be slower (and might not always result in a really smooth flow without some post editing), it is an approach that allows users to work on their own without a lot of expertise in audio processing software. And it allows for a simple approach to re-recording a short clip when they make a mistake. Recording a whole chapter without error is difficult even for very proficient readers. So unless someone can use Audacity or Audition to remove the mistakes later, there’s little hope of ever getting a high-quality recording. I am not a recording specialist, but from what I know of field recording, it is my understanding that outside of the world of trained professional voice actors, it is not common to attempt to record very large clips consisting of lots of sentences. Since your process appears to involve the use of HearThis as a sustainable approach to recording after your gone, you might consider using the time you have with them helping them to learn the program well and passing along as much knowledge as you can about how to produce good quality recordings.
HearThis keeps its data in ProgramData\SIL\HearThis. (Although this is not a secret , we intentionally don’t make a huge point of telling users about this because we want o discourage them from accidentally doing things that might mess up their data.
Finally, I was able to confirm that using Aeneas, you can potentially generate usable timing files that ffmpeg could use to split up the audio into smaller clips. It will almost certainly not be perfect, so it will require some manual tweaking. It will probably easiest to do this using Aeneas within Scripture App Builder, but it does have a command-line interface if you want to try to set up batch files to automate this.

Thank you Tom. That’s very helpful.

“Not too much work” means while it’s a little cumbersome, it is something I would do - something done in auto-pilot mode : ) Once a keyboard shortcut path is established, it goes rather quickly.

I agree it may be good to just start in HearThis on these new projects so after I leave they are up and running.

You have been a good help in my thinking through my workflow and gives me more information to come up with the best solution.

I do appreciate your work and those who work with you creating these tools to get the Gospel out. A huge ministry and impact!

Great. One thing we have talked about doing (and though it hasn’t happened yet, it wouldn’t be too much work) is making it possible to open the current clip in HearThis using your default (or perhaps a specified) audio editing program. That would at least make it simple to do a little ad-hoc cleanup on particular clips.

1 Like