[Richard Lyons]

Hi guy – thats all really helpful advice – much appreciated, looks like separate layers with Add TX mode plus Glow effect is the way to go… cheers

[Richard Lyons]

Hey guys many thanks for the feedback – thats really helpful, the Cow is a wonderful place! Cheers

[Richard Lyons]

Hi guys – many thanks got it all sorted in the end – freeform pro looks good, but seemed to be Windows only? Cheers

[Richard Lyons]

Hi Dave,

Thanks for the heads up. i actually need markers on a layer in AE, not the sequence, which allow me to have lot more.

[Richard Lyons]

Thanks Dan – works great – you are the man!

Cheers…

[Richard Lyons]

Hi Nick – cheers, even faster.

I tested it fine with a couple of clips and have a question – I have reset the start timecode of the sequence to 01:00:00:00 and trimmed off the front 25 seconds off the main clip so it now has a new start frame. When i export the first clip it still retains the original start timecode of 00:00:25:18. Is there a straightforward way to rewrite / create new timecode for the exported clips based on its position in the sequence timecode rather than its original?

Many thanks,

Rich

[Richard Lyons]

Thanks for letting me know that I am at least swimming in the right direction.. ;-P

[Richard Lyons]

Hi Jeremy,

Have tested the amended capture and sequence settings here and it works! (FCP does see it as progressive and keeps that on export and re-import)… looks like I may have to recapture it all again… 😉 / ;-(

unless you know of another way…?

[Richard Lyons]

Hi Jeremy,

I tried creating the preset (with Interlaced turned off in the Prores Advanced codec options dialog also), dropped in the captured clip, confirmed I did NOT want to match the sequence to the clip (as it sees it as upper field dominant) and exported again. The exported file was still seen by FCP as Upper Field dominant… ;-(

The other issue is that the material (many hours) has already all been captured in this way so to try and avoid recapturing if at all possible…

[Richard Lyons]

Hi Jeremy,

Thats very helpful, many thanks.

If I was using it myself that would not be a problem and I would certainly employ your route, but I am having to supply these to a client who requires the files to be progressive as they are using them in FCP or some other NLE app.

If the files are not recognised as progressive when they import they may reject them…Compressor produced files that import into FCP as ‘None’ but took a long time to render in comparison to the FCP export and I need to create a fast workflow…