Recently I have been looking in to making the VisionDrive system more usable, more specifically being able to extract videos and audio without using the VDAnalyser program, which seems to re-encode when exporting, which would be affecting quality. While on my search I found some interesting things from a user called Wimpster. One of them being a perl script which displays information about the file structure from the VD-3000 system, luckily it is a very similar structure as the VD-8000 which I personally own. Wimpsters' original script can be found here, all credits are due to him, this script explains the structure of .vd files very well although there are changes with dual camera systems.
I edited the script and created a password recovery script of sorts. This would be handy if a password for a VisionDrive system has been lost, or if lawful access needs to be gained to the video files. The modified version can be found here. If either scripts are downloaded obviously change the extension to a .pl and run under perl and the result will simply output to the terminal. The usage is as such:
./info.pl <file name>
The files can either be the _vd.cfp configuration file from the root of the SD Card or from a .vd video file. Interestingly enough the structure of the files are fairly simple and non of the passwords are hashed / encrypted. The code can be found after the break if the file is un-downloadable.
From my limited experience with the VisionDrive system, it seems that there is a minority of noises / sounds that can not be turned off in the configuration through the Windows application. Noises such as the Audio Recording on / off are very annoying and activate on every boot.
A quick solution around this is to create zero byte files (empty files) and replace the sound files, such as "soundoff.raw" and "soundon.raw". In the case of the sound recording on / off options, I would leave one of them, in case you do need to change the setting so you can tell when the mode is changed.
Now I have a non-invasive monitoring system, that will only make noises if there is an issue, such as the SD Card becoming faulty. Watch this space regarding more VisionDrive projects.
Many people would have run in to the issue of wanting to review video files created by a VisionDrive unit while not having the SD Card attached. The default program VDanalyser.exe will not allow it to be opened without the original SD Card inserted which can be a major bother.
Thanks to Pinni3 who has described the methods to create an offline exe with another version of the Vision Drive system.
Personally I have a Vision Drive VD-8000HDS/400R and the steps below will explain how do this with your own VDAnalyser.exe version. The method includes creating a new .exe without the check for the SD card included.
- Get ODBG from http://www.ollydbg.de/
- Import / Open the VDAnalyser.exe in ODBG.
- Click the run button to start the analysis of the program.
- Right click on the CPI main thread and search for > all referenced text strings.
- Find the Text String "Please insert authentic SD card", which is near the bottom of the text strings windows.
- Right click and follow in disassembler.
- Select the rows shown in the picture so we can remove them.
- Right click > binary > Fill with NOPs.
- Right click on the modified rows and Copy to executable > All modifications.
- If asked "Copy selection to executable file? Reply with "Copy All"
- Now close the window and save the executable.
You now have an .exe that is a version of VDAnalyser.exe that can be opened without the original SD Card being inserted.