Tim Mccallister
Forum Replies Created
-
In the vein of this thread, I too had some old B&W 16mm transferred –> 5K (3840×2880, 4:3 Aspect Ratio, ProRes4444 10bit) but unfortunately due to my naivete, it was scanned into .709 rather than .2020.
Question: Is it worth it to have Resolve remap it into .2020 for doing an HDR correction down the road? Or is this just (an analogy of) creating empty pixels that aren’t there in the first place? I ask because there’s a video tutorial online of how to do this, but it seems on a technical level this would be an empty exercise that doesn’t provide extra dynamic range if it wasn’t there in the first place…
I realize HDR mostly works best with color, but having seen the recent 4K of Halloween (1978), there’s a definite wider range of Bright to Dark, especially in the outdoors sunlit scenes where the girls are walking/talking in their neighborhood, an additional ceiling I’d love to have access to. I mean, Schindler’s List and Elephant Man are in HDR (albeit, by brilliant cinematographers, but still…).
Apologizing ahead of time for my newbie status…
-
Can someone please respond to my post?
Indie Filmmaker
-
Tim Mccallister
March 29, 2020 at 11:09 am in reply to: Create Nested Timeline: Vegas udderly crashes (pun intended)Sorry, that doesn’t help me. It’s pretty straightforward what I laid out.
Indie Filmmaker
-
Tim Mccallister
March 29, 2020 at 7:58 am in reply to: Create Nested Timeline: Vegas udderly crashes (pun intended)Tell me where you get lost.
Indie Filmmaker
-
You know what? The way you did it is just fine. I’m used to doing projects that are multi-level and nested where things have to ripple up. Sounds like yours was a simpler timeline, and the zooming into a larger file on your 1080p timeline would look great.
So, ignore my suggestion.
Indie Filmmaker
-
As this is a week old, I assume you just forged ahead…
When mixing different frame sizes, the Project Settings should match the largest frame size:
In your instance, if your 4K is at 4096×2160, set it to that.
The smaller HD footage will scale up in the Preview Window for viewing purposes.
Do your repositions on the 4K footage.
Then render to the HD frame size.
(The 4K footage will downscale within your project to fit the 1920×1080 frame size.)Indie Filmmaker
-
My video project was at 1920×816 due to an anamoprhic image (2.35). Changing that to 1080p fixed the problem.
Indie Filmmaker
-
Kristian,
I just bought the Intensity Shuttle for USB 3.0
Capturing SD footage to 1080i59.94, with the SD to HD setting on Pillarbox, does NOT Pillarbox; it zooms into the SD image and crops the top and bottom of the original 4:3 footage.
This is seemingly a software glitch in the settings of the Desktop Video Utility. Is there a fix? Blackmagic refuses to address it in the forums.
How are we supposed to capture/upconvert SD footage on the fly if this doesn’t work? I’ve seen this issue around the web and no one is getting answers.
Indie Filmmaker
-
Tim Mccallister
May 8, 2016 at 1:40 am in reply to: Intensity Pro-How to pillar box SD to HD upconversion?I just bought the Intensity Shuttle for USB 3.0
Capturing SD footage to 1080i59.94, with the SD to HD setting on Pillarbox, does NOT Pillarbox; it zooms into the SD image and crops the top and bottom of the original 4:3 footage.
This is seemingly a software glitch in the settings of the Desktop Video Utility. Is there a fix? Blackmagic refuses to address it in the forums.
How are we supposed to capture/upconvert SD footage on the fly if this doesn’t work? I’ve seen this issue around the web and no one is getting answers.
Indie Filmmaker
-
Here you go, everyone…
https://www.dropbox.com/s/jjxeit835e1kko5/FFS%20DV-to-HD%20Workflow.pdf?dl=0
And this is the project the paper refers to — btw, it’s VERY NSFW.
Indie Filmmaker
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.