John thanks for correcting me as I was a bit hasty in my response. The settings I referred to is for CatDV to serve the proxies via http to the “Pro Client”. Scott as John illustrates this can be done by mapping the media path metadata to the corresponding http url in the path mapping preferences of the client. Keep us updated on how it goes as this is a very desirable workflow. We have customers doing this with their own internal and external web servers but not with S3 that I am aware of?
Ok this seems odd for sure, can you send a few screen grabs showing the error and a log from the CatDV client? Please also include other info if possible like version info for your OS, NLE and CatDV and the codecs in play as well.
I have not seen this before but when stuff like this pops up it usually is traced back to a graphics card conflict. Send along these screen shots with a log from the client (under the help menu) to support@squarebox.com and they can take a closer look. Include any pertinent system spec too OS and what not.
One way to prevent this is to make a field set! This will not gather odd bits from other groups not using the same filed set. See preferences field definitions and save a field set.