big input stream

--Apple-Mail-11-967360157
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Antonio,

If you're working with big images (anything greater than 1024 pixels  
wide or tall qualifies as big for ARToolKit) you will run into a  
variety of hard-coded size limits in various places in the toolkit.  
There are some in the tracker (libAR) and some on the output side.

At the moment, the way I usually tackle these limits is to scale the  
image down to 1024 pixels each side, and use that size for tracking  
(with appropriate size changes to the camera parameters). The  
resulting pose estimation can then be applied to the full-size image  
for rendering.

Proper handling of HD image streams is something that will definitely  
be tackled in ARToolKit in the future... we just have to find the  
time. Patches from the community always welcomed!

Regards,
Phil.

On 17/04/2007, at 10:21 AM, Antonio Bleile wrote:

> Hi,
>
> I'm currently experiencing a problem when the marker
> size is too big (in pixels...!). I have an HD stream
> and whenever the marker is too close to the camera and
> thus the marker is projected on let's say a 600x600 pixel
> region, ArToolKit(Plus) does not track anymore. Of course
> it becomes worse on photographic images taken from cameras
> with high megapixel values (>= 10...). Is this a hardcoded
> limitation somewhere? Any switches?
>
> Regards,
>
>   Toni

--Apple-Mail-11-967360157
Content-Transfer-Encoding: base64
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGITCCAtow
ggJDoAMCAQICECKlRj17Ar/nRHuR8uhUEacwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDIxODIyMzgyNloXDTA4MDIxODIyMzgy
NlowQjEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEfMB0GCSqGSIb3DQEJARYQcGhp
bEBlZGVuLm5ldC5uejCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMFM7RZK14/1EBHq
xm3qClBRGN0s0ueca/LLI8lixA/CP94ntSTX86fV8JnHc3pnufkPKDwhtv06u+VS5kdUqJXTWTs7
HLhtBzMeN3kfZfpyg3+oTEt4v1chsnYNom5eclCBG89bSgqhALm6bhALz1R8f5PHQwT4ANLFt/QA
0LvS8WhCTDOvRLP7MM8dbiiIbVX4ignPayfv0XGv0Kn7/Drk3595cN1682DvSQb5//A1B25whBHo
gMi7HCtrjKTkvZBtBISz16FbD4Sjw4mspdVPO5CFBpOWBc6hHBo/hvGJOt9Rje3hHp4lOUX0xwwx
gBui9eLtOpdiq0zvECmoPisCAwEAAaMtMCswGwYDVR0RBBQwEoEQcGhpbEBlZGVuLm5ldC5uejAM
BgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBQUAA4GBAIqwE+pdP6xZLNOjZTQTxiHbo1SRJsX9gZo0
fat6zZPBoSJilT+5g4tgyj1cAogSXdcPPNzSuKk3HL/WklD0MQzSrZYQRrV8HlnxtTq17P9eQ9NP
cWrGPlF6EgXTN5bVVEH31gmCvOd/wSsRW/IZ8e671i+LjGH2ps/65GUmmSp2MIIDPzCCAqigAwIB
AgIBDTANBgkqhkiG9w0BAQUFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2Fw
ZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UE
CxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNv
bmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUu
Y29tMB4XDTAzMDcxNzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjELMAkGA1UEBhMCWkExJTAjBgNV
BAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h
bCBGcmVlbWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxVc1X7
TrnKmVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J8CuFWqo/
cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7n2XRxSpUhQ9IBH+nttE8YQRA
HmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4oDagNIYy
aHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJlZW1haWxDQS5jcmwwCwYDVR0P
BAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwyLTEzODANBgkqhkiG
9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aUnX9MIbj4Nh+qLZ82L8D0HFAgk3A8
/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowgT2Vfldr394fWxghOrvbqNOUQ
Gls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCAxAwggMMAgEBMHYwYjELMAkGA1UEBhMCWkExJTAj
BgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJz
b25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhAipUY9ewK/50R7kfLoVBGnMAkGBSsOAwIaBQCgggFv
MBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA3MDQxNzIwNTA1Nlow
IwYJKoZIhvcNAQkEMRYEFC1k0lS7EBrqGSPr530y99rhgXTpMIGFBgkrBgEEAYI3EAQxeDB2MGIx
CzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYD
VQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQIqVGPXsCv+dEe5Hy6FQR
pzCBhwYLKoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29u
c3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNz
dWluZyBDQQIQIqVGPXsCv+dEe5Hy6FQRpzANBgkqhkiG9w0BAQEFAASCAQCB3zsjAeFZoTC3fvRQ
Awz1T4fQV+q/6n+l5igv/lsC6Wq3oOdIaTcH3B6UfMVqslTnvqekxKaqdN1iDDwzpwf1q6digPz1
uYkL2+dvKqwEHPB3cjpgizbpWfVHBHRQP5fNP3fHkV/VQg3VnqI+NSp9PtgHGyiVlTDRoF+hbuy6
s6bJLRtms/HsovcrofjbB++OXzT1OoUEtWLynyyeuoMQblc8MlK6Poaf6xKKTOYvrT0DRaOdNY1e
jDPCdHkwgCQjTijRGY8vcxhx5YVU3g8slQ8OQW8DR3PgV56b4VeQGTfSLd10VRNCLlSmj/scr9c/
RIyM3Dw8lRpGZ3hF6mFSAAAAAAAA

