By pengwang19841984
on Tue, 03/11/2014 - 04:45
Vuforia SDK Version: 2.8.7 -
Description with steps to reproduce:
It can be readily replicated. I installed the sample app from Vuforia website on iphone 4S with iOS7 and cloud-reco'ed only once. After one day check the reco-count, it is increased by either 2 or 3. I used apple mac mini mavericks OS and xcode 5.
Notice that this is an important bug directly related to the pricing on cloud reco (i.e. 2x or 3x over-charge). Greatly appreciate your help.
- Development OS (Mac OS X, Windows, Linux): Mac OS X Mavericks - Mobile OS and Version: ios 7 - Mobile Device Manufacturer and Model name: iphone 4S - Do the Vuforia Sample Applications show the same behavior?: exactly the same behavior
Multiple count for one cloud reco
Hi,
how can you be sure that the app recognized the target only once ?
Multiple count for one cloud reco
Dear Vuforia,
Multiple count for one cloud reco
I will try to reproduce / verify this issue, doing the same test
Multiple count for one cloud reco
Quick update:
are you stopping the TargetFinder when the target is detected ? (i.e. in the callback in which you get the the TargetSearchResult) ?
Multiple count for one cloud reco
Dear Vuforia,
Thank you for your advice. I will try it out.
Multiple count for one cloud reco
Yes, for the sample, we have definitely taken your suggesion into account and we plan to upate it soon.
Multiple count for one cloud reco
I just have the same problerm!!!!
It's about 4 times more than I scan；
Multiple count for one cloud reco
As I explained in my previous message, You need to stop the Target Finder when a target is recognized, otheriwse Cloud Reco keeps scanning in the background and as you move the device around you might get additional reco events.
Multiple count for one cloud reco
I'm experimenting the same problem with cloud recognition and I followed all the tips exposed here.
Multiple count for one cloud reco
Hi,
as I said previously, as long as the TargetFinder is running (i.e. until you don't stop the CloudReco scan), you might incur in more than 1 reco event, even if the target in view is the same.
Multiple count for one cloud reco
Multiple count for one cloud reco
Yes, you correctly stop Cloud Reco, which indeed will prevent further reco events from happening;
Multiple count for one cloud reco
Ok, now I see where is the problem and If I understand well, there's nothing to do with this issue (as a client) .
Is there any plan to solve that extra calls?
Multiple count for one cloud reco
I've checked with our team and the common understanding of this is that the number of reco events (what you refer to as "the extra calls") is not necessarily mapped 1-to-1 with the number of times a New Search Result is reported to the client SDK API;