Aaahh thank you everyone! Made it to Round 5 this is insane! Thank you thank for all of your support!
Sorry I've been gone for a few days. I didn't want to come back here until I had good news to report about EXIF. Which means...
*** EXIF is back!! ***
It's been a crazy struggle trying to preserve it, the JPEG spec is weird. I still need to run more tests on this, but it's in all likelyhood I'll have this update ready for download sometime next week
It pains me to say that a light meter simply is not possible. Developers don't have access to the light hitting the sensor, only the video stream that is made after the light hits the sensor. Since this video gains up and down depending on the brightness of the image, it won't be possible to add a light meter :/
Thanks for the detailed report about how you use ProShot, I'll recreate your steps and see what I can do about it.
Hmm, I'm wondering about that excessive battery drain. There was an issue with v2.4 that was caused by not releasing the accelerometer when the app is suspended under lock screen, but I've done thorough testing on the Lumia 920 with ProShot under lock and after 8 hours, found zero battery drain (with the phone in airplane mode). I'll have to revisit my tests and try it with different settings configurations.
The phone call is definitely the cause of the problem. The camera hardware freaks out if an image capture is interrupted by a phone call. I'm not sure what can be done about that, but I will file a bug report with Microsoft.
Just a little background before we begin
ProShot delivers the absolute highest quality visual experience possible on Windows Phone. It taps into your phone's GPU for real-time HD effects like black and white, and contrast / saturation adjustment. No other app out there offers this at HD resolution (Camera360 and SophieLens, though wonderful apps, all run at 640x480 or 640x360). Because I wanted HD devices to have HD visuals, the power requirements are higher.
When running, ProShot maxes out one of two threads (think of threads as lines of code execution). It leaves the second thread relatively untouched. You can say that ProShot uses approximately 50% of the CPU on HD devices like the Lumia 920 or 8X. These power requirements are actually less than some games.
Having said all of that, I have run thorough tests with ProShot on two Lumia 920s, and while the phone does get warm, I found it to be no different than playing a game. Up until v2.5, the phone definitely got hot during normal use (it was maxing out both threads), but with v2.5 I was able to cut CPU usage in half.
Ah, sorry for being too wordy. Do you have v2.5+ installed? How hot does your device get, and after how long of normal use? Were you playing games or placing a phone call before using ProShot? Do you live in a very hot environment?
This would not be hard to do, but it would require me to change the way I handle aspect ratios. Currently, they are global values, and not tied to individual modes. In testing, I found that it confused users if each mode (Auto, P, M, C1, C2) had different aspect ratio options. Plus, all 'pro' cameras I've used so far don't assign custom aspect ratios to camera modes. I really dislike saying 'no' to a feature request, but I don't think this is one I see making it