Exposure Value=[2];Exposure compensation,0 : -2EV,1:-1EV,2: 0EV,3 : +1EV,4:+2EV
White Balance=[2];Set White BÿMance,0 :Auto,1: Daylight,2:Cloudy,3:Tungsten,4:Fluorescent,
Contrast=[2] ;Set Contrast ,0 :-2,1:-1,2:Normal,3:+1,4:+2,
Color Effect=[1];Set Color Effect,0 : Standard,1:Mono,2:Sepia,3:Cooler,4:Cool,5:Warm,6:W armer,
Saturation=[2];Set Image Staturation,0 :-2,1 :-1,2:Normal,3:+1,4:+2,
{MicroDVR mov 2012/10/09 v0.49}
{LDMICDVR,v1.1S,01/06/2012}
Annoyingly getting it to dump the CA_DUMP.RAW config seems to have been a fluke as I cannot recreate it. If I flatten the config .BIN file completely it will accept it as long as it prefixes and suffixed with ANEKA001. I just need to work out what the 160 remaining values do I think!More success! I've been playing with the UnCamHD online config generator that creates a DCTCONFIG.bin. I placed this on the SDCard with the uengmode file to engage engineering mode and received an error "Cfg file error: Check Magic Err!"
I looked at the bin file and noticed it started and ended with Roral008. Looking for this in the RUnCamHD firmware that is just before the path for DCTCONFIG.bin. On the M127 this is ANEKA001.
I simply replaced Roral008 with ANEKA001, added the DCTCONFIG.bin and uengmode file to the SDCARD, booted the machine and I receive Update config success!
Remove those files from the SDCARD and rebooting the machine, I magically have the folowing file on my SCARD.
CA_DUMP.RAW
With the contents:
Code:Exposure Value=[2];Exposure compensation,0 : -2EV,1:-1EV,2: 0EV,3 : +1EV,4:+2EV White Balance=[2];Set White BÿMance,0 :Auto,1: Daylight,2:Cloudy,3:Tungsten,4:Fluorescent, Contrast=[2] ;Set Contrast ,0 :-2,1:-1,2:Normal,3:+1,4:+2, Color Effect=[1];Set Color Effect,0 : Standard,1:Mono,2:Sepia,3:Cooler,4:Cool,5:Warm,6:W armer, Saturation=[2];Set Image Staturation,0 :-2,1 :-1,2:Normal,3:+1,4:+2, {MicroDVR mov 2012/10/09 v0.49} {LDMICDVR,v1.1S,01/06/2012}
It seems we can now set White Balance among other parameters! I'll have a play and see what else I can discover is configurable.
Hello OdanOYou are correct. Corrected Zip attached
Thank you for your feedback, and I'm very happy that you making your own white balance versions, and that someone it benefiting from the Type B port. I am aware that I've broken playback (all models), that happened so long ago, and I have no idea which extension did it. I'm probably not going to fix that.Hello OdanO
Thank you very much for the last B-version 6.1. Finally, the exposure flickering is gone and the video has 18 frames per second. I made a version with RGB=512-256-256 and one with RGB=512-256-192 so that I have a suitable white balance for my films. I need the 2nd version for film material with a blue tint. My wife looks not so happy, because I'm now scanning all the footage again.
I have found one bug in version 6.1: The playback of the movies no longer works on the device.
Good day to each other,