[Mark Rodway]

Could you not export directly via compressor? Saving creating the self contained movie in the first place?

File>Export>Using Compressor.

It’s a work around for the time being – but isn’t resolving your issue….

Regards,

Mark

[Mark Rodway]

April,

How big are these stills? Best practice seems to be to keep the resolution down to about twice that of the sequence resolution.

I believe .png is better than jpeg also – so you could try this?

Regards,

Mark

[Mark Rodway]

Keith,

We’ve just got the default 8 tracks of real time audio set…………..

How might that influence the issue????

Regards,

Mark

[Mark Rodway]

My pleasure – glad I could help.

[Mark Rodway]

Russ,

Had an opportunity to test the RAM with this project on Friday. Have been on other projects until now.

Render 1 – Both old and new (crucial) RAM – very occasional glitches
Render 2 – New (crucial) RAM only – very occasional glitches
Render 3 – Old RAM only – glitch free – Crucial RAM goes back today for replacement…..

Thanks for the heads up on that one Russell – the errors were so minor and infrequent, but on fairly longform (12minutes+) projects – they were causing me a real headache. I don’t think that I would have reached a RAM conclusion if it wasn’t for your steer.

Great result – many thanks.

Mark

[Mark Rodway]

Not sure that this is 100% technically correct – but if you just change the field dominance of your clips in your bin to None then your footage should then be read correctly as Progressive.

(right click the field dominance tab in the browser – and you can do it on multiple clips at one time)

[Mark Rodway]

It sounds similar to when FCP detects a timecode break. The deck will slow down and frame by frame find the break to be able to carry on recapturing…..

Have you checked the tape to be sure????

To be sure – change your preferences to abort capture on timecode break and see what happens – best of luck.

Mark

[Mark Rodway]

Just to follow up with what was the issue……………

Thank you Michael – I’d suspected it might be the 25 PfS / 50i issue as I said in a previous post – but your post pretty much confirmed that for me.

What I found is that although my timeline was ‘progressive’ – Blackmagic doesn’t support 25Pfs – only 50i – hence the garbled picture on edit to tape. So the deck had to be set to 50i.

A technical query – A ‘progressive’ (no field dominance) timeline – laid off onto tape at 50i – is that still technically progressive – as both fields are the same???????

Many thanks for your input – everyone who has posted.

[Mark Rodway]

Eric,

Thanks I’ll double check for that – and indeed it is a HDW – M2000 (I think I may have noticed if otherwise!!!)…. It looks like more than a sync issue though. I’ve left for the evening now – but I thought that I might check the settings on the deck – I’m 99% sure that 1080 25pfs was what it was showing…..

Mark

[Mark Rodway]

Russ,

Hmmmmmmmmm………….. That’s a sharp insight……

Yes, we have added additional RAM in recent months. We’ve added an additional 4x2GB crucial RAM.

What effect might this be having – and what’s my solution.

Many thanks for taking time to work on this issue with me.

Mark