[Cin] exportEDL, timecode patches

[Phyllis Smith]

OK, checked into GIT, the export edl patches for CMX3600 generation.

Andrea, if you have time, could you rebuild just to make sure everything
compiles OK for you (and maybe try to load into another NLE to see if you
have more success or if we just do not know how to do it.

Andrew, you should check my work because there were a lot of patches and
then patches to the patches, and I am easily confused.  So in the end, I
believe I got it right.  Here is what I ended up doing:
(1) added exportedl.c.patch,
(2) ignored 0001-..., 0004, 0005, 0006 exportedl patches in this thread,
(3) applied patches 0035-..., 0036, 0037, 0038, 0042, 0043.
(4) Recompiled and tested cinelerra with a bunch of cuts and moving
sections around to generate an Export EDL file.
(5) Manually looked at the generated CMX3660 video file and saw that it
"seemed" to look comparable to explanations in:
   https://xmil.biz/EDL-X/CMX3600.pdf
pages 11-14

Also, applied Andrew's patch (for high fps) to pluginfclient.C to match the
other changes in ffmpeg.C.  Like I mentioned previously, I have not tested
nor know how to test.

Andrew, I found the Android tablet (that has not been powered on for 3-4
years!) and am moving on to checking out Termux.  At least I hope I can.
Thanks for all the work you do to keep Cinelerra going. ...Phyllis

On Mon, Jul 5, 2021 at 11:30 AM Andrew Randrianasulu via Cin <
cin at lists.cinelerra-gg.org> wrote:

> Updated patches, this time I tried to import resulting edl into Final Cut
> Pro for PPC Mac (mac os 9.2.2 on qemu/andoid 0.o) and they worked at least
> cuts show up, and dissolves (there currently no code for handling wipes)
>
> I am not sure if ^z^z tail actually harmless, you can comment writing this
> tail in patches if unsure/want to test different NLE
>
> yeah, I missed newline after FCM line, and last line in file..
>
> for my surprize FCP 1.2.5 (from 1999!) uses Windows line endings (seen as
> ^M in mcedit) - may be they were re-using dos/windows code there?
>
> I simply run 'unix2dos -f' on edl file from patched CinGG and then
> optionally set Document/creator attribs (mac-specific, under Macos 7.5.5 in
> Basilisk2 emulator, with ResEdit app) to TEXT/KeyG (four symbols for each,
> case-sensitive! ) - this allowed FCP to see my edl correctly, but you can
> select 'show all files' in import->edl menu under 'file' menu item..
>
>
>
>
> On Monday, June 21, 2021, Andrew Randrianasulu <randrianasulu at gmail.com>
> wrote:
>
>> I think I enabled _writing_ timecode info into rendered files (tested mxf)
>> if you set timecode for your timeline manually - it should be respected.
>> If you render selection of your timeline  - timecode will be set at start
>> timecode of your render position.
>> if you render selection with already altered (via clapping icon) timeline
>> - it also should work.
>>
>> I found you (sometimes?) need to hit 'align timecodes' menu item for
>> refreshing asset timecode info.... but such action will mes up timeline if
>> some assets had no real timecode info....
>>
>> Anyway, try to test those patches and told us how useful (or dangerous?)
>> they are...
>>
>> In theory I think this is good idea to get embedded timecodes into
>> rendered files (rel. to your working timeline) , but may be you sometimes
>> want zeroed tc in output files?
>>
>>
>> --
> Cin mailing list
> Cin at lists.cinelerra-gg.org
> https://lists.cinelerra-gg.org/mailman/listinfo/cin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cinelerra-gg.org/pipermail/cin/attachments/20210708/1f578d6a/attachment.htm>