After more than 1.5 years of work, we are planning to release the refactoring version of Kdenlive in august, part of the KDE 18.08 Applications release. But taking such a decision is not easy. Most of the code was rewritten, which also means many possible regressions. So while we are very excited to have the opportunity to finally release our work to the public, it’s also a bit stressful. So what now ?
Well that’s where we need you. The latest refactoring code has been published as an AppImage, and we need some feedback. So you can help us by downloading the latest AppImage, and try it on your computer (just download the file, make it executable through your file manager and run it).
Improvements and new features include:
- Clips with video and audio are now automatically separated when dropped in timeline
- All clip types in timeline can now easily be disabled/enabled
- Slowmotion should work reliably
- The long standing issue where moving groups of clips corrupted timeline should be gone
- Most effects now use a common keyframe interface
- Insert/lift/overwrite should work reliably
- Easily share your rendered video through KDE’s Purpose library (YouTube, NextCloud, Twitter, Kde connect,…) requires a recent KF5 environment, not enabled on the AppImage.
- It is now possible to generate lower resolution clips for the timeline preview to have a faster rendering
- Resizable track height
- Several overlay guides available for each monitor
- New keyboard layouts can be installed in 1 click (we need help to create interesting layouts)
And most importantly, the code is now much cleaner and ready for new features.
You should be able to create new projects, add clips, move them in the timeline, add effects and compositions, and render your projects. But there are still a number of known issues that we are working on:
- Compatibility with older kdenlive project files is not perfect
- The curves effect does not work (Bézier curves works)
- Composition settings don’t update on resize
- A performance issue in audio thumbnails causes major slowdowns on high zoom levels
Some feedback on this beta version would be really appreciated. So please help us, test this AppImage version and let us know what you think of it. You can leave comments in this post, or on our mailing list, and we will soon organize a bug squashing day to make this release as reliable as possible!
So we hope to hear from you soon!
Where do you want the feedback? Forums? Blog? Bugzilla?
So far not even 1 crash 🙂 great work!
“You can leave comments in this post, or on our mailing list…”
I believe they aren’t ready to accept feedback within the KDE bug tracker as of now.
I’ve never used Kdenlive before so jumped on this version. With Fedora 28 it works well. Some minor UI issues in a few minutes of testing but basic usage of separate video and auto files rendered together was fast, easy, and turned out well on my first ever use of it. Seems great to me 🙂
Hey guys! Amazing work so far! I’m in love 🙂
Video and audio workflow is great, transitions work (and moving these things in groups doesn’t cause corruption on Re-Open! :))))))) )
I found a couple of bugs so far that I’ve put into a video. 1 or two of them are to do with effects, but I suspect that you guys probably know about them already, so please forgive those if you do.
I’ll do more testing and come up with some better reports, but this is a quick little report.
https://drive.google.com/open?id=1T5ULFHnHe4jM1vWUVkA3enygxHJvc2z8
Thanks again! Looking forward to the future of Kdenlive!
Did you guys write some automated tests for this refactor or nah?
Yes, will post here what alcinos responded to you on Reddit for people here to be aware of as well:
==== begin quote ====
You’re probably looking at the wrong branch. The correct one is “refactoring_timeline” and has a full tests/ directory : https://cgit.kde.org/kdenlive.git/tree/tests?h=refactoring_timeline We currently have 4k loc for tests alone, amounting to 2-3k assertions. We use Catch (https://github.com/catchorg/Catch2/tree/master/docs) and Fakeit (https://github.com/eranpeer/FakeIt) and are setting up a CI to monitor coverage and test breaking. We also fuzzed the timeline operations in the early stages of the project to discover corner cases of the operations. So yeah, safe to say that the project is “tested” to some extent.
Of course I won’t claim that it is bug-free, and that we will never hit any regression ever, especially since it is incredibly hard to unit test UI interactions. But then again, this is a complicated piece of software, and even pro softwares like Premiere also crash a fairly often. And yet they have a dedicated development team, not just 2 developers on their free time.
==== end quote ====
Hey, since you seem to know about this stuff you are welcome to join the devs and give us a hand. 😉
Did you solve the multicam sync problem in that new form of Kdenlive? Something like Pluraleyes for Adobe Premiere? Thank you for your work.
I am a big fan of Kdenlive and I have two important quick notes on the new features:
1- Splitting audio and video by default is very annoying and I don’t remember I needed it, so pleeeease put this feature as an option and make it as default.
2- The option to add effects and transitions when right click on A/V tracks is removed, pleeeeeease put it back because it was very helpful.
Finally I hope you add a link to Kdenlive site to post any wish/bug directly without a need to have an account, that will be very helpful and encouraging.
From now on the a/v splitting will be the only way forward if we want to add professional features such as advanced editing tools.
You can report bugs for the refactoring branch here or the mailing list, otherwise you’ll have to use the KDE Phabricator or Bug tracker.
Regarding the A/V splitting, why does a video clip retain audio data even after it’s been split in the refactoring branch? After it’s automatically split, if I delete the audio and then move the video down into an audio track, it turns back into audio.
If you don’t let us move audio clips into video tracks, maybe you should also disallow moving video clips into audio tracks?
For the record, I also find the A/V splitting extremely clunky and annoying, but if that’s going to be the way it is, I would hope it at least works in a logical manner.
I have some notes about keyframe editing and showing it in timeline.
1- Showing the keyframe in timeline is useless specially of there are more than one keyframeable parameter.
2- The ability to modify the ease in and ease out of the keyframes is very limited.
So, this is my suggestion of more usable keyframing interface.
1- Each keyframeable parameter should have a way to activate it, like having a small button beside it or changing its color.
2- There must be a separate panel to control the ease in and ease out of the current a active parameter, and one parameter is activated each time.
I have an experience with 3DS MAX and blender, and I think these professional apps should be learned from to get a better keyframing interface.
Best wishes,
Splitting Audio is the first thing i did in every project since starting with kdenlive 🙂
Every professional grade tool does that! Good work.
Final Cut Pro X is a “professional grade tool” which keeps the audio and video as part of the same visual “clip” in the timeline until you choose to manually detach it.
It’s simple by default and powerful when needed.
I always split/separate video and audio but they are still together. Only when you ungroup a clip then you can delete either video or audio. But if you could delete audio just after dragging into the timeline this would be a bug.
It’s not about whether they’re functionally locked together, it’s about the visual cue that they’re part of the same object.
I actually do use separate video and audio clips in a lot of my projects, but with the current Kdenlive I’m able to group them together and move them anywhere in the timeline that I want (and I use mostly video tracks because I can enable/disable audio/video per-track anyway.)
In the new version, audio clips can only be in audio tracks, which means I’m going to end up having a bunch of empty space in between corresponding video and audio clips. That makes it harder to see what I’m doing and harder to click on things that I want to move.
If the default layout gave us alternating V/A/V/A tracks, then that would make more sense, but it would also make video transitions more complicated because now you’ve got audio tracks separating the video tracks. It’s adding so much complication to my workflow that simply wasn’t present in the current version.
After the Paris Sprint we decided to always have the tracks separated in order to add professional features such as advanced editing tools. This is paradigm we ended up choosing in order to move forward.
The term “advanced editing tools” is extremely vague and subjective. Thanks for letting us know you’re locked into your paradigm, though.
Hi, I meant to say advanced *trimming* tools. Here you can find out a bit about them:
https://kdenlive.org/en/video-editing-applications-handbook/#trim
I cannot test at the moment (vacation). Would it be helpful if you could select/lock an audio track i.e A2 and when you drag a clip onto the time line all audio track get onto that A2 track. On the end you can mute this A2 track. BTW: They start to clear the mismache of video/audio track.
As in set it as the target/active track?
Oh, enjoy your vacation. 🙂
@farid. I meant select by double click an a video or audio track (on the header part). So when you drag a clip onto the timeline it get on this selected one. As soon as you double click another track this get locked. (On my vacation Win 10 PC I don›t have a virtual machine installed for testing).
Will there be a windows version?
Soon.
I have encountered a couple of problems in a few minutes of use. Position and Zoom effect is no longer able to use keyframe. (Possibly other effects also) I cannot change the length of a clip by double clicking and setting the value. It appears to work, but after clicking “Okay”, it will revert to the previous value or even change to an unspecified value. I like the look and feel and hope the bugs can be worked. I love and use Kdenlive regularly.
I believe position and zoom is being deprecated and replaced with Transform.
It’s me or the Zoom is not possible anymore in the Project Monitor?
At the first glance, I thought the same, but the zoom controls appear when you move your mouse cursor to the top right corner of the monitor.
So far, I’ve run into issues involving the Gain effect (not saving what I’m setting it to at all), the Fade in and Fade out effects acting like transitions with regards to clips laid on top of other clips when that didn’t matter before, and I also find the new video/audio splitting system not only annoying, but downright inconsistent (if the video and audio get split and I delete the audio, then it should be gone, and it shouldn’t come back when I drag the remaining video clip into an audio track, but it does for some reason.)
I’ve been giving the refactoring branch a wide berth because I know you guys have been working hard on it, but I’ll be on the lookout for a bug squashing day like you mentioned in your post. I’ve always felt out of place whenever I’ve joined your IRC channel, but I’d love to help get some of the issues worked out before this gets released as stable. Last time there was a big Kdenlive change (with the transition to KF5), I ended up using an old version for nine months while the new “stable” one got smoothed out, and at this point I’m concerned that I might need to do that again.
Sometimes I get the feeling that open-source developers don’t care about the user experience or opinion and only listen to themselves. I hope kdenlive developers will care about our wishes and complains and make it easier to submit the feedback through the site or the app itself.
It seems they solved some bugs in the meantime already. On Sunday / Monday a new beta will come.
As Farid is posting here they look for sure on this input. If you found some inconsistency like audio goes not on video track but the other way around, maybe is a good idea you post such issue on the mailing list or in the bug tracker because then the developer get automatically announced.
I agree with you completely, they are definitely looking for input and I disagree with Mahmoud’s assertion.
That said, the devs asked specifically for feedback “in this post, or on our mailing list,” so it sounds like they’re planning to check up on the comments here.
That is NOT what I’m trying to say at all, Mahmoud. I think the KDE developers (and the Kdenlive devs specifically) care very much about user experience, and it’s only fair that they make the program the way they want it, since they’re doing the work. Please don’t turn my constructive criticisms of a beta branch into an attack on open-source developers.
I am a big fan of open source and kdenlive, and that what makes me angry when I see the apps I love having many bugs and design issues while they can be much better giving the amount of work done in their development.
I do care that kdenlive becomes more usable and powerful,and I would feel sad if more users stop using it because it becomes more difficult and more buggy.
Happy to hear it makes you sad, it means you care. But have you done anything to help? like at least contributing with a bug report? 🙂
Based on what you make this statement? Have you been following everything that has been happening in the last 2 years? Besides having all the communication channels (email, bug tracker and phabricator) open, we have a monthly meeting to talk with the community. So…
It seems that a bunch of users (including me) didn’t like forcing splitting A/V tracks, are you going to do something about this, and I don’t think unsplitted A/V tracks is a problem regarding adding advanced effects.
I wish there is a simple send feedback (wish/bug report) option (in the app and the site) that does not require registration.
Also there should be a wish list where the user can see his/her wish and if it is going to be implemented.
Many times I face some bugs or have some suggestions but I step back when I face a form that requires registration.
Why don’t you put any future changes on the website and see if the users are happy with them, or if they have more important features in their minds.
Are you going to take my suggestions about keyframes editing in your account.
By the way, the Captcha is very annoying when it comes to select images with signs and road, etc, I almost closed my browser and stopped sending the feedback. I spent like 10 minutes trying to finish the Captcha.
Not least due to the level of SPAM we receive we kindly ask you to help the project by correctly registering so you can voice your concern in a properly documented manner. It’s quick, and you won’t get SPAMmed, unlike so many other sites. If you cannot stand captchas (I don’t like them either) and this is your gripe, well, I’m afraid we can’t help you then.
If you don’t like what you see and get, you’re free to help another project or pay for what you need in a commercial product. Open Source is not about everyone getting her own wishes granted by the OpenSourceFairy, but to help each other to get something done by cooperating, making concessions, and also accepting that not every wish gets granted.
It’s like real life, it’s even real life.
We use the KDE infrastructure so you’ll have to subscribe to be able to use the forum/phabricator/bug-tracker. Those are the places to report bugs and features. You can also try the mailing list. 😉
Again I ask you to check out the last blog posts we’ve done where you can see what has been going on…
Do you have a better alternative than the current captcha?
I highly appreciate you differentiated feedback that cares to explain and, well, differentiate. There’s reason and a tiny amount of passion 😉
Regarding the captcha, the images are confusing and you need to do more than one slide sometimes and it get frustrating. So if images are replaced with text input or less confusing images that will be good.
As for the fade in/out, I’m not exactly sure if I remember that idea correctly: there are bascially two groups with respect to how these effects work in the stable branch: those finding it useful and those who don’t. While I personally would have liked to keep the current effects as is, and then adding the separate fade to transparency twin effects, I vaguely remember the open discussion in a cafe to be clearly in favor of the old is broken, fix it. That’s as far as I remember.
You know, I have shown up to a cafe before, and the one I was at consisted of someone I didn’t know saying “we’re going to talk about X,” a few people giving yes/no responses to some very basic questions, and then the organizer deciding to move on.
I appreciate that Kdenlive is developed in the open and that it attempts to involve its community in its development, but from my experience, a cafe meeting should not be considered representative of the entire userbase.
What I’m basically hearing right now is that if I want features I find useful to be retained, I should hop into IRC and whine loudly, which I don’t think is what the developers actually want.
Actually thats not how it works. At the beginning of every Café we decide some talk points openly on a pad and everyone is welcome to opine. Also the first 15 minutes of every Café are free topic open for any one to talk about anything they want about Kdenlive. Also you can always write an email to the mailing list if you have anything to say. You are free to whine loudly but i doubt anyone will give you ears. Remember this is a community project made by people on their free time, so you are always welcome to participate anyway you like.
I just want to say that overall I’m in love! This is gonna be such an awesome release.
I’m giving Kdenlive some pretty bad hardware and very heavy material to work on here, so keep that in mind. A quadcore Intel Celeron N3450 and 4GB of ram, running Kubuntu and editing lots of 4K h264 material and highres images.
For crashes and bugs I’ll try to explain my experience, but it takes too long time to see the exact conditions that produces them. I will talk mainly about proxys.
First of all I need proxys for my material, I went with 1024×576. The proxy experience is inconsistent, sometimes it will report “failed to create proxy” for material that will work later if I create a new project.
If I try to create proxys of many clips at once it will sometimes crash. When it crashes and I reopen, the clips will be set to not be a proxy, but if I try to create a proxy it will be almost instant and the clip is marked with a “P”. This will be false, as the clip is not yet a proxy. I must disable then enable proxy for this clip to make it be the proxy.
This next one might or might not be related to the above problem of a crash during proxy-creation. It seems like it should be though. The clip is the proxy, but will only play until a certain time into the clip, but will then be stuck on this frame during the rest of the clip. This looks like a unfinished proxy to me.
I couldn’t get too much further into editing on the beta on this machine, but the whole thing looks and feels so professional! Incredible. I love the automatic split and dedicated tracks of video and audio. I also love how keyframes work. Great job, when it’s stable it will be an absolute blast to use.
PS: This is on my wishlist and one of the reasons me and a couple of my friends despise Premiere Pro. It sucks at subtitling, the interface is bad and the rendering is equally bad. A dedicated subtitle function would put you ahead of them in this regard. Davinci Resolve has done this best imo, a dedicated subtitle track above all video tracks, each subtitle it’s own clip (not available in the project bin) and a customizable unified track style for all subtitles by default. A dropdown for exporting srt or burning subtitles into video during render. Just wanted to mention it 🙂
THANK YOU FOR THIS!
The fix of the proxy crash will be in the next beta release soon. Stay tuned and keep testing.
Thanks! 🙂
Just did a quick test of the beta. Titleclip template, don’t update after editing. When adding a second video, then part of sound track is not shown, although sound is there when I play the video in the monitor.
That should have state Titleclip thumpnail in list of clips. Sorry.
Hey guys, I’m using Kdenlive 18.08 beta17. It’s faster and smoother than old versions. But I’m having difficulties in generating proxy, whenever I try to generate proxies the project shuts down unexpectedly. Also everytime project theme is changing to default whenever I close the project. Seeking for solutions. Thanks
This as already been fixed and will be available in the next release.
Thank you so much for this! I tried to test AppImage beta 17 with a small example project and got it finished somehow but experienced quite a lot of problems with it:
1. When I added a new video track, then compositing did not work by default on this track: I only saw the picture on the top track, although that image was supposed to be mostly transparent.
The compositing worked by default only on those video tracks that were already in the project when I created it.
When I added “Composite” transition on that layer, then it worked as expected: I saw the image of top track on top of the other tracks. It also started working without “Composite” transition after I switched “Track compositing” setting from default “High Quality” to something else and then back.
2. Sometimes the “Fade to/from black” effects didn’t appear while dragging the respective handles on top corners of the timeline clip. Sometimes they did, but I couldn’t understand what that was depending on. They always appeared when I dragged the “Fade to/from black” effect from effects panel onto video clip on timeline.
3. When hiding or unhiding a video track, the preview in timeline monitor is updated only after changing frame, not immediately.
4. While moving back and forth on timeline, the time cursor in keyframed transitions’ (like “Composite and transform” or “Cairo Blend”) properties panel does not move. The time cursor in effects’ properties panel moves correctly.
5. Splitting clips that have keyframed effects on them gives different results depending on situation and the location where I split them. I would expect that after splitting a clip from between two keyframes, both clips would get an additional keyframe on splitting point so that the visible end result does not change, but I experienced 2 different behaviours at different tries, none of which was expected: a) the first keyframe was moved to the beginning of the second clip and the following keyframes were moved ahead by the same amount of time; b) keyframes were “squashed” close together onto the first clip so that the whole animation would fit on the first clip. It looked like it was squashed by the same amount as the resulting first clip was smaller compared to the initial whole clip (about 3X in my situation).
6. Trimming clips from their beginning on timeline moves effects’ keyframes on these clips by trimmed amount.
7. It happened once that I was unable to add keyframes to a “Composite and transform” transition (“+” button was grayed out on properties panel) that I had already added some keyframes before. This case was fixed by deleting and re-adding the transition, but of course I had to re-add all the previously added keyframes that I had deleted together with the clip.
8. Timeline zone marker is not visible. When I add a Preview Zone, the green bar appears where usually the timeline zone marker should be (the beginning of timeline, first 25 frames), but zone marker itself is not visible.
9. When scrolling mouse wheel while hovering over the “header” of timeline (where the track names and mute icons are), the timeline view does not scroll up or down like it did in previous versions.
10. Spacer tool moves clips only, not transitions.
11. Spacer tools only moves the clips that start after its current location. In the previous versions of Kdenlive, it also moved the clips that had started before the location of spacer cursor but had not ended before that position. This makes it impossible to move all the clips at once if the first clip starts at position 00:00:00:00.
12. Some seconds after deleting any track Kdenlive crashes. It is impossible to recover that project because after pressing “Recover” button on startup confirmation, Kdenlive crashes again immediately.
13. There is no indicator that a track or project bin clip has an effect on it. Previous versions had a star icon for that.
14. While moving clips, effects or transitions around the timeline, Kdenlive often crashes with segmentation faults.
15. I was sometimes unable to drag and drop any effects or transitions on clips (the effects were not put into clip properties after dragging and dropping). Then, after clicking around randomly for some time, the problem just went away.
Anyway, things seem to be improving and I am really looking forward into seeing the next stable version of Kdenlive. 🙂
Wanted to mention something about the transform effect.
This effect is great, especially with controls in the monitor. However, the size slider makes the image scale from the top left corner, when the middle is where you want it to scale from by default. You want to scale from the middle for slow zooms and up scaling small footage, which I think are the most normal operations for this parameter.
It would be great if you could set chapter markers in kdenlive for mp4 files.
The chapter markers I have set with Apple FinalCut Pro X are recognized by all players.
Thanks for the great work!
On my system the 18.08 AppImage crashes right off the bat every time I run it:
/tmp/.mount_UP6i6P/AppRun: line 56: 4142 Segmentation fault kdenlive –config kdenlive-appimagerc $@
I’m on LinuxMint 18.3 with KDE5 desktop.
Can you say what you where doing exactly? Wait for the next release soon and let us know.
Hey,guys!
I have tested the beta version for a while.I find that there are some features in previous version which are pretty useful being removed in the new beta version.I list them in the following list:
Features in previous version:
1、Left click to add a transition while cursor turns into finger shape by hovering it on the left bottom of clips.
2、Easily change transition type in the drop-down menu of the properties window option.
3、Auto-adjust effect range of transition when user moves the clips which are already added a transition
Problem in beta version:
1、Couldn’t add a transition by using the first above-mentioned way.
2、It has only one transition type in the drop-down menu of the properties window option.Couldn’t change the type through it.I have to change it by deleting existing transition and adding a new transition from the transition window.
3、Couldn’t auto-adjust effect range of transition when user moves the clip.
That’s all.Hope these useful features could be put back in beta version.Thanks a lot for your hard work on Kdenlive.
Been using the Kdenlive beta. I add several mp4 videos in sequence. Then I attempt to add another mp4 to a second video track and it crashes every time. Sometimes right when I try to add it, other times when I attempt to manipulate it.
I tried cutting a few clips in Kdenlive Beta 17, sadly after I was done with cutting the first clip and moving the second clip to the timeline the program crashed. When I open it, I’m asked if I want to restore my last progress, if I click ‘Restore’ Kdenlive crashes again.
[quote]
kernel: kdenlive[3793]: segfault at 140 ip 00000000005b3ce0 sp 00007ffd576010a8 error 6 in kdenlive[400000+5a5000]
systemd-coredump[3872]: Process 3793 (kdenlive) of user 1000 dumped core.
Stack trace of thread 3793: #0 0x00000000005b3ce0 n/a (/tmp/.mount_SGnt9G/usr/bin/kdenlive)
[/quote]
Just checked, can’t open the file with beta18 either.
On 18.08-beta17 and beta18, I got a lot of images flashing rapidly in my Project Monitor. If I switch to full screen, the problem stops and if I switch back to my Project Monitor, it’s flashing again. Have a look on this short clip to see what I mean: https://www.youtube.com/watch?v=wf7YLDrdbck
I never had this problem on all stable previous versions.
Seems similar to this: https://phabricator.kde.org/T7082#151035
If not done already, disable GPU acceleration.
Not quite the same IMHO. My timeline is ok. It’s just my Project Monitor who goes crazy, and BTW my GPU acceleration is disable.
Thank you anyway.
Awesome! Thank you so much for your work! Can’t wait when refactored branch become stable.
I’ve noticed a bug. Alpha manipulation/Chroma Key effect. Looks like the Variance slider doesn’t change anything. In previous versions it worked.
Testing 18.07.70
Missing the option to overlay video tracks and click to make a disolve transition. Lot of plugins fail like lift/gamma/gain. What does works and does an amazing job is V.stab.Deshake!
Hey everyone, thank you for all the great work you have done and will do in the future!
I used this appimage briefly and I want to share the issues that I have been having thus far. I may update you with more bugs in the future but I think this is enough for now.
1. Changing themes doesn’t work properly. I tried to change my theme to Breeze Dark and got a message like, “kdenlive needs to be restarted in order to apply the changes.” I clicked Continue and it restarted but did not apply the changes. I have having trouble making Breeze Dark my default theme.
2. Starting Kdenlive stalls when loading up. I normally use version 17.02.0d and whenever I start it, I get a pop-up about not having “dvdauthor” installed. Once I click “Abort”, kdenlive loads immediately. On this version, I see that same pop-up appear but then disappear very quickly and then kdenlive takes about ~17 seconds to start. This is a problem in 18.04.1 as well.
3. No speed function? I can’t find it. I hope we have a keyframable speed function (with adjustable handlebars to smoothen the the flow) in future releases.
4. I can’t find the preview render slider. Normally there is a blue slider I can use above the timeline to create a preview render or only render a selection of my video. I can’t find that here. When I open old kdenlive projects, it is there.
5. Replay won’t work. Once a clip has reached the end, I like to press spacebar to have it play again from the beginning. This isn’t working. I have to manually drag it to the beginning.
6. When I use “Preview” mode for the timeline, the Position and Zoom function doesn’t work properly when I want to move or adjust the size of a picture. If I try to move a picture to the left or right side of the screen, it gets cut off or only goes half of the way there. Changing to High Quality fixes this.
Thank you for taking the time to read this! Looking forward to the next stable release!
Render to mp3 crashes. All other audio format seem to work fine.
If I generate a script and then run it, it will transcode to an mp3, however the rendering speed is about 5x times slower to rendering to all other audio formats.
Output for mp3 rendered without script generation: (Crashes)
//STARTING RENDERING: true , false , “/tmp/.mount_i5RXgW/usr/bin/melt” , “dv_ntsc” , “avformat” , “-” , “consumer:/tmp/kdenlive_rendering_yM3984.mlt” , “/home/elmo2/Documents/untitled2.mp3” , () , (“aq=7”, “threads=1”, “real_time=-1”) , 0 , 6807
Output for mp3 rendered with script. (Renders but very slowly)
//STARTING RENDERING: false , false , “/tmp/.mount_i5RXgW/usr/bin/melt” , “dv_ntsc” , “avformat” , “-” , “consumer:/home/elmo2/Documents/scripts/script001.sh.mlt” , “/home/elmo2/Documents/untitled2.mp3” , () , (“aq=6”, “threads=1”, “real_time=-1”) , 0 , 6807
I will keep the old version, sorry but I can not see anything good in this version and for me the old version works much more intuitive.
I found a few bugs but most of then is already posted by the other users.
Know that this version is heavily under development and will be far superior when it is done.