PhD3: Bug in Zoom Function

OldRadioGuy

Newbie Location: Austin, Texas, USA Joined: Feb 29, 2012 22:38 Messages: 27 Offline

Solved by

Mar 31, 2012 21:13

1. Create a Virtual Image from a RAW file
2. Select that Virtual Image
3. Using either the Zoom dropdown or Ctrl+mouse wheel, from the FIT position zoom in, 50%, 100%, 200%, 300%, etc.
4. At some setting in the zoom, the image in the workspace disappears.
5. Click the spacebar to go back to the Fit position and the image returns to the workspace. Click the spacebar again, and it disappears.

This behavior was not observed when working on the actual RAW image.

Bob PhotoDirector 5; Windows 7 Home Premium 64-bit; 3.40 gigahertz Intel Core i7-3770; 16 GB RAM; AMD Radeon HD 7770; Olympus E-M1 & E-M5

PIX

Senior Contributor Joined: Sep 21, 2011 00:02 Messages: 2910 Offline

Apr 01, 2012 05:49

Hello Bob,

I read your post with interest, because I hadn't encountered the issue here. As is my want, I set off to investigate using RAW files from the following cameras:

☼ Canon 5D MkII (.CR2)
☼ Canon 7D (.CR2)
☼ Casio EX-FH100 (.dng)
☼ Fuji S9600 (.RAF)
☼ Kodak ProBack 645 (.DCR)
☼ Nikon D3X (.NEF)
☼ Nikon D90 (.NEF)
☼ Nikon P6000 (.NRW)
☼ Nokia N95 (.RAW)
☼ Olympus E-3 (.ORF)
☼ Olympus E-620 (.ORF)
☼ Panasonic GH2 (.RW2)
☼ Panasonic LX3 (.RW2)
☼ Samsung NX200 (.SRW)
☼ Sony NEX-C3 (.ARW)

RAW files and vitual copies were tested, using both zoom methods. I wasn't able to replicate your observations. I zoomed through "Fit" - 25%, 33%, 50% 100 - 800%. At no time did any image disappear from the preview screen. The only thing I did notice was a short delay as the zoomed image rendered.

I'm not sure why that would occur with the virtual photos & not the RAW file. It's possibly related to GPU processing, but it would be difficult to call it a "bug" given the above observations.

The PC used for testing is Win7 (64-bit), CPU: Core i7 920 @ 2.67GHz, 8GB RAM, GPU: Nvidia GTX 260

PIX PIX YouTube channel

OldRadioGuy

Newbie Location: Austin, Texas, USA Joined: Feb 29, 2012 22:38 Messages: 27 Offline

Apr 01, 2012 08:27

PIX, after seeing your post this morning, I opened PhD3 again.

However, I cannot replicate the issue now.

I encountered this behavior after running PhD3, a competing product and an external editor for a couple of hours. I was doing a feature and performance comparison.

Since you cannot replicate this behavior either -- using all of those different RAW format files -- I have to believe the observed phenomenon was related to memory/graphics card.

Bob PhotoDirector 5; Windows 7 Home Premium 64-bit; 3.40 gigahertz Intel Core i7-3770; 16 GB RAM; AMD Radeon HD 7770; Olympus E-M1 & E-M5