Linux-pkremote new version!

bobD · 03-14-2009, 01:35 AM

I see there is now a deb package for pkremote.(no compile needed- just download extract and install).

SourceForge.net: PK-Remote

Has anyone tried this with a K200D and if so how did it go?.

tkz · 03-14-2009, 03:04 AM

I also have K200D and was going to try the software but there seems to be only deb package i386 for 32 bit systems. That would not install on my 64 bit system. Too bad there was no source code either so it was impossible to try compiling from source too.

Interesting piece of software though. Thanks for the info!

Paul Hunt · 03-14-2009, 03:39 AM

All the goodness is found here: https://sourceforge.net/projects/pkremote/

Paul

*jbinpg* · 03-15-2009, 05:20 PM

Tried the latest pkremote with my Ubuntu Jaunty 9.04 alpha today. Works fine with the only glitch being the udev rules don't seem to be working so I have to run it as root to see the camera. The rules themselves seem fine syntactically so this might be a bug in Jaunty. Otherwise nice and fast and all the tweaks are there.

Jack

JimmyA · 03-30-2009, 10:26 AM

I have a K200D and I'm going to check it out. Recently converted a laptop to Ubuntu Linux and hpe I can connect the camera without problems. Thanks for the link

Ramiro · 04-15-2009, 05:18 AM

Hi, I'm one of the pkremote developers and would love to get some feedback from the users.
jbinpg, have you added your user to the plugdev group?
tkz, the source is in http://pkremote.svn.sourceforge.net/viewvc/pkremote.tar.gz?view=tar

Ramiro

mrcrontab · 04-16-2009, 08:04 AM

I think it's cool that you're doing this! I'm just used to stuff not being available in linux, especially for such a niche like this. I run lightroom half the time in vmware which is achingly slow. I usually have to boot into windows to do any photo stuff, but with this I can do some quick and dirty tether work/tests without rebooting.

I've got a bug to report from my tests, since you're hanging around here

OS: Debian unstable
Camera: K10D
pkremote version: pkremote_0.1.svn20090227-1_i386.deb

When the software started up and connected, I noticed it offered a **** JPEG setting. I thought this was interesting since the K10D only supports ***. I set it to **** to see what would happen, and it crashed:

