I have tried and oh, so many times I have tried using that "t ia2 -exp lock 1/n" command in a ash-script. But So far I have found nothing that even remotely looks like a locked exposure. Am I doing anything wrong? I put that command in a autoexec.ash-file and load it into the root-folder of the card but nothing seems to be happening.
When I tried one of those "Take a pic and then shut down"-scripts those worked. But it just seems to refuse to do exposure-lock.
So far what I have deduced is that it might run the scripts in a sheltered mode. and once the script is done running, it resumes default autoexposure-mode. So a single-line script might be enabling the exposure-lock and then immediately after that (since the script is done) it resumes autoexposure.
I have tried to do a script that takes a pic and then locks exposure and then starts recording for 1000 sec... but that just got my gopro to freeze up in an eternal loop until I pulled out the card and battery and with a separate card-reader I had to delete the ash-script from the card before the GoPro would start working again...
So I'm stumped. I have no idea what I'm doing wrong since so many places are referring to that command as a working method. But I have yet to even see any examples that shows it working. Let alone making it work anything like an exposure lock myself. I mean. It couldn't be that all these people have no idea what an exposure lock is supposed to do, could it? That just sounds too strange to be the case...
When I tried one of those "Take a pic and then shut down"-scripts those worked. But it just seems to refuse to do exposure-lock.
So far what I have deduced is that it might run the scripts in a sheltered mode. and once the script is done running, it resumes default autoexposure-mode. So a single-line script might be enabling the exposure-lock and then immediately after that (since the script is done) it resumes autoexposure.
I have tried to do a script that takes a pic and then locks exposure and then starts recording for 1000 sec... but that just got my gopro to freeze up in an eternal loop until I pulled out the card and battery and with a separate card-reader I had to delete the ash-script from the card before the GoPro would start working again...
So I'm stumped. I have no idea what I'm doing wrong since so many places are referring to that command as a working method. But I have yet to even see any examples that shows it working. Let alone making it work anything like an exposure lock myself. I mean. It couldn't be that all these people have no idea what an exposure lock is supposed to do, could it? That just sounds too strange to be the case...