Page 1 of 1

Problems with Parallax Corrections. Not remembered or Settab

PostPosted: Wed Sep 25, 2013 4:20 am
by RichyT
Hi, just getting back into the uploading.

I have a couple of pictures which had bad parallax when taken. Not sure why but the W3 seems to get confused with close-ups sometimes. I fixed and stored the parallax. They look great in tridef media player on my LG screen but when I upload to Phereo as MPO, the parallax correction is not remembered and the picture is uncomfortably bad. I deleted the ones that were not good but have left one up as an example (It's on my profile, Richy_T, the 3d printed cicada).

There also appears to be no way to correct the parallax once uploaded. Either way would be fine for me. I just don't want to upload stuff that's painful to view. Is there any way I can fix these?

I'd just like to say thanks for putting back the interlaced viewing option too. Not sure how long ago it went back in but it was good to see it when I logged on.

Re: Problems with Parallax Corrections. Not remembered or Se

PostPosted: Wed Sep 25, 2013 9:49 am
by bulkinav
RichyT wrote:There also appears to be no way to correct the parallax once uploaded. Either way would be fine for me. I just don't want to upload stuff that's painful to view. Is there any way I can fix these?

Phereo image handler can read offset information only if it's correctly stored in the EXIF metadata. Apparently, TriDef application saves such data is not entirely correct. I recommend you use a free Phereoshop to work with the stereo images - http://phereoshop.com/

RichyT wrote:I'd just like to say thanks for putting back the interlaced viewing option too. Not sure how long ago it went back in but it was good to see it when I logged on.

Yes, this mode was presented a long time ago :)

Re: Problems with Parallax Corrections. Not remembered or Se

PostPosted: Mon Jun 16, 2014 3:42 pm
by RichyT
Just to be clear, the parallax was fixed on the camera. I just used the Tridef to verify that the correction could be viewed.

It's possible that the camera is storing the correction incorrectly and Tridef is using it anyway but if this is the case, it's probably a bug that Phereo should embrace.