MinistryMedia.org

This is our last video email of the semester at DTS.

This was produced by the amazing team that I am blessed to work with. Ryan Holmes (Production Manager) and Jessica Holland (Producer) traveled to Stillwater, Ok to film this. Joey Woestman (Producer) edited the story and created this video. Jonathan Galloway (Audio Enginner) makes sure that we sound good.

Today my wife sent me a link to this site. Watch the videos. You will be very impressed.

It is very powerful. The stories are amazing. I especially liked the stories from Greg Ellis and Brian Welch.

Logos is Bible software and I have been using it since 1995. Over the years the software has added great academic and practical functionality to Bible study – as well as literally thousands of books to the library.  I originally purchased the scholar’s library (a big package with hundreds of books) and I have been adding to it since then. But since I switched to an Apple a few years ago, running Logos through a virtual PC has been a pain.

I have been trying out Logos for Mac since the alpha was released.  I have to admit – I am a Logos fan, but not a fan of running Windows in order to get to it.

I have been running Logos on my mac using Parallels for well over two years. But the problem is Windows. I really don’t like having to deal with Windows in order to get to Logos. Logos has a great library – but is also very slow.

This was the original concept icon for Logos for Mac

But now, Logos is native on my Mac – and I am a big fan. It runs much faster on my mac than it does in windows. Try searching for “God” in Logos on a Windows computer and you will need a pillow for the nap. But the Mac version – is so much betta.

Now my Greek and Hebrew don’t search correctly (hey, I am still using the beta) but for referencing the hundreds of books in my library. It is awesome. I am really looking forward to the actual release – which is soon!

Last night Logos sent me an email notifying me that they are now accepting pre-orders. The best part is that I only have to spend $59.95 to get the mac version of the engine. For a limited time Logos is offering a free upgrade if you purchase $250 worth of other products from their site.  I already have a huge library and my economy isn’t getting a bail out – so I’ll just stick with the upgrade.  As soon as I get my hands on a copy I will post a thorough review.

The amazing talent that I get to work with here at DTS produced this piece.

Ryan Holmes (Production Manager) and Joey Woestman (Camera) traveled to Green Bay and shot the footage. Jessica Holland (Producer) created this piece. She chose the best shots and great music. Ryan polished the piece in Color and Jonathan Galloway (Audio Engineer) makes sure that is sounds great.

Here is another video created by the amazing people that I get to work with at DTS.

We shot this interview in our basement studio. Jessica Holland (Producer) created this story. She found perfect B-Roll footage from the actual civil war in Kenya. We purchased the footage from ABC news. She chose the music and created a great story. The still images were given to us with permission to use – from the talent.

Apple invited me to a preview and demo of Final Cut Server early in May at SMU.

Could the wizards of Apple come up with another magical tool to make all of our lives better? It seems as if they have tried.

Final Cut Server is Apple’s response to the industry’s cries over asset management. The press release given by apple was:

…powerful software solution for media asset management and workflow automation. A scaleable server application, Final Cut Server automatically catalogs large collections of assets, allows searching across multiple disks and SAN volumes, and enables viewing, annotation and approval of content from anywhere using a PC or Mac. “With the introduction of Final Cut Server, collaboration just got a whole lot easier for millions of editors, producers and clients who work with Final Cut Studio,” said Rob Schoeben, Apple’s vice president of Applications Product Marketing

Anyone who works with multiple Final Cut projects deals with the management of assets. From offline files, to missing assets, red areas in your timeline – FCS tries to alleviate this by doing the work for you. It allows you to catalog and search your assets via meta data and drag resources from project to project. The interface is separate from Final Cut Studio (not really integrated) – which is a plus and a minus.

In a production workflow where number individuals might work on the same project,FCS tries to bridge the gap between editor, producer and reviewer through it’s online interface for reviewing, commenting and management.

The demo was performed at a distance. It was installed on a laptop and running on a machine that we couldn’t actually touch. The interface was shown to us on a project – we couldn’t login and play with it ourselves(like NAB – back when Apple did NAB). I don’t think that we would have actually wanted to touch it – since the Apple rep kept saying “that button is supposed to do this – but it keeps crashing on me”.

From a philosophical standpoint, it looks like a great idea. But as I look at the backend, it looks like iTunes/iPhoto library for my video assets. This isn’t a bad thing, unless you need to find the files by using finder. iTunes and iPhoto work because they use meta data. Meta data (descriptive information) is used to describe content. If I place a picture of a chicken in iPhoto – it doesn’t know it’s a picture of a chicken unless somewhere I have typed the name “chicken”. The same applied to assets in Final Cut Server. Unless someone painstakingly adds meta data descriptions to all of your assets – you will not have a clue which video is of a car and which video is of – my chicken.

