Michael Gissing
195
COW Coins
190
DaVinci Coins
3
Solve Coins
Forum Replies Created
-
My 2009 MacPro died a few days ago. I was testing it to sell to a friend for parts, particularly the power supply which is what died. So that’s it, off to the ewaste recycle. I no longer have anything Apple in my life.
This silly feud with NVIDIA is one of many reasons why I will not step back into the Apple world for hardware or software.
-
If you have to go xml, then you are better off opening the project in Resolve where the codecs still work. You’ll have to redo grade, mix stuff anyway and might as well use the tools designed for that.
-
What are your timeline settings? p or i?
-
I would seriously heed Nick’s advice and create an interlaced version for the DVD. If you deinterlace and then reinterlace for the DVD you are losing resolution. 29.97 DVDs are interlaced.
Taking the interlaced output back in as a finished file and then using the Nattress deinterlacer on the complete file for the web version is the best way to get maximum results for both uses.
-
[john whiteway] “And why do so many things I’ve read (primarily a long piece by Patrick Inhoffer) emphasize the impotance of exporting and backing up both database and project files? Is this simply as a safely measure in case something screws up when upgrading to 15?”
Yes. In all my updates since Resolve 9 I have just allowed the new version to convert the database. The backup of both database and individual projects gives you the option of importing projects into a new database if the conversion of the old database somehow fails. I backup database and project files on a fairly regular basis anyway to an external drive just in case. Also in the future if I need to revisit a project I can import just that project. So this is just an extension of good practice whenever a new version, especially a beta, is installed.
-
In my small world of indie docos at the bottom of the world X has little traction. The main trend I see is Resolve taking a place at the expense of both X and Pr.
The other trend is away from Apple hardware. I think the hardware trend might be the driver of some to abandon X. But some editors tell me the ease of handover to me by staying in Resolve is also significant.
-
Quicktime player is the likely problem, not Resolve. Try other players like VLC. Also avoiding .mov might help with gamma errors on playback with other players. Judging output on computer screens with players like QT is more likely to reveal issues that have nothing to do with Resolve.
-
Yes that is not expected behaviour and might be a bug related to the camera original footage. One way to tell is to render a 1080p version, bring that back into a new timeline and then output the 720p. If it fixes it then it points to a bug with the camera original format. If it doesn’t it might be a project setting regarding scaling so check your project settings.
-
The output file has some cropping? Letterbox, pillar box, both?
I’ve often output 1080 from a UHD timeline without any issue. While it renders it displays smaller on the screen which is what I am guessing you mean but that is simply because the project and monitoring is set to UHD so it appears smaller on my screen but the output file has not cropping. If it is just the display during render then that is normal. If it is something else and apparent in the file then please clarify
-
If you select a clip in the timeline and right mouse click, the revealed menu will have Link at the bottom of the list. If clips are linked (usually audio & video) that will have a tick next to it. You can unlink or relink the audio & video by toggling this option.
If you select all the clips in a timeline it is possible to use that menu to link all the clips together. That would mean selecting one clip would select all of them in the timeline, which is the behaviour you are reporting. So check that you have not inadvertently linked all the clips in that timeline.