Michael Gissing
195
COW Coins
190
DaVinci Coins
3
Solve Coins
Forum Replies Created
-
The best key on my standalone Fairlight is a jump back and play key where you can set the size of the jump. So no matter what you are doing you hit one key and you jump the required duration and the timeline plays.
I’m looking forward to getting the Blackmagic control for Fairlight which will hopefully still have the best key in the history of editing and work on all pages in Resolve. Meanwhile you might be able to come up with some sort of macro maybe?
-
If you have an external drive, I would try putting the render files on that, not the internal. I presume your media is on an external. It is less critical these days to avoid having media on a system drive but it is still good practice to avoid clogging up the system drive with media. If you are having trouble playing ProResLT then there is something seriously wrong.
Also just check the render file attributes to make sure you are setting the codec correctly. It is confusing in the preferences as renders and optimised media are set separately. Finally are you waiting for the render bar to turn blue before playback?
-
HD or 4k? What’s the frame rate? Which drive are the renders going to? Lots of info needed to try and see where the problem might be.
I’m assuming Resolve 15 because you mention Fusion, If you are on an early beta it might be worth going to the latest beta5 as this may also be an old bug that has been fixed.
-
The other thing to consider is this was an underpowered machine from the GPU side. It would still not be expensive to get a machine that outperformed. Say you went crazy and spent half as much as an iMac Pro you would get a screamer, particulalry if you are using Adobe or Blackmagic software as well as FCPX. If you were not using FCPX, I wouldn’t bother with Mac OS and just run a win box. Even easier to install and setup.
And with a Win box, as Shane says, don’t let it update. Mine stay off the internet until I need to do some updates or register software, then they are disconnect from the internet but not ethernet. Rest of the time a Linux laptop is my front end to the internet. Apart from the cost savings of build your own, I also keep power supplies and all monitors, keyboard, mouse etc. The iMacs are a very wasteful design that requires junking perfectly good components just to do incremental upgrading. My monitors are now nine years old. Mouse and keyboard older. Power supply is six. All perfectly working. Cut down on ewaste.
-
Might have to contact Blackmagic. Firstly to report a bug and to get support. If it worked before then it’s perhaps a bug.
-
Did you see both cards on a previous version of Resolve? Beta5 is available which would be worth trying. The first beta is usually the most buggy.
Also make sure you’ve downloaded the Studio version. The free version only lets you use one GPU. I am assuming you were using the paid for Studio version if you had previously been able to see the two Titan Xs.
-
I find it unusual that they built in a sound recorder. Surely anyone shooting 65mm film will have a separate sound recordist and clappers. It’s a weird hybrid camera for sure. At least they should sell a few to Tarantino and Nolan.
-
I’ve jumped in to Resolve 15 beta4 and it is considerably faster and snappier than 14. Stabilize is amazingly quick to analyse. OFX plugins continue to improve and the improvements in the Fairlight page are a big step. I must force myself to use Fusion although the Boris CC11 tools are doing a lot of things for me that Fusion can do like screen replacements. The series I am working on has a fair bit of GFX comps and putting them back together in Fusion would make sense whilst matching live action grades to box insert footage will be a treat.
The beta has been incredibly stable for me. Only one crash causing issue is after a lot of stabilizing, I am getting an out of memory problem with my GPU (GTX1080) and that requires a restart.
There are so many things in 15 that even with my expectations of BMs fast dev, this is quite amazing.
-
Yes it’s easy and described well in this video.
https://www.youtube.com/watch?v=FifgKAezJX4 -
My thought is the sequence settings are not a standard pixel aspect that FCP is happy with hence the rendering. The audio just makes it worse. I’ll bet the audio files are fine in any FCP broadcast standard sequence. The non standard sequence is the issue.
When transcoding to ProRes, a standard pixel size needed like 720 x 486 to be chosen as Shane has pointed out.