I am new to this forum and a long time DJI product user. I run into this challenge with my Osmo Action 4 and hope you can help. I searched the forum and online, without luck. Any suggestions and tips are very welcome.
Situation and challenge
I mount my Osmo Action 4 to a moving object (bike, car)
I set up a certain framing when I start
Then when I film on the move (bike, car) and come to a standstill the camera image (not the camera) moves the full frame of the picture down, evey single time
It’s very obvious when watching the footage. See the sample video: https://youtu.be/zqpVVOPRa0E
Then, when I start moving again, it goes back to the original framing that I choose at the start.
Tested settings
This happens in Rocksteady, Rocksteady+ and Horizon balance
It happens both at 60 and 50FPS
I have updated the camera to the latest firmware
I have exhausted my own creativity in switching settings on and off
It’s not the mount that is moving. It happens in any environment/weather condition
As you can imagine it makes that part of the footage useless, or at least demands a lot of post editing.
I think it could be the stabilization, right before it did a jump (that is normal) so it adjust itself a bit and too far down again.
You record in 16:9 or 4:3?
Thank you for the reply. This was recorded in 16:9. I tested it in 4:3 as well, with the same result.
I see what you mean in the sample video.
It happens ever single time when I come to a stop (for example at a stop sign or a trafiic light). And also when I try to do it very slowly. In those situations it feels it only drops, without a jump. But maybe I am wrong.
But have you tried if it happen while walking or just panning/tilting while standing too?
Thanks! I will wait for DJI to reply.
It doesn't happen when walking, panning or tilting. It's " only" in this specific scenario, yet every single time Which makes the footage look very amateurish and therefore useless.
could be the Gyro. when I go to reach for my camera, it's on the move already. I gotten used to this and I try not to let it bother me anymore.. hope DJI can pass this to the team for a real answer good luck.
To narrow down the issue; try turning off all EIS, and use wide FOV d onot use the dwarp, and see if that wondering goes away. As noted by Johensenfoto, you may try a calibration, and noted by Osmonauta, of the earlier thread of the latter model.. Personally I sat dow nthe Pocket 3 and it as well adjusted the Horizon. I should have shown the file but its in my vlog instead enjoy
The only way to stop this is to turn off image stabilization. During the braking process, the gyro sensor is influenced by the G forces that arise during braking. This behavior is also a problem with long curves, recognizable by a tilting horizon (in the opposite direction). DJI hasn't implemented a solution to this problem yet... maybe they can do it in the Osmo Action 5.
Excellent feedback so far. I will definitely read and try the tips mentioned above.
Andreas, I totally get your point, although that stabilization, of course, is one of the charms of the camera. It’s interesting how sensitive the gyro sensor/software supposedly is. Thanks!
as the Gryo can be adjusted only By DJI, they made Off, RS, RS+ and HB, if you want to go into the lower resolution and use HB/ full HB in a lower res. give them a shot, DJI will they correct, think not
Andreas Dueck Posted at 5-31 03:50
The only way to stop this is to turn off image stabilization. During the braking process, the gyro sensor is influenced by the G forces that arise during braking. This behavior is also a problem with long curves, recognizable by a tilting horizon (in the opposite direction). DJI hasn't implemented a solution to this problem yet... maybe they can do it in the Osmo Action 5.
I think I am seeing this behavior when leaning with my motorcycle for longer. I see slight angle adjustments every now and then. It kinda'f sucks and funny thing is, I don't remember seeing this before, so either it's because of some video setting I messed with that negatively influences the EIS or it's something that started happening after a firmware update.