for devs: vacant jobs, must-have features, status & overview / for users: a poll

[adcz]

I personally think mantis is a bit more organized...

[PhyrePhoX]

in the end it can be any bugtracker. mantis is as popular as bugzilla. problem is the forum integration (same login). remember, patience is a virtue

[adcz]

problem is the forum integration (same login). remember, patience is a virtue

mm...yeah...integration could be hard to do, especially with 2 different scripts. if you write your own bug tracker tho, it would be much simpler (I think less work would be required to write a whole new script than integrate mantis ). and you can always copy over classes from mantis that are useful

basically all there is to integrating is:
* connect to smf user table (smf_members) and do auth thru there (plus access profile settings)
* when creating post in bugtracker, also post in smf database to posts as new thread with title as topic, and an auto-generated first post (with details, category, etc) into (smf_boards I believe), do all discussions in forum

well not too sure on the details...I did not really go farther than integrating user table when I was integrating w/ar site I was working on.

[chiuki]

21 - in playback - which item is currently shown? - needs master of ASM. what i mean in detail: when in playback, we need to find out the filename of the currently shown item (1234.jpg or 2333.avi for example).

I did this for my SD870. Not via ASM, though. I wrote a memory browser and found the address that points to the playback file name. More details here: Playback filename in CHDK « Brainy Hobbies

With the memory browser, you should be able to find the address for different camera models.

47 - exif data - write either more (or more accurate) data into the exif fields, or - if not possible - into extra textfiles (either a small database or a corresponding txt to each jpg).
update: at least include something like "this pic was taken on a camera that was enhanced by CHDK. you can get it from (insert link). chdk needs ads
                                             

Instead of exif, I wrote a library to read IPTC metadata. Right now it only reads the captions field. Details: IPTC parser « Brainy Hobbies

Now, how do I get these changes back to the code base?

[PhyrePhoX]

hi, just yesterday i linked to your site in the "chdk and the media" thread, i guess you noticed that as well

cool things you found out, just a small hint: cyril42e did the same thing in here My modifications to CHDK, it's just that we didnt include it anywhere yet, it's always a matter of finding these different adresses on the different machines i havent checked the code of both of yours, so i dont know if it actually different.
the iptc thing: i dont exactly understand it yet, what is you did, how can one benefit?

you could either apply for an assembla account from one of the devs like grand or ewavr, or when you dont have that "Much" changes you can "submit" these to either me or jucifer, as we could get it into trunk or branch.

[fe50]

Hi chiuki,

#47 EXIF data: LjL is also working a solution to write a EXIF structure with the real CHDK data & settings, first writing them in a textfile corresponding to the picture, later this can also be the base for implementing all kind of meta data handling within CHDK: Exif in RAW mode.

OT: hehe, The SD870 is getting one of the "motors" of further CHDK development 

[chiuki]

Yup PhyrePhoX, thanks for linking to my blog.

Actually, I started poking at memory to get the playback file name precisely because I read the post by cyril42e. He did not explain how he got the address, though, so I ended up writing my own memory search program to find out.

Both IPTC and EXIF are metadata headers. I started looking into IPTC because Picasa uses that to store the caption data. So far I managed to extract the caption written by Picasa and display that on the screen. In other words, as you browse the images, the camera display the caption on the screen at the same time. I want to have on-camera caption editing, and reading the caption is the first step to writing it.

Looks like we can use EXIF comment field for the caption. Since we want CHDK to write other EXIF data as well, it may make more sense to store the caption there as well.

There are a few things I'd like to check in:

• The memory search program. That way other people can use it to find the address for the playback file name and other useful addresses.
• The helper function to return the playback file name. I made it such that if I know the address, I copy out the file name. Otherwise it just returns NULL.
• The IPTC library, if people are interested.

I will send a PM to grand for an assembla account.

[PhyrePhoX]

actually you have to create the account for yourself, grand will only allow it to have write rights on the CHDK workspace. i know that grand is busy with RL atm, so he might not answer in time. ewavr also can do it.
but they probably dont give you the right, remember, you are a "2 post" guy - don't take that as an offense, it is just a matter of security and trust. remember, there are a lot of people who can get your code into the trunk/branches for you.
hope you will have a great time here

[chiuki]

Fair enough.

PhyrePhoX, would you mind being the middleman? Do you want to see the svn diff, or should I attach the files themselves?

[PhyrePhoX]

i'd suggest opening a new thread, describing your changes in detail and attaching a diff and maybe even binaries for others to test. i will patch the trunk as soon as we get some feedback on this matter, some positive that is
but i'm sure people will appreciate it, as long as you provided detailed information about what and maybe how you did it.

[fe50]

chiuki,

diff's and a short explanation of the features on a own thread will be nice, that's the way i prefer...and you'll get more feedback !

[PhyrePhoX]

updated first three posts to reflect current development in the juciphox branch, also edited the poll to show you which of the desired features already made it into the build.
still a lot of gaping holes in the wishlist - developers unite and fix these

[Cemjk]

part 3:
64 - built-in image/video viewer - i understand divx videos cannot and probably will never be played. and also tiff files can never be shown. However, i do not understand why the camera displays files ONLY if they are named after in a special formatted way (some ISO standard), even if they have been recorded with the same camera. same applies to movies. it is very annoying copying my vacation pictures to the sdcard only to find out (when i'm at friends) that the camera does not show them. maybe some ASM guru finds out the image/video "filter" of the cameras and kind of disables or enhances it. this way we ultimately have a portable imageviewer/movieplayer without having to rename/reorganize all media first. difficulty: high. priority: low. useful: very useful.

Viewing images on Cannon cameras is more or less solved (follow link), but needs preprocessing and special names. So I think this is two things first get images to be shown on camera (not CHDK work) wither by converting them or naming them correctly with the right EXIF. Or Hacking the camera to accept all images, anywhere on the SD card.

Has anyone identified the location of the image decoder calls/callbacks?

[PhyrePhoX]

updated first three posts again with either status (is it in trunk yet?) or with a link to the bugtracker ID (created tickets from most of these issues). had to edit alot and cut most of the color tags to have it still fit into three posts (20k char limit per post) - phew!