Question
Archival services with Flash Media Server
I work for a broadcasting company and we do live telecast of
various events, mostly related to professional sports. We currently
have a Windows Media Encoder 9 setup with Windows Media Server,
etc. I have a custom written application that archives all of our
broadcasts. This was accomplished with the M$ media SDKs. Archival
means we record each one of our daily live feeds for review and
archival purposes (game footage for coaches, stuff like that).
We are currently looking at h.264 capable setups, or something equivalent. We have been playing around with Adobe's encoders, media server, and all that. We are impressed with the quality. Switching to this right now has some logistical complications, mostly related to an operational requirement based on our current business model. Simply switching to h.264 overnight isn't going to be possible; we will need to prepare.
So, with that in mind, I have a question relative to SDKs and Flash. My current application (the archiver) can archive up to 120 events simultaneously on a single, reasonably fast machine on a fast network. I have to be able to record at least 60 on a given night, the 120 was discovered during testing and its faltering is relative to network collisions and getting ethernet up to 40% utilization more than not having enough CPU to process the streams. I would need something similar for Adobe. I have the spec (at least the public domain version) for the tunnelling protocol so reverse engineering this isn't going to be a big deal. What I'm mosly interested in is an SDK with functionality that allows me to record a lot of streams in software for archival purposes. This SDK has to be smart enough to deal with Disk I/O VERY intelligently because clearly anything more than 8-12 realtime stream records to a disk in a linear fashion is going to overload the hard drive.
Before anyone starts spouting off about DRM and piracy, we are recording the broadcasts we own. This is for archival and this archival process has to be automated (the app isn't JUST a recorder, there's a whole process shielded from the operators of this thing for defining stream locations, where to save the files, and all that). I realize all this code that automates this process for our company would still need to be written. What I'm interested in specifically are readers and writers for flash streams, especially relative to network reading and disk writing (intelligent disk writing; I've written custom implementations of MMS, HTTP, etc that mash the hard drive).
In a nutshell, is there an equivalent SDK for Adobe's technology as the Windows Media Format SDK is for WMV files? This is currently the only hurdle in implementing Adobe's h264 technology in lieu of our current setup (which is 100's of encoders and locations at the current time, all over North America.
Thank you for your time.
We are currently looking at h.264 capable setups, or something equivalent. We have been playing around with Adobe's encoders, media server, and all that. We are impressed with the quality. Switching to this right now has some logistical complications, mostly related to an operational requirement based on our current business model. Simply switching to h.264 overnight isn't going to be possible; we will need to prepare.
So, with that in mind, I have a question relative to SDKs and Flash. My current application (the archiver) can archive up to 120 events simultaneously on a single, reasonably fast machine on a fast network. I have to be able to record at least 60 on a given night, the 120 was discovered during testing and its faltering is relative to network collisions and getting ethernet up to 40% utilization more than not having enough CPU to process the streams. I would need something similar for Adobe. I have the spec (at least the public domain version) for the tunnelling protocol so reverse engineering this isn't going to be a big deal. What I'm mosly interested in is an SDK with functionality that allows me to record a lot of streams in software for archival purposes. This SDK has to be smart enough to deal with Disk I/O VERY intelligently because clearly anything more than 8-12 realtime stream records to a disk in a linear fashion is going to overload the hard drive.
Before anyone starts spouting off about DRM and piracy, we are recording the broadcasts we own. This is for archival and this archival process has to be automated (the app isn't JUST a recorder, there's a whole process shielded from the operators of this thing for defining stream locations, where to save the files, and all that). I realize all this code that automates this process for our company would still need to be written. What I'm interested in specifically are readers and writers for flash streams, especially relative to network reading and disk writing (intelligent disk writing; I've written custom implementations of MMS, HTTP, etc that mash the hard drive).
In a nutshell, is there an equivalent SDK for Adobe's technology as the Windows Media Format SDK is for WMV files? This is currently the only hurdle in implementing Adobe's h264 technology in lieu of our current setup (which is 100's of encoders and locations at the current time, all over North America.
Thank you for your time.
AdChoices