Registered Member
|
There is an issue with the transparency of my PNG images and kdenlive. When I import the image, I do have "transparent for background images" selected.
The top is the actual image. The bottom is how kdenlive see's the image and it renders ugly like that. Any ideas? |
Registered Member
|
Not sure why that happens with Bitmaps. I have always had to do graphics in a vector format. ( Inkscape ) it will do drop shadows but you have to do the text line by line.
Good Luck E |
Registered Member
|
You need a second clip for the transition to work with. In the clip monitor you'll always see this burned-out effect, never mind. In the timeline your png clip needs to have a transition (such as affine) and a clip to combine with; either simply a black color clip or some video clip. MLT needs the second clip, otherwise it simply ignores transparency. So, pngs work fine, as I use them as well as svgs. The trick to understand is you need a background.
|
Registered Member
|
Actually it doesn't help when I use composite or affine over top another video... It still looks poopie, as you can see.
Using the line-by-line method seems like an archaic method. Surely there has to be a solution? It's weird. |
Registered Member
|
What do you mean by "line-by-line method"? I can't follow your train of thought.
What size is your png image? It looks as if magnified. For instance, when your project is FullHD 1920x1080 then either use pngs in this frame dimensions. Alternatively, make sure you use Size 100% in your composite/affine transitions, never check "distort". BTW, the only thing the "transparent background" toggle does is telling Kdenlive to add a transition whenever you drag such marked clips into the timeline. It's a little misleading toggle, I think. |
Registered Member
|
Also not sure exactly of his method... But my PNG was built at 1920x1080, so that can't be the issue but... I could try making ultra high resolution I suppose and see what that does...
|
Registered Member
|
A higher resolution isn't necessary and may even cause unwanted resizing artefacts.
Can you please show how you set up your project and which settings you use for the transitions? Otherwise it is nearly impossible to help. |
Registered Member
|
Not sure what exactly you're looking for but here are some pics that hopefully help.
|
Registered Member
|
btw in the image I switched to using a title clip instead of the PNG file.
|
Registered Member
|
Great! Thanks for posting images, that's really helpful!
One tricky detail catches my eye: why do you use the crop, scale, position effect on the title? That shouldn't be necessary? Another thing? Why is force deinterlace overlay switched on? It's probably not hurting, I just want to be sure. |
Registered Member
|
Crop because I used a semi-transparent background in my title.
The forced overlay was just a shot in the dark, it didn't do anything noteworthy. I wonder if this happens on the 15.x versions... |
Registered Member
|
Uhoh, what do you mean by "semi transparent" background? I'm asking because I've seen problems coming from alpha values that don't proper blend in so you get ragged contour lines instead of smooth: the reason then is that depending on your image the colors don't smoothly blend in too, so alpha values that are not blending well too cause ragged outlines. But, just an idea coming back from some hidden neuron...
|
Registered Member
|
The choppy edges happened before I did anything with transparency.
|
Registered Member
|
And the transparency effect I implemented when I used the "title editor". The issue is only when I import a transparent PNG
|
Registered Member
|
I still don't understand why you don't get the choppy edges, as I have png-based titles used for several videos produced in Kdenlive for my YouTube channel. By the way, choppy edges in the clip preview are normal (MLT "feature"), but in the project view they should be gone when your png clip is composited onto another clip.
Alas, for more complex titling you may consider using .svg titles perhaps? Inkscape is quite useful for this, albeit it lacks the nice feature of the built-in title editor to show the current frame in the background. |
Registered users: Bing [Bot], Google [Bot], kde-naveen, Sogou [Bot]