Resolve9 Lite not reading TC right

[Gunleik Groven]

Ok. 1st I thought I'd have messed up, but then...

Get the "timecode extent" answer on conform

Guessed I had messed up, but it seems resolve doesn't read the AC right.

Have tried with single clips to conform, and same shit.

Project edited in FCP7, 1st shot at resolve9 lite. Have done my fair bit of conforms in my life, but this is confusing


TC in FCP (and is the same in RCX)

Resolve message:

Resolve TC read from r3d (also claims the reelname to be wrong BTW)

 

[Matthew Scott]

Same here...

 

[Kevin Marshall]

Can't tell from the grabs, but did you use subclips in editing? That's usually when I've seen Resolve give the timecode extents error. Resolve doesn't like subclips.

 

[Gunleik Groven]

Can't tell from the grabs, but did you use subclips in editing? That's usually when I've seen Resolve give the timecode extents error. Resolve doesn't like subclips.

Resolve 8 had no issues of several instanses of the same clip being used. But it is a good hunch. Most of the piece is from one recording.

Only problem is that even when I try to conform a single clip, same thing happens.

RCX conforms just fine though. And it conforms the prores files fine.

 

[Gunleik Groven]

"It" in the above post being Resolve...

 

[Gunleik Groven]

Hm...

Updated everything to check if this was a system incompatibility, but result is still the same.

I am apparently not the only one seeing this...

 

[John Tissavary]

Check and make sure that you're reading absolute, some devices like the Pix 240 cause the metadata to come through incorrectly ending up mixing absolute & edgecode.

To force absolute:

Settings > Camera Raw > Red > Timecode: absolute (not 'camera')

 

[Gunleik Groven]

OK. THX will try.

I have conformed some 15 hours of material in Resolve (full) 8 with TOD, but I'll try.

The proxies are from RCX, exported the same way I used to work with Resolve 8...

But I haven't tried this! Thanks!

G

 

[Shiblon Wixom]

In my experience, the FCP7 project may be corrupted. If you transcode with video + sound synced, and then in FCP7 you move or slip or offset the embedded audio or video away from each other, sometimes it will cause a bug and report or track incorrect TC info. At which point your xml or edl will be off slightly or out of whack and need to be manually readjusted in Resolve or CS6. Try out putting an XML or EDL and re-import into FCP7, it will probably be wrong as well, indicating your project is corrupt.

 

[Peter Chamberlain]

Just for confirmation, Resolve full and Resolve Lite use and offer the same conform functionality. If you have found an issue in one it will be in the other.
One hint to help chase your issue. Review the Conform EDL list of timecodes for in and out points and see if this matches your FCP project.
Peter

 

[jimhare]

Another thing to look at - if you used muti-cam editing in FCP then all bets are off...

The only way I have found to get out of FCP when using multi-cam is via EDL instead of XML, as FCP screws the entire thing up and you just get random TC throughout.

 

[Gunleik Groven]

Thanks. Know about the multicam thingy. Have kinda conformed a bit in my day...

 

[Gunleik Groven]

Thanks. The "Absolute" did it... Silly but true!