Forum Replies Created
-
Thanks Marc!
Just had the exact scenario with 14.0.6 this afternoon with a normal install and everything looking fine until the last second and then crash.
I am sending logs along to BMD in hopes of isolating the culprit. Sounds like 14 is a lot of fun, looking forward to seeing it someday.
Dave
Dave Pickett
Colorist
Spectrum Grading
http://www.davepickett.com
404-775-8519 -
Hi Bill,
I may simply be forgetting the video drivers that may need updating. In my latest unsuccessful attempt to launch 14.0.6 today, I updated my Ultra Studio Mini Monitor to 10.9.5.
I’m not using CUDA on my Mac and I cannot recall needing any other video drivers. Am I forgetting something?
I’m glad to hear of a similar problem that was overcome however.
Thanks,
Dave
Dave Pickett
Colorist
Spectrum Grading
http://www.davepickett.com
404-775-8519 -
Thanks for the reply Peter.
I would be happy to send you my capture logs but I believe they are non existent.
After the aborted install I erased and restored my hard drive to its state about one hour before installing Resolve 14.
I suppose I could tempt fate and install it again to try to repeat the crash but I’m not too keen on that just yet.
If anybody else has an idea as to how I could share this data with Black Magic please chime in.
Thanks,
Dave
Dave Pickett
Colorist
Spectrum Grading
http://www.davepickett.com
404-775-8519 -
Dave Pickett
September 19, 2016 at 1:54 pm in reply to: Ongoing Resolve instability on Late 2013 Mac Pro OS10.11Hi Marc,
I haven’t sent any logs to BMD. Is there a log within Resolve that I can access?
Occasionally I will get the Apple log after a force quit asking if I want to report it and I usually do. However, a much larger percentage of the time Resolve will simply stop responding to my commands and I save and quit rather than Resolve crashing. When I do, Resolve appears to quit yet I have learned that I still need to force quit after it “phantom quits”. Once I do that and restart I do not get the crash prompt.
A headache to be sure which is why I wanted to report to the group. I haven’t tried the partition yet because I am in the middle of a nice gust and don’t want to blow anything away accidentally.
Thanks for your tip!
Dave
Dave Pickett
Colorist
Spectrum Grading
http://www.davepickett.com
404-775-8519 -
Dave Pickett
September 16, 2016 at 12:08 am in reply to: Ongoing Resolve instability on Late 2013 Mac Pro OS10.11Therein lies the rub Hector.
I haven’t been able to confirm anything save for that the Mac is operating in a way that Apple deems correctly. To their credit Apple has provided diligent support via Apple Care. It would be nice if Black Magic would mention whether or not they have heard of similar issues and perhaps lend some guidance?
I have been using Resolve and Logic on this Mac since, you guessed it, Late 2013 and it was stable as a rock. A great plug and play solution. Suddenly last fall I began having these problems. I suspect that it was/is a Resolve/Logic/UA/Mac software update tangle.
That is why it seemed counter intuitive. It worked great for two years and then suddenly it didn’t. Old story I know.
I agree that there probably aren’t enough users of my specific apps to generate noise. I think the partition sounds like the way to go.
Thanks for your reply.
Dave Pickett
Colorist
Spectrum Grading
http://www.davepickett.com
404-775-8519 -
Thanks Marc. An external drive seems to make sense for a lot of reasons.
As far as backing up the user database I think the best answer is yes and no. My old user folder complete with configs and projects exists on my back up drive yet when I select that file pathway on the new user database it does not link. The pathway will mount but no old user appears.
I’m sure the BMD guys can chime in more knowingly but it seems that there is more going on “under the hood” similar to the hidden .gallery. When I used the Mac to copy and paste my old user into the new 12.5.2 user, it shows up and loads but at least the GUI is the old version 12.something. Checking “About Resolve” to see which something it is shows the current 12.5.2. So there is something missing when trying to recover a user in that way. Further, that user crashed almost immediately several times.
I would agree that backing up stills to a separate drive is good policy. The hidden .gallery doesn’t make a lot of sense in this case.
One thing I would look out for with 10.11.5 that Apple has shared with me is an issue with audio extensions. I use non Apple audio software and Resolve linked to those in the local database – audio menu. Those extensions are causing a known error in 10.11 and may have contributed to my instability. I removed those yesterday as well. Apple audio files reside in the OS. Non apple audio files reside in the Library.
Dave Pickett
Colorist
Spectrum Grading
http://www.davepickett.com
404-775-8519 -
Dave Pickett
March 22, 2015 at 1:18 am in reply to: 3 Different Resolves in different facilities with same issue in 1 week.That is possible yet I was able to recreate the scenario again by changing RED decoding settings from Project to Clip and back to Project in the main Gui page lower left. I had been doing a lot of RED footage last week so perhaps that has something to do with why I had the epidemic so to speak.
The real interesting part was that each of the 4 times this occurred the color timeline thumbnails would change with the corrections but the monitor and the scopes would not. So the corrector was receiving data from the control panel and behaving correctly yet the video out remained static. Further, any corrections I did apply while trying to wake up my static display seemed to save so that when I restarted the system, those corrections were in place, just not displaying prior to restart. And this was on three separate Macs, two with legacy towers with Cuda and one with a nMacPro with Thunderbolt.
I did test switching to the the Camera Raw config menu to toggle the RED decode settings to see if I could wake it up but to no avail. Is there a function in Resolve that automatically bypasses all nodes when toggling RED decoding parameters? I wouldn’t think so. You would want to see what those changes did to your existing grade. Further, why would it show up in the timeline thumbnails if bypassed?
All Resolves were 11.2 on Macs.
Dave Pickett
Colorist
Spectrum Grading
http://www.davepickett.com
404-775-8519 -
Dave Pickett
March 13, 2015 at 11:39 am in reply to: 3 Different Resolves in different facilities with same issue in 1 week.Good question Peter.
I updated to 11.2.1.002 yesterday on my own system before I began the session which had the issue. Earlier this week I was in two other facilities and had the same issue but did not check which version they were running. The first time I figured it was a local system bug. The second location made me pause a bit and then when it occurred twice in my own system I wanted to raise the flag.
I will check the software versions of the other two places today and report back.
As far as the cache goes Joe I assume all three parties are set up diligently in a way that has provided healthy operation since the advent of Resolve 11. Things certainly change but that would be a startling coincidence of sudden onset cache issues.
Dave Pickett
Colorist
Spectrum Grading
http://www.davepickett.com
404-775-8519 -
Rohit, I will post a crash report upon the next attempt should it happen. It has been instantaneous every time thus far and I ceased trying.
Joseph, my final intention for the footage was to encode some spots to provide a client some specific examples even if SD and rather dated. I had luck in about 2010 using Resolve to capture reference picture from DigiBeta and figured it would behave somewhat similarly but it did not, at least in this case.
Keep in mind I was also knee deep in 10.9.3 Mavericks quicksand during my initial post. 10.9.4 and Resolve 11 seem to be a lot happier but I haven’t had the desire to fire up the deck and press my luck.
Thank you gentlemen for your suggestions. One of the things I miss about the post industry of yesteryear is the group atmosphere to go through these aggravations with. That and the Everest sized piles of film to work on.
Dave Pickett
Colorist
Spectrum Grading
http://www.davepickett.com
404-775-8519 -
I agree Marc that early adoption of OS updates is perilous. This was an auto update that I neglected to disable upon receiving the cylinder a few months ago. Mind those settings!
Hard to say exactly what is going on but 10.9.3 has caused similar problems for other pro users and the chatter is that it’s code relating to Open CL.
In practical terms, your session will grind to a halt a few scenes in. Then Resolve will not quit properly and then force quit ceases to function (as well as most other apps) and you end up hard booting. The next hurdle is renders that hang indefinitely. One workaround for renders that has kept me trudging has been to open a new session, import the media and use Color Trace. That process somehow unlocks the render demon.
Apple suggested migrating back to 10.9.2 which is my plan. There is also the 10.9.4 public beta gambit followed shortly by Resolve 11 itself.Dave Pickett
Colorist
Spectrum Grading
http://www.davepickett.com
404-775-8519