render output file timecode offset

2015tc

We find some output file timecode offset 1 frame before, but use internal coded render is ok.

So We have make a new project with only 1 clip and render whole clip without grading.

but the problem still happened.

Resolve 18.1.4 , voukoder 13 , Connector 0.10

render setting : inividual clips, voukoder format, source resolution, 422 mov output.

RESULT

Source file : C002C093_2211....MXF START TC 14:14:23:14 END TC 14:17:07:06

render output file : Untitled01281589.mov STARt TC 14:14:23:13 END TC 14:17:07:05

in the log file, time code also is wrong.

[14:14:38] Timebase: 1/25 (25.00 fps)

[14:14:38] Options: _pixelFormat=yuv420p _timecode=14:14:23:13 opencl=1

voukoder.org/attachment/1761/

Vouk

I'll investigate this. Could be just a rounding issue.

Vouk

Can you provide me a clip where I can reproduce this with?

2015tc

Thanks for reply,

We have prepare another clip for your test,

But the size about 3G, How send to you privately ?

Vouk

Maybe you can share this with a filehoster like dropbox, or similar?

iAvoe

Try with a different multiplexing format like MP4 or MKV. I've looked into a bunch of similar issues but they don't seem to be exact like yours. Content below are my researches:

It at first looked like the multiplexer within ffmpeg is rounding, but the offset timing does not match (time code shows 1 millisecond offset, but 25fps is 40ms per frame like START TC 14:14:23:54).

With the high amount of occurence in multiple projects, I assumed every project's timecode offsets the same, this could be the MOV multiplexer received a bad timecode input from ffmpeg (but this bug has been solved, according to the last post)

Assuming every project's timecode offsets differently, this could be caused by a segmented source input, but DaVinci itself doesn't have this issue, which debunks that.

There is a post in the bottom of discussion actually replicated this issue, one reply says specify -r <fps> into ffmpeg may fix this, but there are no more followups.

The log file shows you are encoding at YUV4:2:0 with h264, though.

2015tc

Here the files,

Timecode TEST – Google Drive

1) Canon RAW file 25p : A004C115_190911KM_CANON.CRM

2) Resolve project 25p : Timecode_test2.drp

Thanks,

Vouk

Got it, thanks. Does this happen with all clips or just with some? If it happens to all clips I can just add 1 to the timecode.

2015tc

Not all clips have problem.

We have try different format, run on different pc, different output.

We still don't find the fact that create problems.

Thanks

Vouk

Please update to connector ~~0.11~~ ~~0.12~~ latest version and tell me if the issue has been fixed.

Edit: Improved timecode generation even more.

jonathonirons

Hi, came here because I am also experiencing a timecode issue with Voukoder 13 + Resolve Connector 0.12 + Resolve Studio 18.1.4 exports.

My normal timelines have a starting timecode of 00:59:59:00, at 23.976fps, but the export's timecode starts at 01:00:02:14. If the timeline starts at 01:00:00:00, then the exports starts 1sec later at 01:00:03:14.

I tried different encoders within Voukoder's settings but no luck. I was previously trying to fix an odd resolution output issue that was Resolve's fault, so this is a completely fresh installation of Voukoder 13 and Connector 0.12 that Vouk posted earlier this morning.

Vouk

Right, I forgot about the fractional framerates ... working on it again.

jonathonirons

If I could banish them from the Earth, I would! Love that a 4K HDR project still needs to make sure it's playable on an NTSC CRT.

Vouk

Okay, please try connector 0.12.1.

And for the coders in this forum - This is the current code:

Code

std::string VoukoderFormat::GetTimecode(double seconds)
{
    std::stringstream timecode;

    // HRS
    const int hrs = std::floor(seconds / 3600.0);
    seconds -= hrs * 3600;
    timecode << std::setw(2) << std::setfill('0') << hrs << ':';

    // MIN
    const int mins = std::floor(seconds / 60.0);
    seconds -= mins * 60;
    timecode << std::setw(2) << std::setfill('0') << mins << ':';

    // SEC
    const int secs = std::floor(seconds);
    seconds -= secs;
    timecode << std::setw(2) << std::setfill('0') << secs << ':';

    // FRM
    const double n = m_info.video.timebase.num;
    const double d = m_info.video.timebase.den;
    timecode << std::setw(2) << std::setfill('0') << std::ceil((seconds * d) / n);

    return timecode.str();
}

Alles anzeigen

I'm not sure about the last std::ceil (always round up) at the end ... or if it should be a std::round (round to nearest integer) ...

jonathonirons

Just tested it, looks like the starting timecode went from 01:00:02:14 to 01:00:02:15.

Vouk

0.12.2?

jonathonirons

Well... I'm afraid 0.12.2 is not recognized by Resolve. Voukoder no longer shows up in the list of Formats.

I replaced the bundle with 0.12.1 and it was back. I updated to 0.12.2 again and restarted the computer, and Voukoder was gone again.

jonathonirons

Saw that you uploaded 0.12.3 - just installed it and everything seems to be working now! Thanks so much for your help.

Vouk

Nice! I shouldn't be working that late anymore. It's almost 11pm here.

2015tc

We have try 0.12.3, it works fine and fix the problem.

But it look like will cause some other format have problem.

for example. we have some clips base on arri raw 'arx' , cine file and

mxf file. it works fine under ver 0.10, but have one frame offset in ver 0.12.3.

Thanks for your help.

render output file timecode offset

Vouk 21. März 2023 um 11:46

Benutzer online in diesem Thema