Re: Experimental version - 0.8.27
1) Processor: AMD Ryzen 5 2500U - 4 cores, 8 logical processors:
a) 2 Instances, 1 camera each, idling (not recording): 4 at 0%, 1 at 25%, 2 at 50%
b) 2 Instances, 1 camera each, recording: 4 at 0%, 1 at 25%, 1 at 50% with spikes, 2 at 100%
c) 1 Instance, 2 cameras, idle: 6 at 0%, 2 at 50%
d) 1 Instance, 2 cameras, recording: 6 at 0%, 1 at 25% with spikes, 1 at 100%
I think you are right - It looks like the 2 Instance mode gets twice as much processing power, which may be what lets it double the frame rate. Is there any opportunity to use additional threads/cores?
2) The xml file I was referring to is the Capture History in App Data. I think both instances of Kinovea are trying to write to it at the same time. I uploaded the xml file and the error text in bug tracker #421.
The AutoIt script hits record for Instance 1 (Face On - FO) and then record for Instance 2 (Down the Line - DL) with no wait time in-between to keep the two recordings as synced as possible. It also ends the recordings almost simultaneously.
The error seems to have gone away after I added a 0.05s delay between clicks. I also uploaded the Capture History after adding the delay. The file entries after adding the delay only show the Instance 2 (DL) recordings, whereas the earlier file entries without the delay show recordings from Instance 1 (FO) and/or Instance 2 (DL). Some of this is due to the 1 Instance, 2 Capture Screen setup runs also.
I installed a second version of Kinovea in its own directory so that the two instances would not share files, but it appears that they both are still using the same C:\User\App Data\Capture History\Date.xml file.