pkremote: pkremote.c:1667: jpeg_quality_combo_changed_cb: Assertion `val >= 0' failed.
Aborted

So I learned my lesson and restarted it, but it crashed again immediately with the same error.

It crashed on other computers too, immediately, without picking the bad setting. I think it successfully set it in my camera and then had no idea how to read back somehow. The camera still showed *** in the menu.

strace if its worth anything to you: http://kobnet.net/misc/pkremote_strace.txt

I fixed it by selecting *** from the jpeg settings menu on the K10D

It never affected my camera itself in any way, that is just funny how the setting gets stuck in there.

I didn't try setting resolution to 14MP after that!

Anyway thanks for this, it will work great with linux on my laptop dumping pefs to a network share and lr/windows auto-importing them on a desktop as I shoot.

nanok · 04-16-2009, 02:59 PM

Originally Posted by Ramiro

Hi, I'm one of the pkremote developers and would love to get some feedback from the users.
jbinpg, have you added your user to the plugdev group?
tkz, the source is in http://pkremote.svn.sourceforge.net/viewvc/pkremote.tar.gz?view=tar

Ramiro

hi ramiro,

welcome to the forum, and thank you and your colleagues for the great work!

i was about to post asking "what to do next", i started to read the source code instead and while doing so (painful for me, i am no coder

), i realized it uses the scsi_generic subsystem. in short: maybe add a note to the README: try "modprobe sg" if your camera is not "detected".

thanks again, and please let us know if there is anything we can help with/test etc (perhaps people with the samsung versions of the ist series will help test/add those models also, for a start)

now, how do i turn the polarizer from pkremote? :-D

nanok_damn_this_is_cool

nanok · 04-16-2009, 03:17 PM

crontab: when i connect my k20d the settings are 14mp and **** amongst others, it works fine (obviously). perhaps your k10d was recognized as k20d for some reason

my version of pkremote reads "0.5" in the "about" window (it was built from source as i run amd64)

with your camera connected, try the following:
cat /sys/class/scsi_generic/*/device/model

the logic in the source code seems to rely on this to figure out what model of camera it is, this might help figure out if it's the logic for selecting the model connected which is to "blame", or something else (that is, untill ramiro finds a moment to get meaningful info from you

)

Dom · 04-16-2009, 03:42 PM

Sweeeeeeeeeeeeeeeeeeeeeeet.

I didn't know there was one.

Tethered shooting for my Linux box. OK it means switching back to Debian again. Unless it's available for Fedora.

nanok · 04-16-2009, 03:51 PM

you can compile it on fedora if that's what you are using. just make sure you have the dev libs for gtk2 and glade (see the readme), the compilation is extremely simple and lightning fast (at least it was for me).

Dom · 04-16-2009, 04:12 PM

Originally Posted by nanok

you can compile it on fedora if that's what you are using. just make sure you have the dev libs for gtk2 and glade (see the readme), the compilation is extremely simple and lightning fast (at least it was for me).

When I get my new box, in a week or so, I've been thinking about switching back to Dabian again (not ubuntu). As for gtk2 and glade I know I've got both installed at the moment. When my shiny new K20D is in my slight over excited hands I'm going to have a play.

nanok · 04-16-2009, 04:53 PM

no problem, debian is my choice too, but it would be pointless to switch the system just for one application, if the decision was taken prior to that, it makes sense.

mrcrontab · 04-17-2009, 10:15 PM

Originally Posted by nanok

with your camera connected, try the following:
cat /sys/class/scsi_generic/*/device/model

the logic in the source code seems to rely on this to figure out what model of camera it is, this might help figure out if it's the logic for selecting the model connected which is to "blame", or something else (that is, untill ramiro finds a moment to get meaningful info from you )

# cat /sys/class/scsi_generic/*/device/model
ST380815AS
DIGITAL_CAMERA

Haha, not much to go on with DIGITAL_CAMERA

Do you guys get different results there? Could be my semi-screwed debian. I do use my own kernel rather than debian's as well.

/proc/bus/usb/devices and lsusb give correct K10D model identification.

Looks like it is expecting to see "K10D" in place of "DIGITAL_CAMERA" as far as I can tell.

I'll load up a box with default ubuntu in a bit and see what I get on that.

Ramiro · 04-20-2009, 03:54 AM

Hi, thanks for the feedback.
Mr Crontab, thanks for reporting that bug, I can reproduce it on my system, so we'll work on that as soon as we have a little time.
btw, /sys/class/scsi_generic/sg0/device/model = DIGITAL_CAMERA does identify a K10D, provided that
/sys/class/scsi_generic/sg0/device/vendor = PENTAX
(I guess it's sg1 in your system, as you have a scsi drive too).

nanok, I'll add the "modprobe sg" hint to the readme. Actually, I had that problem the first time I tried pkremote

The polarizer turning function still does not work, we're working hard on that

The first version of pkremote was written by Pontus Lidman as a monolithic application, and it worked only with a K10D. After some time Dominik Behr added support for the K20D. My own contribution was re-building the app as a library with all the low level functions and pkremote itself as a graphic frontend. I also wrote a command line frontend (pslr-shoot) which may be useful for making stop motion movies with the help of crontab (the demon, I mean, not the member of this forum), or for controlling the camera within a non-graphic environment, such as those little embedded devices. It works great on my nslu2.
Recently, we added (we hope) support for the gx10, merging an old patch from a polish guy called Safin.
I'd like to hear some reports from Samsung users too, maybe I'll try on a Samsung specific forum.

Thanks,
Ramiro