So, I have to apologize for the CLibInit errors people have been running into when trying to compile the latest version. I left a reference to FlareTracker in FLARManagerProfiler.as when testing, and did not notice this caused Flash Builder to attempt to compile FlareTracker.as even though the default application is FLARManagerExampleLauncher.as.
This minor release, v1.0.3, fixes that problem. There’s not much else new here, except a couple minor bug fixes. As always, you can download via SVN or via the download link on the FLARManager page. You no longer have to get the flare* libraries to compile FLARManager; hope this helps all of you who’ve been struggling with CLibInit.
After learning today about a very clever trick by Deepanjan Das, I decided to implement it in FLARManager.
The trick, in short:
only send the camera source to FLARToolkit while there is noticeable motion.
less jitter when the marker is held still in front of the camera.
To implement in FLARManager:
Download the latest from svn, particularly FLARManager.as, FLARConfigLoader.as, and FLARCameraSource.as. the changes will automatically take effect.
To tweak the value, set activityThreshold within the <flarSourceSettings> element in flarConfig.xml. Set higher to further reduce jitter in stationary markers, and set lower to allow more freedom of motion with stationary markers.
Minor update to FLARManager v1.0. Imagination has requested that I not distribute their libraries, so I’ve removed them from the FLARManager distro. This will make it easier for us to ensure both FLARManager and the flare* products are as up-to-date as possible, as well as smoothing out some other potential distribution issues.
However, this means that getting flare*tracker and flare*NFT projects running requires a bit more work. As such, I’ve reverted the examples and tutorials to use FLARToolkit, which I can distribute along with FLARManager, and also created this page to describe, in-depth, how to implement the various tracking engines that FLARManager supports.
Please take a moment to download the latest version of FLARManager and the current evaluation SDKs for flare*tracker and flare*NFT to ensure you’re up-to-date. And feel free to pester me with questions (as comments, below) about setting up your projects — I need your help to get the documentation as clear as possible.
Hello folks. I’m happy to announce that FLARManager is finally all growed-up!
FLARManager v1.0 has been quite a while in the making, especially the movement from v0.7. This is due to a number of factors; one of these has been working out the final details, between ARToolworks and Imagination, of flare*tracker and flare*NFT integration, which i first previewed in this blog post. But the major factor is the amount of restructuring that has gone into FLARManager.
Why restructure? FLARManager is now able to work with any tracking library, just as it’s able to work with any 3D framework. And switching between tracking libraries is as simple as this:
FLARToolkit: new FLARManager("flarConfig.xml", new FlarToolkitManager(), this.stage);
flare*tracker: new FLARManager("flarConfig.xml", new FlareManager(), this.stage);
flare*NFT: new FLARManager("flarConfig.xml", new FlareNFTManager(), this.stage);
Obviously, the freedom given to application developers, creatives, and agencies by natural feature-tracking is the biggest element of this release to be excited about. But the restructuring goes deeper — FLARManager can now function as a link between *any* tracking library and *any* 3D framework. Developers are no longer bound to decisions based on limited availability or documentation; they are free to choose the tools that work best for them. (Some Californian CEOs would do well to pursue similar goals.)
i first announced this at FITC Toronto a few weeks ago, but was waiting to tie up some loose ends before i announced it here.
the newest version of FLARManager, which will be released shortly, abstracts the marker-tracking library out from the marker management framework (FLARManager’s core).
what does this mean?
in short, it means that FLARManager can now easily be updated to support any flash-based marker-tracking library. FLARToolkit (currently at v2.5.3) is the most obvious player, and FLARManager continues to support FLARToolkit. additionally, the newest version FLARManager will support flare*tracker and flare*NFT.
what are flare*tracker and flare*NFT?
flare*tracker is a marker tracking engine much like FLARToolkit, and applies many of the same concepts. however, it is written completely from scratch in Alchemy, so it can achieve framerates up to 45+ fps. also, it supports six different marker types, including BCH ID-markers (with marker id encoded directly into the marker pattern, so no need to load pattern files and no speed penalty for many different patterns) and Data Matrix markers (with a url encoded into the marker pattern).
flare*NFT is a ‘natural feature tracking’ engine, which means that it can track any printed image. not just square markers with black borders. any 2D image, from a magazine cover to a product box to a photograph, can be tracked. and since flare*NFT is also based on ARToolkitPlus, and written in Alchemy, it also shows great performance, generally around 30+ fps.
check out the following videos to see the difference between the three engines. and stay tuned for the release…
FLARManager – FLARToolkit 2.5.2. the FLARManager we all know and love.
FLARManager – flare. note the ID-marker, and framerates averaging in the 35-40fps range.
FLARManager – flareNFT. natural feature tracking made easy. blur? occlusion? glare? no problem.