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 <[email protected]> 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?