Forum

My fault the website address is http://www.houseofjacob.us

You need to upload the sermon to your website and make it visible to the public. Your web host likely has some kind of space limitation, i.e. your website account is allowed 25mb or 1gb or something. You will then have to manage this carefully, especially as sermon files can quickly fill that space up. Compressing your sermons will allow you to fit more on the site and allow visitors to download them more quickly, but the audio quality is lower. The churches I know encode the sermons anywhere from 32 to 96 kbps in the MP3 encoding, we use a bitrate of 32kbps to save space and a typical sermon file is 6 to 10mb.

You can upload the sermon three ways, inside the Sermon Browser file area, in the media area, or directly through FTP. Since many hosting packages have an 8mb upload limit per file in PHP, I recommend uploading through PHP to a sermons folder. This also avoids some of the permissions problems with uploading through the browser. (FYI FileZilla is an excellent free FTP tool for uploading and downloading files)
Once the sermon is uploaded, then you can link to it inside Sermon Browser. If you specify the same path in Sermon Browser for your uploads, you will already see unlinked files you just uploaded.

I am willing to help further on the scripture display, but you should concentrate first on getting the MP3 uploaded and working. Then you can tweak which version for the passage display in the Templates section of Sermon Browser.

Hey Scotlynn,
I finally got the upload on the Sermonbrowser site but there is no audio. What am I doing wrong now????

100mb sermon files seems huge to me. The sermon file size is pretty important for a couple of reasons.

1) You will quickly fill up your hosting account with large files. 20 sermons will take 2gb.

2) Visitors will have more problems downloading and streaming these larger files, especially with slower connections. A 30 hour sermon encoded at 32kbps will generate a 5 to 6 mb MP3 file, which is workable for even a dial-up connectionm as the kilobytes/minute is low enough that the sermon can be downloaded in the background while it is playing in their browser.

3) You are placing additional strain on your hosting server by streaming out huge files. If 5 people listen to a 5mb file, it requires the server to send out 25mb of data. If 5 people list to a 100mb file, it is 500mb of data, 20x more work with reduced bandwidth for everything else.

Look into get Audacity as a recording and editing package. You can record with your existing setup, or record directly into Audacity. If you install the Lame encoder in Audacity, you can create MP3 files directly from Audacity and specify the output rate before you export. We record directly into Audacity, which allows us to see the recording quality and control it better. Here is an example (this is a screenshot I just found on Google images, so it is just a random example):

Then we clean up the recording after service, clipping off the front and back and then we export it to MP3 at 192kbps for CDs and for our archive, and then we export the same file at 32kbps for our website. The first time we create the MP3, it asks for the tags, and we carefully enter the Author, Title, etc… making the file ready for podcasting as well. And sermon browser can create a sermon record from those same tags when we add it to the website.

We upload the web mp3 to our Sermon Browser upload folder, then go to Sermon Browser –> Files and tell it to create a Sermon Record for this new file, we fill in the remaining fields (Bible passage, Series…) and we are done. Very very smooth and professional result.