Even with fixing the file with a free program like HandBrake as Jeff suggested, sometimes the results will be far from perfect due to the lack of of frames in the original footage.
On the whole it is far better to use files in a project that share a common frame rate, bit rate, audio sample rate, and resolution. I notice a lack of reasonable GOP structure in the file as well which may cause audio sync problems when you come to edit the footage. While most files will play back fine in video players the same files seldom run well in video editors if they do not conform to a standard format most video cameras would use.
If XSplit has any user forums, if it were me I would post questions there as to how to set the program up for use with video editing programs as the online manual is not very specific.
. . . . I notice a lack of reasonable GOP structure in the file . . . .
I do not see any mention of the GOP file length, the only data I can find is that the GOPs are I and P frames only - no B frames and uses one reference frame which should not be an issue.
The conversion issue is not as bad as it looks from the figures below
The average framerate is very close to the desired /specified frame rate, I would expect the conversion to be better than the range of frame rates the figures would suggest.
If my calculations are correct, this is equivalent to approx 0.1% or 3.4 secs, of frames missing in total time of 3429 secs.
I looked at the XSplit forums and manuals earlier and they are a little sparse on posts and information. The program is somewhat basic in its set up - the only option that is available and of importance is the Force constant frame rate.
In that case John if those settings don't enable MEP to use the resulting files, all files will have to be converted again for use in MEP. In OBS, the broadcast settings can be used as file output settings.
. . . . In OBS, the broadcast settings can be used as file output settings . . . .
That is true, if the 'use stream encoder' option is used - however this does limit the encoding format to the same as the streaming format and therein lies a potential issue..
The streaming format should always be set to the receiving/distribution site requirements eg GOPs of 50 - 120 frames length, however long GOPs are not good for editing where a GOP length of 12 - 30 is preferable.
When recording to a different format streaming and local recording are 2 separate processes.
Both processes may use the same source data, eg from the video frame buffers, however when streaming OBS uses the streaming settings, when recording either on its own or while streaming, OBS creates a separate process with a separate encoder and uses the recording settings.
The independent processing saves resources ie to encode once for streaming and then take that stream to decode/re-encode is adding an extra step and possibly losing quality.
. . . . all files will have to be converted again for use in MEP . . . .
As we have seen with the MediaInfo although the local recording Force constant framerate is checked either frames are being dropped or XSplit is reverting to VFR .