After more time the system doesn't seem to be hanging so hopefully I got this sorted out. Is it possible that as I did Mac OS combo updates along the way that the OS would revert to the native OS graphics card driver without me doing anything. I like to think that when I went through all the trouble of getting the matching Nvidia driver for the exact system build number that I also set the settings to use the web driver and not the native driver but I can't be sure. So many ways to shoot myself in the foot.
---In Avid-L2@yahoogroups.com, <bigfish@...> wrote :
I'm cross posting this to edit list and Avid L-2. This is more Resolve Mac related but I'm testing an Avid round trip type workflow.
About a year ago I finally installed my Cyclone Microsystems Expansion Chassis on my home MacPro mid 2012 12 core 2.66Ghz, 64GB Ram, GTX-680 GPU in tower. I have two Titan X GPUs in the Expansion Chassis. I know Avid won't take much advantage of them but I figured they would be a big plus for Resolve.
Initially I was running OS 10.9.5 or maybe 10.10.5 IIRC. When I installed the expansion chassis I found that the Titan X GPUs showed up as some sort of generic without the correct GPU name. Some of this seems to be related to the expansion chassis. Even in Resolve IIRC the GPUs were recognized in a generic form.
At that point I think I went through the process of getting the proper Nvidia driver for the mac OS build. Once I did that IIRC the Titan X GPUs started being listed by their correct name. I was also informed during this process that multiple GPUs could only work properly in OS Sierra 10.12.X. I upgraded the OS to where I'm at now of 10.12.5. I know I should get up to 10.12.6 for proper Avid spec but I haven't bothered as yet.
Part of the reason I decided to go expansion chassis was running the GTX-680 and trying to run 4096x2160 DCI in Resolve tests the computer would vaporize randomly. I got prompts about not enough GPU Vram. When I say vaporize I mean just that. System would hang and no opt,cmd,esc would get me to force quit and cursor locked etc...
Today a year or so later I'm finally trying to do a 4K test with my current project and it is still vaporizing every 10 minutes or so. It seems to happen when I right click but I don't have any pattern. As I was about to try a clean install on another drive I decided to check the Nvidia driver to see if it was up to date. To my surprise I found that the Nvidia setting window showed that it was using the native OX X Default Graphics Driver. I switched that setting to NVidea Web driver and checked for updates. It said I was up to date. So far it hasn't vaporized as I poke around and do a bunch of right clicks.
I'm guessing that because I downloaded the proper Nvidia drive last year that made the Titan X cards be recognized properly as far as their name but it would seem that because I wasn't running the Nvidia Web driver set in the Nvidia Driver Manager there might have been a glitch that was causing the vaporizing in Resolve. Does anyone know if Mac OS 10.12.5 has a TitanX compatibility in it's OS X Default Graphics Driver? If it does is it possible that that native OS driver isn't what Resolve likes and the the Web Driver should be used? I'm going to do more research on this but so far it seems more stable on the web driver and not the OS driver. This makes sense to me but it is only a guess as I'm very new to the Resolve ecosystem. Vaporizing doesn't help build my confidence but then I learn more from failure than success.
John Moore Barking Trout Productions Studio City, CA bigfish@...
__._,_.___
Posted by: bigfish@pacbell.net
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (2) |
Have you tried the highest rated email app?
With 4.5 stars in iTunes, the Yahoo Mail app is the highest rated email app on the market. What are you waiting for? Now you can access all your inboxes (Gmail, Outlook, AOL and more) in one place. Never delete an email again with 1000GB of free cloud storage.
this is the Avid-L2
SPONSORED LINKS
.
__,_._,___
No comments:
Post a Comment