Thanks for starting this thread @flashinyourface. Let’s make this the official thread for discussing issues with the first beta version (aka version 0.1.1 / build 2).
There are a few major bugs in this version, as well as some minor bugs and some improvements that desperately need to be made. Here are a few details on the most common issues:
Color conversion wrong / constantly changing
This version has some bugs and instability in the code that figures out which part of the current scene is film, and which part of the film are individual frames. Every time it updates its understanding of what it’s seeing, it adjusts the colors so that the individual frames are, on average, properly exposed and color balanced (as in a proof sheet). But if it fails to find the film frames, incorrectly uses parts of the image that aren’t film as input, the colors get messed up. So what you’re seeing is FilmLab sometimes getting it right, and sometimes getting it wrong, even though the input isn’t changing much.
I’m have plans to improve this ASAP. Hopefully the next beta build (which should be ready in the next week) will be significantly better.
Capture shows unprocessed negative
If you see a full, unprocessed scene instead of a cropped and corrected positive, it means FilmLab failed to find the film frame matching the place you tapped. This is another symptom of the problem described above.
Colors in captured positive are washed out
There are two reasons for this. First is the frame recognition issue again - if FilmLab doesn’t crop the frame properly it may treat the sprockets hole area as part of the frame, and the bright white light shining through the sprocket holes throws off the exposure. Secondly, currently FIlmLab is doing a very simple JPEG capture using your device’s auto-exposure, which results in underexposed scans with poor dynamic range. Once I get raw capture back up and running, this should get a lot better.
UI buttons disappearing
This comes from the fact that I haven’t written the UI code to deal with device rotation yet. So when you rotate your phone or tablet, buttons like the close button can end up off-screen. Rotating your device should bring them back into view. This will be fixed in the next beta release or two.
Thanks for taking the time to test this build and report bugs, everyone! I think this site is going to be a great resource for discussion, and I’m feeling very motivated to get you all a new and improved build as soon as possible!