--Apple-Mail-11-967360157--

From:	Philip Lamb <phil@e ..........>	Received:	Apr 17, 2007
To	ARToolKit Mailinglist <artoolkit@h ..................>
Subject:	Re: big input stream
--Apple-Mail-11-967360157 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Antonio, If you're working with big images (anything greater than 1024 pixels wide or tall qualifies as big for ARToolKit) you will run into a variety of hard-coded size limits in various places in the toolkit. There are some in the tracker (libAR) and some on the output side. At the moment, the way I usually tackle these limits is to scale the image down to 1024 pixels each side, and use that size for tracking (with appropriate size changes to the camera parameters). The resulting pose estimation can then be applied to the full-size image for rendering. Proper handling of HD image streams is something that will definitely be tackled in ARToolKit in the future... we just have to find the time. Patches from the community always welcomed! Regards, Phil. On 17/04/2007, at 10:21 AM, Antonio Bleile wrote: > Hi, > > I'm currently experiencing a problem when the marker > size is too big (in pixels...!). I have an HD stream > and whenever the marker is too close to the camera and > thus the marker is projected on let's say a 600x600 pixel > region, ArToolKit(Plus) does not track anymore. Of course > it becomes worse on photographic images taken from cameras > with high megapixel values (>= 10...). Is this a hardcoded > limitation somewhere? Any switches? > > Regards, > > Toni --Apple-Mail-11-967360157 Content-Transfer-Encoding: base64 Content-Type: application/pkcs7-signature; name=smime.p7s Content-Disposition: attachment; filename=smime.p7s MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGITCCAtow ggJDoAMCAQICECKlRj17Ar/nRHuR8uhUEacwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDIxODIyMzgyNloXDTA4MDIxODIyMzgy NlowQjEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEfMB0GCSqGSIb3DQEJARYQcGhp bEBlZGVuLm5ldC5uejCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMFM7RZK14/1EBHq xm3qClBRGN0s0ueca/LLI8lixA/CP94ntSTX86fV8JnHc3pnufkPKDwhtv06u+VS5kdUqJXTWTs7 HLhtBzMeN3kfZfpyg3+oTEt4v1chsnYNom5eclCBG89bSgqhALm6bhALz1R8f5PHQwT4ANLFt/QA 0LvS8WhCTDOvRLP7MM8dbiiIbVX4ignPayfv0XGv0Kn7/Drk3595cN1682DvSQb5//A1B25whBHo gMi7HCtrjKTkvZBtBISz16FbD4Sjw4mspdVPO5CFBpOWBc6hHBo/hvGJOt9Rje3hHp4lOUX0xwwx gBui9eLtOpdiq0zvECmoPisCAwEAAaMtMCswGwYDVR0RBBQwEoEQcGhpbEBlZGVuLm5ldC5uejAM BgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBQUAA4GBAIqwE+pdP6xZLNOjZTQTxiHbo1SRJsX9gZo0 fat6zZPBoSJilT+5g4tgyj1cAogSXdcPPNzSuKk3HL/WklD0MQzSrZYQRrV8HlnxtTq17P9eQ9NP cWrGPlF6EgXTN5bVVEH31gmCvOd/wSsRW/IZ8e671i+LjGH2ps/65GUmmSp2MIIDPzCCAqigAwIB AgIBDTANBgkqhkiG9w0BAQUFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2Fw ZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UE CxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNv bmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUu Y29tMB4XDTAzMDcxNzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjELMAkGA1UEBhMCWkExJTAjBgNV BAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxVc1X7 TrnKmVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J8CuFWqo/ cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7n2XRxSpUhQ9IBH+nttE8YQRA HmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4oDagNIYy aHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJlZW1haWxDQS5jcmwwCwYDVR0P BAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwyLTEzODANBgkqhkiG 9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aUnX9MIbj4Nh+qLZ82L8D0HFAgk3A8 /a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowgT2Vfldr394fWxghOrvbqNOUQ Gls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCAxAwggMMAgEBMHYwYjELMAkGA1UEBhMCWkExJTAj BgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJz b25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhAipUY9ewK/50R7kfLoVBGnMAkGBSsOAwIaBQCgggFv MBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA3MDQxNzIwNTA1Nlow IwYJKoZIhvcNAQkEMRYEFC1k0lS7EBrqGSPr530y99rhgXTpMIGFBgkrBgEEAYI3EAQxeDB2MGIx CzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYD VQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQIqVGPXsCv+dEe5Hy6FQR pzCBhwYLKoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29u c3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNz dWluZyBDQQIQIqVGPXsCv+dEe5Hy6FQRpzANBgkqhkiG9w0BAQEFAASCAQCB3zsjAeFZoTC3fvRQ Awz1T4fQV+q/6n+l5igv/lsC6Wq3oOdIaTcH3B6UfMVqslTnvqekxKaqdN1iDDwzpwf1q6digPz1 uYkL2+dvKqwEHPB3cjpgizbpWfVHBHRQP5fNP3fHkV/VQg3VnqI+NSp9PtgHGyiVlTDRoF+hbuy6 s6bJLRtms/HsovcrofjbB++OXzT1OoUEtWLynyyeuoMQblc8MlK6Poaf6xKKTOYvrT0DRaOdNY1e jDPCdHkwgCQjTijRGY8vcxhx5YVU3g8slQ8OQW8DR3PgV56b4VeQGTfSLd10VRNCLlSmj/scr9c/ RIyM3Dw8lRpGZ3hF6mFSAAAAAAAA --Apple-Mail-11-967360157--

From:	"Antonio Bleile" <antonio.bleile@s ........>	Received:	Apr 17, 2007
To	"'ARToolKit Mailinglist'" <artoolkit@h ..................>
Subject:	big input stream
Hi, I'm currently experiencing a problem when the marker size is too big (in pixels...!). I have an HD stream=20 and whenever the marker is too close to the camera and thus the marker is projected on let's say a 600x600 pixel region, ArToolKit(Plus) does not track anymore. Of course=20 it becomes worse on photographic images taken from cameras with high megapixel values (>=3D 10...). Is this a hardcoded=20 limitation somewhere? Any switches? Regards, Toni -- Ing. Antonio Bleile Seac02 S.r.l. via Avogadro 4 10121 Torino Italia Tel. +39.011.197.006.52 Fax +39.011.197.006.53 E-mail antonio.bleile@s ........ Sito www.seac02.it Questa E-mail =E8 rivolta unicamente alle persone o enti ai quali =E8 indirizzata. Essa pu=F2 contenere informazioni la cui riservatezza =E8 = tutelata. Sono vietati la riproduzione e qualsiasi uso di questa e-mail e/o delle informazioni in essa contenute in mancanza di autorizzazione del destinatario.=20 This e-mail is intended only for the person or entity to which is = addressed. It may contain information that is privileged, proprietary, = confidential, attorney work product or otherwise exempted from disclosure under = applicable law. Copying, dissemination or use of this e-mail or the information = herein by anyone other than the intended recipient is prohibited.=20

From:	Daniel Wagner <daniel@i ...............>	Received:	Apr 17, 2007
To	ARToolKit Mailinglist <artoolkit@h ..................>
Subject:	Re: big input stream
hi Antonio, Look into config.h Look for AR_AREA_MAX, AR_CHAIN_MAX, MAX_BUFFER_WIDTH & MAX_BUFFER_HEIGHT. Since those values influence the memory consumption they are usually set to a useful mininum... I hope that helps, Daniel

From:	Antonio Bleile <antonio.bleile@s ........>	Received:	Apr 18, 2007
To	ARToolKit Mailinglist <artoolkit@h ..................>
Subject:	Re: big input stream
Well, actually, changing the values indicated by Daniel worked out ok for me, I get a correct pose estimation for HD. I'm using ArToolKitPlus, perhaps there are some more limitations in ArToolKit (can't imagine why...). Regards, Toni Scrive Philip Lamb <phil@e ..........>: > Antonio, > > If you're working with big images (anything greater than 1024 pixels > wide or tall qualifies as big for ARToolKit) you will run into a > variety of hard-coded size limits in various places in the toolkit. > There are some in the tracker (libAR) and some on the output side. > > At the moment, the way I usually tackle these limits is to scale the > image down to 1024 pixels each side, and use that size for tracking > (with appropriate size changes to the camera parameters). The > resulting pose estimation can then be applied to the full-size image > for rendering. > > Proper handling of HD image streams is something that will definitely > be tackled in ARToolKit in the future... we just have to find the > time. Patches from the community always welcomed! > > Regards, > Phil. > > On 17/04/2007, at 10:21 AM, Antonio Bleile wrote: > > > Hi, > > > > I'm currently experiencing a problem when the marker > > size is too big (in pixels...!). I have an HD stream > > and whenever the marker is too close to the camera and > > thus the marker is projected on let's say a 600x600 pixel > > region, ArToolKit(Plus) does not track anymore. Of course > > it becomes worse on photographic images taken from cameras > > with high megapixel values (>= 10...). Is this a hardcoded > > limitation somewhere? Any switches? > > > > Regards, > > > > Toni > > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.