Dear Avid,
After over a year trying to get you to fix a number of bugs in Interplay, and now Mediacentral, Capture I'm ready to throw the towel in the ring. Multiple cases further, bugs being logged, fixes being released that do not fix the problems, new features only being half ready in some beta stage. The new version numbering just being ignored. Anyway...
I have recently setup 6 Glookast servers with Capture 2017.2.4 and the system is basically unusable. Since the introduction of the new API device service that replaces the framework device service Interplay/Mediacentral Capture has lost the ability of correctly determining the status of airspeed and glookast servers.
If, for example, a Glookast channel looses a valid SDI signal the system goes into a warning state it never comes out of it when signal returns and that channel can't be used to record anymore. You restart the API device service and it all off a sudden become aware it can.
If you dare to restart the API device service while some channels are recording you have lost those until you stop all recordings and restart all services again.
L2 support has been providing the help they could but the problem is 100% a development issue.
My question is simple Avid: Are you going to put the development resources in to make Capture a product that can actually be used in a broadcast environment again or should we just buy Glookast, MOG or Telestream ingest servers and schedulers and not bother anymore?
↧