![]() ![]() Specifically memory, drives, raid controller and raid controller cache battery. If you are using an HP or Dell server check through ILO or iDrac that all hardware is happy. The FTP section of the Transfer Manager server is what craps out- and that's the section we need, as it has the DHM which re-packages the file as a flat MXF. Avid MediaCentral-UX is used for collaborative media production within the proprietary Avid production environment for users of various roles. The FTP to the device (a flip factory or a Nexio server, we are trying both) directly works. Description: Avid MediaCentral-UX (Unified Experience) is a web-based utility that allows multiple users to work with multi-media files and projects hosted in a proprietary Avid environment. If it happens we failover the Interplay enigne in a cluster (or restart the Interplay engine if it were a single engine). Workgroup to workgroup is fine, the data does get to the TM server itself. It is supposed to be fixed but on one site with many users we still see occasional performance issues. But I have not been able to exclude Mediacentral 100% from releasing connections if users do not correctly log out. Make sure Nexis client on the Interplay engine is 2021.3.x. ![]() Interplay engines can run out of TCP port resources which causes delays in both Access and Mediacentral eventually resulting in complete loss of connectivity. Have you restarted your Nexis client after cleaning your cache? Perform:Ĭluster: crm resource restart AvidAllEverywhere Run: avid-system-check and have a look if you see anything weird. Check DNS configuration on the mediacentral server and entries for Interplay engines, Indexers, etc. First check if time and date are in sync. ![]()
0 Comments
Leave a Reply. |