Seems pretty fast, but a drone can easily max out the scale at +/- 500 dps. * Gyro full scale of +/- 1000 degrees per second or +/- 2000 dps. Typically the hardware low pass filter available in MEMS sensors should do, but some have trouble with particularly strong vibrations. This is both to meet the Nyquist criteria, but also to filter some of the high frequency vibrations encounted on drones if using higher sampling rates. * Low pass filter to remove sensor noise/vibrations above 100 Hz. ![]() Accelerometer (and magnetometer) rates can be lower, but it might also be simpler to log everything at the same rate. ![]() 500 Hz may be required if noise is particularly bad). The required logging rate may increase depending on how the well the data is processed internally due to the potential of aliasing (e.g. * Gyro logging rate of at least 200 Hz captures all the motion data we're interested in. Most of it is based on some ongoing collaboration with an action camera manufacturer, so things might differ for a larger setup. If any blackmagic people are reading this, here are some tips/info which could be handy for implementing gyro data logging successfully. ![]() ![]() As the BMPCC has the sensor hardware already, it could certainly be neat to support it in the future if IMU logging is enabled.įurthermore, I have a proof of concept openfx resolve plugin, which when finished, will be able to apply the relevant gyro-based image stabilization steps in the editor without re-encoding the footage. While I haven't used blackmagic gear personally, I've been trying to add support for as many sources of motion data as possible, which allows for more hardware flexibility and post processing possibilities, especially since the program is open source.
0 Comments
Leave a Reply. |