I have added an update to ImageWalker 2.31 that fixes a problem where images could not be loaded from external hard drives. You can download it from the normal place http://www.imagewalker.com/ImageWalkerSetup231.exe
Glad to have fixed that problem. I had to buy three different external drives before I reproduced the error. At least I have plenty of backup space!
Friday, October 23, 2009
ImageWalker 3
Been a while but I assure you ImageWalker 3 is still in the pipe-line. Here is a screen shot to prove it.
Saturday, January 24, 2009
Obama Posters
Great detective work and a happy ending for photographers getting credit for their work.
I am always amazed by how much photography gets used and reused without permission.
Wednesday, January 07, 2009
ImageWalker 3.0
It has been quite a while since I added an entry here. In my defence, I have been off travelling the world and prior to that extremely immersed in my day job.
ImageWalker 3.0 is a new version of ImageWalker written in WPF and .NET 3.5. It is still not ready for even a beta phase so I won’t be releasing anything yet.
ImageWalker 3.0 will be far more focused on workflow and connectivity. The idea is to support the modern/connected user: import, keyword, search, upload to Flickr/Facebook, synchronise to Flickr/Facebook, synchronise comments added in Facebook back to local images, manage backing up images to Skydrive/Amazon s3 and a few other tasks. Of course it will still do all the things it does now :)
Using C# to write for .NET has many advantages and can lead to better designed and tested applications. Now-a-days I am finding it arduous to go back to fix bugs in C++ as almost all the coding I do is in C#.
The ImageWalker 3.0 is 100% managed (C#) and does not call out (Pinvoke) to any old C++ code. To this end I have invested time in writing my own managed infrastructure: for example image codecs and thumbnail/keyword indexing database. I will discuss them in further blog posts.
ImageWalker 3.0 is a new version of ImageWalker written in WPF and .NET 3.5. It is still not ready for even a beta phase so I won’t be releasing anything yet.
ImageWalker 3.0 will be far more focused on workflow and connectivity. The idea is to support the modern/connected user: import, keyword, search, upload to Flickr/Facebook, synchronise to Flickr/Facebook, synchronise comments added in Facebook back to local images, manage backing up images to Skydrive/Amazon s3 and a few other tasks. Of course it will still do all the things it does now :)
Using C# to write for .NET has many advantages and can lead to better designed and tested applications. Now-a-days I am finding it arduous to go back to fix bugs in C++ as almost all the coding I do is in C#.
The ImageWalker 3.0 is 100% managed (C#) and does not call out (Pinvoke) to any old C++ code. To this end I have invested time in writing my own managed infrastructure: for example image codecs and thumbnail/keyword indexing database. I will discuss them in further blog posts.
Tuesday, September 30, 2008
Monday, April 21, 2008
Wednesday, November 07, 2007
ImageWalker now supports XMP
Took me about a month (of odd evenings) to add XMP support to ImageWalker. I adhere to the IPTC Core Schema for XMP and it all seems to be compatible with Windows Vista and Adobe Photoshop.
ImageWalker will now read image metadata from XMP or IPTC and will save updates to both these blocks. I am interested in your experiences so feel free to email me on Zac@ImageWalker.com. Download build 12 from here and give it a try.
ImageWalker will now read image metadata from XMP or IPTC and will save updates to both these blocks. I am interested in your experiences so feel free to email me on Zac@ImageWalker.com. Download build 12 from here and give it a try.
Graffiti from the local area
I have seen many people taking shots of this on Rosebery Ave, Farringdon here in London
Monday, September 24, 2007
XMP, IPTC or EXIF
I have been doing research on what options I have for supporting XMP. It is a priority for me but with the image meta data standards being so ambiguous it seems like a lot of work to take on.
So where should I store an images description: XMP, IPTC or EXIF. All three blocks I guess. What happens if when scanning an image the multiple results for a description are different, do I take the IPTC or XMP value?
In the XMP schema, I have even more options with the different schemas available. For example the Author property can potentially be stored in the following locations:
The Creator tag in the XMP Dublin Core schema:
/ifd/xmp/purl.org/dc/elements/1.1/dc:creator
The Artist tag in the EXIF schema:
/ifd/{ushort=315}
The Artist tag in the EXIF schema embedded in an XMP block:
/ifd/xmp/ns.adobe.com/tiff/1.0/tiff:artist
So I guess one option is just to reverse engineer what Windows Vista does but even the Microsoft APIs scare me: just read this!
I am currently working on a .NET version of ImageWalker (v3.0) and what I would like to do is focus on that after this release. The problem is I am not sure how long before the .NET version is releasable. Bit of a dilemma really, if the .NET version comes along quickly I will add XMP to that; if it is slow I will add it to next release of V2.3x.
Being a one man part time project makes everything slow...need to work faster!
So where should I store an images description: XMP, IPTC or EXIF. All three blocks I guess. What happens if when scanning an image the multiple results for a description are different, do I take the IPTC or XMP value?
In the XMP schema, I have even more options with the different schemas available. For example the Author property can potentially be stored in the following locations:
The Creator tag in the XMP Dublin Core schema:
/ifd/xmp/purl.org/dc/elements/1.1/dc:creator
The Artist tag in the EXIF schema:
/ifd/{ushort=315}
The Artist tag in the EXIF schema embedded in an XMP block:
/ifd/xmp/ns.adobe.com/tiff/1.0/tiff:artist
So I guess one option is just to reverse engineer what Windows Vista does but even the Microsoft APIs scare me: just read this!
I am currently working on a .NET version of ImageWalker (v3.0) and what I would like to do is focus on that after this release. The problem is I am not sure how long before the .NET version is releasable. Bit of a dilemma really, if the .NET version comes along quickly I will add XMP to that; if it is slow I will add it to next release of V2.3x.
Being a one man part time project makes everything slow...need to work faster!
Subscribe to:
Posts (Atom)
