Forum Replies Created
-
Posts
-
If you are referring to the standalone version of the app, then no. There isn’t a way to do that. I don’t have any immediate plans to do that, since it requires a lot of basic infrastructure to be created first that’s not present in the app (because the app browses “real” files and as such it doesn’t have the ability to browse “fake” files.
Photos itself has that ability, so if you are using the extension, you can duplicate the image and work with that.
—Nik
Hi Erik,
One RAW Power user I have interacted a lot with does a lot of astrophotography, but he uses dedicated software that does focus stacking. I will ask him if he has any suggestions for you, though.
Hi Vlado,
Yes, there will be videos. I can make a note to look into making them downloadable – is that so you can view them offline?
Hi Sue,
Thank you for your interest in the app. Sorry for the late response – I did not see your post.
For now, I suggest leaving your library in Aperture. You can use RAW Power 2.0 as a file browser or as a Photos extension (editing one image at a time) and get used to the app and its features.
RAW Power 3.0 will have support for Photos libraries (using macOS Catalina), so you will be able to use it as an alternative interface to your library. It will not have the exact same features as Photos (each will have unique features). At that point, it might make sense to move from Aperture to Photos.
I hope that helps. You can email support@gentlemencoders.com if you have more questions (or reply on this thread).
I did not receive your email with your email address – if you already sent it, please send it again (a regular email) to support@gentlemencoders.com.
Thanks.
–Nik
I have fixes for this bug. If you are interested in beta testing it, please email support@gentlemencoders.com. Thanks.
Hi,
I’m sorry you are encountering a problem with export. I spent a while trying to reproduce this; I believe I finally know what is happening. There are two different bugs.
1) I store the list of images in the order you select them, but iOS reorders them (an iOS call I make apparently does not respect the order I pass in)
2) The “original file name” setting is not working reliably.I do not have a workaround at this time for either problem. The fixes are not trivial; they will take some time to make.
I’m sorry I don’t have a better answer right now.
Hi,
I believe that the “swipe turning into full-screen” issue is the device occasionally registering a tap vs. a swipe (which is determining in part by distance the finger moves when it is touching the screen, as well as how long). There may be a way to ignore taps in this situation, but I would have to look into it (there isn’t a way directly with iOS – I’d have to implement some kind of heuristic).
There is not a current way to view the real RAW version without entering edit. There are two reasons for that:
1) often, the RAW is not present on the device and has to be downloaded. Downloading the RAW would greatly affect the interaction experience when moving through the library. It could be a preference, of course. Right now there is already an issue where the app needs to download the full-size preview – this would be worse with RAWs.2) RAWs require a lot of memory, so it puts a lot of pressure on the system. Memory pressure can lead to crashes (when an app uses too much memory, iOS terminates the app). This is an issue some customers experience currently even with the current system, so I’m sure it would be worse.
If RAW loading occurs automatically, then as people swipe through the library, the app will have to start and stop RAW loads. Unfortunately, there isn’t a way to do that in iOS – it’s possible to cancel a download, but not a decode. As a result, memory will spike as there are multiple images being decoded at once, which will certainly crash the app. The app can wait a few seconds before loading the RAW, but a) that is annoying in its own way and b) everyone swipes at a different rate. The result is that some people swipe at just the right rate to have a terrible experience. This happened a lot with Aperture 1.0.
Both issues could probably be overcome, but it’s quite a bit of work. Something I’ll think about for the future, but not something I can do right now.
Hi Erik,
I have thought a little bit about soft-proofing but not much. The basic idea is pretty simple – it’s a matter of changing the output color profile used when rendering images for display or output (but there are some gotchas that have to accounted for or the results will be incorrect). Embedding a profile is also straightforward.
It’s not on my near-term list, but it is something that is on the list for a future release. There are some very important (and large) features that are taking priority.
V3 will support Photos libraries (similar to the way RAW Power for iOS works). The existing file browser system will continue to exist with new features, etc. No worries there.
RAW Power uses Google Analytics to measure the usage of some features (for example, how much people use the Extension vs. the standalone app vs. the Lightroom plugin). There isn’t any personal information tracked. It also does not use any advertising IDs.
Hi Erik,
Inline:
Use a fixed number of digits for exporting with custom name and sequence, potentially as a parameter with a default value of 3 digits that the user can modify.
I’ll put that on the list for a future release.
Export in the (chronological) order in which the images are being displayed in Raw Power.
This is a bug – it should respect the sort order. I’ll put that on the bug list.
When exporting files, set the file creation date to the original image capture date.
I checked Aperture, Photos, and Lightroom. None of them set the file creation date to the original image capture date (all preserve the EXIF capture date, as does RAW Power). In general, I’m hesitant to mess with file creation dates. If the other two issues are resolved, I believe your situation would be okay, since the images would come in the right order.
