Below are answers to frequently asked questions about OSnap!. If you have an idea for a question that you think should appear here, don't hesitate to get in touch with us.
By leaving a positive review in the App Store, you help make OSnap! better! OSnap! is an independent project and your support is both critical to the app's success and immensely appreciated! Go hit 5 stars in the App Store! Okay, we're done begging!
With OSnap! Pro you get the following important additional features:
If your project's orientation is set to 'Portrait' your landscape photos will be squeezed and letterboxed in order to fit (ditto for portrait photos in a 'Landscape' project). You can adjust the orientation of your OSnap! project by navigating to your project's settings and locating General > Orientation and choosing 'Landscape'.
The vast majority of errors that occur when attempting to export content to the iOS Photos app are caused by permissions settings. In most cases OSnap! will recognize this problem and alert you to the need to adjust your settings; once in a while, however, the error information returned can be nonspecific or misleading. If you are encountering errors when attempting to export content, please insure that OSnap! has proper permissions (iOS > Settings > Privacy > Photos > OSnap!).
Please be aware that the Photo Import feature requires a one time In-App purchase of $2.99. To purchase Photo Import: from the OSnap! home screen tap the Shopping Cart button in the upper left and then choose Photo Import.
Once the In-App purchase is complete, the Photo Import option will appear. There are two different spots in OSnap! where you can import photos:
Please see the screenshot below for illustration (red circles indicate Photo Import button).
Make sure that you have your chosen external cloud service (Dropbox, Google Drive, etc.) installed on your iOS device. Navigate to any screen that allows you to import photos, tap the import button, and then choose "Import JPGs From Other Sources". From the Browse screen, ensure that your cloud service is enabled by tapping the Menu icon (a circle with three dots in the upper right) and choosing 'Edit'.
Importing photos using 3rd party extensions such as Google Drive, Dropbox and others can sometimes result in bugs or issues such as the photos failing to import or the UI becoming unresponsive, particularly when attempting to import a large number of photos at once. Unfortunately, these extensions are created by 3rd party developers and are outside of the control of OSnap! (The Dropbox extension in particular is notoriously buggy). If you encounter issues, following are some tips and workarounds:
One way you can do this is to enable OSnap! Listening Mode by tapping the Sound icon on the toolbar of the OSnap! camera screen. Once Listening Mode is enabled, OSnap! will snap a photo anytime you make a loud sound (e.g, clapping your hands). Another great method for triggering photos without touching the device is to use a pair of headphones with volume controls attached to the wire; plug the headphones into your device and use the volume+ button to capture photos.
Additionally, if you are using OSnap! Pro 2 you can do either of the following:
Voice Commands: From the camera screen tap the Sound icon on the toolbar and choose 'Use Voice Commands' which will initiate a display with instructions. You can then speak commands aloud such as 'Snap Photo' and 'Start Timer' to control OSnap! using your voice.
OSnap! WiFi Assistant: Using OSnap! WiFi Assistant, activate Live Photo Capture and then use the 'Snap Photo' button in WiFi Assistant to capture photos.
iPhones have a mute switch on the side of the device that you can use to silence the shutter sound while taking pictures. Recent iPad models can be muted by swiping down to access the control panel. Unfortunately, iPods lack a convenient method to mute the device; you can, however, achieve the same effect by plugging headphones into your device. Some countries do not allow the shutter sound to be silenced when taking photos; in these cases none of the above solutions will work. Programmatically silencing the shutter sounds is not allowed by Apple.
Photo Burst is a new feature available in OSnap! Pro 2. Make sure Photo Burst is enabled (OSnap! Project Settings > Photo Capture > Photo Burst Enabled). From the camera screen press and hold the capture button; OSnap! will begin a continuous photo burst until the button is released. Please note, all photos captured with a Photo Burst will be captured with Photo Quality Priority set to 'Speed'.
In OSnap!, navigate to your project settings and then choose WiFi Assistant > Transfer Pics & Videos via Wifi. Follow the instructions from there. Please be aware that OSnap! WiFi Assistant requires a one time In-App purchase of $3.99.
If you have double checked, tripled checked and checked again that you have entered your OSnap! Connection ID exactly as it appears on your iOS device, then the possibility exists that it could be an issue with your WiFi network. Some home WiFi routers employ Access Point (AP) isolation by default, also known as "client isolation". AP isolation disallows connected devices from 'seeing' each other on the network. You can read more about AP isolation here. AP isolation must be disabled on your wireless router in order for OSnap! WiFi Assistant to function.
Don't panic, the embedded EXIF orientation of the photos is correct. Some older versions of Windows do not honor embedded EXIF orientation data in JPEG files and therefore photos can appear to be rotated incorrectly. If you open and view the same photos using most image viewing/editing software (e.g. Photoshop) you will see the photo orientation is actually correct. You can read more about Microsoft's decision to exclude JPEG data on this Microsoft Community thread.
Rendered video resolution is dictated by the FIRST image in the sequence. If you are rendering video from a project that contains many different photos of varying resolutions, make sure that the FIRST photo in the sequence is high resolution in order to achieve a correspondingly high resolution video. OSnap! will always render videos at the maximum possible resolution given your device capabilities, but will not render at a higher resolution than the FIRST photo in the sequence. Maximum resolution varies depending on the device you are using. Below is a table containing max OSnap! video resolutions for common iOS devices:
4:3 | 16:9 | 1:1 (square) | |
iPhone 6s/+ | 3200x2400 | 3840x2160 (4K) | 2560x2560 |
iPad 2017/iPad Pro/+ | 3200x2400 | 3840x2160 (4K) | 2560x2560 |
If you have just purchased a new iOS device and are using Apple's regular migration process to move your data from your old device to the new device, all of the projects and data in OSnap! should be transferred without issue. Having said that, there may be times when you are in a different situation and want to move your OSnap! data to a different device. Follow these steps to do so:
OSnap! captures high resolution camera generated still photos (not video frame captures like many other apps with similar functionality). Although this creates high quality images, it can also put a heavy load on the camera hardware of your device during rapid capture sessions. Following are some fixes, each of which in isolation will probably remedy the issue:
OSnap! uses a local database to keep track of all of the information in your OSnap! projects. Although unlikely, attempting to write to that database in the middle of a device battery failure could potentially result in catastrophic corruption and a complete loss of information, photos and videos. Because users can spend months and even years working on their OSnap! projects, a scenario like the one mentioned above is simply not worth the risk. Additionally, the battery information reported by the system is not particularly precise and 5% ends up being the lowest feasible target.
Your device camera flash can only fire so fast. If you are shooting with fast timed intervals and need artificial light, use the 'torch' instead of the flash.
Make sure that you have your chosen external cloud service (Dropbox, Google Drive, etc.) installed on your iOS device. Navigate to your OSnap! project's home screen and tap the Music Note icon at bottom, and then choose "Select Other Audio File". From the Browse screen, ensure that your cloud service is enabled by tapping the Menu icon (a circle with three dots in the upper right) and choosing 'Edit'.
Photo Quality Priority is a new feature available in OSnap! Pro 2 that can be set to 'Quality' or 'Speed'. See explanations below:
Quality:Keeping the device camera readied and snapping photos for long periods of time expends a lot of energy; there's currently no easy way around this. Make sure you have OSnap!'s "Darken Screen to Save Battery" option selected to help combat this problem. For timed photo shoots that run for many hours, however, you will most likely need to plug your device into an external power supply.
Although OSnap! may appear to suspend a photo shoot well in advance of exceeding your hard drive limit, keep in mind that thumbnail and preview images may still need to be generated for each photo taken and, consequently, additional hard drive space will be required. Also, OSnap! does not want to fill your iOS hard drive completely to the brim (which can often cause unforeseen problems), so it takes a relatively conservative approach in this area.
This would be a really cool idea in theory. The problem is it doesn't work. Once you start getting resolution up above the figures specified above, you start running into system errors with saving, playing and exporting videos. You can, of course, export your photos at full resolution and import them into a desktop video editing program in order to create very high resolution videos.
Depending on the specifics of your project and device, OSnap! can sometimes seem to take its sweet time rendering videos. OSnap! places a lot of emphasis on rendering your videos at very high quality, so that the result is extra smooth, vivid and clear. The app uses high resolution camera generated still photos (not video frame captures), and also takes special care to mimic and accommodate your chosen frame rate in the video output. OSnap!'s live playback feature is designed to allow you to tweak your project to perfection before rendering so that you only have to render once. If you are looking for ways to cut down on video rendering time, effective strategies include: 1) shooting with lower resolution photos; and 2) lowering the frame rate of your project (both of which require up front planning of course).
If you have a great idea for a new feature, drop us an email at or feel free to post on our Facebook page. We keep a running list of all of our feature requests, and OSnap! continues to evolve and improve as a result of user input. Having said that, if you are interested in seeing OSnap! updates, one of the most important things you can do is to leave us a positive review in the App Store. The success of the app is due in no small part to user reviews, and the more momentum OSnap! gains, the more we are able marshal the resources necessary to design and implement new features.
The human eye is an amazing thing, capable of detecting subtle difference in video even at very high frame rates. Because of this OSnap! uses special processing algorithms to maintain fidelity to your chosen frame rate, outputting H.264 video at non standard frame rates in order to ensure there are no differences between your live playback preview and your final video. If we were to mindlessly drop frames in order to render video at a more standard frame rate, you would certainly be able to tell the difference. YouTube does exactly this, converting and standardizing your video frame rate to something close to 30 FPS. This standardization, combined with YouTube compression, can sometimes result in a slightly 'jerky' video, usually only noticeable in situations where video smoothness is important such as cloudscapes or sunsets. To date, the best way to mitigate this effect is to try and plan for a frame sequence that is 30 FPS which, when uploaded to YouTube, should undergo less of a drastic frame rate change.
Although very rare, a few reports of this problem have surfaced as a result of extremely low device storage space at the time of video render. If this happens to you, you should check your remaining device storage space (iOS > Settings > General > Usage > Available).
On your iOS device tap this link, then select 'Enter Code Manually' and then enter your code.