Michael Gissing
195
COW Coins
190
DaVinci Coins
3
Solve Coins
Forum Replies Created
-
[Oliver Peters] “A few of the editors mentioned it highly. It’s a free download with donation requested. Seems pretty full-featured and it’s 64-bit Windows and Mac.”
And Linux. It’s working on my Linux Mint laptop. Thanks for the heads up. Pretty impressed so far.
-
Here’s a few more ways – right click on the clip in the edit page and untick link, then select & delete the audio only. Lock the video track and select the audio and hit delete. Go to the Fairlight page, select the audio and hit delete. I’m sure there are even more ways around this as it is a basic function and no doubt in the manual.
-
Resolve has issued a new point update (16.2.6) so that the new fcpxml1.9 is supported. One less thing to worry about. BM sure are quick off the mark.
I must say I’m a bit puzzled by the idea that Sony is to blame for Apple dropping or not at least bug checking codec support. It’s got to be a bug. Just like the weird curves behaviour that people tried to pretend was a feature until Apple fixed it
-
Fairlight page. It only copies audio and so being linked to video is not going to change your video track like on the Edit page or force a clumsy workaround.
Fairlight also shows you layers (which you need to enable) so you place atmos fill on top of the clip and can easily crossfade between those layers. It is one of the most powerful features of Fairlight. The edit page is not the place for audio finesse.
-
[Simon Ubsdell] “Select all the title clips on your timeline by lassoing them.Then edit one of the instances and they will all update accordingly.”
I am doing some titles at the moment so I just checked and changing font deleted all text. Other features can be changed like drop shadow etc but changing fonts on a lasso group doesn’t seem to work
-
All NLE software approaches the same task with slightly different methodology. Vegas is probably the odd one out. Having multiple timelines, stacking them and also using compound clips is how many editors would approach your problem.
I think you are on the right track unless you expect Resolve to be the same as Vegas. It is far more like Premiere.
-
FCP7 was EOLd so long ago. Unless someone has turned the disks into iso images and uploaded them, you might find it easier to buy an external CD/ DVD Rom drive that plugs into a usb port and install from there.
If you want to download an NLE that is vastly better than FCP7 then I recommend Blackmagic’s Da Vinci Resolve.
-
H264. Likely the 8 bit problem. Resolve settings are fine except you should be using 1080p not PsF.
Also weird that the pixel aspect is reporting 1440 x 810. Likely just quicktime players inability to get info correctly. I never trust QT player for anything much.
-
That’s banding not moire. Most common cause is using an 8 bit codec not a 10 bit. There’s a lot of ways to have introduced the problem.
How was the original timelapse made? What codec did you choose to render the timelapse in. What codec are you outputing from Resolve? What TV are you watching it on? Every step there is a potential to cause banding.
-
My experience differs. I work in documentary and never see any ProResRAW from Sony or Canon cameras just the internal XAVC/ H264, 265 variants. ProRes RAW requires an external recorder and as far as I know, Atomos are the only recorder licensed so far. As a codec, it has had little traction in the past couple of years. What percentage of your work is ProResRAW?
When it was released I worried it might take hold in production but so far it just hasn’t for me. But as I said, target the problem, not the symptom. Apple needs a petition to make ProResRAW playback free just like BRAW and I would gladly sign it.