Calf Visinse 3D VR180 Camera Test - Walking with Gimbal

My previous attempts to walk with the Visinse failed miserably. Even when using a weighted rig, carried in two hands, the result was still too shaky to be enjoyed in VR.
So I got myself a gimbal and tried again.
This is a plain walk through the forest, so don't expect anything exiting here. This is about testing the hardware in a challenging environment, where branches and leaves come close to the camera and one can experience real close 3D vision.
Also the rich details of the environment are hard on the video encoding algorithms and provoke huge artifacts when used with poor hardware encoders, or low bit-rates.
The Visinse performs quite acceptable, but there is still room for improvements at firmware level.
To be fair I have to point out that this Video was shot with the 2.1.2 firmware, which is now outdated.
I haven't found the time to do something comparable with my updated Visinse, yet.
However, one can observe the major issues the camera had so far, like (partially) freezing frames for example. I verified that the 3.0.8 firmware still duplicates frames sometimes, when it can't keep up, but at least, it doesn't seem to only freeze parts of the image anymore, which was really annoying.
It still duplicates an old frame for only one eye sometimes, which is also awful in VR.
Besides that we still have strong chromatic aberrations at the sides of the image and the overall contrast is too strong in most situations dropping details in the shadows.
At least the contrast issue has been addressed in the new firmware and the shadow areas are no longer that dark. There seem to be a new option to switch between different profiles, but I haven't found the time to try that one out either.
Once again I used my own lens correction setup to calculate the equirectangular view required for VR180 at YT, when no explicit lens correction data is available for fish-eye. The Visinse can do that projection in real time, but with the 2.1.2 firmware the algorithm worked pixel by pixel, introducing strong distortions. Therefore I did not use the in-camera processing.
This is one thing that seems to have improved a lot in the new firmware.
Maybe I'll actually start using it, because the re-projection the way I do it is very time consuming.
Also the original audio of the camera has been dropped in favor of a field recorders track, which has unfortunately been bombed by my cellphone inducting data traffic noise to the microphone.
But still the original audio of the camera is useless, besides syncing real recordings to it. There is no other way to put it.
I'm looking forward to give it another try with the 3.0.8 firmware, but I need to wait for the weekend to have some usable daylight at this time of the year.