Registered Member
|
Hi,
I have a strange problem with latest versions of kdenlive. When I try to play any video (preview / project), it's extremely choppy, even though video is synced to audio. I tried to use many different auio / video drivers (I'd prefer XV and Pulse Audio) and also to turn off audio / video syncing but nothing helps, it's chopping without changes. Also it consumes 100% of CPU (Intel 2.6 GHz), while other video editors / players works absolutely ok (vlc, mplayer, cinelerra, kino, LiVES, ...). I have ATI Radeon HD 2600 video adapter and I use original drivers from ATI without problems Thanks for replies |
Registered Member
|
Version 0.7.6?
Are you working with AVCHD sources? |
Registered Member
|
First of all: Many, many thanks to all the persons, who work on this program :-)
Now to the topic: It seems i have the same problem: Bad performance since the last version. In the last version(0.7.5) i can cut AVCHD (my camera Panasonic SD 300), but now i cant (not with this performance). With the old (and good) DV-videomaterial: no Problem, all ok. I downloaded a another AVCHD-footage and try: There it's the same. I try the SVN Version (today): There it's the same. Now the details: Adding clips to timeline: Programm freeze for a few second. Move around of the Clips in timeline: ok Playing the timeline: - If the clip starts with Clip-beginning at 0 (in-point=0): all ok - If the clip starts has been trimmed, that the Clip-beginning is a few seconds later (in-point>0): BAD :-( You have to wait a few seconds (4-10) a then the timeline is going on playing. How long you must wait depend (a little bit) on the length of cutted out materials at clip-beginning (size of in-point). But with transcoding or the workaround of http://kdenlive.org/forum/not-actually-bug-very-bad-feature-076 i can work :-) My soft-/hardware: Sidux 64Bit, AMD Phenom 4x3,0Ghz, Radeon HD 3200 (driver radeon) |
Registered Member
|
soeren, the behaviour you describe is exactly what is expected. In previous versions, cutting or scrubbing AVCHD would yield artifacts, which can make the render useless. This was fixed in the most recent version, but you pay a major performance penalty. If you can learn to be careful about seeking and be patient, you may use AVCHD directly. Otherwise, you should transcode it as you have done. We are hoping to improve the performance issue, but we opted for slow and correct over fast and incorrect in the meantime.
|
Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]