Michael Gissing
195
COW Coins
190
DaVinci Coins
3
Solve Coins
Forum Replies Created
-
Is Resolve on Win 11 recommended? I’m still on Win 10 pro and I haven’t seen an updated list of compatible OS and hardware lately. The BM forum might be the place to check on compatibility issues. It’s also where bug reports for 18 beta should be lodged.
-
I’m on Win and the option is there in the drop down. I used it on a BMPCC 4k braw shot as only braw has the gyro data embedded.
I’m also running the studio version so it may not be on the free version yet
-
What version of Resolve are you using? Codec compatibility is on ongoing process and you might just need a more recent version of Resolve
-
V18Beta 6 inlcudes the gyro option.
-
I have a couple of convolution reverb plugins and some impulse responses for car interiors. If you add that to studio recorded dialog it will sound like it is recorded inside a car
-
If you go to Keyboard Customization you can search and find any of the Resolve preset keyboard shortcuts. You may find many commands that are not even assigned to keys as there are lots of shortcuts. You can always change a shortcut to something more suitable or even use the Pr shortcuts by selecting in the drop down menu top right of the Customization panel.
-
There are conditions placed on creative commons licensing. There is more than one type of CC license so it is important to find out which one applies. Some CC licensing prohibits being used commercially. Others not so but all require some form of attribution. By being on a Wiki the license type should be displayed as the Wiki page might have sourced them from elsewhere. The license however should be clear in the attribution. Using them in a commercial doco is not a simple assumption that they are public domain. You do need to check and attribute. Are you altering the image by cropping, flopping or coloring?
Sorry it’s not simple but the good thing is that if the Wiki pages has done its job the different type of CC license should be documented.
-
Have a look at Shutter Encoder. It has various edit, merge etc modes that don’t re-encode.
https://www.shutterencoder.com/en/
-
It shouldn’t make a difference. But AAFs are quite rare in my world. It is mostly Resolve to Resolve, or Pr via XML with FCPXxml occasionally. All those are working well.
-
All other NLEs are cross platform so Apple would benefit from more FCPX sales as it forces users to it’s OS and hardware.
I read some posts from others about the response from Apple. Curious what people here think about it. My take is that Apple see it as a failure to market and train users. Which is like saying there’s nothing to develop, fix or change. My guess is the panel of experts will not be the keen users who have been screaming for basic bugs to be fixed and features to be added.