Avid MediaCentral Platform Services ReadMe V2.10.7.2 Avid MediaCentral Platform Services ReadMe V2.10.7.1 Where can I find documentation for MediaCentral v2.10.x?Īvid MediaCentral Platform Services ReadMe V2.10.7 (updated April 12, 2022) This article contains a list of documentation for Avid MediaCentral v2.10.x I have send an email to Dave and will open a case if he wants me to.Avid MediaCentral Version 2.10.x Documentation
#Avid mediacentral 2.10.x documentation windows 7
I haven't tested capture client under windows 7 but will hopefully be able to try that next week. This behavior resembles a bit the inews command client under windows 10. So I thought could it be that this is a bug fixed in 2017.2.4? So I contacted my colleague Dimitris who is at another brand new site where I installed 2017.2.4 and I asked him to create a new capture user and change the layout and favorites to see how it behaves and it has the exact same problem. The windows user under which this is done, a normal user or administrator does not affect the behavior. So each time the user is closing and starting up the capture client he requires an import of the layout and a random favorite creation. leaves the favorites bar empty until a new favorite is created and the client magically loads all favorites previously created. Fortunately there is the export import functionality of the layout so it can be restored quickly. the interplay capture client refuses to keep the layout of the interface when opening and closing the capture client.
#Avid mediacentral 2.10.x documentation upgrade
Yesterday after expanding a 3.7.2 system (yes the upgrade to 2017.2.4 is pending) with another airspeed to 16 channels I also needed to create a new capture user as each user will use different favorites for different checkin locations.ġ. 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?Ī single channel failing requiring an API service restart, which requires you to stop all recordings on all channels is simply not viable.Īfter more then a year of testing and troubleshooting Interplay/Mediacentral capture I thought the product didn't have any 'unknown' issues for me. L2 support has been providing the help they could but the problem is 100% a development issue. 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. You restart the API device service and it all off a sudden become aware it can.
If, for example, a Glookast channel looses a valid SDI signal the system goes into a warning state it never comes out of when signal returns and that channel can't be used to record anymore. 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.
I have recently setup 6 Glookast servers with Capture 2017.2.4 and the system is basically unusable. The new version numbering just being ignored. 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.
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.
0 kommentar(er)
