Registered Member
|
Hello. I think I am about bald now.
I have been trying to render video and the render either crashes or outputs audio only. First I tried to render a lossless H.264 video, It renders audio only. FFV1 - renders a couple frames only and all of the audio. HuffYUV renders perfectly fine, but is HUGE. 380mb for a 7 second video @ 1920x1080. WMV & MPEG-2 renders audio Only VOB renders fine but is low quality WebM & MPEG4-ASP/MP3 (DivX compatible) Crash with the following error message.
and MP4 - the dominating format (h264/AAC), & MP4-H265 (HEVC) are greyed out. (missing libx264, libx265) Where do you get these how are they installed? I didn't have these problems until I switched to the newest version 17.12.0, Previously using.... Im not entirely sure, 16.x.x I have tried to delete the folders from both appdata roaming & local. All of mt MLT properties appear to be point in the right direction, which is to the current version of Kdenlive i have installed. Im not sure what the problem is, If this a problem in the code can someone please point me to a download for a version that works? Otherwise, some help for my ineptitude is desperately needed. I don't know didly squat about file formats, codecs, coding, etc. I just want a nicely compressed video and isn't too big(filesize), or too lossy that can be uploaded onto youtube. Many thanks. |
Registered Member
|
Are you open to running it on Linux?
|
Moderator
|
just replace the FFMPEG binaries with these: https://ffmpeg.zeranoe.com/builds/win64 ... shared.zip BTW , when switching to a newest version ... better to delete some folders on APPDATA with KDENLIVE name... there are some topics already on this forum.
Please... there is not an installer for Windows users.. and (looking at the forum posts) on latest 3 months ... there have been more installations for windows than for linux. (not defending Windows.. .i hate W10 and Microsoft changes on windows update and market.. i'm thinking to switch back to Windows 8.1 on my main PC) |
Registered Member
|
"I tried to render a lossless H.264 video, It renders audio only."
I just had the same experience. The program took 27 minutes to render a 2m40s video (input was AVCHD 1080p/60 with AAC ambient audio). The result said mp4 but all I got was an 8mb (!) audio file . |
Moderator
|
using these (and with "these" i mean .. this package an not others) binaries? https://ffmpeg.zeranoe.com/builds/win64 ... shared.zip after replacing binaries, kill all old istances of the kdenlive application (or better.. restart the pc) and try again. |
Registered Member
|
Same problem here. Version 16 can find the H264 codec just fine but 17.12 can't find it or use it at all. I've installed it exactly the way the instructions say but it just can't find them. The wizard says they aren't there and the render menu says "Unsupported video codec: libx264"
|
Moderator
|
FFmpeg binaries linked on "instructions" are not working. please use https://ffmpeg.zeranoe.com/builds/win64 ... shared.zip (no issues on 3 Windows10-PC , just tested)
|
Registered Member
|
Well, using those old libraries helped some. I can now render using the OLD-TV Definition presets.
I found a fix for the webM extension, for those having problems with that. USE by creating a new rendering profile and pasting the below into parameters, for generic definition.
Basically you are changing the acodec from vorbis to libvrobis
So you should be able to to do the same for the high def 4k
Kdenlive still cant find the x256 libraries. Not sure how to fix this. |
Registered Member
|
My own experience after ffmpeg bin update as described above:
H265 is not rendering correctly: droping frames H264 is rendering well if it helps... |
Registered Member
|
I have Linux too, but I created a large video project in Windows. How do I port the video project to Linux without rebuilding it from scra**h? (if rendering is promised to work) Starting from s***tch is a huge waste of time. |
Registered Member
|
Guess why. The old AVStream.codec was DEPRACATED (I never heard this particular word in a positive context in my life. This word's meaning is as ugly as it sounds.) They could have kept supporting it SIMULTANEOUSLY, IN PARALLEL, TOGETHER WITH, COMPATIBLE WITH AVStream.codecpar. But instead, they selected the minimalism logic: DEPR***TE! Why not depracate all legacy support altogether, if depracation was a good thing? |
Registered users: abc72656, Bing [Bot], daret, Google [Bot], Sogou [Bot], Yahoo [Bot]