[Chris Tsamados]

Hi Michael thanks for the reply.

I checked the field dominance of the effected clips (I think this is the same as field order?), and it was set to ‘none’, yet the clips which are fine were ‘Lower Even’ and were incidently filmed on a different video camera. I then tried out the shift fields filter to try and correct the problem (I changed it to -1 as I thought this would be the same as Lower Even) but this had little impact. I then tried +1 and None but again these made no difference.

I also used the search facility and was reading a thread that was suggesting that the problem was only visible through a MAC and Quicktime (which I thought would explain the reason why I was’t seeing it onboard the camera or my PC). However when I then played back my sequence on a CRT monitor I could still see the problem. BTW I think its worth adding that I’m shooting in PAL.

I may try burning a DVD and seeing if the problem is evident on it.

[Chris Tsamados]

Well I hope it was that the scratch disks were nearly full because the edits have been TX’d in most case. I think more than likely it was because at the time the MAC hard drive was almost full.

BTW David I checked the Render options and the ‘full’ has been selected. Another theory that the editor has told me is because I am exporting the finished dub as a Quicktime movie it is rendering it for that but not rendering the timeline.

[Chris Tsamados]

Our workflow has now been revised. When we do the dubs the edit points can be cross referenced with the document by clicking the cursor to the beginning of the timeline and using the Next Time button to jump to the edit points. The original timecode is then displayed on the canvas window and you can use the previous and next frame to check the in and out points. Apparently this was known by one of the editors but he had failed to pass it on to me (a Transmission Controller who just does a few dubs every now and then when they are snowed under). Also we now have to spool through the entire dub when they’re completed to make sure theres no black sections.

One of the editors is going to take a look at your method on Monday.

[Chris Tsamados]

Thanks alot for your answer.

Actually an on air problem has just occured because of the way we were working before. Namely I was working from a dub sheet and forgot to press enter after marking an inpoint and then laid the section down to the timeline and it used the previous in point. When the programme TX’d it included a section of repeated footage and also a bit of black. Not good and so easy to make a mistake using our method.

Hopefully we can duplicate your method and avoid these problems again.

[Chris Tsamados]

Yes I do have video on multiple tracks. I’ll give your idea a try thanks.

Hopefully the array is fast enough it’s an Omneon array:

https://www.omneon.com/resource_center/datasheets/DS-MediaStores.pdf

There is a possibility something could have been confgured wrong as we are having a lot of teething troubles while relocating.

[Chris Tsamados]

Anyone have any ideas?

Thanks.

[Chris Tsamados]

Yes it does make sense what your saying but my problem is that its not even attempting to render the transitions even at a reduced resolution. Its just skipping passed those bits.