Jake Blackstone
Forum Replies Created
-
I’m actually at a loss trying to think of any other color grading software, that DOESN’T allow adding more points to the existing window. Nope, Resolve is the only one:-)
-
I couldn’t care less which panel you decide to use. I just have a problem with this bullshit about the ethernet connection problems. There are zero problems with the ethernet connection. You like big balls Sasha, I get it, good for you, but stop spreading this MC Color ethernet connection problems FUD, because you look silly claiming it. This, so called, problem just doesn’t exist no matter how many times you repeat it…
-
What connection problems??? Going on three years using MC Color and I NEVER had any connection problems.
-
I see, yes, if you select the window first by clicking on the dot, then Cmd and arrow left or right does work. I can use it with Quickeys. Not ideal, but better, than using the pulldown menu or trying to hit the invisible dot…
BTW, the Cmd+arrow shortcut works on all windows. -
I tried Cmd+Arrow (Up and down) and I got nothing. Would like to know the secret…
-
While we’re on the subject of shortcuts, I have another gripe in connection with the shortcuts.
Say, I start Resolve and the shortcut for jumping between cuts is arrow UP and arrow DOWN. If I restart Resolve, that shortcut mysteriously changes to Page UP and Page DOWN. And then on the next restart it may go back to arrow UP and arrow DOWN or not. Every time I start Resolve I must check all shortcuts and reprogram my shortcuts as needed. Or the Lightbox shortcut. Sometimes the shortcut for it there and sometimes it’s just empty. Anyone else experienced it? -
Maverick is the first OS, that rolls CUDA drives into the OS, meaning now it’s up to Apple to provide the CUDA drivers for various nvidia cards. Right now Apple hard at work incorporating OpenCL support, delegating CUDA to a second tier. That is why, if you are using nVidia cards you’re better off to hold off the migration to Mavericks until CUDA support had been sorted out. Even though CUDA with GTX 680 officially supported, along with K5000 and K4000, I found Resolve under Mavericks is still slower and quite choppy.
-
“knowing that cuda is not supported in Mav”
And where did you get this great nugget of information?
And even if that was the truth, which it obviously is not, why pulling GTX 285 and leaving GT120 (both nVidia cards supporting CUDA) will alleviate your problem? -
Well, as I said in the name of the post “It’s not add bad as usual”. I din’t say, it’s all fixed:-)
Let’s examine the improvements in cache implementation since we all started to complain.
1. Cache now persistent, unlike before. Now cache doesn’t get erased every time you quit the project. Although, as I already had said, Resolve randomly “forgets” some cached events. And the question is how to manage the no longer needed cache still needs to be addressed.
2. Now you can toggle “all bypass” without invalidating the cache. I’m still mystified why doing the same with a single node causes the opposite.
So now, for short form projects, like commercials with Red material, I can invoke a full debayer quality, enable the “cache all” and invite clients to have a drink. In a short period of time I can playback the commercial in full quality with all effects in real time with no dropped frames. If the client wants a fix, I still can do it without re-rendering the whole thing.
Is the caching in it’s present form perfect? Not by a long shot. Can I use it now in somer instances, Heck yeh!
The reason for my original post was the idea, that finally I can see the forward movement on the cache front. Said that, there is still a LOT of work needs to be done before caching can be used as it’s intended.
And now, how about some progress on the panel re-mapping? 🙂 -
No reason to freak out yet.
I had the same issue with my 2009 4.1 MacPro randomly shutting down, just as described. Mind you, my GPU for GUI is GTX 570, which is perfectly fine to use without worrying about overdrawing the power.
I had done two things since and the problem is gone and the computer works perfectly since.
1. I vacuumed all openings used for cooling.
2. I updated my 4.1 MacPro to 5.1, while upgrading 8 core CPUs to 12 core CPUs and swapping 1066 MHz RAM for 1333MHz RAM. It is possible, that newer CPUs even with more cores are drawing less power or there was a bad RAM connection. Regardless, things may be not so dire, as you may think…