Harry,
some more information would be helpful on this. What platform are you using, and what’s your computer specs (cpu, OS, RAM, etc.)?
Also how were the TGAs created? Another version of PS? Another application? What OS?
Any more infomation would really help.
thanks,
-Adam
TGAs were created in that very copy of PS8. XP Pro, 2g RAM, P4 3ghz. They’re small (128×128, 64×64, 48×48, 32×32) images, and there are a few thousand, all told, across a couple hundred directories.
Damn. Here we go again – P4 3.0, 2GB RAM, XP pro. Why do these numbers keep coming up when there’s a major problem with CS?
I know, I know, – it’s bad hardware, bad RAM etc. Yada yada.
I’ve held my peace for months now, but CS today steadfastly refused ("not enough RAM") to open a PanoTools Tiff image when ImageReady opened it instantly.
Pourquoi? (To save the obvious responses: 49% RAM allocated, HUGE scratch disk, all updates applied).
Sorry, harry – this helps little with your specific problem, but (directed to Adobe) something overall is really wrong here.
Fred.
Fred,
have you tried using the Adjusted Refresh plug-in to see if that lets you use PanoTools in CS? I’m curious if it’ll help.
Harry,
I’m still trying to reproduce your file browser issue, but so far haven’t been able to. I’m going to try on a machine similar to yours and see if that makes a difference.
-Adam (the PS QE performance "ninja" @ Adobe)
Thanks for looking into it.
Yes, Adam, both the MP plugin and the adjusted refresh plugins are in place.
The problem was not in using PanoTools with PSCS, it was in getting PS to open a TIFF file that PanoTools had created (329MB RGB). PS point blank refused to open it ("not enough RAM") – I restarted (both app & computer), trashed prefs, tried RAM allocation all the way down to 10% with no success.
In desperation I tried to open it in ImageReady and it opened instantly. I’m not keen to heap all the blame on PS, btw, I strongly suspect that XP has a whole lot to do with it, but I wish the connection could be made/publicized (in moronese so the rest of us can understand) with the steps being taken to cure it so that we can all get on with our work. These "not enough RAM" full stops are really annoying.
I’m on my second MoBo (Asus P4P800 Deluxe) and third set of RAM (now 2GB Corsair TwinX PC 3200 DDR, 4x 512MB as dual channel), so have pretty well ruled out faulty hardware – unless Asus is hiding something……….
I’m kinda hoping SP2 for XP may "address" the problem, though I cannot understand why PS baulked when IR didn’t.
Fred.
Fred – that could be related to some of the TIFF writing bugs in PanoTools. You might want to check with the author for updates.
Will do, Chris – but I’m still puzzled as to why PS didn’t & IR did (open the file, that is).
IR has a different TIFF reader than Photoshop.
Chris, What is the reason for this? Anything to do with animation? Can we drag the tiff plug-in into PS for different results?
Regards
Mark
If Fred would be willing to do the experiment and (after backing up the original of course) copy the TIFF plugin from IR into PS, this may be a useful workaround for others with similar issues.
(Aargh…I apologize for continuing the hijacking of this thread. We should move the TIFF discussion elsewhere.)
Mark – no, just the fact that IR and Photoshop started from separate teams.
