Jump to content

Welcome!

Sign In or Register to gain full access to our forums.

Photo

Problems processing PTM vs HSH?


  • Please log in to reply
23 replies to this topic

#1 Ansley

Ansley

    Advanced Member

  • Members
  • 30 posts
  • LocationLos Angeles, CA

Posted 20 March 2014 - 09:37 PM

Has anyone had trouble processing a PTM when an HSH would work? 

 

Our latest batches of rock art photos will not process as PTM's, but when I use the HSH method, it does work.

 

As a test, to make sure I had all the former software issues cleaned up, I re-processed (as a new project) an old photo set that had worked in the past, and it processed as a PTM again with no problem. 

 

I am stumped. 

 

Thanks for any ideas.

 

Ansley


  • Howardbaf likes this

#2 Carla Schroer

Carla Schroer

    Advanced Member

  • Administrators
  • 366 posts
  • LocationSan Francisco, CA

Posted 20 March 2014 - 10:04 PM

Ansley -  I moved this topic over to the processing forum, since it is a processing question (you originally posted it inthe highlight capture forum)

 

I have seen cases where ptm worked, but not HSH, usually due to a permissions problem with HSH needing to write to a cache file.  Hmm, never seen this go the other way.  Can you upload your project .xml file?  There is usually more information in there about what is going on that can help us trouble shoot.

 

Carla



#3 Ansley

Ansley

    Advanced Member

  • Members
  • 30 posts
  • LocationLos Angeles, CA

Posted 20 March 2014 - 10:19 PM

XML of the batch that processed as an HSH, but would not process as a PTM attached.

 

Thanks!

Ansley

Attached Files



#4 Ansley

Ansley

    Advanced Member

  • Members
  • 30 posts
  • LocationLos Angeles, CA

Posted 21 March 2014 - 12:05 AM

I am attaching the XML of the failed PTM. The HSH worked and I attempted the PTM again as a new project. I will try re-processing the HSH as a PTM next week.

 

Thank you,

Ansley

Attached Files



#5 Ansley

Ansley

    Advanced Member

  • Members
  • 30 posts
  • LocationLos Angeles, CA

Posted 03 April 2014 - 03:45 PM

I have tried reprocessing an HSH as a PTM and still get the dreaded "Unknown error detected" message box.

 

I tried processing another old batch of photos as a new PTM project again too and it worked fine.



#6 Ansley

Ansley

    Advanced Member

  • Members
  • 30 posts
  • LocationLos Angeles, CA

Posted 07 April 2014 - 04:46 PM

I should also probably mention that I am unable to open the RTIBuilder application. I can only run the RTIBuilder[Console].



#7 John Anderson

John Anderson

    Advanced Member

  • Members
  • 34 posts
  • LocationNext to the Pond, Sligo, Ireland.

Posted 07 April 2014 - 07:02 PM

Hi everyone. I'm just ending a few months' sabbatical. I don't really want to go back to work, but someone has to pay for my beer.

 

I'm intrigued by Ansley's processing problem.

 

I read the XML file she posted, and her images appear to be tagged .JPG, e.g  jpeg-exports\CA-LAN-374_p1_spJ_e21-12.JPG.

 

We had a similar problem some months ago, finding that the software recognized only lower case tags (.ie .jpg) and not upper case (i.e .JPG).

 

I note she wrote " I re-processed (as a new project) an old photo set that had worked in the past, and it processed as a PTM again with no problem. "

 

Is she perhaps using a new camera, or another RAW-to-jpeg conversion program?

 

 

I'll be posting soon details of how the local fairies (common in Ireland) crashed my colleague's bicycle (with him on it) into a ditch, and how this minor catastrophe resulted in the construction of an inexpensive but accurate RTI light positioning system....

 

Beer beckons!

 

Good night.

 

John Anderson


  • Ansley likes this

#8 Ansley

Ansley

    Advanced Member

  • Members
  • 30 posts
  • LocationLos Angeles, CA

Posted 07 April 2014 - 07:13 PM

John,

 

Excellent insight. I changed computers and the OS in the middle of the project. Our old files are indeed .jpg and the new files are .JPG. The next hurdle is figuring out if I can change .JPG to .jpg.

 

I have only been using the j-pegs and have not been doing any conversions.

 

Thank you and cheers!

Ansley



#9 John Anderson

John Anderson

    Advanced Member

  • Members
  • 34 posts
  • LocationNext to the Pond, Sligo, Ireland.

Posted 07 April 2014 - 07:58 PM

Ansley, go to

 

http://www.den4b.com...product=renamer

 

ReNamer renames file tags. Download the (free) installer version from the page above. Just install and run. You specify the change you want (in this case change JPG to jpg). You can select individual files to change, or batch run a number of files in a folder.

 

We use it to convert from Adobe's .JPG to .jpg. It's easy to use. If you have any problems, please PM me!

 

John.


  • Ansley likes this

#10 Carla Schroer

Carla Schroer

    Advanced Member

  • Administrators
  • 366 posts
  • LocationSan Francisco, CA

Posted 11 April 2014 - 05:52 PM

John, 

 

