Open Media Project

I've been working hard on getting manual scheduling working correctly here at OMF. I just committed a new version of OM Timeslot Scheduler, which has a lot of changes. All output created by new functionality is separated off in a grey experimentation area only visible to user 1 and certain roles. Scheduling now supports the pairings module. There is also a non-pairings system section that I could use some help debugging, as it's hard for me to test on our system.

So I've finally made the move to St. Paul, MN and am working for Tightrope full time and only partially helping out my old PEG station through the internet. This means that I finally have some "free" time to do some developing for the Open Media Project. There has been a bunch of talk on IRC lately about separating some of the functionality in the different modules and I think Krenyen has already done a lot towards that with the simpler om_show module and the new om_airing module.

Just wanted to drop a line and let others know there are some auto-installation options that might be helpful for ffmpeg newbies. I wrote a small article on one setup and gave some tips. You can view the details here:
http://www.elvisblogs.org/other/howto-install-ffmpeg-ffmpeg-php-and-code...

After a lengthy discussion about metadata in 2009 (see here for one instance) kreynen created a new PBCore module to allow those using the Open Media Project to base their genres on PBCore – PBS’s internationally used genre list of 228 terms – which kreynen details nicely here .

So I know this is something of a wide-ranging question but I was wondering if there were essential pieces I should know before trying out OM_Install+OM_Me? Seems to presently be the same moduleset kreynen mentioned in a previous post as OM_Lite.

I'm hoping to get CMAP to a point where they can begin using CiviCRM and OM_Project on a local dev install by next week and have enough information and configuration done for them to be able to move forward with MERCI deployment on their own.

Now that the Open Media Foundation has completed, or is about to complete, its obligations for the Knight Foundation grant to develop the Open Media Project, and now that we are at the same level on the playing field, with no one entity carrying any more weight, or responsibility, than any other, perhaps it is time that we, as co-equals, embrace a federation model, or some other egalitarian approach, for the creation of an association of developers, implementers, and end-users of the Open Media tools, with a guiding principal of openness and transparency in all communication and deliberations.

Hi,

We are finally in the process of moving our entire site to Drupal and gradually start using the OM tools. I was thinking of starting with just managing our metadata in Drupal, that is shows and what you call projects (we organize only be member, but I suppose we'd have to use one project for each member).

However, trying to install om_show lots of other modules are also required, most of which we wouldn't use at this stage. Are all those really required to manage show metadata? Particularly I'm wondering about these:

Creative Commons is offering Catalyst grants of up to $10K empower individuals and communities deeply rooted in the principles of openness and sharing. The current configuration requirements that limits Open Media implementations to hosting in the same physical location as the archive and playback server have been a deal breaker for many stations. Most stations lack the bandwidth and/or staff with system and network administration skills required.

When it works, media_mover is an amazing piece of code. But when something goes wrong, media_mover is the Achilles’ heel of Open Media workflows. A few of the stations we worked with during the beta didn't need media_mover, but because we were trying to build on a common platform they got it anyway. Both channelAustin and Portland Community Media had already invested in encoders far superior to what a media_mover/ffmepg_wrapper configuration could do. Those stations were getting all of the disadvantages of media_mover while leveraging very few features.