Forum Replies Created
-
Jake Blackstone
March 22, 2014 at 11:06 pm in reply to: Please tell us which Cuda and NVidia driver versions we need for Mac Pro 2012 and Resolve 10.1.3 not to crash instantlyWhat part of Minimum system requirements under the Important information don’t you understand?
• Mac OS X 10.8.4 Mountain Lion
• 12 GB of system memory is recommended and 8 GB is the minimum supported
• Blackmagic Design Desktop Video version 9.7.7 or later
• CUDA Driver version 5.5.25
• NVIDIA Driver version – As required by your GPU
• RED Rocket-X Driver 2.1.5 and Firmware 1.3.0.4 or later
• RED Rocket Driver 1.4.36 and Firmware 1.1.17.3 or later -
Yes, thank you Dwaine.
And here are my thoughts from that conversation as well, in case people missed it.1. Shortcuts choice is strictly a choice in order to utilize an existing edit software shortcuts, like FCPX or Premiere. In those editing packages there are no shortcuts for something like “Lightbox” or “Add version”, because they don’t exist. So, changing shortcuts to FCPX or Premiere should have no effect on any shortcuts not edit related. And under no circumstances should shortcuts just disappear, like it happens with with Lightbox, “Add version” or many others.
2. Opening old projects shouldn’t be the reason for Resolve to go to the old shortcuts as is the opening someone else’s projects on your system. Your choice should ALWAYS prevail, regardless of which project you open. Otherwise that’s not even a choice but a force.
I completely agree, that shortcuts should be moved to the Preference section. I can’t imagine anyone would NEED to change shortcut selection on per project basis.
Anyway, this “non bug” took way too much of my time and as I said earlier, i’m just going to file it under another weird BMD creative decision and learn to live with it. -
It happens all the time, completely random. Restating Resolve doesn’t change this behavior.
-
And I’m telling you after using all panels in this order- Wave, MC Color-Elements, I decided to go back to MC Color. I have been on MC Color for close to three years and I had NEVER had a disconnect, NEVER. Did I say NEVER? I don’t know why your hearsay would be more important, that someone who had used the MC Color panel for that long. As I said, I couldn’t care less what panel people using. Personally, I think Elements with it’s present mapping is a waste of money, because I can work equally effective with MC Color as with much more expensive Elements. But that just me. So, enjoy your new panel, good luck with it, but for the love of god stop the bullshit about MC Color disconnects. Because it’s just that-BULL SHIT! MC Color doesn’t have the disconnect problem!!!
BTW, enjoy your Elements with Resolve, but god forbid you’d like to use it with another software. What? They didn’t warn you? Resolve will not relinquish the control, even if you shot down Resolve. Oops. On the other hand I can have number of different software running and MC Color will just switch back and fourth between all of them. And how about using your Elements with other computers? Well you’d need to unplug and re-connect it to another computer. Not with MC Color. If your MC Color is connected to the Ethernet hub, all you have o do is to flip the control to another computer and voila, the other computer now controls it. No fumbling with connectors in the back. Anyway, good luck.
Thank you. -
Thank you for the information Peter.
I just would like to ask for one thing.
Could BMD elaborate a bit more on the “general performance and stability improvements”?
Often with a new Resolve version, shortcuts may get changed, all of a sudden something starts working, that wasn’t working before, new shortcuts become available, that weren’t there in previous versions. All that missing information often discovered by trial and error or by someone posting it on site, like this one. I’m sure everyone appreciates software updates and general performance and stability improvements, but it’s the unwanted surprises, that would be nice to avoid. -
Jake Blackstone
February 27, 2014 at 8:59 am in reply to: Selecting and moving multiple points of a window in Resolve?Yes, you can’t select multiple points of the window in Resolve. You are better off doing the roto in Mocha and using the resulting matte in Resolve.
-
You ended to render 59.94i
-
I think a better comparison would be for Ford to require only Ford tires to be used, if you wanted to go over 20 MPH:-)
-
Looking at your picture, it’s clear, that you already key’d and modified his skin. I say that, because he’s very yellow and even more so, I can see a lot of blue noise at the top of the picture, where your key needs clean up. This is the case of using basics before trying to overcomplicate things. Your basic grade is incorrect. And because of that, you’re creating other problems down the road. You need to step back and start all over. Right now you’re heading in wrong direction…
-
Harris, you’re on fire today:-)
OK, just a couple for me.
1. In V9 3 way grading had 3 wheels and LOG mode had 4. So, it was easy to see the mode you’re in. In V10 it’s not easy to tell them apart any longer. Now both windows look exactly the same with 4 wheels. How about making 3WAY window to look a bit more different from LOG, so you’d be able to easily tell which mode you’re in? How often you’re trying to adjust Gain, only to realize, you’re in the LOG mode?
2. The little dots on top of windows, like the curves windows or LOG/3Way windows are way to small and way too dark. How many of you would need to keep clicking on them before you select the proper window.
3. Proper render cache. Enough said…