Good catch!!  I didn't see that.  

 

I'll note that this issue is a limitation of the ptmfitter from HP, and therefore not something we can fix.  In the new RTIBuilder we will detect this issue and issue a more useful error messsage.

 

This is also discussed in this thread:

 

http://forums.cultur...enamer#entry539


  • Ansley likes this

#11 John Anderson

John Anderson

    Advanced Member

  • Members
  • 34 posts
  • LocationNext to the Pond, Sligo, Ireland.

Posted 11 April 2014 - 06:18 PM

Hi Carla,

 

Greetings from the Emerald Isle! Well, I'm back at work just one week and already well into my supply of Prozac and Valium, washed down with an endless supply of office coffee!

 

The .jpg v. .JPG problem has caught out quite a few users; an error message would be great, and I hope my recent post clarifies the matter.

 

While I was away, Mike our chemist managed to drive his bicycle (although he insists a leprechaun pushed him) into a ditch. A damaged front wheel gave me an idea for a low cost, simple, but precision light array for RTI. Construction is within anyone's capabilities. More details soon.

 

With best wishes,

 

John.

 

 

PS Expect a few $$$ donation soon.



#12 kathrynpiquette

kathrynpiquette

    Advanced Member

  • Members
  • 22 posts

Posted 28 June 2014 - 02:03 PM

Hi Carla and all,

 

@Carla: Above (20 March 2014) you mention: "...usually due to a permissions problem with HSH needing to write to a cache file". Are there details anywhere on the Forum about how to address this problem. I searched around but did not see anything. I am having a problem with RTIBuilder on my new Mac. (Granted I was a PC user for years, so still getting up to speed on Mac and might be overlooking something basic?)

 

Machine:

MacBook Pro Retina, OS X 10.9.2 (13C64)

 

Symptoms:

1. PTMs fit fine

