this post was submitted on 26 Sep 2024
12 points (100.0% liked)
Blender
2733 readers
1 users here now
A community for users of the awesome, open source, free, animation, modeling, procedural generating, sculpting, texturing, compositing, and rendering software; Blender.
Rules:
- Be nice
- Constructive Criticism only
- If a render is photo realistic, please provide a wireframe or clay render
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Why do you use composite nodes? What do you want to accomplish?
I happen to accomplish similar result with shader nodes on a plane as I am more familiar with them.
image
Edit: made it work as you will still be outputting an image with Output>Format>Reslotution regardless of crop of composited images
So essentially what I'm doing is thumbnails for my yt-videos, the scene itself is my logo & a video episode number (geonode thing that generates number outline, etc, all I need to do is change the number in geonode settings).
Essentially:
the ground "plane" is a shadow catcher.
Then in compositor I want to add eg. game logo & some screenshot/relevant scene/background from game -> position/rotate them (separately) -> done. This is essentialy once-and-done.
Occasionally the logo and background don't play nicely, so the logo needs some dropshadow, for this I sometimes just use the logo's alpha to make a black version of it & offset it somewhat under the original logo.
(the left-corner of the first word of the logo)
And this is where the cropping issue can happen. And as stated in op, I could add padding to the image, but again extra step OR do it logos/backgrounds in gimp.. etc etc, there are out-of-blender options, easy ones. But: Ideally I'd want to automate everything for the ultralaziness. :)
edit: I did at once point add the logos as planes in the scene (as seen in the object outliner), but that was bit fiddlier than just dropping them in place in compositor, and similar "dropshadow" issue still existed, kinda. Some offset second plane does work - kinda. But logos tend to vary in size and aspect ratio, so it becomes fiddly rather quick - the compositor is easier in this case.
So I think the second "alpha over" node like showed in root comment would work. The top link in the node sets the size of the working area so plugging in something in the size of the render region will work. (The scale node is obscured due to my carelessness)
it's still padding but not a bilion of pixels as you feared.
weird, yesterday I couldn't get it to work with generated 4k x 4k square of just alpha, but today it does work a charm. Must have been tired and derped something fierce.
Eitherway, so far, as far as jank solutions go, it seems to be the least jank. Thanks.