transmote speaks…

design + art + code
  • portfolio
  • rss
  • Home
  • About
  • FLARManager: Augmented Reality in Flash
    • FLARManager intro
    • FLARManager documentation
    • Inside FLARManager
      • Inside FLARManager: Getting Started
      • Inside FLARManager: 2D Marker Tracking
      • Inside FLARManager: Basic Augmented Reality
      • Inside FLARManager: Loading Collada Models
      • Inside FLARManager: Customization
      • Inside FLARManager: FLARManager Miscellany
  • Contact

FLARManager documentation

 

FLARManager API Documentation

The complete FLARManager ASDoc reference can be found here:
http://transmote.com/flar/reference

 

FLARManager config file

The preferred method for initializing FLARManager is to pass the path to an external XML configuration file into the FLARManager constructor:

var flarManager:FLARManager = new FLARManager("flarConfig.xml");

In the FLARManager distribution, flarConfig.xml is located in /resources/flar/, so the whole path relative to the bin-debug folder is ../resources/flar/flarConfig.xml, which yields:
new FLARManager("../resources/flar/flarConfig.xml");

The configuration file can be called whatever you like, as long as you format it according to the following specifications. There are four top-level nodes, and each node accepts a number of attributes. The <patterns> node also accepts a list of child nodes. Attributes for these nodes are listed below, along with their types and default values. Required nodes and attributes are marked as such; if a non-required attribute is omitted, its default value will be used.

  • <flarSourceSettings>
    • sourceWidth
    • sourceHeight
    • displayWidth
    • displayHeight
    • framerate
    • downsampleRatio
    • loaderPath
    • useProxy

     

  • <flarManagerSettings>
    • mirrorDisplay
    • smoothing
    • adaptiveThresholding
    • adaptiveThresholdingSpeed
    • adaptiveThresholdingBias
    • sampleBlurring
    • markerUpdateThreshold
    • markerRemovalDelay
    • minimumLabelSize
      • <smoother>
        • name
      • <thresholdAdapter>
        • name
        • speed
        • bias

     

  • <cameraParamsFile>
    • path

     

  • <patterns>
    • resolution
    • patternToBorderRatio
    • minConfidence
    • size
    • <pattern>
      • path



 

<flarSourceSettings>

[attributes]

  • sourceWidth:Number=640
    Width at which to capture video. This is the value passed to Camera.setMode() in FLARCameraSource.as.
     
  • sourceHeight:Number=480
    Height at which to capture video. This is the value passed to Camera.setMode() in FLARCameraSource.as.
     
  • displayWidth:Number=640
    Width at which to display video.
     
  • displayHeight:Number=480
    Height at which to display video.
     
  • framerate:Number=30
    Framrerate at which to capture video. This is the value passed to Camera.setMode() in FLARCameraSource.as.
     
  • downsampleRatio:Number=0.5
    The amount to downsample camera input. The captured video is scaled down by this value before being sent to FLARToolkit for analysis. FLARToolkit runs faster with more downsampling, but also has more difficulty recognizing marker patterns. A value of 1.0 results in no downsampling; a value of 0.5 (the default) downsamples the camera input by half.
     
  • loaderPath:String=""
    If this value is set, FLARManager will create a FLARLoaderSource instead of the default FLARCameraSource. The file located at this path will be used by the FLARLoaderSource.
     
  • useProxy:Boolean=false
    If true, FLARManager will create a FLARProxy instead of the default FLARCameraSource.
     

[children]
none.

 

<flarManagerSettings>

