Blase Theodore
Forum Replies Created
-
hehe nice work.
-
I’m sorry I messed up the name. You need a program called “automap Pro” made specifically for the launchpad, that lets you program the keys with shortcuts. I think its $30.
If you want to use the macros I wrote, you’d need to also buy Quickkeys. In your case, you could just use automap pro and get most of the buttons (including storing/pasting grades 1-8) without quickkeys.
-
I have consolidated this post and will put our requests in the COW Blackmagic forum. If something’s missing, please add now before I post.
-flesh line
-Double-Diamond type display for RGB gamut errors
-Any form of 3D represented Color Gamut (preferably interactive)
-pixel count
-blacking measurement tool.
-matte presets -
Hopefully I’m not thread-jacking this (as I believe the answer is directly pertinent to your job.)
In the event that you’re working with an interlaced HD format and need to go to an SD interlaced format, then the question falls to how resolve samples the frame.
If it samples whole frames (1/30th), sampling an interlaced HD frame would actually be counterproductive, as the sampled pixels would basically be averaged against 2 different points in time. There’s no correlation I’d see between an HD scanline, and what eventually becomes an SD scanline.
If thats the case, would converting to a progressive format right off the bat result in a better image?
If it samples each field (1/60th), then you have something analagous to:
HD_60i can effectively downsample to SD_60p, which can effectively become 60i.
HD_30i can effectively downsample to SD_30p, which can effectively become 30i.If that’s the case, then there could be artifact issues with how 2 fields independently scaled and processed line back up with each other at the end.
An early-on progressive workflow might theoretically improve that as well?Going with the assumption that Resolve has a good downsampling algorithm, has anyone done this comparison test for HD interlaced material?:
- Progressive material in resolve (pre-rendered through compressor, field control: best) rendered out as SD interlaced.
- Interlaced material in resolve (checkbox for interlaced) rendered out as SD interlaced.
If I have my facts spun around, please correct me.
-
[Ola Haldor Voll] “I know for a fact that Compressor doesn’t do a good job. Thin lines and fine details will flicker, and it will be kind of jumpy in “crash pans” or fast motions.”
Ola, when you used Compressor, were you turning on Frame Controls and setting scaling to “best”? It defaults to “fastest” if you don’t change it, which means Compressor sucks if you don’t tweak it.
Figured I’d at least mention it, in case you weren’t already doing that.
Also, make sure you’ve set resolve to “smoother filter” instead of “sharper filter” in the resize setting.
-
Hehe sure, happy to share.
When I get around to the next version, I’m adding the following buttons:
- Config page
- Conform page
- Color page
- combine mattes
- RED metadata popup
If there’s something here that’s still missing, let me know and I’ll try to include it.
-
Ehh, $500 honestly not such a bad deal after they threw in that $19,000 discount for Resolve.
I’m guessing the old DaVinci probably charge $10k for that same “add-on”.Just sayin.
-
Off the top of my head, here’s the formats that I know work from personal experience..
(never tested PAL)If anyone sees one I missed, please add..
- uncompressed (all flavors)
- DVCProHD
- XDCam EX (and probably all flavors)
- Prores (all flavors)
- DnxHD (only tested 220 – requires $500 avid support ad-on)
- H264
- DV
-
Excellent. Marked as solved. Thanks Anders!
-
[Margus Voll] “My idea was to use 2 cubix boxses on slot 1 and 2.”
Right exactly. That may be the appropriate solution (if there was indeed ever a problem.)