darktable/libgphoto2
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Thumbnail support added. gtkam works now.

Browse Source 
git-svn-id: https://svn.code.sf.net/p/gphoto/code/trunk/libgphoto2@7226 67ed7778-7388-44ab-90cf-0a291f65f57c
This commit is contained in:
Theodore Kilgore
2004-06-29 23:19:29 +00:00
parent 79503d7cce
commit be8ebe5f2e
3 changed files with 32 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
camlibs/aox/ChangeLog
View File

@@ -1,3 +1,9 @@
2004-06-27 Theodore Kilgore <kilgota@auburn.edu>
* library.c: Support for PREVIEW added.
* README: Updated to reflect recent changes.
2004-04-05 Hubert Figuiere <hfiguiere@teaser.fr>
* aox.c (aox_get_picture_size): Declare variables first

24
camlibs/aox/README
View File

@@ -55,6 +55,11 @@ first and the high-resolution photos only after that. In other words, in
that situation the pictures will not be downloaded in the order in which you
took them.
The camera also supports "video clip" mode, in which the camera keeps taking
frames so long as one holds down the shutter button. Unfortunately, there is
not much point in implementing that until the low-resolution non-standard JPEG
format is better understood, because that is what it uses.
Some things which work for me, with various gphoto2 options:
gphoto2 --summary
@@ -91,5 +96,22 @@ it should work for others, too. Please report any problems or bugs to me or
to the gphoto-devel mailing list.
Copyright by Theodore Kilgore, November 11, 2003.
kilgota at auburn.edu
kilgota@auburn.edu
Additional remarks, June 27, 2004:
First the good news:
Thumbnail capability has been added, and the library should be fully functional
now with a GUI frontend. I have tested both gtkam and digikam. Gtkam works very
nicely for me, but for unknown reasons my digikam somehow fails to display the
thumbnails. That is probably the fault of my digikam setup, because it fails for
all of my cameras. It may work for you and if you want to use digikam then
certainly you should try it.
The bad news:
The camera has "video clip" capability, meaning that with a certain camera
setting it is possible to hold down the shutter button and keep shooting
frames (the only limitation being the amount of free memory in the camera).
Unfortunately, the clip mode uses the non-standard JPEG compression, and thus
there is no point in trying to implement clip mode until the compression mode
is understood.

5
camlibs/aox/library.c
View File

@@ -90,7 +90,7 @@ camera_abilities (CameraAbilitiesList *list)
else
a.operations = GP_OPERATION_CAPTURE_IMAGE;
a.folder_operations = GP_FOLDER_OPERATION_NONE;
a.file_operations = GP_FILE_OPERATION_NONE;
a.file_operations = GP_FILE_OPERATION_PREVIEW;
gp_abilities_list_append (list, a);
}
return GP_OK;
@@ -196,6 +196,7 @@ get_file_func (CameraFilesystem *fs, const char *folder, const char *filename,
aox_read_picture_data (camera->port, data, len, n);
switch (type) {
case GP_FILE_TYPE_PREVIEW:
case GP_FILE_TYPE_NORMAL:
if ((w == 320)) {
gp_file_detect_mime_type (file); /* Detected as "raw"*/
@@ -213,7 +214,7 @@ get_file_func (CameraFilesystem *fs, const char *folder, const char *filename,
p_data[w*i + w - 1 - j] = temp;
}
}
/* Not only this, but some colunns are
/* Not only this, but some columns are
* interchanged, too. */
for (i = 0; i < w*h/4; i++) {
temp = p_data[4*i +1];