Follow

Trigger Image Errors and their Solutions

Your Trigger Image is too large

Solution: Check the size of your Trigger Image. Images uploaded to the Aurasma Studio should be no larger than 500,000 pixels (hight x width). You can edit the size of your image in a program like Paint or Picture Manager. 

Your Trigger Image is too sparse

Solution: With this error, the Studio is letting you know that Aurasma will struggle to recognise your image because there is not enough graphical detail in it for it to pick up on and identify your image as unique. Sparse images lack graphical detail, or possibly contain large gaps of blank space between more detailed parts of the image. Solutions include either using the masking tool to block Aurasma from wasting time viewing blank areas it will not recognise, or cropping the image before uploading it so as to minimise blank space and concentrate pixels around parts of the image which will be more easily identified. You may also consider using an alternative Trigger Image. 

Your Trigger Image is too dark

Solution: With this error, the Studio is letting you know that the relative darkness of the image is making it more difficult for the technology to recognise the graphical features within it. You can try using the masking tool / cropping the image pre-upload to block Aurasma's view from the darkest parts of the image and focus its attention on lighter, more recognisable sections. If the image is very dark though, you may want to consider using an alternative Trigger Image. 

Your Image is too complex

Solution: Here, Aurasma is finding that there is so much graphical information in the image that it is not always sure which part of the image it is looking at. This can result in a jittery, unstable launching of the Overlay on recognition of your Trigger Image as Aurasma is not sure where to place the Overlay in relation to the image. This problem is often caused by repeating patterns in an image - if the same pattern / logo / image is used in both the top-left and bottom-right corners of an image, Aurasma may not know where to place the Overlay in relation to the image as it could get the corners confused! Other images may simply have too much detail - imagine a photo of thousands of stars in the night sky or boats in the sea. Again, Aurasma may struggle to identify the image from an information overload. Use the masking tool to block Aurasma's view from these very detailed areas of an image.

Images uploading at the wrong degree of rotation

Solution: If an image opens at the right rotation degree on your computer, but then appears to rotate on upload, this could be due to the angle at which a phone camera was held when the photo was initially taken. You can simply rotate the image on your desktop by 90 degrees in the opposite direction, save it, and then try to upload again. We have found this then helps to upload the image at the right rotation. This advice holds for Overlays as well.    

Was this article helpful?
0 out of 2 found this helpful
Have more questions? Submit a request

Comments

  • Avatar
    Shawn Bishop

    The rotation of images by 90 degrees is a major pain!!!!

    And the solution you have here is not only time consuming but also ineffective. If for example, you take 25 student images (triggers) at the wrong orientation, you would only know this once you upload them. Then you would have to go back into a different program and change orientation on 25 images and then upload them all again. What a pain.

    Also, Aurasma occasionally, just flips them back after you re-upload. This means you can make all the corrections to fix thing and then re-upload, but Aurasma changes them to 90 degrees wrong again. I think Aurasma is trying to be helpful by predicting the correct orientation, but it ends up messing things up too often.

    A very simply solution would be to allow rotation once in Aurasma!!!

Powered by Zendesk