[attributes]

  • mirrorDisplay:Boolean=true
    If true, video and detected marker data are flipped horizontally. (NOTE: As of v0.6, transformation matrices are flipped correctly, and developers no longer need to flip the DisplayObjectContainer into which the transformed objects are drawn.)
     
  • smoothing:int=3
    Apply a smoothing algorithm to transformation matrices generated by FLARToolkit. Smoothing is equal to the number of frames over which FLARManager will average transformation matrices; the larger the number, the smoother the animation, and the slower the response time between marker position/orientation changes. A value of 0 turns smoothing off.
     
  • adaptiveThresholding:Boolean=true

    NOTE: this attribute is deprecated and removed in v0.6. Use thresholdAdapter instead.
    Adaptive thresholding can result in better marker detection across a range of illumination. This is desirable for applications with low lighting, or in which the developer has little control over lighting conditions, such as with web applications.
     

  • adaptiveThresholdingSpeed:Number=0.3

    NOTE: this attribute is deprecated and removed in v0.6. Use thresholdAdapter instead.
    The speed at which the threshold changes during adaptive thresholding. Larger values may increase the speed at which the markers in uneven illumination are detected, but may also result in instability in marker detection.
     

  • adaptiveThresholdingBias:Number=-0.1

    NOTE: this attribute is deprecated and removed in v0.6. Use thresholdAdapter instead.
    The direction toward which adaptive thresholding trends. Lower thresholds favor environments with too little light; higher thresholds favor environments with too much light.
     

  • sampleBlurring:int=1
    The amount of blur applied to the source image before sending to FLARToolkit for marker detection. Higher values increase framerate, but reduce detection accuracy.
     
  • markerUpdateThreshold:Number=80
    If a detected marker is within this distance (pixels) from an active marker, FLARManager considers the detected marker to be an update of the active marker. Else, the detected marker is a new marker. Increase this value to accommodate faster-moving markers; decrease it to accommodate more markers on-screen at once.
     
  • markerRemovalDelay:int=1
    Number of frames after removal that a marker will persist before dispatching a MARKER_REMOVED event.
     
  • minimumLabelSize:int=100
    Provides direct access to FLARLabeling_BitmapData.minimumLabelSize, which is the minimum size (width*height) a dark area of the source image must be in order to become a candidate for marker outline detection. Higher values result in faster performance, but poorer marker detection at smaller sizes (as they appear on-screen).
     

[children]

  • smoother
    IFLARMatrixSmoother to use to apply smoothing to transformation matrices generated by FLARToolkit. This defaults to FLARMatrixSmoother_Average, but developers can implement their own smoothing algorithms. See Inside FLARManager: Customization for more information.
     
  • [attributes]
    • name:String='FLARMatrixSmoother_Average'
      The name of the smoother class to use. If the class resides somewhere other than com.transmote.flar.utils.smoother, a fully-qualified class name must be used.
       
  • thresholdAdapter:String='DrunkWalkThresholdAdapter'
    Adaptive thresholding can result in better marker detection across a range of illumination. This is desirable for applications with low lighting, or in which the developer has little control over lighting conditions, such as with web applications.
    The default threshold adapter is DrunkWalkThresholdAdapter, but developers can implement their own adaptive thresholding algorithms. See Inside FLARManager: Customization for more information.
     
  • [attributes]
    • name:String='DrunkWalkThresholdAdapter'
      The name of the threshold adapter class to use. If the class resides somewhere other than com.transmote.flar.utils.threshold, a fully-qualified class name must be used.
       
    • speed:Number=0.3
      The speed at which the threshold changes during adaptive thresholding. Larger values may increase the speed at which the markers in uneven illumination are detected, but may also result in instability in marker detection.
       
    • bias:Number=-0.1
      The direction toward which adaptive thresholding trends. Lower thresholds favor environments with too little light; higher thresholds favor environments with too much light.
       

 

<cameraParamsFile>

–REQUIRED–
[attributes]

  • path:String="" –REQUIRED–
    The path to the FLARToolkit camera parameters file (e.g. FLARCameraParams.dat or camera_para.dat). FLARToolkit requires this file to initialize and run.
     

[children]
none.

 

<patterns>

–REQUIRED–
[attributes]

  • resolution:int=0 –REQUIRED–
    Resolution (width/height) of marker pattern files. All patterns in a single application must share the same resolution; this is mandated by FLARToolkit. For more information about pattern resolution, see here.
     
  • patternToBorderRatio:Number=50
    Out of the entire width/height of a marker, the amount that the pattern occupies relative to the amount the border occupies. Value is expressed as a percentage (0-100). For example, a value of 50 indicates that the width of the pattern area is equal to the total width (on either side of the pattern) of the border. NOTE: this is not yet implemented by FLARToolkit for multiple markers, and is therefore not yet implemented for FLARManager.
     
  • minConfidence:Number=0.5
    ‘Confidence’ is a value (from 0.0 to 1.0) assigned by FLARToolkit to each detected marker, that describes the algorithm’s perceived accuracy of the pattern match. This value sets the minimum confidence required to signal a recognized marker. Lower values will be more likely to detect both real markers and false positives; higher values will be less likely to detect both real markers and false positives.
     
  • size:Number=80
    The width of a marker (in pixels) on-screen at which the scale of its transformation matrix is 1.0. This can be used to adjust the size that a mode will appear on-screen. If a model is appearing too large, decrease this number, and vice-versa.
     

