[John Sackey]

I spoke to them (Brad I think) at IBC last year and they’re opening a service centre in Europe but sales are all dealt with via the US website.

The Sony pvm is very good as well. I use them at a couple of places and everyone loves them.

[John Sackey]

Look at the new CM range from Flanders scientific. I think that’s what I’ll be going for when its time to upgrade.

[John Sackey]

Yes that’s what I found when I tried transcoding the first time I came up against this problem. The clip spanning needs to be taken care of before anything begins or else you’ll always be dealing with two bits of media.

Not sure about adding reel names with XF utility. It’s the machine room guys that are dealing with it.

[John Sackey]

Apparently the solution is to process the footage with XF utility before the editing process begins which takes the spanned clip and turns it in to a single piece of media. I’m about to start work on a series where this has been done so I’ll soon see if it works.

I think this happens due to AMA linking rather than ingesting so the spanned clip remains two discreet pieces of media. Other than what you’re already doing I haven’t come across another solution once you get to the conform stage.

[John Sackey]

Hi Konstantin.

Sorry about this but I’m now off that job and in another city for a couple of weeks.

My colleague at the facility I’m working in at the moment has pretty much confirmed that the problem would come from AMA linking to the files and the cameras recording those shots across 2 cards. I have a feeling that these projects have gone too far down the road for the problem to get solved other than to export the problem clip as one piece of media then re-import it. Not a problem on short pieces but not the scenario I want to be in on a 60 or 90 minute show.

I think the best solution in the future is to make sure everyone knows to shoot one card at a time (which frankly they should be doing without being told if they’re any good).

If you would still like a look at those files I can get them to you in a couple of weeks but thanks for your interest and help so far.

John

[John Sackey]

Thanks

I’m just exporting an AAF of the last four shots from one of the sequences with the media embedded. The problem clip is the last one, in Resolve the clip just goes black at 08:17:19:05 while in Avid it continues to play.

I’ve just discovered something interesting in Avid though, at 08:17:19:04 when you watch the clip in the viewer there is the little backwards L end of media symbol in the lower right of the window and when you go on to 08:17:19:05 the forwards L start of media symbol appears in the lower left. Could media spanning in the camera be causing problems? In the other sequence with this problem I’m seeing the same phenomena where the clip turns black in Resolve. The only thing I can think of is media spanning in AMA linked files causing these marks to show up in the middle of clips but It’s been a long time since I was an Avid editor.

The source material started as a mix of C300 Canon footage and XDCAM which was AMA linked for editing. I transcoded to DNXHD 185 MXFs then created an AAF for the transcoded sequences for Resolve. The shots that are giving me trouble are from the CF300 originally. I’m not sure what this means in terms of being OP-1A or OP-Atom MXFs, my understanding is they would become OP-Atom upon transcoding?

Here’s a link to the AAF

https://www.sendthisfile.com/RIFfqcgnrkyJvhtrkblKxsmK

It’s just over 2Gb.

I’m staring to think that this is down to AMA linking to shots that span media cards, exporting the clip from Avid as a QT then reimporting it sorts it out but it would be good to get to the bottom of it and to make sure there isn’t a better workaround.

Cheers
John

[John Sackey]

Nope, it’s all 25fps.

The last frame of picture before it turns black isn’t the absolute last frame of the clip, it just turns black before the clip is finished.

I should probably mention I’m using v8.2.2 as well.

Thanks

[John Sackey]

Resolve doesn’t like ridiculous speed changes basically, it might be fixed now but I haven’t had any work from that particular editor submitted to me in some time so i haven’t dealt with these sorts of things for a while. The work around was just to start baking the speed changes in as even if Resolve linked to the clip it would do weird things on the render, either to source or target.

It was nothing to do with mixed frame rates. I think V9 is supposed to be better with speed changes in general.

[John Sackey]

Are any of you guys using XDCAM footage? I’ve found it can cause issues. Graded a Sequence that was 80% XDCAM, left it to render over night, came back , exported XML, it went in to FCP fine then when it came time to reconform some changes I opened up the project but every time I go to the Color window it ‘unexpectedly quits’, also happens if I’m in the conform window and scroll through the time line too quickly. Every other project in the database loads and works fine and this is the only XDCAM project.

This added to the fact of XDCAM’s notorious instability on mac with FCP etc leaves me pretty sure that’s the problem. The guys at BMD say there’s nothing in the crash logs to indicate REsolve or hardware as the cause.

[John Sackey]

Thanks Rohit, I’m at another facility today but I can get my hands on the XML later today and will send.

John