In the kdenlive forum there s also a discussion how it would be possible to have a exchange file format, especially for exchanging audio and video with Ardour. âŚ
As a serious response to calimerox though, why wouldnât that format just be Ardourâs session format? It is open, XML, and not the most difficult to understand, though many things in it are measured by audio samples IIRC which is far more accurate than many video editors. Personally I have toyed around with seeing if i can write a plugin for Lightworks to do exactly this honestly rather than deal with AAF or OMF.
The thing is that EDL is a very simpel format, which the links above hopefully indicates, and since Davinci supports edl import, floss NLEs like Shotcut, Flowblade, Kdenlive and OpenShot, would only have to implement export of one format if Ardour supported import of EDL, that is. This way videos edited in a variety of free open sourced programs could be color graded in the free Davinci(needs heavy hardware for editing video) and the audio could be edited in Ardour.
Yes EDL is very simple, but also somewhat limited as well. Donât get me wrong, I would appreciate at least EDL, but it would also be nice to be able to render out a video clip with it and the raw audio and take those direct into Ardour. For instance EDL has no way of exporting a rough track for instance or mix, so if I am working with one or two others that are editing the video and have a basic thought on audio, they canât convey that on an EDL.
Honestly the Ardour session format really isnât that difficult either when you get down to it. It gets LONG, especially on complex sessions, but if just transferring audio files with no editing, it is fairly simple.
Well, I my eyes the choice is between EDL(too simple to carry all information, but easy to implement), AAF(carries all information, but too complicated to implement) and making up a new format⌠If more Video-NLE projects should be inspired to implement a new export format, it should be as simple as possible and have as much effect as possible. I know that Blender has Ardour export(py): http://blendervelvets.org/en/blue-velvet/ But implementing that doesnât solve the need to export to Davinci Resolve too(which imports edl).
Btw. EDL files have an option to add additional info to each clip like " * From clip name: XXX.mov" and I guess that can be expanded to " * Volume: " and suchâŚ
The alterations are done in comment lines following a clip. Eg. " * From clip name: "
These lines are ignored when importing if those features are not supported, so adding these lines doesnât break the format.
Btw. EDL files have an option to add additional info to each clip like " * From clip name: XXX.mov" and I guess that can be expanded to " * Volume: " and such...
Which then you end up leaving behind the strength of EDL because:
Not everyone will support that
You are no longer talking a âsimpleâ file anymore, and in fact structured XML would likely be easier by the time you get into automation.
Notes
An EDL can store notes, indicated by a line starting with an asterisk (*), between event lines. Notes can be used to clarify events for the editor receiving the EDL, and can include information that the EDL cannot store directly. For example, an EDL canât directly store audio levels of a clip, but the audio level can be stored in the EDL as a note. In the EDL Export dialog, you can choose to export one of the Master Comments 1â4 or Comments AâB.
001 002 AA/V C 02:10:42:13 02:11:16:18 01:00:00:00 01:00:34:05
FROM CLIP NAME:DEBRA ENTERS CAFE WS
OPACITY LEVEL AT 02:10:45:20 IS 0.00%(REEL 002)
OPACITY LEVEL AT 02:10:49:12 IS 100.00%(REEL 002)
CLIP FILTER: COLOR CORRECTOR 3-WAY
AUDIO LEVEL AT 02:10:43:07 IS -INF DB(REEL 002 A1)
AUDIO LEVEL AT 02:10:51:16 IS +0.00 DB(REEL 002 A1)
So the usual hack of adding metadata as comments. Ugh.
It is interesting to see that there actually is at least one âstandardâ for an EDL format. I wonder how many there are in total. One of the reasons I never looked into it was the strong impression that the phrase âEDLâ described a concept rather than a specific format. It is also interesting that AAF exists (and OMF before it), supporting the idea that for many (many) things, EDL format is just insufficient/inadequate.
Iâm still not really 100% clear what Ardour users would gain by being able to import/export via EDL.
Adding EDL support has been on my Ardour ToDo list since about 2008. Mainly for automatically importing and cutting and aligning audio (dialog) from edited video. No meta-data (level, x-fade etc) just 4 point edits. So far it never never got beyond some quick perl scripts to generate Ardour Sessions to get a job done. No direct integration into Ardour.
Time to raise the priority a bit, I suppose
@42 Thank you for taking it into consideration. Iâm trying to help out with the Shotcut and the Flowblade implementations, so let me know if I can help out, provide EDLs, info to understand the format or do tests.
@ x42
I looked at your Sodankyla EDL code and it looks like youâve on top of the EDL stuff back then.
Btw. now Flowblade(from next release) will export EDL: https://github.com/jliljebl/flowblade/issues/252
Unfortunately we found out that there are bugs in the Blender EDL import code, so the way of importing an EDL in Blender and then use Blendervelvets script to export to a Ardour session will result in inaccurate timings.
Added by paul:-
" Iâm still not really 100% clear what Ardour users would gain by being able to import/export via EDL. "
I must admit, Iâm puzzled by this too. Iâve spent most of my life working in the television industry but itâs well over 20 years since I last saw anyone using an EDL.
From what I can remember about EDLâs they essentially describe the relationship between linear (longitudinal) formats (usually tape). But does anybody still use tape for video recording? It certainly doesnât get used by the high end broadcasters any more - and even at domestic level, itâs rare to find anyone who still owns a VTR (e.g. VHS a recorder).
So assuming you were given an EDL nowadays⌠how would you access the actual video?
For 16mm and 35mm film EDL is still the standard. You [usually] get a one-light scan which has a matching timecode burnt in. I did a couple of short films like that (soundtrack in ardour)
âŚbut hardly anyone works with real film anymore.
EDL is the lowest hanging fruit, when it comes to exporting from video editors(most of them export edl) and importing the edited project in Ardour. As mentioned above AAF and OMF are also options, but probably to complex for anyone to bother implementing in Ardour. Of course stems could be exported/imported, but those very limiting.
If you donât agree on EDL as a valid path, my question is what workflow would you guys recommend if people video editing in Shotcut or Flowblade wants to edit their audio in Ardour?