Marc Wielage
Forum Replies Created
-
I would insist that Tero SING the entire manual, perhaps to classic Beatles songs or maybe with a rap percussion accompaniment.
-
I would keep the originals for the simple reason of “protection against disaster.” If calamity struck and multiple drives failed, it’s nice to have the ability to go back to the “original” originals and redo the transcodes. But once the project is done, you could most likely wipe the MT2T files and just keep the transcodes. Drives are cheap.
-
I think Tero is a smart and funny guy, and he’s actually right.
Read Jonny Elwyn’s article on Color Management, which explains part of the problem:
https://jonnyelwyn.co.uk/film-and-video-editing/colour-management-for-video-editors/
Short version: everything looks different on uncalibrated devices, and some operating systems affect the accuracy of colors and level in playback.
-
And on the Advanced Panels, it’s Upper-Shift Display/Cursor to confine the Window Outline only to the Viewer display and not the grading display. It is possible to make this a macro with an external 3rd-party device and do it with the View dropdown selections.
-
[Eric Santiago] “I know this is old but I didn’t see an option for handles on both head/tail.”
In “Individual Clip” mode on the Deliver page, go to the Video tab, open Advanced Options and select “Add ___ Frame Handles” and it will do so to the head & tail of the shots. -
Very bad format for post. Convert it first to a more post-friendly format. There are a zillion conversion programs that will transcode to DNxHD or DNxHR or ProRes out there. For the most part, all Long-GOP H.264/H.265 format are problematic. M2T (MPEG-2 transport stream) files are intended as final delivery files, not for editing or color or VFX.
-
[Bouke Vahl] “Try to totallly crash a shot, (crush all blacks, flatten out all hightlights). Then add a node, and bring it back. Normally, this would be impossible, but in Resolve this is no problem at all.”
That is not exactly true. It is possible to create a “destructive” correction early on in the process that can’t quite be undone later on in the node tree. So there are limits, even with 32-bit float. -
I have seen this happen on rare occasions. Find another spot, move the X crosshair there, and try again.
-
What display are you using for grading? What is the ultimate distribution destination for the project?
In general, if you’re a beginner, my advice is to keep it simple and just use a calibrated Rec709 monitor and forget about anything more complex just yet. Amira and Alexa work just fine in Rec709 — it’s not like certain colors are going to hit a brick wall and fall down.
If your project eventually gets sold for 4K HDR distribution, then you’ll need to think about how to get there… and that’s a long, complex, and expensive road.