Trex Quitting Unexpectedly + TGrabs not showing up on Trex

[chaerimkang01]

Trex Quitting Unexpectedly + TGrabs not showing up on Trex

[mooch443]

Hey,

so from the Log (and screenshot) I can see that there is a problem with the video apparently. It cannot read frame 981, despite the video apparently reporting 983 frames - this could easily be fixed by running

ffmpeg -i video.mp4 -c copy video_fixed.mp4

which remuxes the video to the appropriate length (with barely any time spent, since it is not re-encoding it). Can you let me know if this works?

Despite this, the tadpoles should be tracked in TRex (given correct settings). TGrabs only tracks individuals if you pass it the -enable_live_tracking parameter on the command-line, too. Not sure whether you've adjusted any settings in TRex yet (probably have), but take a look in TRex at what is displayed when you press D there (see here: keyboard shortcuts). It should switch to the RAW view and display numbers. The numbers next to the tadpoles should be cyan if they are in range of your blob_size_ranges settings (see also here: parameter order).

Just a few pointers at the risk of telling you something you already know! Hope it helps :-)

[chaerimkang01]

Hi thank you so much for the detailed response! Yes, copying the video did work. Is it a problem on my end regarding video format? While this is a quick fix, it is a bit inconvenient to have to make a copy when I'm analyzing many videos and it would be great if I could solve the root of the problem too!

Appreciate your work :)

[mooch443]

Hey,

so this is not just doing a "copy". It actually "remuxes" the video, so that the length/timings and so on are correct in the video file itself. It should be quite safe to remove the old file after remuxing it (since codec=copy), but you should make sure that nothing else is missing before you do it (e.g. additional audio/video channels).

However, to me it seems that the video is being converted and the .PV should exist in your system already despite the "crash". Actually, the crash is only a crash of the opening process (the process that opens TGrabs) and not TGrabs itself, as far as I can tell. Of course it isn't pretty to have this happening, and I am "working on it".

-Tristan