Author Topic: Further to Unsupport Format Variants  (Read 3192 times)

Offline psibbald

  • Newcomer
  • *
  • Posts: 9
    • View Profile
Further to Unsupport Format Variants
« on: September 13, 2008, 01:18:11 PM »
Dear Kirk et al,

I'm in the middle of upgrading from PM 4.4.3.3 to a demo version PM 4.5.3.2 running on OSX 4.11 with QT version 7.5. I have a large and ongoing project that I've been working on without much trouble for the past couple of years in the older version but there are things that I want to do using the better more refined editing tools in the newer version that are pushing me rather hard to upgrade .

The older version works fine with all the files, but indicates that more than half are UFV in the newer version of PM.

Files are all PSDs mostly from 16 bit scans, and generally quite large both in terms of file size and dimension though not necessarily so, and in comparison to some of the largest files that are perhaps an order of magnitude larger and will play in the most recent version of PM,  some medium files are seen as UFV.

Note also maximize PSD and PSB file compatibility is set as Always in PS CS3

I've read what you've said elsewhere about QT being a problem, but this does not seem bear out in this case.

For instance I have two files scanned one after another. Both read fine in QT as well as in the older version of PM, but in the newer version the smaller file is designated as UFV where as the larger file shows up fine in PM. Both are about 5500 px across (which is small to medium for this project).

 I'd rather not to be having to switch back and forth between the older and newer versions of PM to do my work since the reason I'm looking at the upgrade is for benefits that I otherwise can't access in the older version.

What can I do about this problem?

-Peter

Offline Kirk Baker

  • Senior Software Engineer
  • Camera Bits Staff
  • Superhero Member
  • *****
  • Posts: 25054
    • View Profile
    • Camera Bits, Inc.
Re: Further to Unsupport Format Variants
« Reply #1 on: September 13, 2008, 04:45:28 PM »
Peter,

I'm in the middle of upgrading from PM 4.4.3.3 to a demo version PM 4.5.3.2 running on OSX 4.11 with QT version 7.5. I have a large and ongoing project that I've been working on without much trouble for the past couple of years in the older version but there are things that I want to do using the better more refined editing tools in the newer version that are pushing me rather hard to upgrade .

The older version works fine with all the files, but indicates that more than half are UFV in the newer version of PM.

Files are all PSDs mostly from 16 bit scans, and generally quite large both in terms of file size and dimension though not necessarily so, and in comparison to some of the largest files that are perhaps an order of magnitude larger and will play in the most recent version of PM,  some medium files are seen as UFV.

Note also maximize PSD and PSB file compatibility is set as Always in PS CS3

I've read what you've said elsewhere about QT being a problem, but this does not seem bear out in this case.

For instance I have two files scanned one after another. Both read fine in QT as well as in the older version of PM, but in the newer version the smaller file is designated as UFV where as the larger file shows up fine in PM. Both are about 5500 px across (which is small to medium for this project).

 I'd rather not to be having to switch back and forth between the older and newer versions of PM to do my work since the reason I'm looking at the upgrade is for benefits that I otherwise can't access in the older version.

What can I do about this problem?

There is nothing you can do about the problem.  You just have been very fortunate that the older version of PM isn't crashing on you because of your large PSD files.  We added code to handle cases where QuickTime would often fail (meaning it would crash) when asked to render large PSD files.  It may be that Apple has finally fixed the crashing problems in the latest versions of QuickTime and the crashing is no longer an issue.

I would appreciate it if you could share a sample image that PM 4.5.3.2 won't load but will load fine into PM 4.4.3.3 with QT 7.5.  Please contact me privately for server upload information.

Thanks,

-Kirk

Offline Kirk Baker

  • Senior Software Engineer
  • Camera Bits Staff
  • Superhero Member
  • *****
  • Posts: 25054
    • View Profile
    • Camera Bits, Inc.
Re: Further to Unsupport Format Variants
« Reply #2 on: September 19, 2008, 01:04:19 PM »
Peter,

I'm in the middle of upgrading from PM 4.4.3.3 to a demo version PM 4.5.3.2 running on OSX 4.11 with QT version 7.5. I have a large and ongoing project that I've been working on without much trouble for the past couple of years in the older version but there are things that I want to do using the better more refined editing tools in the newer version that are pushing me rather hard to upgrade .

The older version works fine with all the files, but indicates that more than half are UFV in the newer version of PM.

Files are all PSDs mostly from 16 bit scans, and generally quite large both in terms of file size and dimension though not necessarily so, and in comparison to some of the largest files that are perhaps an order of magnitude larger and will play in the most recent version of PM,  some medium files are seen as UFV.

Note also maximize PSD and PSB file compatibility is set as Always in PS CS3

I've read what you've said elsewhere about QT being a problem, but this does not seem bear out in this case.

For instance I have two files scanned one after another. Both read fine in QT as well as in the older version of PM, but in the newer version the smaller file is designated as UFV where as the larger file shows up fine in PM. Both are about 5500 px across (which is small to medium for this project).

 I'd rather not to be having to switch back and forth between the older and newer versions of PM to do my work since the reason I'm looking at the upgrade is for benefits that I otherwise can't access in the older version.

What can I do about this problem?

This problem should now be fixed in the 4.5.4 beta version, available in the Announcements section of the forums.

-Kirk