OM Show

channelAustin has been using a proprietary software tool called Content Agent to encode .mov files to the MPEG2 format required for playback on our Synergy Broadcast system. Content Agent in our work flow has been previously discussed. See http://groups.drupal.org/node/19135

We also decided some time ago to use Content Agent to encode H.264 files for VOD on the web with the OM Show module. And so we added an H.264 encode process to the workflow. We've now decided to stop doing that.

This morning I noticed that my site when accessed through http was slow to crawl. Couldn't get in or do anything.

When I finally got in and took a look at the Drupal Reports there was an Error related to the refactored feed from our Telvue:

Message simplexml_load_file(): http://173.76.78.19:3000/thu in /var/www/dev.eastoncat.org/sites/all/modules/om_airing/modules/om_airing_feed/om_airing_feed.module on line 59.

We must have hundreds and hundreds of these messages in a very short period of time last night.

Is this slowing my site performance to a crawl?

After looking at what Jack Brighton has been doing with FieldFrame in Expression Engine (which AFAICT is really similar to Drupal's CCK), hearing BAVC's desire to stick with PBCore, and knowing that CPB is actively working on requirements for PBCore 2.0, I took another look a PBCore. What I found was that most of the terms the beta stations wanted to include in a new standard were really similar to an existing PBCore term.

This is going to be discussed in today's project call, but I wanted to get something posted about what we are asking the stations to do over the next two weeks and why since we have so much to cover during this call.

We started locking CCK fields that are referenced by TVframe so that stations could tell the difference between fields they've added and could edit and fields that would likely cause a problem if modified. Yesterday we had an issue where PCM needed to alter a setting in a locked filed, so I thought I'd post the instructions for unlocking fields for everyone. There might be other ways to do this, but I use phpmyadmin to access the locked column in the content_node_field table.

We've been using the Taxonomy XML to import the hierarchical taxonomy we've been using for genres in Project, Show, and Timeslot Theme. Taxonomy XML now supports taxonomy as a service.