Registered Member
|
I have video A and image B. The first track has video A which is only 1/3 of the width of the rendering window. Image B is on the second video track and it fills the window. Video A is shifted to the left using "Crop/Scale/Tilt". In this video I want image B to show and then fade in with video A. However, when I do this, there is a black box where video A was originally located that also fades in with video A. Should I shift video A using a different tool? How can I fade in without this black box?
|
Moderator
|
usually i use "TRANSFORM" effect to move a clip around the screen.
but also you can use a COMPOSITION instead an a effect ( COMPOSITE AND TRANSFORM) |
Registered Member
|
Worked. Thank you, but now another issue has cropped up. I have video A1 and A2 which are on the top track and image B which is in a second video track. Videos A1 and A2 do not fill the screen, so parts of image B can be seen. Video A1 fades to black and video A2 fades from black. At the beginning of each, image B will become black for about 0.05 seconds (less than the fade). Why does the fade in one track affect the image in another track?
|
Moderator
|
because on your locale the decimal point (separator) is a comma? ( guessing )
|
Registered Member
|
Interesting "point"! I will keep this in mind because I think I have the problem with black areas or "shadows" in many transitions as well (except "transform", that works flawlessly). In my German locale it would be 1.000,00 EUR instead of the English 1,000.00 EUR. |
Moderator
|
Luckily the latest builds are comma/point FIXED
Linux: https://binary-factory.kde.org/job/Kden ... 4.appimage Windows: https://binary-factory.kde.org/job/Kden ... 64-gcc.exe BUT maybe is necessary to restart the project. |
Registered Member
|
Excellent! My Flatpak just updated to 20.08 (I didn't even try the appimage 20.11 yet). 20.08. works like a charm -- at least so far in my little test: Fade-in/out working now as it should, i.e. without these "shadows", and even the transform effect in the "smooth" setting is now making movements much better: "smooth" now instead "bouncy"
Thank you |
Registered users: bancha, Bing [Bot], daret, Evergrowing, Google [Bot], sandyvee, Sogou [Bot]