From: notbob on 11 Jun 2010 09:51 On 2010-06-11, Henrik Carlqvist <Henrik.Carlqvist(a)deadspam.com> wrote: > > Why do you prefer to use the 4 applications mount, cp, rm and umount > Is your camera able to by itself have a cron job take a picture every day > at 11:43 am? You make waaay too many assumpions, and when I do need a camera to take a picture every day at "11:43 am", it certainly won't be a 10 yr old point-n-shoot. What's that ol' Slacker saying? Something about "ask a slacker a question and get ten different answers... all correct". ;) nb --who uses emacs, but not konqueror
From: John K. Herreshoff on 11 Jun 2010 09:58 notbob wrote: > On 2010-06-11, Henrik Carlqvist <Henrik.Carlqvist(a)deadspam.com> > wrote: >> >> Why do you prefer to use the 4 applications mount, cp, rm and >> umount > >> Is your camera able to by itself have a cron job take a picture >> every day at 11:43 am? > > You make waaay too many assumpions, and when I do need a camera to > take a picture every day at "11:43 am", it certainly won't be a 10 > yr old point-n-shoot. > > What's that ol' Slacker saying? Something about "ask a slacker a > question and get ten different answers... all correct". ;) > > nb --who uses emacs, but not konqueror Right he was: mount /mnt/memory use Konqueror to move camera files to network photo drive rename directory with Konqueror umount /mnt/memory (Install new card in camera if current is nearly filled up; keep shots on card until needed again in several months; burn *.nef files to DVD when have enough to fill up a DVD) Examine files with GQView (an excellent program for *.RAW files) and edit using ufraw / gimp combo (beat that Windoze.) John. -- Using the jch_box.
From: Grant on 11 Jun 2010 16:57 On Fri, 11 Jun 2010 08:23:52 +0200, Henrik Carlqvist <Henrik.Carlqvist(a)deadspam.com> wrote: >notbob <notbob(a)nothome.com> wrote: >> Why would I use a dedicated camera application to do any of those things >> when my computer can do the same thing by itself? > >Why do you prefer to use the 4 applications mount, cp, rm and umount >instead of the single application gphoto2? Because sometime they suit the task at hand? > >Maybe you do not access your camera from the cli, but then still, why do >you prefer to use a graphical program like konqueror instead of digikam? > >Yes, sometimes it might be convenient to use the disk interface, >especially if you are unfortunate enough to be at a computer not having >gphoto2 installed. > >There are also occasions when I use stuff like > >cat - > file.txt > >to edit a text file. This might be when I am at some computer which >doesn't have emacs or vi installed. The fact that I am almost allways able >to use the "standard" application cat does not mean that cat is my >prefered tool to edit text files. I've yet to find a unix box without 'vi' ;) But cat - > file.txt is far easier than touching up a file on disk with a magnetised needle ;) > >>> The PTP interface also gives you a few extra features: >... > >> Why would I carry around a computer to do what my camera is capable of >> doing by itself. > >Is your camera able to by itself have a cron job take a picture every day >at 11:43 am? Mine could :) Before the Canon A590 died I was running CHDK in the thing and wrote a script to take photos at preset times, including daily sequences ;) Poor cam died about six weeks after warranty expired. But then, I had taken around 140k shots with it, playing with CHDK. Shooting the sky each six seconds during daylight hours takes its toll. > >Computers are used to automate tasks, using the right interface they also >get useful to automate tasks with your camera. Yes, but the Canon P&S has been hacked, CHDK project let's people script their cam's operation... I was the manufacturers were more open to letting people really play with these modern products. CHDK -> Canon Hack Development Kit, fairly active group last I was there, they can always use more people who like reverse engineering ARM code. My current P&S is not ported to CHDK, and my attention is elsewhere this year, so I'm not working on it. It's hard to reverse engineer what was written in C when you only have assembler, and that 32bit ARM chip has two modes of operation (thumb & normal) which complicates interpretation of the ROM dump. Back on topic, of course it was much easier to process large image collections from the cam under slackware, by mounting cam's memory in an adapter and treating it like normal memory. Also, there's memory card recovery techniques that work very easily from Linux CLI with standard tools like 'dd'. Beats writing an app. under windoze to perform the same task. Finally, for best management of flash memory cards, it is better to read them, then reformat in the camera, rather than read then erase particular photos in a high level application. One is better off starting fresh from format, rather than creating filesystem holes and fragmentation that slow down the cam's operation. Usually I plug in the cam, fire up the camera's transfer app. and download the latest images. Selection and further processing is done in my favourite image editor. When the cam memory gets full enough to slow things down, I'll format the flash memory. I don't delete image files individually, that's too slow. Each to their own ways. Thanks to whomever it was mentioned 'convert' -- I couldn't remember the ImageMagick utility name when I wrote an earlier reply. Yes, it's more difficult to use than some graphics app., but it has the advantage of being scriptable; and is another classic unix style tool, mix'n'match with shell scripting and other tools to make your very own custom photo batch processor. That's when treating the cam's memory stick like a disk is easier to handle -- unless there's a CLI PTP protocol handler out there, I've not looked for one. Cheers, Grant. -- http://bugs.id.au/
From: Henrik Carlqvist on 12 Jun 2010 05:10 Grant <omg(a)grrr.id.au> wrote: >>Is your camera able to by itself have a cron job take a picture every day >>at 11:43 am? > I was running CHDK Ok, you can :-) > That's when treating the cam's memory stick like a disk is easier to > handle -- unless there's a CLI PTP protocol handler out there, I've > not looked for one. It seems as if you have found your prefered way to get pictures out of the camera. However, if you are still interested in a cli PTP protocol handler you could check out gphoto2. regards Henrik -- The address in the header is only to prevent spam. My real address is: hc3(at)poolhem.se Examples of addresses which go to spammers: root(a)localhost postmaster(a)localhost
First
|
Prev
|
Pages: 1 2 3 4 5 6 7 Prev: Mplayer question/problem Next: Seamonkey compile problem slackware realated? |