Showing related tags and posts accross the entire site.
-
You must have a host name entry for the License server, which is also the File Manager. Without it, no worky. a sample host file entry 192.168.1.10 PrimaryFilemanager It might be easier to simply copy the host file entries on your working portserver and paste them to the non-working one. JDS
-
I am seeing the same problem- same effect, DNxHD 145, 720p/59.94, XP system, Composer 3.1.1 Safe levels had no effect. need a fix, or BCC gets ripped out, folks. JDS
-
Isis 2.0.2 has been pulled from distribution. If you have it, don't install it- if you've installed it, roll back ASAP to 2.0.1 Severe issues with Interplay servers and clients, Severe issues with AMA
-
where in the "launch" process does this error come up.
-
Make sure your interplay folder path is set correctly on ALL users who are sharing the project- otherwise your Interplay project folder becomes a bloody mess. JDS
-
your question listed the 8200, 8400 is qualified, you will need the R380 version of the ATTO, the ST is only a JBOD. JDS
-
Your total metadata is not on the SD- only partial, some is on the storage. What patch- I may have already done it. And- in a 2 SD environment, you can patch the standby, fail over, then patch the new "standby" JDS
-
to save money, or for some other reason? <edit> I hate it when I ask a dumb question to see it answered in the OP. It would not be recommended to do so, I've never seen it in the wild. That isn't to say it would not work, just that you may run into unanticipated issues down the line that...
-
Apparently you have no idea how the Unity File system works, and it's relationship with the active metadata. Unity only appears to be organized as a batch of workspaces. The Unity file system has NOTHING to do with windows file systems as you know it- and running this crap on the engine could cause...
-
have you rebuilt media databases from the Systems that created them? If this question makes no sense, then you need to get a Unity qualified service rep in. JDS