2. HSH/*.rti  fit with no error messages. The resultant *.rti file is c.400 KB?! It should be over 200MB based on the same data being fitted on my old PC. The Mac-processed smaller file, of course, will not open in RTIViewer.

 

Tests:

1. Stab in dark: Changed the permission from "read only" to "read and write" in my library for the cache file folder "everyone" and "wheel". The "system" already had these permissions. This had no effect on the fitting.

2. Tried fitting when the folder was in my normal directory structure, ensuring no spaces in file names

3. Tried fitting with the folder on the desktop

4. Copied the HSH fitter to another location so I could be sure the Builder "knew" where to find it -- in case the built in path/location was faulty

5. Finally, I made sure OS was up to date and restarted computer. Still no joy: fitting appeared to happen normally without errors but file was again ridiculously small and useless.

 

I am stumped and after scanning the xml file it is not clear to me what the problem might be. I attach the xml file from my most recent attempt. I am grateful for any advice on how to solve this problem!

 

Best wishes - Kathryn

Attached Files



#13 Carla Schroer

Carla Schroer

    Advanced Member

  • Administrators
  • 366 posts
  • LocationSan Francisco, CA

Posted 30 June 2014 - 05:18 PM

Kathryn -

 

Thanks for the details.  I have never seen or heard of this problem occurring on a mac.  As you noted there have been instances on PCs.  I can say that we have one machine running Mac OS 10.9 (Mavericks) and the hshfitter is working, so it doesn't appear to be a general problem with Mavericks.  Also, the fact that the hshfitter is running and is producing a file (even though it isn't a correct one) rules out some issues like spaces in pathnames.

 

Also, just to be clear about the permissions issue, it isn't a question of whether the user has permission to execute the hshfitter (since the program is clearly running) it is a question of whether the user has permission to write to the temporary Cache file - which is a file created within the RTiBuilder app directory structure.  One thing you could check is whether your user login has administrative privileges.  I know there have been a number of changes in the default security settings with Mavericks, and while I don't know that that is related to what you are seeing, it seems worth trying a few experiments.

 

Carla



#14 kathrynpiquette

kathrynpiquette

    Advanced Member

  • Members
  • 22 posts

Posted 05 July 2014 - 11:42 AM

Hi Carla,

 

Thanks for this feedback. I can confirm that I have administrator privileges. I have not been able to figure out how to check that the Cache file aspect is happening properly. Is there anything I should look into? I am getting pretty desperate to fit my growing pile of RTI data that needs to be done using HSH (the PTM fitting is working just fine).

 

Is anyone out there using Mac OS 10.9.4 and successfully producing *.rti files?

 

Many thanks - Kathryn



#15 Taylor Bennett

Taylor Bennett

    Advanced Member

  • Members
  • 134 posts

Posted 05 July 2014 - 09:43 PM

Kathryn, I'm using OS 10.9.4 and I didn't run into any problems processing both .rti and .ptm files.  I'm sorry I can't think of much to suggest, except running the disk utility to repair permissions.  Sorry to hear you're having this trouble; it can be very frustrating.  I could also offer to process some files for you if you're in a crunch.



#16 kathrynpiquette

kathrynpiquette

    Advanced Member

  • Members
  • 22 posts

Posted 11 July 2014 - 05:37 PM

Thanks for your reply Taylor, and for your generous offer to process data for me. I am happy to report that the problem is now fixed and I am able to get these exciting IR RTI images of the Herculaneum papyri into the hands of eager  papyrologists!

 

So -- as a new Mac user as of a few weeks ago, the first time I installed RTIBuilder I think I must have run it from the desktop and at that point also dragged the icon onto the dock. I did not appreciate that I had to drag the dmg file into the applications folder first. I soon corrected the location of the dmg file but failed to update the icon on the dock (or rather assumed it had happened automatically since, after I had deleted the incorrectly located dmg file and downloaded a fresh copy for correct installation, I was able to click happily on the dock icon and successfully fit PTMs. As mentioned previously, I could seemingly fit using HSH, but the file turned out to be "empty" (about 40kb in size). It is curious that I received no error and the xml shows a successful HSH fit.

 

Thanks to the xml file you sent me for comparison, I was able to spot the problem, highlighted below. Only then did I realise that the dock icon was not launching the software from the correct location (i.e. the Application folder). Here are the key differences to look out for in the xml toward the end of the process:

 

GOOD: LEVEL="Information" USER="">HSHfitter Path found : /Applications/RTIbuilder-v2.0.2.app/Contents/Resources/Java/Fitters/HSHfitter/hshfitter</xc:event>

 

BAD: LEVEL="Information" USER="">HSHfitter Path found : /Volumes/RTIbuilder 2.0.2 beta/RTIbuilder-v2.0.2.app/Contents/Resources/Java/Fitters/HSHfitter/hshfitter</xc:event>

 

In addition to making sure there are no spaces in the file path, one must also make sure that RTIBuilder is in /Applications and not /Volumes. In the latter case, another clue that something is wrong is the presence of /RTIbuilder 2.0.2 beta.



#17 EBF

EBF

    Newbie

  • Members
  • Pip
  • 3 posts

Posted 16 July 2014 - 11:09 AM

Hi Carla and All,

 

Carla, you mentioned on 20 March 2014 that sometimes the HSH fitter won't work where the PTM fitter will "due to a permissions problem with HSH needing to write to a cache file." I think I may be having this problem but if so, don't know how to fix it.

 

I am not able to build RTIs using the HSH fitter on my new computer (a Macbook Pro Retina with OS X 10.9.4). The PTM fitter is working completely fine. When I try to build an RTI using the HSH fitter, everything works perfectly until the very end of the cropping process, when I receive an error popup that says "Unknown Error Detected!"

 

Any suggestions?

 

Cheers,

Emily



#18 Carla Schroer

Carla Schroer

    Advanced Member

  • Administrators
  • 366 posts
  • LocationSan Francisco, CA

Posted 16 July 2014 - 02:07 PM

Emily,

 

Hmm - when the HSHFitter can't write to the cache (which is in a temp file) it usually doesn't fail with an error, you just get a tiny (like 4kb) file as a result.  The fact that you are getting the "Unknown error" is usually something different. Can you post your project .xml file and that might give a clue.  You can look yourself toward the end of the file and see if there is an error message there.  If there is an issue with publishing that publicly, you can email it to me "info at c-h-i.org" and I'll take a look.  I'm at a conference for the rest of the week, so I won't be able to look at it until tonight.

 

Carla



#19 EBF

EBF

    Newbie

  • Members
  • Pip
  • 3 posts

Posted 20 July 2014 - 10:05 AM

Thanks Carla,

 

I've sent two .xml files to your email to check out.

 

A few examples of the errors from the .xml files are:

error on line 313 at column 19: Failed to parse QName 'xc:xc:

error on line 510 at column 19: Failed to parse QName 'xc:xc:'

error on line 510 at column 19: Failed to parse QName 'xc:xc:'

error on line 507 at column 19: Failed to parse QName 'xc:xc:'

error on line 426 at column 19: Failed to parse QName 'xc:xc:'

 

It is quite interesting actually; I've tried messing around with my file location and the way I process the source images. I have deleted and re-downloaded the software and tried a number of computers. As a result, I was able to get two more RTIs to build with the HSH fitter. However, when I repeat my workflow exactly, it fails to work again. Every time I receive the same unknown error. 

 

Looking forward to your insight!

 

Cheers,

Emily



#20 Carla Schroer

Carla Schroer

    Advanced Member

  • Administrators
  • 366 posts
  • LocationSan Francisco, CA

Posted 20 July 2014 - 10:57 PM

Emily -

 

The problem seems to be the number one issue when processing RTIs which is that you have spaces in your path name.  This should actually fail on both PTM and HSH, so possibly you moved the files between trying to build them with the different fitters?

 

The telling line in the XML file is near the top:

 NAME="ProjectPath" VALUE=".../Desktop/Dissertation/IoA Corner Base"/>

 

Note the spaces in IoA Corner Base

 

The same issue appears in this one: NAME="ProjectPath" VALUE=".../Desktop/Dissertation/IoA Large Tile Impression"/>

 

Please read the description here: http://forums.cultur...in-rti-builder/

 

In the planned update to RTIBuilder we will detect this error and provide a more useful error message. 

 

Carla






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users