Recent content by Gueria

The last script "autoexec_medium_fov_beta2.zip" doesn't need landing and reboot if you accidently change the video mode in flight. By selecting again 1080p25 or 30 Narrow, the script will still be effective. My script completly replace the narrow mode in 1080p25 and 30. So in flight you will be...

This is the script with no banding on the side. Frame rate is still incorrect, the video will look slightlty accelerated. (acceleration is less present in 25f/s mode).

The camera firmware is independant from the phantom firmware. The modded one with improved bitrates is based on 1.30g. Mine is still 1.29, wich came with my 3.08 phantom, like you I think. Technically you can downgrade the camera firmware without problem, but I couldn’t find any official link...

Every time after booting, yes.

The improvement I made concerns the narrow field of view. The purpose was to have a larger fov without any aliasing or pixel jagginess like in the actual wide fov. So my script gives you what I call a medium fov in replacement of the actual narrow fov. You have to select either 1080p30 narrow...

WARNING BETA SCRIPT : frame rate is incorrect + some pixel banding on the right edge of video. I've been very busy these past week, and couldn't yet get the correct frame rate. However here is the beta script for the medium fov : captured area is 3232 x 1824 instead of 2304x1296. It will...

You're welcome :) I'm close to release another script, based on the idea that it could be possible to capture a larger window in 1:1 native pixel mapping...It seems to work :) now I have to deal with timings wich are very tricky to get back to 30 or 25 f/s. This script will provide a FOV...

Glad you like it :) I think it should also work for 1080p25 mode, you just have to set camera to 1080p25 narrow, and then reboot the phantom. Also it seems that my script makes the video softer, you may try also hard sharpening (no need to reboot). In fact internally, the narrow and wide mode...

So here is the script : You first have to put the camera mode in 1080p30 Narrow FOV, plug usb, unzip the "autoexec.ash" file to root of sdcard and then reboot the P2V+. The narrow field will be replaced by a "super wide" fov, with slightly better quality than default wide fov : Area read by...

Exactly, for the wide FOV there's is a 2x2 binning process used by the sensor. final pixel color is averaged using 2 adjacent pixels in x and y. This process produces some aliasing. Area used : (3840 x 2176), divided by 2 = 1920 x 1088 For the Narrow FOV, as SKyDude said, it's a native 1:1...

Here is some more tests with these commands : t ia2 -adj tidx -1 0 -1 t is2 -shp fir_mode 0 t is2 -shp fir 10 0 0 0 0 0 0 t is2 -shp fir_mode 1 t is2 -shp fir 10 0 0 0 0 0 0 t is2 -shp fir_mode 2 t is2 -shp fir 10 0 0 0 0 0 0 t is2 -shp fir_mode 3 t is2 -shp fir 10 0 0 0 0 0 0 t is2 -shp...

Can you give some details on how the dji app send commands to the camera to change video mode ? Also for the bitrates, did you edit directly the firmware.bin, or throught AFT tool ?

A5S50 ? from config output : .... DSP_CODE_IMG="../ucode/a5s_50/orccode.bin" DSP_MEMD_IMG="../ucode/a5s_50/orcme.bin" DSP_DATA_IMG="../ucode/a5s_50/default_binary.bin" "The A5s50 supports the standard interlaced HD broadcast format 1080i60 optimized for display on TV."

Config file is interesting but read only (output from "config" command). see attached

I've been fiddling with autoexec.ash commands since my last post here, but without any succes regarding resolution improvement. It was a very slow process as I couldn't get a direct shell to camera (Ambsh shell). it's maybe possible to get the direct shell with a serial console connection to...