SonotaCo.JP
SonotaCo Network Japan Forum
|
 |
|
|
| 前のトピックを表示 :: 次のトピックを表示 |
| 投稿者 |
メッセージ |
ceres
登録日: 2012.02.16
記事: 17
|
 日時: Wed Jun 25, 2025 12:54 am 記事の件名: Time in *.XML files |
 |
|
I have one question - in .XML files, individual points are referred to as "fno". If I understand correctly, if "interlaced"=1, fno means "field", if "interlaced"=0, fno means "frame". So the frequency is equal to fps when "interlaced"=0, and equal to fps*2 when "interlaced"=1. But what is the time of the first frame/field?
For example:
y="2014" mo="8" d="11" h="0" m="28" s="30.230000"
interlaced="1"
fs="59"
so the time for
fs="59" is 30.230000 seconds
fs="60" is 30.250000 seconds
fs="61" is 30.270000 seconds
etc.?
Moreover, the time displayed on each frame of the video is slightly different.
Could you please explain, how it actually is? |
|
| トップに戻る |
|
 |
SonotaCo
Site Admin
登録日: 2004.08.07
記事: 13282
所在地: 139.67E 35.65N
|
| 日時: Sun Jul 13, 2025 10:52 am 記事の件名: Re: Time in *.XML files |
|
|
Sorry for the late reply.
| ceres wrote: | | I have one question - in .XML files, individual points are referred to as "fno". If I understand correctly, if "interlaced"=1, fno means "field", if "interlaced"=0, fno means "frame". So the frequency is equal to fps when "interlaced"=0, and equal to fps*2 when "interlaced"=1. |
Yes,this is correct.
| ceres wrote: |
But what is the time of the first frame/field?
For example:
y="2014" mo="8" d="11" h="0" m="28" s="30.230000"
interlaced="1"
fs="59"
so the time for
fs="59" is 30.230000 seconds
fs="60" is 30.250000 seconds
fs="61" is 30.270000 seconds
etc.?
Moreover, the time displayed on each frame of the video is slightly different.
Could you please explain, how it actually is? |
y="2014" mo="8" d="11" h="0" m="28" s="30.230000" is the PC time + "+msec"(msec) when the trigger frame data was passed to UFOCapture application.
Where "+msec" is the value set in the Input sheet.
In your case , if you set head=60, then it is the time of fs=61.
I believe it is equal to the time shown by super imposed time on the frame.
(be aware that 2 fields in one interlaced frame have same time stamp)
Also, because, there are delays in camera, device deriver, and, Windows's task que mechanism,
a time recorded by Windows application always has some uncertainty and frame delay.
"+msec" is a value for its manual compensation. but some uncertainty cannot be avoided. |
|
| トップに戻る |
|
|
|
|
新規投稿: 不可
返信投稿: 不可
記事編集: 不可
記事削除: 不可
投票参加: 不可
このフォーラムで添付ファイルを投稿 できません
このフォーラムでファイルをダウンロード できます
|
Powered by phpBB © 2001, 2005 phpBB Group
|
Top Page
FAQ
検索
メンバーリスト
ユーザーグループ
登録する
プロフィール
プライベートメッセージをチェックする
ログイン
