frame_rate doesn't seem to map predictably across parameters

[aperkes]

frame_rate doesn't seem to map predictably across parameters

[mooch443]

Sorry for the silly speed values :-) I presume that in your case it is using meta data from the video, which is likely set to 1fps from the .mp4 file or whatever. You should be able to overwrite this by setting frame_rate manually during the conversion.

Are you saying this does not work, or did you try entering it in TRex? Setting frame_rate in TGrabs manipulates how timestamps are generated for each frame. These are then saved to the .pv video format and used for important calculations - frame_rate was included in TRex from the beginning, but read-only. Just FYI, basically. Atm it can be changed on startup, but basically mostly affects GUI functionality and calculation of some tracking properties. You are correct in that this should probably be more consistent. I have updated the documentation, but haven't uploaded it yet since that would also change other unrelated things.

Currently, I suggest changing this when you're converting the video - also because it makes sense to set this meta data only once and then have it be part of your video file (in my opinion).

[aperkes]

I only tried setting it in Trex, I'll be less sloppy and just set it in Tgrabs or during ffmpeg conversion (In my defense, I do actually want the video to play back at 25 fps, because watching them at 1 fps is a drag, so Tgrabs is probably the place i'll set it.) Thanks!

…

On Mon, Feb 6, 2023 at 2:45 PM Tristan Walter ***@***.***> wrote: Sorry for the silly speed values :-) I presume that in your case it is using meta data from the video, which is likely set to 1fps from the .mp4 file or whatever. You should be able to overwrite this by setting frame_rate manually during the conversion. Are you saying this does not work, or did you try entering it in TRex? Setting frame_rate in TGrabs manipulates how timestamps are generated for each frame. These are then saved to the .pv video format and used for important calculations - frame_rate was included in TRex from the beginning, but read-only. Just FYI, basically. Atm it can be changed on startup, but basically mostly affects GUI functionality and calculation of some tracking properties. You are correct in that this should probably be more consistent. I have updated the documentation, but haven't uploaded it yet since that would also change other unrelated things. Currently, I suggest changing this when you're converting the video - also because it makes sense to set this meta data only once and then have it be part of your video file (in my opinion). — Reply to this email directly, view it on GitHub <#190 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABRNK6RYAGECVMTI5M62I6DWWF5H5ANCNFSM6AAAAAAUPMB5TY> . You are receiving this because you authored the thread.Message ID: ***@***.***>