7 results found
IOS9 latest version, iPhone 5
And I can't update all either because it gets stuck on BTZS1 vote
I have moved this item to a support request. Please see my email to you.
When using the timer for very long exposures, the phone can go to sleep if I don't occasionally touch the screen to keep it awake. If possible it would be useful to block the sleep function when using the timer.2 votes
By design, if you want to keep the screen active you should adjust your iOS device settings. Note however that this is not necessary as if the device is asleep while the exposure time is active, it will notify the user with an alert before the timer expires.
Given current method of entry (tapping multiple times with finger blocking view), it takes a bit of time to enter initial low value. To speed up this process, it would be easier to start with a more common EV value (most people aren't shooting with 0 low EV).2 votes
The plan is to handle this another way, via exposure records defaults. Basically, each user will be able to set the starting defaults for the input elements of new exposure records. So if you want the EV to start at 10 you’ll just set your personal defaults to that value.
In light of this plan, I’m declining the general suggestion that it be hard-wired to start at 10 instead of 0.
Btw, currently you can tap and hold the EV/Zone values and they will increment for as long as they are held down. They will also speed up the longer they are held. This makes it a bit easier to get larger value faster than repeatedly tapping.
When exporting film data from Plotter users may select to include reciprocity adjustments by selecting a letter/number combination specific for a film/developer combination (e.g., A7 for HP5+ in Xtol 1+1). These adjustments are based on testing conducted by Davis. In my experience, these are often not ideal at best. The first character in the 2 character value is the exposure class which adjusts for exposure reciprocity. There are five fixed classes each corresponding to one specific value (1.17, 1.23, 1.29, 1.35, 1.42). The second character is called "G" class which is an adjustment for contrast change with increased exposure time.…1 vote
Given some more thought and some experiments with the calculations, I just don’t see the benefit for the increased complexity.
While not ideal, because of the iPhone’s small screen size this was the only viable trade off for having a UI that is quick and responsive while changing multiple related values. The alternative was to create UI that was spread across multiple popup screens or to have longer scrolling screens, which would have hidden the vital information from being viewed all at once.
One thing to check is to make sure you have the speaker volume turned up on your device as these UI controls give an audible feedback when tapped. This should help you in knowing what the values are even if you can’t fully see them while changing them.
Currently, when working in Imperial (vs. metric) measurements ExpoDev can handle feet & inches but not sub-inch measurements. The question becomes, how do you input these: fractions or decimal? At what resolution? 10ths of an inch, 16ths or something even smaller?
This would be the only place in ExpoDev that needed to deal with fractional inches and I’d rather not add that complexity. Using millimeters is a much clearer case and most camera’s that I’ve seen that have built-in scales that use millimeters. The focus spread DOF calculations in ExpoDev also already use millimeters because of this.
At this point I am very hesitant to add this because of the added complexity.
Expand the timer function so that the timer "beeps down" before the shutter release has to be pressed and the timer actually begins.
In the Palm Version, there were a series of beeps before the timer actually started. One could start the timer, and gather oneself to depress the shutter release when the timer started. In the current version, unless I have missed a feature, one has to depress the START AND the shutter release at exactly the same time. In shorter exposures ( e.g., 2-3 seconds ) the potential for significant exposure errors can exist if one isn't exactly "on" with the START button and the shutter release. In longer exposures, small inadvertent errors will obviously have much less relevance.4 votes
I am declining this for now. See my previous comment on why this isn’t needed any longer.
- Don't see your idea?