![]() ![]() ![]() The Shutter Encoder version has had the audio edits removed to match the video-only EDL produced by Lightworks, and the spacing of the EDL has been adjusted to match the CMX-3600 format. Those related to LUT usage on each of the effect clips and wouldn't affect things here anyway. I have manually edited both EDLs for clarity!!! The Lightworks EDL has had all comments removed. I created an EDL in Lightworks from the original timeline, and I exported that same timeline as an MP4 and used Shutter Encoder to detect the cuts and generate an EDL. The cuts should not have been hard to identify, but I deliberately included one dissolve to see what would happen. I chose that sequence because I felt that it was a good series of cuts between wide, medium and close up shots. ![]() I've just done a test exporting a section of a sequence of effects shots from a feature that I worked on a while back. It also means that things like dissolves are a potential source of confusion when deriving an EDL from composite video and could be missed. The reel name may increment or it may be the same - it wouldn't matter. All that it has to do is detect a change in the video significant enough to be a cut and mark it as a new event when generating an EDL. At one stage they couldn't even reliably read their own EDLs! I don't know whether that's still the case, because I have let my subscription to Media Composer and Symphony lapse, but I would doubt it. I said earlier that Avid were a law unto themselves. I also probably still have the original CMX EDL specification somewhere, which I definitely had as a hard copy. I probably still have the source somewhere about, although it's probably on a floppy, and therefore effectively inaccessible. It was written in Borland C, and was a command line program. The original EDL data could be appended to each event as a comment if desired (although why would you) and the whole thing was only a few K in size. I also provided the option to search and replace reel names, to generate B-roll EDLs for transitions, and to sort the EDL order into A, B or C mode. That was necessary because as I recall slo-mo and GPIs could confuse the issue somewhat, and Avid EDLs seemed to be a law unto themselves. ![]() It usually did this completely automatically, but could be manually overridden if there were ambiguities in the EDL. The situation in the '90s with EDL compatibility was so bad that I wrote my own converter that would take any of half a dozen different "standard" formats and convert them to a CMX format. I'm rather thankful that requirements for EDLs are becoming less and less, although it's still common for colourists to require them for grading purposes. Every manufacturer seems to have their own version. Did I do something wrong or is the EDL format not compatible with Lightworks?Ĭlick to expand.There is definitely no true standard EDL. My attempt to import it into Lightworks was unsuccessful (empty). There I also find a possibility to export an EDL file. " Cut detection" With the previous version 14.1 I briefly tried the function "Analysis" > "Cut detection". Maybe it is different with the version to be installed, or the latest Win 10 version? If I close the browser window immediately and click on "Browse" again, I get to the last used directory as desired. " button : After each program start, my desktop directory is always displayed the first time I browse. " Change input and output points": The opening player, in which the settings are made, must not be closed before converting, otherwise the settings will be lost. Converting with Shutter Encoder solved the problem. The sample rate of 24k in my original file caused Lightworks to crash when trying to create proxies or transcodes. Solution: "Advanced features" > "Force profile" > " high444" (limited compatibility).Īudio Sample Rate: In my case it was good that by default the sample rate of the original is not used, but 48k by default. This profile leads to an error message and abort when converting losslessly. Lossless compression "CQ 0": By default the profile "high" seems to be used, even if "Force profile" is disabled. Tests with the portable version 14.2 for Windows 64 Bit: See also the similar suggestion by user "hugly" to create a ".mov" file for Lightworks. I'm testing Shutter Encoder (thanks for the tip), currently with H.264 (input and output) (mp4). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |