From info-volumizer-owner@els.sgi.com Wed Mar 8 22:31:55 2006 Received: (from majordom@localhost) by els.sgi.com (8.12.10/8.12.2/els-2.2) id k296UaB81749088; Wed, 8 Mar 2006 22:30:36 -0800 (PST) Received: from web60920.mail.yahoo.com (web60920.mail.yahoo.com [209.73.178.248]) by els.sgi.com (8.12.10/8.12.2/els-2.2) with SMTP id k278Qgx31716110 for ; Tue, 7 Mar 2006 00:26:42 -0800 (PST) Received: (qmail 41606 invoked by uid 60001); 7 Mar 2006 08:26:41 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=bVw0gMNm3Flgs1wgAIMrmNoseo3QleSSxtclMKMZcfd8sLeSalBE2hL8S+Nf7hmcFTguvMl2ppU5HC+aUdCjZeaQwBjY91WaxUArF5qJm2dfY6Ft5xO86EordveqxVJJuvphspscLvLT6QM4hVgUmxbxdPFGq2tg4SDqQN/t/S0= ; Message-ID: <20060307082641.41604.qmail@web60920.mail.yahoo.com> Received: from [69.225.241.46] by web60920.mail.yahoo.com via HTTP; Tue, 07 Mar 2006 00:26:41 PST Date: Tue, 7 Mar 2006 00:26:41 -0800 (PST) From: Michael Wiley Subject: [info-volumizer] Rendering very slow on XP Pro SP2 using Quadro FX 500 AGP To: info-volumizer@els.sgi.com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-info-volumizer@els.sgi.com Precedence: bulk Reply-To: info-volumizer@els.sgi.com Hi, I am experiencing a strange problem with Volumizer. I'll try to explain it as clearly as possible. First of all, my system configuration is as follows: Hardware Platform: Intel Pentium III dual processor system 927 MHz w/ 1.00 GB RAM Graphics Port: AGP 4X Graphics Card: Quadro Fx 500 with 128 MB RAM for AGP Operating System: Microsoft Windows XP Professional 2002 with Service Pack 2 Volumizer Version: 2.7 Problem Description: I have written a Volume Rendering application to render a medical imaging dataset using volumizer. The data size is approximately 13.1 MB. I am using Visual Studio .NET 2003 IDE. The language used to write the application is unmanaged C++. If I launch the application from within the IDE (using the F5 key or the Debug->Start New Instance menu option) it runs fine and the interactive rotation of the rendered volume yields a near real-time frame rate. However, when I launch the application by double clicking on it or from a command prompt it makes my system unusable and very slow. Furthermore, I don't see the rendered data on the screen. In the meantime, the cpu is continuously utilized by the application's process. I have to kill this process from the task manager in order to gain usability of my system. In order to isolate the issue I tried running SGI's XMLViewer demo app which ships with Volumizer. I started the app by double clicking on it and opened the binary.vz file (bonsai tree dataset). After the dataset finished renderig on the screen I tried to interactively rotate it. However, this caused my system to slow down and I noticed in the task manager that one of the CPU's was continuously being used by the XMLViewer.exe process. After about a minute the screen finished the rotate request and rendered the rotated bonsai tree. But, obviously something is wrong here as the response is unusually very slow. Now, to experiment further, I added the XMLViewer.exe file to a Visual Studio solution so that I could launch it from within the IDE. I used the Debug->Start New Instance menu option to launch XMLViewer app. I opened the same binary.vz dataset and now I could interactively rotate the rendered dataset with almost realtime response. Can anyone point out what the problem could be? It seems to be some enviroment related issue as the both the XMLViewer and my application seem to work OK if launched from within the IDE but these same applications fail miserably when run outside the IDE. I doubt if it is the card that has the problem. If there was something wrong with the card the application would have failed when launched from within the IDE. I also have checked that I have the latest drivers from NVIDIA. Have the folks at SGI run across this issue? It should be very easy to recreate as the sample XMLViewer app supplied with Volumizer fails. Let me know. Thanks, Michael Wiley. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From info-volumizer-owner@els.sgi.com Wed Mar 8 22:31:55 2006 Received: (from majordom@localhost) by els.sgi.com (8.12.10/8.12.2/els-2.2) id k296UbWE1780675; Wed, 8 Mar 2006 22:30:37 -0800 (PST) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by els.sgi.com (8.12.10/8.12.2/els-2.2) with ESMTP id k22KZ7x31640575 for ; Thu, 2 Mar 2006 12:35:08 -0800 (PST) Received: by wproxy.gmail.com with SMTP id 71so502504wri for ; Thu, 02 Mar 2006 12:35:06 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=KvZIooAijjvNSuOvaRJ4/kyB6VIBL9AlW4pvQRnht9R9YxMnP8OApAm3YxiN1H2KktDRqL8ARsCBA7a5nLQlgizopqwS0v7Qt+aB0TqDm2NDBcmhkauW8NU/44WHAQPULZ8WIwMgOufs1A6/UM8YdCOq+kMarjGViSliVTw6M8I= Received: by 10.65.204.19 with SMTP id g19mr913164qbq; Thu, 02 Mar 2006 12:35:06 -0800 (PST) Received: by 10.65.75.15 with HTTP; Thu, 2 Mar 2006 12:35:06 -0800 (PST) Message-ID: <2df3dd7f0603021235r2f4e4b58mf6d56469c960c20f@mail.gmail.com> Date: Thu, 2 Mar 2006 15:35:06 -0500 From: "Kiran Vaka" To: info-volumizer@els.sgi.com Subject: [info-volumizer] IFLLoader cannot read TIFF data, (2.9, WindowsXP) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_16033_3648275.1141331706727" Sender: owner-info-volumizer@els.sgi.com Precedence: bulk Reply-To: info-volumizer@els.sgi.com ------=_Part_16033_3648275.1141331706727 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline SGkgYWxsCgpJIGhhdmUgcmVjZW50bHkgaW5zdGFsbGVkIFNHSSBPcGVuR0wgVm9sdW1pemVyIHYy LjkgZm9yIFdpbmRvd3MgKGV2YWx1YXRpb24KbGljZW5zZSksIGFuZCBhbSB0ZXN0aW5nIG91dCB0 aGUgZGVtb3MgYW5kIHNhbXBsZSBwcm9ncmFtcy4gVGhlIHN5c3RlbSBPUyBpcwpXaW5kb3dzWFAg JiBncmFwaGljcyBjYXJkIGlzIDY0bWIgblZpZGlhIEdlRm9yY2VGWCA1MjAwLgoKSSBpbnN0YWxs ZWQgTGliVGlmZiBmb3Igd2luZG93cyB2My42LjEgZnJvbSBoZXJlIChjb21wbGV0ZSBwYWNrYWdl IGV4Y2VwdApzb3VyY2VzKQpodHRwOi8vZ251d2luMzIuc291cmNlZm9yZ2UubmV0L3BhY2thZ2Vz L3RpZmYtd2luMzIuaHRtCgphbmQgYW0gdXNpbmcgTWljcm9zb2Z0IFZpc3VhbCBTdHVkaW8gNi4w IGRldi4gZW52aXJvbm1lbnQuCgpXaGVuIEkgcnVuIHRoZSBiYXRjaCBmaWxlIGZvciAnU2ltcGxl IFRlc3QgQXBwbGljYXRpb24nLCBpdCBydW5zIGZpbmUsIGFuZCBJCmdldCB0aGUgQ1QgSGVhZCBy ZW5kZXJlZCBvbiB0aGUgc2NyZWVuLgoKTm93LCBJIGdvIHRvIFNpbGljb24gR3JhcGhpY3M+T3Bl bkdMIFZvbHVtaXplcj5zcmM+YXBwcz5zaW1wbGU+d2luZG93cyBhbmQKb3BlbiB2aWV3LmRzcCBp biBkZXYuIGVudi4gYW5kIGNvbXBpbGUgaXQuIEl0IGNvbXBpbGVzIGZpbmUgd2l0aCBubyBlcnJv cnMgLAomIHdhcm5pbmcKLi4uXGxvYWRlcnNcdm9sdW1lbG9hZGVyLmgoNzEpIDogd2FybmluZyBD NDI3NTogbm9uIGRsbC1pbnRlcmZhY2UgY2xhc3MKJ3Z6TWVtb3J5JyB1c2VkIGFzIGJhc2UgZm9y IGRsbC1pbnRlcmZhY2UgY2xhc3MgJ1ZvbHVtZUxvYWRlcicKClRoZSBwcm9qZWN0IHNldHRpbmdz IGFyZSBsaWtlIHRoaXM6CgpJbmNsdWRlOgpDOlxQUk9HUkFNIEZJTEVTXEdOVVdJTjMyXElOQ0xV REUKQzpcUFJPR1JBTSBGSUxFU1xTSUxJQ09OIEdSQVBISUNTXE9QRU5HTCBWT0xVTUlaRVJcSU5D TFVERQpDOlxQUk9HUkFNIEZJTEVTXFNJTElDT04gR1JBUEhJQ1NcT1BFTkdMIFZPTFVNSVpFUlxT UkNcTElCCgpMaWJyYXJ5OgpDOlxQUk9HUkFNIEZJTEVTXEdOVVdJTjMyXExJQgpDOlxQUk9HUkFN IEZJTEVTXFNJTElDT04gR1JBUEhJQ1NcT1BFTkdMIFZPTFVNSVpFUlxMSUIKCmFuZCBJIGhhdmUg YWxzbyBzZXQgdGhlIHBhdGggdG8gdGhlIGRsbHMgaW4gdm9sdW1pemVyIGFuZCBsaWJ0aWZmIGxp YnJhcnkKQzpcUHJvZ3JhbSBGaWxlc1xTaWxpY29uIEdyYXBoaWNzXE9wZW5HTCBWb2x1bWl6ZXJc YmluXApDOlxQcm9ncmFtIEZpbGVzXEdudVdpbjMyXGJpbgoKQnV0IHdoZW4gSSB0aGUgcnVuIHRo ZSBjb21waWxlZCBwcm9ncmFtICggUnVubWUuYmF0ICksIHRoZSBwcm9ncmFtIGNyYXNoZXMuCk9u IGV4cGxvcmluZyBJIGZvdW5kIHRoYXQKSUZMTG9hZGVyICpsb2FkZXIgPSBJRkxMb2FkZXI6Om9w ZW4oImZpbGVOYW1lIik7CmlzIHJldHVybmluZyBOVUxMLCBhbmQgaGVuY2UgZXhpdCgwKSBpcyBi ZWluZyBjYWxsZWQgYWZ0ZXIgdGhhdCwgdGVybWluYXRpbmcKdGhlIHByb2dyYW0uClNvbWVob3cs IHRoZSBJRkxMb2FkZXIgKCBvciBUSUZGTG9hZGVyICkgaXMgbm90IGFibGUgdG8gcmVhZCB0aGUg ZGF0YXNldAoKSG93IGRvIEkgc29sdmUgdGhpcyA/IEFtIEkgIGRvaW5nIHNvbWV0aGluZyB3cm9u ZyBoZXJlLCBtaXNzaW5nIG91dApzb21ldGhpbmcsCm9yIGlzIHRoZXJlIGEgcHJvYmxlbSB3aXRo IHRoZSBsaWJ0aWZmIGluc3RhbGxhdGlvbiAsIG9yIHdpdGggaWZsbG9hZGVyID8KCkkgd291bGQg bGlrZSB0byBzb2x2ZSB0aGlzIHF1aWNrbHksICYgdGVzdCBzb21lIG1vcmUgYXBwbGljYXRpb25z IGJlZm9yZQpkZWNpZGluZyB3aGV0aGVyIHRvIGJ1eSB0aGUgcGVybWFuZW50IGxpY2Vuc2UuCgpU aGFua3MgaW4gYWR2YW5jZS4KCnJlZ2FyZHMKS2lyYW4K ------=_Part_16033_3648275.1141331706727 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline SGkgYWxsPGJyPjxicj5JIGhhdmUgcmVjZW50bHkgaW5zdGFsbGVkIFNHSSBPcGVuR0wgVm9sdW1p emVyIHYyLjkgZm9yIFdpbmRvd3MgKGV2YWx1YXRpb24gbGljZW5zZSksIGFuZCBhbSB0ZXN0aW5n IG91dCB0aGUgZGVtb3MgYW5kIHNhbXBsZSBwcm9ncmFtcy4gVGhlIHN5c3RlbSBPUyBpcyBXaW5k b3dzWFAgJmFtcDsgZ3JhcGhpY3MgY2FyZCBpcyA2NG1iIG5WaWRpYSBHZUZvcmNlRlggNTIwMC4K PGJyPjxicj5JIGluc3RhbGxlZCBMaWJUaWZmIGZvciB3aW5kb3dzIHYzLjYuMSBmcm9tIGhlcmUg KGNvbXBsZXRlIHBhY2thZ2UgZXhjZXB0IHNvdXJjZXMpPGJyPjxhIGhyZWY9Imh0dHA6Ly9nbnV3 aW4zMi5zb3VyY2Vmb3JnZS5uZXQvcGFja2FnZXMvdGlmZi13aW4zMi5odG0iPmh0dHA6Ly9nbnV3 aW4zMi5zb3VyY2Vmb3JnZS5uZXQvcGFja2FnZXMvdGlmZi13aW4zMi5odG08L2E+PGJyPgo8YnI+ YW5kIGFtIHVzaW5nIE1pY3Jvc29mdCBWaXN1YWwgU3R1ZGlvIDYuMCBkZXYuIGVudmlyb25tZW50 LiA8YnI+PGJyPldoZW4gSSBydW4gdGhlIGJhdGNoIGZpbGUgZm9yICdTaW1wbGUgVGVzdCBBcHBs aWNhdGlvbicsIGl0IHJ1bnMgZmluZSwgYW5kIEkgZ2V0IHRoZSBDVCBIZWFkIHJlbmRlcmVkIG9u IHRoZSBzY3JlZW4uPGJyPjxicj5Ob3csIEkgZ28gdG8gU2lsaWNvbiBHcmFwaGljcyZndDtPcGVu R0wgVm9sdW1pemVyJmd0O3NyYyZndDthcHBzJmd0O3NpbXBsZSZndDt3aW5kb3dzIGFuZCBvcGVu IAp2aWV3LmRzcCBpbiBkZXYuIGVudi4gYW5kIGNvbXBpbGUgaXQuIEl0IGNvbXBpbGVzIGZpbmUg d2l0aCBubyBlcnJvcnMgLCAmYW1wOyB3YXJuaW5nPGJyPi4uLlxsb2FkZXJzXHZvbHVtZWxvYWRl ci5oKDcxKSA6IHdhcm5pbmcgQzQyNzU6IG5vbiBkbGwtaW50ZXJmYWNlIGNsYXNzICd2ek1lbW9y eScgdXNlZCBhcyBiYXNlIGZvciBkbGwtaW50ZXJmYWNlIGNsYXNzICdWb2x1bWVMb2FkZXInCjxi cj48YnI+VGhlIHByb2plY3Qgc2V0dGluZ3MgYXJlIGxpa2UgdGhpczo8YnI+PGJyPkluY2x1ZGU6 PGJyPkM6XFBST0dSQU0gRklMRVNcR05VV0lOMzJcSU5DTFVERTxicj5DOlxQUk9HUkFNIEZJTEVT XFNJTElDT04gR1JBUEhJQ1NcT1BFTkdMIFZPTFVNSVpFUlxJTkNMVURFPGJyPkM6XFBST0dSQU0g RklMRVNcU0lMSUNPTiBHUkFQSElDU1xPUEVOR0wgVk9MVU1JWkVSXFNSQ1xMSUI8YnI+Cjxicj5M aWJyYXJ5Ojxicj5DOlxQUk9HUkFNIEZJTEVTXEdOVVdJTjMyXExJQjxicj5DOlxQUk9HUkFNIEZJ TEVTXFNJTElDT04gR1JBUEhJQ1NcT1BFTkdMIFZPTFVNSVpFUlxMSUI8YnI+PGJyPmFuZCBJIGhh dmUgYWxzbyBzZXQgdGhlIHBhdGggdG8gdGhlIGRsbHMgaW4gdm9sdW1pemVyIGFuZCBsaWJ0aWZm IGxpYnJhcnk8YnI+QzpcUHJvZ3JhbSBGaWxlc1xTaWxpY29uIEdyYXBoaWNzXE9wZW5HTCBWb2x1 bWl6ZXJcYmluXCAKPGJyPkM6XFByb2dyYW0gRmlsZXNcR251V2luMzJcYmluPGJyPjxicj5CdXQg d2hlbiBJIHRoZSBydW4gdGhlIGNvbXBpbGVkIHByb2dyYW0gKCBSdW5tZS5iYXQgKSwgdGhlIHBy b2dyYW0gY3Jhc2hlcy4gT24gZXhwbG9yaW5nIEkgZm91bmQgdGhhdCA8YnI+SUZMTG9hZGVyICps b2FkZXIgPSBJRkxMb2FkZXI6Om9wZW4oJnF1b3Q7ZmlsZU5hbWUmcXVvdDspOzxicj5pcyByZXR1 cm5pbmcgTlVMTCwgYW5kIGhlbmNlIGV4aXQoMCkgaXMgYmVpbmcgY2FsbGVkIGFmdGVyIHRoYXQs IHRlcm1pbmF0aW5nIHRoZSBwcm9ncmFtLiAKPGJyPlNvbWVob3csIHRoZSBJRkxMb2FkZXIgKCBv ciBUSUZGTG9hZGVyICkgaXMgbm90IGFibGUgdG8gcmVhZCB0aGUgZGF0YXNldDxicj48YnI+SG93 IGRvIEkgc29sdmUgdGhpcyA/IEFtIEkmbmJzcDsgZG9pbmcgc29tZXRoaW5nIHdyb25nIGhlcmUs IG1pc3Npbmcgb3V0IHNvbWV0aGluZywgPGJyPm9yIGlzIHRoZXJlIGEgcHJvYmxlbSB3aXRoIHRo ZSBsaWJ0aWZmIGluc3RhbGxhdGlvbiAsIG9yIHdpdGggaWZsbG9hZGVyID8KPGJyPjxicj5JIHdv dWxkIGxpa2UgdG8gc29sdmUgdGhpcyBxdWlja2x5LCAmYW1wOyB0ZXN0IHNvbWUgbW9yZSBhcHBs aWNhdGlvbnMgYmVmb3JlIGRlY2lkaW5nIHdoZXRoZXIgdG8gYnV5IHRoZSBwZXJtYW5lbnQgbGlj ZW5zZS48YnI+PGJyPlRoYW5rcyBpbiBhZHZhbmNlLjxicj48YnI+cmVnYXJkczxicj5LaXJhbjxi cj48YnI+Cg== ------=_Part_16033_3648275.1141331706727-- From info-volumizer-owner@els.sgi.com Thu Mar 16 13:50:10 2006 Received: (from majordom@localhost) by els.sgi.com (8.12.10/8.12.2/els-2.2) id k2GLmxTu1904580; Thu, 16 Mar 2006 13:48:59 -0800 (PST) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.197]) by els.sgi.com (8.12.10/8.12.2/els-2.2) with ESMTP id k2AIWsx31784314 for ; Fri, 10 Mar 2006 10:32:55 -0800 (PST) Received: by nproxy.gmail.com with SMTP id x37so591802nfc for ; Fri, 10 Mar 2006 10:32:53 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=GAcptQKq1yfgcmdRiInQO6DwTXJGrvU2zKjhmnizVP4qRwz1vWiFsQE7gNBw8V4PXrHWgHTxOUVBRozlN2Q/ZNx4of8khxWls98I2GADVqWa47zyU5sfW2mcB2f8Y5BFeFCGMJMs6vhGVFmJU0X8BmL4XaP2Jc03Jq/HmHDiKFE= Received: by 10.48.42.10 with SMTP id p10mr1532734nfp; Fri, 10 Mar 2006 10:32:53 -0800 (PST) Received: by 10.48.217.6 with HTTP; Fri, 10 Mar 2006 10:32:53 -0800 (PST) Message-ID: Date: Fri, 10 Mar 2006 13:32:53 -0500 From: "Kevin Wang" To: info-volumizer@els.sgi.com, praveenb@sgi.com Subject: [info-volumizer] 3D cliptexture In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_5565_29554568.1142015573481" References: Sender: owner-info-volumizer@els.sgi.com Precedence: bulk Reply-To: info-volumizer@els.sgi.com ------=_Part_5565_29554568.1142015573481 Content-Type: multipart/alternative; boundary="----=_Part_5566_17367711.1142015573481" ------=_Part_5566_17367711.1142015573481 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Praveen, I tried to use 3D cliptexture in our demo. attached is the volumizer debug log. The problem is the everything seems to be working except that I cannot see anything on the screen. I wonder if it has anything to do with image size since it is not power of 2. I hope you can find something strange in the debug log. Look forward to your reply. -- Kevin ------=_Part_5566_17367711.1142015573481 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Praveen,

I tried to use 3D cliptexture in our demo. attached is the volumizer debug log. The problem is the everything seems to be working except that I cannot see anything on the screen. I wonder if it has anything to do with image size since it is not power of 2. I hope you can find something strange in the debug log. Look forward to your reply.
<= div style=3D"direction: ltr;">
-- Kevin

------=_Part_5566_17367711.1142015573481-- ------=_Part_5565_29554568.1142015573481 Content-Type: text/plain; name=demolog.txt; charset=us-ascii Content-Transfer-Encoding: 7bit X-Attachment-Id: f_eklhflg2 Content-Disposition: attachment; filename="demolog.txt" [kwang@be volumizerdemogcc323]$ ./AtamaiVolumizerDemo Initializing debug Level to: 5 Volumizer (3): ================================================ Volumizer (3): Checking for 'volumizer_linux' license Volumizer (0): ================================================ Volumizer (0): = OpenGL Volumizer 2.9 = Volumizer (0): = DEMO EDITION = Volumizer (0): ================================================ Volumizer (0): = For information about purchasing the full = Volumizer (0): = OpenGL Volumizer product, visit = Volumizer (0): = http://www.sgi.com/software/volumizer/ = Volumizer (0): ================================================ Volumizer (0): = Demo License Expiration in 52 days = Volumizer (0): ================================================ Volumizer (4): Object 85c33c8 ref() -> Ref count = 2 Volumizer (4): Object 85c33c8 unref() -> Ref count = 1 Volumizer (4): Object 85c34f0 ref() -> Ref count = 2 Volumizer (4): Object 85c3440 ref() -> Ref count = 2 Volumizer (4): Object 85c34f0 unref() -> Ref count = 1 Volumizer (4): Object 85c3440 unref() -> Ref count = 1 Volumizer (5): Client attribute stack maximum depth = 16 Volumizer (4): Vendor string = NVIDIA Corporation Volumizer (4): Renderer string = GeForce 6600 GT/AGP/SSE2 Volumizer (2): NVIDIA GeForce graphics Volumizer (5): vzPlatformInfo::vzPlatformInfo(): ARBImaging = yes Volumizer (5): vzPlatformInfo::vzPlatformInfo(): ARBFragmentProgram = yes Volumizer (5): vzPlatformInfo::vzPlatformInfo(): ARBVertexProgram = yes Volumizer (5): vzPlatformInfo::vzPlatformInfo(): ARBFragmentShader = yes Volumizer (5): vzPlatformInfo::vzPlatformInfo(): ARBVertexShader = yes Volumizer (5): vzPlatformInfo::vzPlatformInfo(): ATIFragmentShader = no Volumizer (5): vzPlatformInfo::vzPlatformInfo(): SGITextureColorTable = no Volumizer (5): vzPlatformInfo::vzPlatformInfo(): SGIColorMatrix = no Volumizer (3): ARBFragmentProgram::init(): GL_ARB_fragment_program supported Volumizer (3): ARBFragmentShader::init(): GL_ARB_fragment_shader supported Volumizer (2): ClipRenderImplementation::ClipRenderImplementation(): Assuming available texture memory to be 115 MB Volumizer (3): vzClipRenderAction::setLODThreshold: Setting the threshold value to be 1.000000 Volumizer (1): Data dimensions = 181, 217, 181 Volumizer (1): Texture type changed to VZ_UNSIGNED_SHORT Volumizer (1): Number of Components = 1 Volumizer (3): vzParameterClipTexture::setBrickDimensions(): Texture brick dimensions = (181, 217, 181) Volumizer (2): ParameterClipTextureImpl::setPhysicalMemorySize: Physical Memory Size = 67108864 bytes Volumizer (4): Object 86f0c70 ref() -> Ref count = 2 Volumizer (4): Object 86f0c70 unref() -> Ref count = 1 Volumizer (2): ParameterClipTextureImpl::setGeometryROI: Geometry ROI = (0.000000, 0.000000, 0.000000) - (181.000000, 217.000000, 181.000000) Volumizer (0): ClipRenderInterface: Scaling geometryROI to (181.000000, 217.000000, 181.000000) Volumizer (0): NumberOfLevels is 1 Volumizer (3): vzParameterClipTexture::setDataLoaderCB(): Data loader CB = 40639bf8, User data = 8738ba8 range:0 65535 Volumizer (4): Object 86f0e40 ref() -> Ref count = 2 Volumizer (4): Object 86f0e40 unref() -> Ref count = 1 Volumizer (3): vzClipRenderAction::manage : Number of shapes currently managed = 1 Volumizer (3): ParameterClipTextureImpl::initClipTextures(): Number of clip-textures in shape 85c35c0 is 1 Volumizer (2): vzParameterClipTexture: Original volume dimensions = (181, 217, 181) Volumizer (2): vzParameterClipTexture: Texture brick size = (181, 217, 181) Volumizer (2): vzParameterClipTexture: Num of leaves = (1, 1, 1) Volumizer (2): vzParameterClipTexture: Num of levels = 1 Volumizer (2): vzParameterClipTexture: Number of threads not set. Using 1 loader threads Volumizer (3): Level 0: Bricked Volume dimensions = (181, 217, 181) Volumizer (3): Level 0: Texture brick dimensions = (181, 217, 181) Volumizer (3): Level 0: Total number of texture bricks = (1, 1, 1) Volumizer (3): ParameterClipTextureImpl::createTreeLevels(): Total physical memory = 67108864 bytes, Phys brick size = 14218274 bytes Volumizer (3): ClipLevel 0, Number of physical bricks = 5, computed dims = (2, 2, 2), actual bricks = 8 Volumizer (3): ClipLevel 0, Memory remaining = 67108864, Suggested number of physical bricks = 8, dims = (2, 2, 2) Volumizer (3): ClipLevel 0: Physical window size = 14218274, Actual number of bricks = (1, 1, 1) Volumizer (3): Initializing level 0 Volumizer (4): Object 85c33c8 ref() -> Ref count = 2 Volumizer (4): Object 86f0e40 ref() -> Ref count = 2 Volumizer (4): Object 86f0e40 ref() -> Ref count = 3 Volumizer (4): Object 86f0e40 ref() -> Ref count = 4 Volumizer (4): Object 86f0e40 unref() -> Ref count = 3 Volumizer (4): Object 86f0e40 unref() -> Ref count = 2 Volumizer (2): ClipLevel::initialize(): Original appearance has 2 parameters. Clip-level appearance has 1 parameters Volumizer (4): Object 85c34f0 ref() -> Ref count = 2 Volumizer (4): Object 873dea0 ref() -> Ref count = 2 Volumizer (4): Object 873dea0 unref() -> Ref count = 1 Volumizer (2): ClipLevel 0: Data Dimensions = (181, 217, 181) Volumizer (2): ClipLevel 0: Geometry ROI = (0.000000, 0.000000, 0.000000) - (181.000000, 217.000000, 181.000000) Volumizer (2): Level 0: Total number of physical memory bricks = (1, 1, 1) Volumizer (2): Level 0: Number of physical bricks in the window = (1, 1, 1) Volumizer (2): Level 0: Total physical memory window size is approximately 14218274 bytes Volumizer (3): BrickedVolume::setCurrentWindow: Load queue not set for level 0 yet! Volumizer (2): ParameterClipTextureImpl::createTreeLevels(): Number of levels = 1, Allowed memory size = 67108864, Actual maximum = 14218274 Volumizer (2): Creating LoadQueue for 1 levels Volumizer (2): Creating 1 loader threads Volumizer (3): ClipLevel #0: Physical window size = (1, 1, 1) bricks Volumizer (3): LoadQueue:: Elements on load queue = 1 Volumizer (4): Object 85c35c0 ref() -> Ref count = 2 Volumizer (4): Object 85c3440 ref() -> Ref count = 2 Volumizer (4): Object 86f0e40 ref() -> Ref count = 3 Volumizer (4): Object 85c33c8 ref() -> Ref count = 3 Volumizer (3): ClipShapeManager::beginDraw():Number of shapes currently managed = 1 Volumizer (2): Physical Brick (0, 0, 0) not in main memory, loading... Volumizer (2): loadNow()::Given brick 86f27a8 not scheduled for read. New index (0, 0, 0), this = 86ef240 Volumizer (0): Extents are: 0, 180, 0, 216, 0 ,180 Volumizer (0): Level is: 0 filename:/data/kwang/tmp/sbrain.mhd extent:018002160180 Volumizer (5): loadBrick took 1126 ms, Rate = 12.62 MB/sec Volumizer (1): loadNow()::Phys bricks in mem = 1, returning Volumizer (4): Object 82543e0 ref() -> Ref count = 2 Volumizer (5): Pixelstore settings: SKIP_PIXELS: 0, SKIP_ROWS: 0, SKIP_IMAGES: 0, ROW_LENGTH: 181, IMAGE_HEIGHT: 217 Volumizer (5): glTexImage3D called for (181 x 217 x 181) texture (loading into (256 x 256 x 256) texture), data ptr = 0, ID = 4 Volumizer (5): glTexSubImage3D called for (181 x 217 x 181) texture (loading into (256 x 256 x 256) texture). ID = 4 Volumizer (5): vzTMRenderAction: Total texture memory consumed: 33554432 Volumizer (2): ClipRenderImplementation:: Total texture memory used = 32 MB, Download = 32, Render = 32 Volumizer (3): ClipShapeManager::draw():Drawing shape 85c35c0 Volumizer (5): TMInternalGPUShaderImpl::initShader(): Generated fragment shader 1 Volumizer (5): This works fine after binding the shader Volumizer (4): Object 85c34f0 ref() -> Ref count = 3 Volumizer (4): Object 825f720 ref() -> Ref count = 2 Volumizer (4): Object 825f6a0 ref() -> Ref count = 2 Volumizer (4): Object 825f6a0 unref() -> Ref count = 1 Volumizer (4): Object 825f720 unref() -> Ref count = 1 Volumizer (3): Computing adjacency list... Volumizer (3): ClipShapeManager::beginDraw():Number of shapes currently managed = 1 Volumizer (5): vzTMRenderAction: Total texture memory consumed: 33554432 Volumizer (2): ClipRenderImplementation:: Total texture memory used = 32 MB, Download = 0, Render = 32 Volumizer (3): ClipShapeManager::draw():Drawing shape 85c35c0 Volumizer (3): ClipShapeManager::beginDraw():Number of shapes currently managed = 1 Volumizer (5): vzTMRenderAction: Total texture memory consumed: 33554432 Volumizer (2): ClipRenderImplementation:: Total texture memory used = 32 MB, Download = 0, Render = 32 Volumizer (3): ClipShapeManager::draw():Drawing shape 85c35c0 ------=_Part_5565_29554568.1142015573481-- From info-volumizer-owner@els.sgi.com Thu Mar 16 13:50:11 2006 Received: (from majordom@localhost) by els.sgi.com (8.12.10/8.12.2/els-2.2) id k2GLmx771919798; Thu, 16 Mar 2006 13:48:59 -0800 (PST) Received: from gobbles.engr.sgi.com (gobbles.engr.sgi.com [192.102.97.44]) by els.sgi.com (8.12.10/8.12.2/els-2.2) with ESMTP id k2GLkEx31891903 for ; Thu, 16 Mar 2006 13:46:15 -0800 (PST) Received: from PRAVEEN (mtv-vpn-sw-corp-0-143.corp.sgi.com [134.15.0.143]) by gobbles.engr.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id k2GLkD2v241132 for ; Thu, 16 Mar 2006 13:46:14 -0800 (PST) From: "Praveen Bhaniramka" To: Subject: RE: [info-volumizer] IFLLoader cannot read TIFF data, (2.9, WindowsXP) Date: Fri, 17 Mar 2006 03:16:15 +0530 Message-ID: <010b01c64943$109ae160$8f000f86@PRAVEEN> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_010C_01C64971.2A531D60" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2096 In-Reply-To: <2df3dd7f0603021235r2f4e4b58mf6d56469c960c20f@mail.gmail.com> Importance: Normal Sender: owner-info-volumizer@els.sgi.com Precedence: bulk Reply-To: info-volumizer@els.sgi.com This is a multi-part message in MIME format. ------=_NextPart_000_010C_01C64971.2A531D60 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi Kiran, Sorry for the late reply. Since, you are being able to run the simple test application, I am assuming that everything is fine with your system and the installed libraries, including libtiff and Volumizer libraries. The IFLLoader source code is provided along with the Volumizer sample code and is installed under src/lib/loaders directory. Please check in there to see what might be going on. Please make sure that the correct DLLs for vzLoader library is being loaded by the application. - Praveen -----Original Message----- From: owner-info-volumizer@els.sgi.com [mailto:owner-info-volumizer@els.sgi.com] On Behalf Of Kiran Vaka Sent: Friday, March 03, 2006 2:05 AM To: info-volumizer@els.sgi.com Subject: [info-volumizer] IFLLoader cannot read TIFF data, (2.9, WindowsXP) Hi all I have recently installed SGI OpenGL Volumizer v2.9 for Windows (evaluation license), and am testing out the demos and sample programs. The system OS is WindowsXP & graphics card is 64mb nVidia GeForceFX 5200. I installed LibTiff for windows v3.6.1 from here (complete package except sources) http://gnuwin32.sourceforge.net/packages/tiff-win32.htm and am using Microsoft Visual Studio 6.0 dev. environment. When I run the batch file for 'Simple Test Application', it runs fine, and I get the CT Head rendered on the screen. Now, I go to Silicon Graphics>OpenGL Volumizer>src>apps>simple>windows and open view.dsp in dev. env. and compile it. It compiles fine with no errors , & warning ...\loaders\volumeloader.h(71) : warning C4275: non dll-interface class 'vzMemory' used as base for dll-interface class 'VolumeLoader' The project settings are like this: Include: C:\PROGRAM FILES\GNUWIN32\INCLUDE C:\PROGRAM FILES\SILICON GRAPHICS\OPENGL VOLUMIZER\INCLUDE C:\PROGRAM FILES\SILICON GRAPHICS\OPENGL VOLUMIZER\SRC\LIB Library: C:\PROGRAM FILES\GNUWIN32\LIB C:\PROGRAM FILES\SILICON GRAPHICS\OPENGL VOLUMIZER\LIB and I have also set the path to the dlls in volumizer and libtiff library C:\Program Files\Silicon Graphics\OpenGL Volumizer\bin\ C:\Program Files\GnuWin32\bin But when I the run the compiled program ( Runme.bat ), the program crashes. On exploring I found that IFLLoader *loader = IFLLoader::open("fileName"); is returning NULL, and hence exit(0) is being called after that, terminating the program. Somehow, the IFLLoader ( or TIFFLoader ) is not able to read the dataset How do I solve this ? Am I doing something wrong here, missing out something, or is there a problem with the libtiff installation , or with iflloader ? I would like to solve this quickly, & test some more applications before deciding whether to buy the permanent license. Thanks in advance. regards Kiran ------=_NextPart_000_010C_01C64971.2A531D60 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
Hi=20 Kiran,
 
Sorry = for the late=20 reply. Since, you are being able to run the simple test application, I = am=20 assuming that everything is fine with your system and the installed = libraries,=20 including libtiff and Volumizer libraries.
 
The = IFLLoader source=20 code is provided along with the Volumizer sample code and is installed = under=20 src/lib/loaders directory. Please check in there to see what might be = going on.=20 Please make sure that the correct DLLs for vzLoader library is being = loaded by=20 the application.  
 
-=20 Praveen
 
 
-----Original Message-----
From:=20 owner-info-volumizer@els.sgi.com = [mailto:owner-info-volumizer@els.sgi.com]=20 On Behalf Of Kiran Vaka
Sent: Friday, March 03, 2006 = 2:05=20 AM
To: info-volumizer@els.sgi.com
Subject:=20 [info-volumizer] IFLLoader cannot read TIFF data, (2.9,=20 WindowsXP)

Hi all

I have recently installed = SGI=20 OpenGL Volumizer v2.9 for Windows (evaluation license), and am testing = out the=20 demos and sample programs. The system OS is WindowsXP & graphics = card is=20 64mb nVidia GeForceFX 5200.

I installed LibTiff for windows = v3.6.1=20 from here (complete package except sources)
http://g= nuwin32.sourceforge.net/packages/tiff-win32.htm

and=20 am using Microsoft Visual Studio 6.0 dev. environment.

When I = run the=20 batch file for 'Simple Test Application', it runs fine, and I get the = CT Head=20 rendered on the screen.

Now, I go to Silicon Graphics>OpenGL = Volumizer>src>apps>simple>windows and open view.dsp in = dev. env.=20 and compile it. It compiles fine with no errors , &=20 warning
...\loaders\volumeloader.h(71) : warning C4275: non = dll-interface=20 class 'vzMemory' used as base for dll-interface class 'VolumeLoader'=20

The project settings are like = this:

Include:
C:\PROGRAM=20 FILES\GNUWIN32\INCLUDE
C:\PROGRAM FILES\SILICON GRAPHICS\OPENGL=20 VOLUMIZER\INCLUDE
C:\PROGRAM FILES\SILICON GRAPHICS\OPENGL=20 VOLUMIZER\SRC\LIB

Library:
C:\PROGRAM=20 FILES\GNUWIN32\LIB
C:\PROGRAM FILES\SILICON GRAPHICS\OPENGL=20 VOLUMIZER\LIB

and I have also set the path to the dlls in = volumizer and=20 libtiff library
C:\Program Files\Silicon Graphics\OpenGL = Volumizer\bin\=20
C:\Program Files\GnuWin32\bin

But when I the run the = compiled=20 program ( Runme.bat ), the program crashes. On exploring I found that=20
IFLLoader *loader =3D IFLLoader::open("fileName");
is returning = NULL, and=20 hence exit(0) is being called after that, terminating the program.=20
Somehow, the IFLLoader ( or TIFFLoader ) is not able to read the=20 dataset

How do I solve this ? Am I  doing something wrong = here,=20 missing out something,
or is there a problem with the libtiff = installation=20 , or with iflloader ?

I would like to solve this quickly, = & test=20 some more applications before deciding whether to buy the permanent=20 license.

Thanks in=20 advance.

regards
Kiran

------=_NextPart_000_010C_01C64971.2A531D60-- From info-volumizer-owner@els.sgi.com Thu Mar 16 13:50:10 2006 Received: (from majordom@localhost) by els.sgi.com (8.12.10/8.12.2/els-2.2) id k2GLmxul1896533; Thu, 16 Mar 2006 13:48:59 -0800 (PST) Received: from theremin.irus.robarts.ca (theremin.irus.robarts.ca [198.20.40.10]) by els.sgi.com (8.12.10/8.12.2/els-2.2) with ESMTP id k2DFZux31826548 for ; Mon, 13 Mar 2006 07:35:56 -0800 (PST) Received: from [198.20.40.102] (be.irus.robarts.ca [198.20.40.102]) by theremin.irus.robarts.ca (8.12.10/8.12.10) with ESMTP id k2DFZsZI006088; Mon, 13 Mar 2006 10:35:55 -0500 (EST) Message-ID: <441591F8.7020207@imaging.robarts.ca> Date: Mon, 13 Mar 2006 10:38:32 -0500 From: Kevin Wang User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040805 Netscape/7.2 X-Accept-Language: en-us, en, zh-cn MIME-Version: 1.0 To: info-volumizer@els.sgi.com, praveenb@sgi.com Subject: [info-volumizer] 3D cliptexture Content-Type: multipart/mixed; boundary="------------000406040909010800060603" Sender: owner-info-volumizer@els.sgi.com Precedence: bulk Reply-To: info-volumizer@els.sgi.com This is a multi-part message in MIME format. --------------000406040909010800060603 Content-Type: multipart/alternative; boundary="------------050305050106080304090400" --------------050305050106080304090400 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi Praveen, I tried to use 3D cliptexture in our demo. attached is the volumizer debug log. The problem is the everything seems to be working except that I cannot see anything on the screen. I wonder if it has anything to do with image size since it is not power of 2. I hope you can find something strange in the debug log. Look forward to your reply. -- Kevin --------------050305050106080304090400 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit
Hi Praveen,

I tried to use 3D cliptexture in our demo. attached is the volumizer debug log. The problem is the everything seems to be working except that I cannot see anything on the screen. I wonder if it has anything to do with image size since it is not power of 2. I hope you can find something strange in the debug log. Look forward to your reply.

-- Kevin
--------------050305050106080304090400-- --------------000406040909010800060603 Content-Type: text/plain; name="demolog.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="demolog.txt" [kwang@be volumizerdemogcc323]$ ./AtamaiVolumizerDemo Initializing debug Level to: 5 Volumizer (3): ================================================ Volumizer (3): Checking for 'volumizer_linux' license Volumizer (0): ================================================ Volumizer (0): = OpenGL Volumizer 2.9 = Volumizer (0): = DEMO EDITION = Volumizer (0): ================================================ Volumizer (0): = For information about purchasing the full = Volumizer (0): = OpenGL Volumizer product, visit = Volumizer (0): = http://www.sgi.com/software/volumizer/ = Volumizer (0): ================================================ Volumizer (0): = Demo License Expiration in 52 days = Volumizer (0): ================================================ Volumizer (4): Object 85c33c8 ref() -> Ref count = 2 Volumizer (4): Object 85c33c8 unref() -> Ref count = 1 Volumizer (4): Object 85c34f0 ref() -> Ref count = 2 Volumizer (4): Object 85c3440 ref() -> Ref count = 2 Volumizer (4): Object 85c34f0 unref() -> Ref count = 1 Volumizer (4): Object 85c3440 unref() -> Ref count = 1 Volumizer (5): Client attribute stack maximum depth = 16 Volumizer (4): Vendor string = NVIDIA Corporation Volumizer (4): Renderer string = GeForce 6600 GT/AGP/SSE2 Volumizer (2): NVIDIA GeForce graphics Volumizer (5): vzPlatformInfo::vzPlatformInfo(): ARBImaging = yes Volumizer (5): vzPlatformInfo::vzPlatformInfo(): ARBFragmentProgram = yes Volumizer (5): vzPlatformInfo::vzPlatformInfo(): ARBVertexProgram = yes Volumizer (5): vzPlatformInfo::vzPlatformInfo(): ARBFragmentShader = yes Volumizer (5): vzPlatformInfo::vzPlatformInfo(): ARBVertexShader = yes Volumizer (5): vzPlatformInfo::vzPlatformInfo(): ATIFragmentShader = no Volumizer (5): vzPlatformInfo::vzPlatformInfo(): SGITextureColorTable = no Volumizer (5): vzPlatformInfo::vzPlatformInfo(): SGIColorMatrix = no Volumizer (3): ARBFragmentProgram::init(): GL_ARB_fragment_program supported Volumizer (3): ARBFragmentShader::init(): GL_ARB_fragment_shader supported Volumizer (2): ClipRenderImplementation::ClipRenderImplementation(): Assuming available texture memory to be 115 MB Volumizer (3): vzClipRenderAction::setLODThreshold: Setting the threshold value to be 1.000000 Volumizer (1): Data dimensions = 181, 217, 181 Volumizer (1): Texture type changed to VZ_UNSIGNED_SHORT Volumizer (1): Number of Components = 1 Volumizer (3): vzParameterClipTexture::setBrickDimensions(): Texture brick dimensions = (181, 217, 181) Volumizer (2): ParameterClipTextureImpl::setPhysicalMemorySize: Physical Memory Size = 67108864 bytes Volumizer (4): Object 86f0c70 ref() -> Ref count = 2 Volumizer (4): Object 86f0c70 unref() -> Ref count = 1 Volumizer (2): ParameterClipTextureImpl::setGeometryROI: Geometry ROI = (0.000000, 0.000000, 0.000000) - (181.000000, 217.000000, 181.000000) Volumizer (0): ClipRenderInterface: Scaling geometryROI to (181.000000, 217.000000, 181.000000) Volumizer (0): NumberOfLevels is 1 Volumizer (3): vzParameterClipTexture::setDataLoaderCB(): Data loader CB = 40639bf8, User data = 8738ba8 range:0 65535 Volumizer (4): Object 86f0e40 ref() -> Ref count = 2 Volumizer (4): Object 86f0e40 unref() -> Ref count = 1 Volumizer (3): vzClipRenderAction::manage : Number of shapes currently managed = 1 Volumizer (3): ParameterClipTextureImpl::initClipTextures(): Number of clip-textures in shape 85c35c0 is 1 Volumizer (2): vzParameterClipTexture: Original volume dimensions = (181, 217, 181) Volumizer (2): vzParameterClipTexture: Texture brick size = (181, 217, 181) Volumizer (2): vzParameterClipTexture: Num of leaves = (1, 1, 1) Volumizer (2): vzParameterClipTexture: Num of levels = 1 Volumizer (2): vzParameterClipTexture: Number of threads not set. Using 1 loader threads Volumizer (3): Level 0: Bricked Volume dimensions = (181, 217, 181) Volumizer (3): Level 0: Texture brick dimensions = (181, 217, 181) Volumizer (3): Level 0: Total number of texture bricks = (1, 1, 1) Volumizer (3): ParameterClipTextureImpl::createTreeLevels(): Total physical memory = 67108864 bytes, Phys brick size = 14218274 bytes Volumizer (3): ClipLevel 0, Number of physical bricks = 5, computed dims = (2, 2, 2), actual bricks = 8 Volumizer (3): ClipLevel 0, Memory remaining = 67108864, Suggested number of physical bricks = 8, dims = (2, 2, 2) Volumizer (3): ClipLevel 0: Physical window size = 14218274, Actual number of bricks = (1, 1, 1) Volumizer (3): Initializing level 0 Volumizer (4): Object 85c33c8 ref() -> Ref count = 2 Volumizer (4): Object 86f0e40 ref() -> Ref count = 2 Volumizer (4): Object 86f0e40 ref() -> Ref count = 3 Volumizer (4): Object 86f0e40 ref() -> Ref count = 4 Volumizer (4): Object 86f0e40 unref() -> Ref count = 3 Volumizer (4): Object 86f0e40 unref() -> Ref count = 2 Volumizer (2): ClipLevel::initialize(): Original appearance has 2 parameters. Clip-level appearance has 1 parameters Volumizer (4): Object 85c34f0 ref() -> Ref count = 2 Volumizer (4): Object 873dea0 ref() -> Ref count = 2 Volumizer (4): Object 873dea0 unref() -> Ref count = 1 Volumizer (2): ClipLevel 0: Data Dimensions = (181, 217, 181) Volumizer (2): ClipLevel 0: Geometry ROI = (0.000000, 0.000000, 0.000000) - (181.000000, 217.000000, 181.000000) Volumizer (2): Level 0: Total number of physical memory bricks = (1, 1, 1) Volumizer (2): Level 0: Number of physical bricks in the window = (1, 1, 1) Volumizer (2): Level 0: Total physical memory window size is approximately 14218274 bytes Volumizer (3): BrickedVolume::setCurrentWindow: Load queue not set for level 0 yet! Volumizer (2): ParameterClipTextureImpl::createTreeLevels(): Number of levels = 1, Allowed memory size = 67108864, Actual maximum = 14218274 Volumizer (2): Creating LoadQueue for 1 levels Volumizer (2): Creating 1 loader threads Volumizer (3): ClipLevel #0: Physical window size = (1, 1, 1) bricks Volumizer (3): LoadQueue:: Elements on load queue = 1 Volumizer (4): Object 85c35c0 ref() -> Ref count = 2 Volumizer (4): Object 85c3440 ref() -> Ref count = 2 Volumizer (4): Object 86f0e40 ref() -> Ref count = 3 Volumizer (4): Object 85c33c8 ref() -> Ref count = 3 Volumizer (3): ClipShapeManager::beginDraw():Number of shapes currently managed = 1 Volumizer (2): Physical Brick (0, 0, 0) not in main memory, loading... Volumizer (2): loadNow()::Given brick 86f27a8 not scheduled for read. New index (0, 0, 0), this = 86ef240 Volumizer (0): Extents are: 0, 180, 0, 216, 0 ,180 Volumizer (0): Level is: 0 filename:/data/kwang/tmp/sbrain.mhd extent:018002160180 Volumizer (5): loadBrick took 1126 ms, Rate = 12.62 MB/sec Volumizer (1): loadNow()::Phys bricks in mem = 1, returning Volumizer (4): Object 82543e0 ref() -> Ref count = 2 Volumizer (5): Pixelstore settings: SKIP_PIXELS: 0, SKIP_ROWS: 0, SKIP_IMAGES: 0, ROW_LENGTH: 181, IMAGE_HEIGHT: 217 Volumizer (5): glTexImage3D called for (181 x 217 x 181) texture (loading into (256 x 256 x 256) texture), data ptr = 0, ID = 4 Volumizer (5): glTexSubImage3D called for (181 x 217 x 181) texture (loading into (256 x 256 x 256) texture). ID = 4 Volumizer (5): vzTMRenderAction: Total texture memory consumed: 33554432 Volumizer (2): ClipRenderImplementation:: Total texture memory used = 32 MB, Download = 32, Render = 32 Volumizer (3): ClipShapeManager::draw():Drawing shape 85c35c0 Volumizer (5): TMInternalGPUShaderImpl::initShader(): Generated fragment shader 1 Volumizer (5): This works fine after binding the shader Volumizer (4): Object 85c34f0 ref() -> Ref count = 3 Volumizer (4): Object 825f720 ref() -> Ref count = 2 Volumizer (4): Object 825f6a0 ref() -> Ref count = 2 Volumizer (4): Object 825f6a0 unref() -> Ref count = 1 Volumizer (4): Object 825f720 unref() -> Ref count = 1 Volumizer (3): Computing adjacency list... Volumizer (3): ClipShapeManager::beginDraw():Number of shapes currently managed = 1 Volumizer (5): vzTMRenderAction: Total texture memory consumed: 33554432 Volumizer (2): ClipRenderImplementation:: Total texture memory used = 32 MB, Download = 0, Render = 32 Volumizer (3): ClipShapeManager::draw():Drawing shape 85c35c0 Volumizer (3): ClipShapeManager::beginDraw():Number of shapes currently managed = 1 Volumizer (5): vzTMRenderAction: Total texture memory consumed: 33554432 Volumizer (2): ClipRenderImplementation:: Total texture memory used = 32 MB, Download = 0, Render = 32 Volumizer (3): ClipShapeManager::draw():Drawing shape 85c35c0 --------------000406040909010800060603-- From info-volumizer-owner@els.sgi.com Thu Mar 16 13:56:15 2006 Received: (from majordom@localhost) by els.sgi.com (8.12.10/8.12.2/els-2.2) id k2GLu0XX988806; Thu, 16 Mar 2006 13:56:00 -0800 (PST) Received: from gobbles.engr.sgi.com (gobbles.engr.sgi.com [192.102.97.44]) by els.sgi.com (8.12.10/8.12.2/els-2.2) with ESMTP id k2GLtVx31866901 for ; Thu, 16 Mar 2006 13:55:32 -0800 (PST) Received: from PRAVEEN (mtv-vpn-sw-corp-0-143.corp.sgi.com [134.15.0.143]) by gobbles.engr.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id k2GLtV2v241264 for ; Thu, 16 Mar 2006 13:55:31 -0800 (PST) From: "Praveen Bhaniramka" To: Subject: RE: [info-volumizer] Rendering very slow on XP Pro SP2 using Quadro FX 500 AGP Date: Fri, 17 Mar 2006 03:25:33 +0530 Message-ID: <011801c64944$5cb5f430$8f000f86@PRAVEEN> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2096 In-Reply-To: <20060307082641.41604.qmail@web60920.mail.yahoo.com> Importance: Normal Sender: owner-info-volumizer@els.sgi.com Precedence: bulk Reply-To: info-volumizer@els.sgi.com Hi Michael, This does seem to be a strange issue. I am pretty sure that I have not run into this issue before. As you indicate, it could be an environment related issue. Are you sure that the application is using the correct DLLs in each case, including the OpenGL DLLs? From your explanation, it sounds like the application is using a software rendering path when you run it outside the VC++ IDE. I am not sure what could prompt that though... Can you try building the other Volumizer sample applications installed under VZROOT/src/apps/simple/ directory and running them? E.g. if you run the simple/pguide application from a console, setting VOLUMIZER_DEBUG_LEVEL to 5 should provide you with the debug messages from Volumizer. That should tell you whether you are using accelerated GL rendering or not. Hth, Praveen > -----Original Message----- > From: owner-info-volumizer@els.sgi.com > [mailto:owner-info-volumizer@els.sgi.com] On Behalf Of Michael Wiley > Sent: Tuesday, March 07, 2006 1:57 PM > To: info-volumizer@els.sgi.com > Subject: [info-volumizer] Rendering very slow on XP Pro SP2 > using Quadro FX 500 AGP > > > Hi, > > I am experiencing a strange problem with Volumizer. > I'll try to explain it as clearly as possible. First > of all, my system configuration is as follows: > Hardware Platform: Intel Pentium III dual processor > system 927 MHz w/ 1.00 GB RAM > Graphics Port: AGP 4X > Graphics Card: Quadro Fx 500 with 128 MB RAM for AGP > Operating System: Microsoft Windows XP Professional > 2002 with Service Pack 2 > Volumizer Version: 2.7 > > Problem Description: > I have written a Volume Rendering application to > render a medical imaging dataset using volumizer. The > data size is approximately 13.1 MB. I am using Visual > Studio .NET 2003 IDE. The language used to write the > application is unmanaged C++. If I launch the application > from within the IDE (using the F5 key or the Debug->Start New > Instance menu option) it runs fine and the interactive > rotation of the rendered volume yields a near real-time frame rate. > > However, when I launch the application by double > clicking on it or from a command prompt it makes my > system unusable and very slow. Furthermore, I don't > see the rendered data on the screen. In the meantime, > the cpu is continuously utilized by the application's > process. I have to kill this process from the task > manager in order to gain usability of my system. > > In order to isolate the issue I tried running SGI's > XMLViewer demo app which ships with Volumizer. I > started the app by double clicking on it and opened > the binary.vz file (bonsai tree dataset). After the > dataset finished renderig on the screen I tried to > interactively rotate it. However, this caused my system to > slow down and I noticed in the task manager that one of the > CPU's was continuously being used by the XMLViewer.exe > process. After about a minute the screen finished the rotate > request and rendered the rotated bonsai tree. But, obviously > something is wrong here as the response is unusually very slow. > > Now, to experiment further, I added the XMLViewer.exe > file to a Visual Studio solution so that I could > launch it from within the IDE. I used the Debug->Start > New Instance menu option to launch XMLViewer app. I > opened the same binary.vz dataset and now I could > interactively rotate the rendered dataset with almost > realtime response. > > Can anyone point out what the problem could be? It > seems to be some enviroment related issue as the both > the XMLViewer and my application seem to work OK if > launched from within the IDE but these same > applications fail miserably when run outside the IDE. > I doubt if it is the card that has the problem. If > there was something wrong with the card the > application would have failed when launched from > within the IDE. I also have checked that I have the > latest drivers from NVIDIA. > > Have the folks at SGI run across this issue? It should > be very easy to recreate as the sample XMLViewer app > supplied with Volumizer fails. > > Let me know. > > Thanks, > Michael Wiley. > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > From info-volumizer-owner@els.sgi.com Fri Mar 17 07:57:40 2006 Received: (from majordom@localhost) by els.sgi.com (8.12.10/8.12.2/els-2.2) id k2HFuR6O1930912; Fri, 17 Mar 2006 07:56:27 -0800 (PST) Received: from gobbles.engr.sgi.com (gobbles.engr.sgi.com [192.102.97.44]) by els.sgi.com (8.12.10/8.12.2/els-2.2) with ESMTP id k2GM8Hx31925443 for ; Thu, 16 Mar 2006 14:08:17 -0800 (PST) Received: from PRAVEEN (mtv-vpn-sw-corp-0-143.corp.sgi.com [134.15.0.143]) by gobbles.engr.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id k2GM8G2v241387 for ; Thu, 16 Mar 2006 14:08:16 -0800 (PST) From: "Praveen Bhaniramka" To: Subject: RE: [info-volumizer] 3D cliptexture Date: Fri, 17 Mar 2006 03:38:18 +0530 Message-ID: <018901c64946$24e0abc0$8f000f86@PRAVEEN> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_018A_01C64974.3E98E7C0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2096 In-Reply-To: <441591F8.7020207@imaging.robarts.ca> Importance: Normal Sender: owner-info-volumizer@els.sgi.com Precedence: bulk Reply-To: info-volumizer@els.sgi.com This is a multi-part message in MIME format. ------=_NextPart_000_018A_01C64974.3E98E7C0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi Kevin, Everything looks fine from the debug messages. You only have 1 clip-resolution in the data set and the only brick at that resolution seems to be rendered by Volumizer. Things to check - - How are you building clip-texture heirarchy in this case? - Do the sample applications, e.g. volview with libvolviewClip.so module work? I assume that you are using your own loader code to create the clip-texture. Is your loader callback being invoked correctly and are you loading the correct volume data in the callback? - Praveen -----Original Message----- From: owner-info-volumizer@els.sgi.com [mailto:owner-info-volumizer@els.sgi.com] On Behalf Of Kevin Wang Sent: Monday, March 13, 2006 9:09 PM To: info-volumizer@els.sgi.com; praveenb@sgi.com Subject: [info-volumizer] 3D cliptexture Hi Praveen, I tried to use 3D cliptexture in our demo. attached is the volumizer debug log. The problem is the everything seems to be working except that I cannot see anything on the screen. I wonder if it has anything to do with image size since it is not power of 2. I hope you can find something strange in the debug log. Look forward to your reply. -- Kevin ------=_NextPart_000_018A_01C64974.3E98E7C0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
Hi=20 Kevin,
 
Everything looks=20 fine from the debug messages. You only have 1 clip-resolution in the = data set=20 and the only brick at that resolution seems to be rendered by Volumizer. = Things=20 to check -
 
- How = are you=20 building clip-texture heirarchy in this case?
- Do = the sample=20 applications, e.g. volview with libvolviewClip.so module work?=20
 
I = assume that you=20 are using your own loader code to create the clip-texture. Is your = loader=20 callback being invoked correctly and are you loading the correct volume = data in=20 the callback?
 
-=20 Praveen
-----Original Message-----
From:=20 owner-info-volumizer@els.sgi.com = [mailto:owner-info-volumizer@els.sgi.com]=20 On Behalf Of Kevin Wang
Sent: Monday, March 13, 2006 = 9:09=20 PM
To: info-volumizer@els.sgi.com;=20 praveenb@sgi.com
Subject: [info-volumizer] 3D=20 cliptexture

Hi Praveen,

I tried to use 3D = cliptexture=20 in our demo. attached is the volumizer debug log. The problem is the=20 everything seems to be working except that I cannot see anything on = the=20 screen. I wonder if it has anything to do with image size since it is = not=20 power of 2. I hope you can find something strange in the debug log. = Look=20 forward to your reply.

--=20 Kevin
------=_NextPart_000_018A_01C64974.3E98E7C0--