You are viewing an archive of the old fxhome.com forums. The community has since moved to hitfilm.com.

PK4 - Camera 'BUSY'

Posted: Fri, 4th Mar 2011, 2:34pm

Post 1 of 3

NPTImaging

Force: 1400 | Joined: 22nd May 2008 | Posts: 2

PhotoKey 4 Pro User

Gold Member

So shot an event last night, have used PK4 many, many times but ran into an issue last night.

Win XP, Canon 20D - tethered, Sony DP150, PK4

Canon remote shooting utility, DPP and PK4 were the only programs running.

I was shooting, Tech was running PK4, exporting a JPEG of the flattened file and printing straight from PK4. Randomly the 20D would show busy on the camera's top LCD and stay busy, I left it for a couple of minutes and it was still busy. Had to turn off camera and drop out the camera battery to hard reboot the camera to get it functional again. This also caused two or three photos to not show up in the destination folder on the PC. This would randomly happen again.

I have run this same combination many times without any issues in the past, the only variation was that we had not exported in the past. Had the Tech stop exporting and all ran fine the rest of the event.

The PC is a dual-core machine, nothing special, don't want to drag and bang around other higher powered machines to event after event. I think this machine may only have 1G RAM. So I guess I need to test this scenario with a higher end machine and see if it is a PC issue or what.

Anyone else ever ran into something like this?
Posted: Tue, 22nd Mar 2011, 7:13pm

Post 2 of 3

NPTImaging

Force: 1400 | Joined: 22nd May 2008 | Posts: 2

PhotoKey 4 Pro User

Gold Member

No one to help?
Posted: Tue, 22nd Mar 2011, 10:48pm

Post 3 of 3

Axeman

Force: 17995 | Joined: 20th Jan 2002 | Posts: 6124

VisionLab User VideoWrap User PhotoKey 5 Pro User MuzzlePlug User PowerPlug User PhotoKey 3 Plug-in User FXhome Movie Maker FXpreset Maker MacOS User

SuperUser

Sorry man, I've never seen anything like that, and don't have the time at present to try setting up for shooting tethered and try replicate it. Have you submitted a support ticket on this issue?