[children]

  • <pattern>
    Each <pattern> node represents a pattern that FLARToolkit will attempt to detect. FLARToolkit can look for an unlimited number of patterns, but as it attempts to match each detected marker against all possible patterns, more patterns mean slower pattern matching (and ultimately, slower overall performance). Developers should keep this list as short as possible for each application. Each <pattern> node has one attribute, path, that describes the path to the associated pattern file (relative to the published SWF).
     


Comments rss
Comments rss
Trackback
Trackback

11 responses

puedo ver el archivo?

logan | 2009/06/01 | 1:26 pm

puedo ver el archivo?

lo siento, mi español es muy malo. by "archivo" do you

ericsoco | 2009/06/01 | 1:44 pm

lo siento, mi español es muy malo.
by “archivo” do you mean the file archives? if so, you can download the source from svn; all the information you need is here:
http://transmote.com/flar

[...] FLARManager documentation [...]

transmote speaks… » FLARManager v0.5 (for FLARToolkit) | 2009/07/18 | 6:26 pm

[...] FLARManager documentation [...]

Hi, is anyway possible to set width and height at

Paolo | 2009/09/18 | 12:38 am

Hi, is anyway possible to set width and height at 100% to make it work like a fluid layout?

thanks

[...] FLARManager documentation [...]

FLARManager v0.6 (augmented reality in Flash) | transmote speaks... | 2009/09/23 | 2:04 am

[...] FLARManager documentation [...]

hi, flarmanger v.5 works great , however when i tested

max | 2009/10/01 | 7:37 am

hi, flarmanger v.5 works great , however when i tested version 6 i get this error :

1044: Interface method getAttachedDestination in namespace org.libspark.flartoolkit.core.labeling:IFLARLabeling not implemented by class org.libspark.flartoolkit.core.labeling:FLARLabeling_BitmapData.

can anyone help ?

Hi Max, I get the same error... Do you solve

Daniel | 2009/11/06 | 8:45 am

Hi Max, I get the same error… Do you solve this?

@Daniel — please look through the comments on the v0.6

ericsoco | 2009/11/06 | 10:30 am

@Daniel — please look through the comments on the v0.6 page. this is a bug in CS4 with classes that implement multiple interfaces, and others have already solved this problem and posted the solution there.

Hi ! I have been using flar manager for multiple markers

Mahesh | 2010/01/29 | 10:29 pm

Hi !
I have been using flar manager for multiple markers but i always get pattern id 0 for all the patterns detected, so that it always display same cube for all markers. But, in my case i have to detect each marker and display different 3D object. could you please help me out ?

@mahesh -- shouldn't be this way. did you modify

ericsoco | 2010/01/30 | 7:03 pm

@mahesh — shouldn’t be this way. did you modify flarConfig.xml? are you using the markers that come with FLARManager?

Sorry ericsoco! it was my mistake. By the way

Mahesh | 2010/02/02 | 6:30 am

Sorry ericsoco! it was my mistake. By the way ,I have been using flar manager ,its awesome man!!!. It made my work easier. Thank you very much for the work you have done.

Leave a comment

You can use these tags : <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Additional comments powered by BackType

Recent Posts

  • elastotron: visage @ YBCA/TVOT weds mar 3
  • FLARManager @ FITC Toronto 2010
  • true fullscreen in AIR on OSX
  • FLAR presentation @ ARDevCamp 2009.dec.05
  • FLARManager v0.61 (augmented reality in Flash)

Tags

3d actionscript Add new tag AR ARDevCamp as3 augmented reality camera Capabilities computer vision connections culture digital elastic event handler exhibit exploratorium fiducial flar flarmanager flartoolkit flash flash player forum garbage collection generative grid interactive Keyboard marker memory mesh mirror notes papervision presentation reflection slides sputnik theory to see tracking video video mirror webcam


rss Comments rss design by jide