1.
Bill Kraus has developed a SDK app that does continuous raw image saving. PM him on Flickr for a beta copy. My Therm-App -> FLIR intensity conversion is also now built into his app.
2. Convert your continuous "video" stream of PNGs into .fffs, as before. To do this in batch, you can use "forfiles" on windows.
eg.
forfiles /p sequence /m *.png /c "cmd /c php splitjpg.php -i flir.jpg -r @relpath -o @fname"
When you get to the step of using splitjpg.php, you need to comment out the line
unlink($destimg.".fff");
so that the FFFs are kept.
Upscaling and sharpening etc. in ImageMagick is not recommended as you'll make really, really big output files (768x576 @ 8.7fps for 5 minutes is over 2GB)
2.5. For correct playback speed, you need to set framerate. You can use a hex editor to edit the byte 8 bytes in front of "FocusDistance". Find where FocusDistance is using EXIFTool.
exiftool -v5 sequence\2015-09-27-130630-360.fff > test.txt
In the above example it has been set to 8fps (integers only).
2.75. For correct timestamps on the files themselves (which would allow for graphing), we need to edit the timestamp in the .fff files. Again, EXIFTool can be used to locate where this is.
The first 4 bytes is UNIX Time, the next 2 bytes is secondsx10^-4, the two bytes after that is even more accurate seconds (not really needed in our case), and the last two bytes are timezone.
Note: Reverse byte orderI have a small java app that will read filenames in the format YYYY-MM-DD-HHMMSS-(msec).fff (as outputted by Bill's app) and write to the fff file the correct time.
See attached can't upload JAR, PM me for a copy. All you need to do is pass it your filename (to do for multiple files just use forfiles as before).
3. Write all your .fff files into a single sequence file. You can use window's binary copy command, eg.
copy /b *.fff mysequence.seq
4. Open the .fff in FLIR Tools. Beware a 7 minute file is about ~1.7GB.