Variable %s_start_tc% indicates zero based TC but %s_info_mediainfo% reports TimeCode_FirstFrame 10:00:00:00

Here you can submit bugreports
Post Reply
User avatar
Silicon
Posts: 98
Joined: Fri Sep 04, 2020 6:34 am

Variable %s_start_tc% indicates zero based TC but %s_info_mediainfo% reports TimeCode_FirstFrame 10:00:00:00

Post by Silicon »

Hi
I need to burn the TC into the video by using Timecode Filter. It works correctly for IMX50/MXF videos, but incorrectly for XDCAM HD422/MXF videos. I've found out, that for theese videos the variable %s_start_tc% indicates start timecode value 00:00:00:00 despite the fact that json %s_info_mediainfo% reports TimeCode_FirstFrame value 10:00:00:00.
Attached please find the text files with values of %s_original_name%, %s_start_tc% and %s_info_mediainfo%.

I should also mention, that Sony XDCAM Viewer app displays start TC 10:00:00:00.

Any idea why theese two values are different?
Thanks for any advice.
Attachments
XDCAM HD422 clip - TC 10-00-00-00.txt
(27.8 KiB) Downloaded 180 times
XDCAM HD422 clip - TC 10-00-00-00.PNG
XDCAM HD422 clip - TC 10-00-00-00.PNG (225.15 KiB) Viewed 3709 times
BR,
Silicon
--------
FFAStrans 1.3.0.2; WebInterface 1.3.0.0
Manager: VM: 2x Xeon E5-2630v3@2.4GHz, 8GB RAM
Workers: 3x HP DL360 G9 (2x Xeon E5-2643v3@3.4GHz,16GB RAM, nVidia M2000)+ 2x Lenovo SR665 (2x AMD EPYC730216C@3.0GHz,128GB RAM, nVidia P2200)
User avatar
Silicon
Posts: 98
Joined: Fri Sep 04, 2020 6:34 am

Re: Variable %s_start_tc% indicates zero based TC but %s_info_mediainfo% reports TimeCode_FirstFrame 10:00:00:00

Post by Silicon »

Oops, it seems I have reported identical issue as user "taner" did few weeks ago - Variable | Start TC | Wrong Result. Sory for that :roll:
BR,
Silicon
--------
FFAStrans 1.3.0.2; WebInterface 1.3.0.0
Manager: VM: 2x Xeon E5-2630v3@2.4GHz, 8GB RAM
Workers: 3x HP DL360 G9 (2x Xeon E5-2643v3@3.4GHz,16GB RAM, nVidia M2000)+ 2x Lenovo SR665 (2x AMD EPYC730216C@3.0GHz,128GB RAM, nVidia P2200)
momocampo
Posts: 592
Joined: Thu Jun 08, 2017 12:36 pm
Location: France-Paris

Re: Variable %s_start_tc% indicates zero based TC but %s_info_mediainfo% reports TimeCode_FirstFrame 10:00:00:00

Post by momocampo »

Hello Silicon,

Maybe a stupîd question but did you check the start tc inside the timecode filter? It could be a trap because the default value is "00:00:00:00" and not the source file start tc (%s_start_tc%). You have to change that if you want to be ok with your input file.
Cheers.

B.
User avatar
Silicon
Posts: 98
Joined: Fri Sep 04, 2020 6:34 am

Re: Variable %s_start_tc% indicates zero based TC but %s_info_mediainfo% reports TimeCode_FirstFrame 10:00:00:00

Post by Silicon »

Hi @momocampo.
The Timecode filter has "Use original medias start timecode" option checked.
And the workflow affected works correctly for IMX50/MXF files.
Attachments
Timecode Filter.PNG
Timecode Filter.PNG (10.26 KiB) Viewed 3697 times
BR,
Silicon
--------
FFAStrans 1.3.0.2; WebInterface 1.3.0.0
Manager: VM: 2x Xeon E5-2630v3@2.4GHz, 8GB RAM
Workers: 3x HP DL360 G9 (2x Xeon E5-2643v3@3.4GHz,16GB RAM, nVidia M2000)+ 2x Lenovo SR665 (2x AMD EPYC730216C@3.0GHz,128GB RAM, nVidia P2200)
momocampo
Posts: 592
Joined: Thu Jun 08, 2017 12:36 pm
Location: France-Paris

Re: Variable %s_start_tc% indicates zero based TC but %s_info_mediainfo% reports TimeCode_FirstFrame 10:00:00:00

Post by momocampo »

Hello,
Ok you're right, there is a bug.
This bug will be fixed in the next release, the 1.2.1.

;)
B.
User avatar
Silicon
Posts: 98
Joined: Fri Sep 04, 2020 6:34 am

Re: Variable %s_start_tc% indicates zero based TC but %s_info_mediainfo% reports TimeCode_FirstFrame 10:00:00:00

Post by Silicon »

Helle dev team
I can confirm that this issue is fixed in version 1.2.1.
Thanks for that!
BR,
Silicon
--------
FFAStrans 1.3.0.2; WebInterface 1.3.0.0
Manager: VM: 2x Xeon E5-2630v3@2.4GHz, 8GB RAM
Workers: 3x HP DL360 G9 (2x Xeon E5-2643v3@3.4GHz,16GB RAM, nVidia M2000)+ 2x Lenovo SR665 (2x AMD EPYC730216C@3.0GHz,128GB RAM, nVidia P2200)
Post Reply