Final Cut Server resolves this by its “Automatic Asset Cataloging”. This process is supposed to scour your server (or servers in our case) and import all assets that it finds. If a piece of media is associated with a final cut project and sequence – it is supposed to be able to import the meta data from your project files. All of those descriptions that you have placed on subclips and captures – will be added into your assets when they are imported into FCS. This sounds great!

The client (the application that you actually use on your computer) is built in java. It is cross-platform – so it runs on both Mac and PC. It supports drag and drop with asset and all of the index information is stored on the final cut server.

Cataloging – all assets – even files that it doesn’t understand – are supposed to be cataloged. One problem that we ran into during our demo was trying to get FCS to ackowledge non Final Cut Studio files. It will import them, but you can’t access them through the java client. We often master our audio in Apple Logic. This is one (of many) file formats that FCS does not regnize. It knows it is file – but doesn’t connect it with logic. Hence the problem – you often have to return to finder and find the files that you are working with. And if you have to spend so much time in finder – how is this helpful? We discovered during the demo that it wouldn’t recognize files from Logic, Photoshop, Apperature, After Effects and Shake. It knows they are files – but doesn’t associate it with the applications that use them. Thus – you must find those files in finder to actually work with them.

Also, if you move a file or rename it in finder or create a version2 – does this automagically show up in FCS? Or does it cause another level of “offline files”?

FCS does help with automation. You can setup watch folders like in Sorenson or Episode for encoding. Drop a file into a folder and it can automatically encode and FTP it to your server. The interface is another GUI for Automator or Applescript – but it is ran from the server level.

Some of the key features:

• Search all of your assets and projects – asset cataloging
• Project check/check out: – and moving a project off of the server to a laptop – then checking it back in to the server. (copies assets or proxies)
• Project review and approve: let a producer or client watch your project over the web and comment
• Automation: Watch for the presence of a file (watch folder) or watching the change of the meta data on a project. Once a file is moved into a watch folder, or the meta data is changed (meta data) it can fire off automated responses. (encode, status emails, move/copy assets, etc…

I know I don’t sound overly positive about it – but I was impressed. I think the transition to FCS for larger production teams – will be a painful learning curve. Would you want to drop your 20 Terabytes of assets into an application – let it rename, move and reorganize all of your files? I guess I’m gonna need that LTO backup sooner than later.

Final Cut Server looks like an early product – it looks like a beta release application. I might want to install it on a test server – maybe run a small project or two through it before I commit our entire post department to this beast.

Amazon is a household name and now that name is becoming more common in webhosting circles.

Why is this important for ministries who use media? = cheap and reliable web storage.

All of the media that you create needs to get into the hands of those that you are trying to reach. Downloadable video and audio has been littering our hard drive for years now. If you want your message to hit the masses – then you have to make it available to them. One common method is to place your media (audio or video) on your website for download. A subscribed download of your media- is called a podcast. Every time your files are downloaded, someone has to pay for the bandwidth. It’s like cell phone minutes – you think you’ve having fun on the phone – until you get the bill at the end of the month and realize that you used up all of your minutes and the overage charges are killing you.

Amazon’s web services devision has a solution for mass download storage. Amazon’s S3 (simple storage solutions) is not for everyone, but it is providing us (DTS) a very cheap alternative for podcast hosting. For a few years we have been using our streaming provider (Akamia) to host our podcasts. Bandwidth for streaming is not cheap, and as a result – as our podcast has grown in popularity so have our bandwidth charges.

Bandwidth is charged by the amount of data that is transferred. For example, if your MP3 is 10 Megabytes in size, you will be charged for every time it is downloaded. If it is downloaded 100 times then you would be charged for 1000 Megabytes (which is equivalent to 1 Gigabyte).

Our streaming provider charged a flat fee of $1.29 per Gigabyte.

Amazon charges $0.18 per Gigabyte! (once you hit 10 Terabytes it drops to $0.16 – and then to $0.13 at 50 Terabytes)

Now let’s imagine that you have a very popular podcast and consume 1 Terabyte of bandwidth each month. On the old provider it would cost you $1290. On Amazon the same bandwidth would cost you only $180!

Now Amazone S3 is not for everyone. But for raw download, the price is untouchable.

http://aws.amazon.com/