Heritage Live uses the Wowza Streaming Engine on the back end to facilitate ingestion of external video and audio sources, transcoding of those sources, and publication to an external site. To setup GoCoder as an ingestion source for the Wowza Streaming Engine hosted by Heritage College and Seminary, please use the following instructions and settings.
The Wowza GoCoder is supported on iOS and Android mobile devices.
- Download the Wowza GoCoder app from the app store on your device (i.e. the Apple App Store or the Google Play Store).
- Once the app is installed, launch it and it will show you a brief legend for each of the apps buttons.
- Open the Server Info section. The settings are as follows:
Host -> Server: streams.heritage-theo.edu
Host -> Port: 1935
Application -> Application: HeritageLive
Application -> Stream Name: can be anything that will identify your device in the system. Use only letters with no spaces.
Login -> Use the Publisher Name and Password sent to you by the Heritage IT department.
- In the Video Options section of the application you can change what is being sent with your stream, such as video & audio, video only, or audio only. You can also change video encoding settings such as the size. For primary video we will be starting with a 720p stream and re-encoding that using the streaming engine on the server. For secondary source such as a secondary classroom, using a lower resolution such as 640×360 would be appropriate. The key is to use a sufficient bit rate. The bit rate setting can be found on the main screen in the lower left corner.
- Once you’ve got all your setting made, try it. Punch the big red button in the lower right corner. If the app is successful in publishing the stream to the server the message will change from Connecting to Connected!
You’re done. Congratulations!
We first used the Wowza Streaming Engine with an Introduction to the Bible course taught by Gord Oeste in the fall of 2015.
Sometimes, Outlook 2007 briefly looses its connection with the back end Exchange 2010 server. This happens despite a healthy network connection on the workstation. If this occurs, there are two ways to get around the issue temporarily.
Enter your fully qualified domain username and password
In the password dialog that has so rudely interrupted your workflow, enter your fully qualified username and password into the fields provided. A fully qualified username is one that also includes the domain name that the user is associated with. For example, if my username is stupendous and my domain is marbles.local, the the fully qualified username is as follow. Note the back slash.
Putting this into our context, my fully qualified username for the Heritage network is as follows. Again, note the back slash.
Next, enter your Heritage account password into the password field.
It's also wise to check the Save Password checkbox so your updated credentials are cached by Outlook.
Then hit OK.
Close Outlook and reopen it
This is as straight forward as it sounds. Just close Outlook and reopen it. It will use cached credentials based on your most recent Windows login to re-authenticate with the Exchange server.
If that doesn’t work
In the event that neither of those things work, logging off and logging back into Windows will force all of your credentials to be re-cached.
The dropped connection is characterized by a message in the bottom right corner of Outlook. It will say something like:
- Password Needed, or
- Offline with Microsoft Exchange.
A successful connection message will read:
- Connected to Microsoft Exchange.
- Online with Microsoft Exchange.
So, make note of the message that shows up in that location.
One-Off Receipt Processing
Add receipt data to the tblReceipts table
- Receipt number (increment from previous number).
- Date the donation was received.
- FID (The ID of the person/company from the persons table.
- Amount of the donation.
- Check off if tax deductible. Most will be.
- Check off Annual Receipt.
Add ReceiptID into the donations table
For the donation, update it’s record in the tblDonations table.
- Find the row that corresponds to this donation by cross-referencing the FID.
- Add the ReceiptID from the tblReceipts table to the receiptID field.
Run the report
Run the Report rptReceipt which grabs the receipts generated for today. It’s formatted on legal sized paper.
Typically, I will print or export this report to a PDF for the office staff to print onto our formal receipt paper.
It’s important to catalog our published media so that they are properly organized, easy to find later, and able to be backed up. The Media folder contains directories for each year. Your media should be saved inside the directory corresponding to the year it was published. A folder should be created for each event/date with the following naming convention.
That way each entry will be sorted by date and easy to find later. Further the description helps for search-ability.
The location for our published media is:
A rough process for publishing media files is as follows…
1. Production - i.e. Capturing audio and video.
2. Save RAW footage to external USB hard disk.
3. Copy RAW footage to internal drive for editing.
4. Editing - compile final cut using an DAW (audio) or NLE (video).
5. Save the completed work to the Media folder.
6. Publish the media to Moodle or other web location.
Get Organized: How to Manage Video Files
For editors, how do you keep track of/organize all of your raw video footage?