Today I was just sorting, metadataring, and processing photos most of the day.
The weather was nice in the morning so I was planning to go out in the afternoon, but the sky got covered in thin cloud. While the weather was still nice, a white sky doesn't usually make for good photography.
In the afternoon I did go out in the garden for a bit.
In the evening I watched 3 Power Rangers episodes with L.
Mauser came back from his trip round Europe and Morocco, and got me a Soviet pilot's hat from East Germany. Nice!
Thursday, 30 September 2010
Wednesday, 29 September 2010
Comp working again!
This morning I went on the internet on Mauser's comp, until my new graphics card arrived around midday.
After installing the new card and latest drivers (and having lunch) I spent most of the afternoon catching up on my email.
In the evening I sorted some photos and did a backup.
After installing the new card and latest drivers (and having lunch) I spent most of the afternoon catching up on my email.
In the evening I sorted some photos and did a backup.
Sunday, 26 September 2010
Pogging and metadataring
This morning I started cutting out some pogs in Photoshop, then went to Church. After Church I finished cutting out the pogs in Photoshop.
After dinner I checked my email while waiting for the pog images to upload. I updated my pog website, then started adding metadata to the photos I took yesterday.
I had some trouble geo-coding the photos, as Robogeo said it couldn't geo-code some of them and would have to convert them to jpegs (I was geocoding a mix of JPG and RAF files). I spent quite a while trying to find what the problem was, and see if there was some way to export the list of geocoded files so I could use exiftool to do the geocoding, but couldn't get anything to work.
Eventually I just downloaded the latest version of Robogeo, it doesn't mention anything in the recent changes about RAF support (and I had tried the previous Robogeo I had installed with the latest version of exiftool already). But it did work, and geocoded my JPEG and RAF files successfully. Unfortunately it couldn't read the save file I had created with the previous version of Robogeo, so I had to re-gecocode (using Google Earth) all the photos.
I also watched an episode of Jetman with L in the afternoon.
In the evening I carried on adding metadata to the photos and uploaded some of them. I did a backup and then went to bed.
After dinner I checked my email while waiting for the pog images to upload. I updated my pog website, then started adding metadata to the photos I took yesterday.
I had some trouble geo-coding the photos, as Robogeo said it couldn't geo-code some of them and would have to convert them to jpegs (I was geocoding a mix of JPG and RAF files). I spent quite a while trying to find what the problem was, and see if there was some way to export the list of geocoded files so I could use exiftool to do the geocoding, but couldn't get anything to work.
Eventually I just downloaded the latest version of Robogeo, it doesn't mention anything in the recent changes about RAF support (and I had tried the previous Robogeo I had installed with the latest version of exiftool already). But it did work, and geocoded my JPEG and RAF files successfully. Unfortunately it couldn't read the save file I had created with the previous version of Robogeo, so I had to re-gecocode (using Google Earth) all the photos.
I also watched an episode of Jetman with L in the afternoon.
In the evening I carried on adding metadata to the photos and uploaded some of them. I did a backup and then went to bed.
Saturday, 25 September 2010
IRing
This morning I did some more work on my geoclustering script, and my Fuji IS Pro arrived. I charged up the battery and read Thom Hogan's review of the S5 Pro, and unfortunately you can't use the D200 battery in the IS Pro, despite the cameras and batteries looking identical.
When the battery had finished charging, I spent a long time trying to get a hood onto the Cokin P holder that would extend behind and in front of it (to stop light hitting the back of the filter as well as stopping light hitting the filter at oblique angles on the front). Unfortunately I couldn't get this to work, so I decided to just mount a hood behind to stop light hitting the back of the filter.
I went out for a short walk and took a few shots, and was impressed with how the IR photos looked on the camera's screen, though you can't zoom in much on the screen.
We went out to a small lake in Corby for a picnic lunch, where I took a few more shots with the IS-Pro. When we got home I processed a few photos and watched an episode of Jetman with L.
Then I spent the rest of the afternoon making Cinnamon Swirls with L. After dinner I finished making the Cinnamon Swirls with L and also had loads of washing up to do (all the dinner stuff plus the cooking stuff, plus picnic stuff).
For the rest of the evening I watched a couple of episodes of Power Rangers with L and processed a couple more IS-Pro photos from today. I'll have to metadata and upload them tomorrow (after doing the pog stuff first).
When the battery had finished charging, I spent a long time trying to get a hood onto the Cokin P holder that would extend behind and in front of it (to stop light hitting the back of the filter as well as stopping light hitting the filter at oblique angles on the front). Unfortunately I couldn't get this to work, so I decided to just mount a hood behind to stop light hitting the back of the filter.
I went out for a short walk and took a few shots, and was impressed with how the IR photos looked on the camera's screen, though you can't zoom in much on the screen.
We went out to a small lake in Corby for a picnic lunch, where I took a few more shots with the IS-Pro. When we got home I processed a few photos and watched an episode of Jetman with L.
Then I spent the rest of the afternoon making Cinnamon Swirls with L. After dinner I finished making the Cinnamon Swirls with L and also had loads of washing up to do (all the dinner stuff plus the cooking stuff, plus picnic stuff).
For the rest of the evening I watched a couple of episodes of Power Rangers with L and processed a couple more IS-Pro photos from today. I'll have to metadata and upload them tomorrow (after doing the pog stuff first).
Friday, 24 September 2010
Uploading and reading
This morning I uploaded a photo to a few photo sharing websites, which actually took quite a long time. I did some vacuuming and sorted and uploaded some photos to my website as well.
In the afternoon I sorted and uploaded more photos, then started looking into the Fuji IS-Pro that I bought yesterday (particularly looking at the filters etc. needed for normal, IR, and UV photography).
In the evening I baked some cookies and carried on looking into IR, and UV photography. For UV photography, it seems that you need a specialised, expensive, and hard to get hold of filter.
For IR photography there are quite a few filters available, so I was mainly researching which one to get. I do have a Hitech Infrared Resin filter already, but it seems very flare prone. I was mainly looking at the B+W 093 and the Hoya R72 filters. The B+W is a higher cut-off, and only passes Infrared, while the Hoya passes Infrared and a bit of visible light.
From what I could gather, it seems like the Hoya R72 is better for false colour IR, while the B+W 093 is better for contrasty black and white true IR photos.
In the end I decided to just purchase the B+W 486 UVIR cut filter so I can use the IS-Pro as a normal camera (S5 Pro). It was expensive though, $100 for a 67mm filter! I decided to go for a 67mm filter size as that fits my current lenses, and I can't really think that it will be a great loss if I purchase a lens with 77mm filter size in the future and so can't use it for normal photography on the IS-Pro.
One thing I did find a bit disappointing is that both UV and IR light focus at different points to normal light, and so a photo taken with visible and UV and IR light will likely be soft. Also, it seems that some lenses aren't suited to UV or IR photography, and according to Bjørn Rørslett, most (all?) of my lenses aren't that great for IR photography.
When I get the camera and we get some decent weather (i.e. not overcast), then I can try the camera with my Hitech resin infrared filter, and see if there is any problem with my lenses or the Hitech filter.
In the afternoon I sorted and uploaded more photos, then started looking into the Fuji IS-Pro that I bought yesterday (particularly looking at the filters etc. needed for normal, IR, and UV photography).
In the evening I baked some cookies and carried on looking into IR, and UV photography. For UV photography, it seems that you need a specialised, expensive, and hard to get hold of filter.
For IR photography there are quite a few filters available, so I was mainly researching which one to get. I do have a Hitech Infrared Resin filter already, but it seems very flare prone. I was mainly looking at the B+W 093 and the Hoya R72 filters. The B+W is a higher cut-off, and only passes Infrared, while the Hoya passes Infrared and a bit of visible light.
From what I could gather, it seems like the Hoya R72 is better for false colour IR, while the B+W 093 is better for contrasty black and white true IR photos.
In the end I decided to just purchase the B+W 486 UVIR cut filter so I can use the IS-Pro as a normal camera (S5 Pro). It was expensive though, $100 for a 67mm filter! I decided to go for a 67mm filter size as that fits my current lenses, and I can't really think that it will be a great loss if I purchase a lens with 77mm filter size in the future and so can't use it for normal photography on the IS-Pro.
One thing I did find a bit disappointing is that both UV and IR light focus at different points to normal light, and so a photo taken with visible and UV and IR light will likely be soft. Also, it seems that some lenses aren't suited to UV or IR photography, and according to Bjørn Rørslett, most (all?) of my lenses aren't that great for IR photography.
When I get the camera and we get some decent weather (i.e. not overcast), then I can try the camera with my Hitech resin infrared filter, and see if there is any problem with my lenses or the Hitech filter.
Thursday, 23 September 2010
My best evening
I spent quite a bit of this morning working on my geo-clustering script, but got stuck and couldn't work out what the problem was. So I spent the rest of the morning and the afternoon taking, sorting, uploading, and processing photos. I also read a few forum threads on dpreview.
I had a really exciting evening buying a new camera and helping L make a video.
I was looking at a camera website that had been emailed to me as being a cheap camera website, not looking to buy anything, but just to see what the prices were like. The prices did look quite good to me. Then I saw they were selling the Fuji IS-Pro for over £1000. I remembered that it was about £500 on Warehouse Express, so I looked on the WEX website, but it was no longer listed.
So I checked the Fuji website, which gives a list of suppliers that you can buy the Fuji IS-Pro from. But when you click through to the retailer, it is just the Fuji category or search page on their website with a search query like Fuji or Fujifilm. And when you look through the items on each retailers website, none of them actually sell the Fuji IS-Pro!
So I google searched, and found Clifton Cameras were selling them for £350. But they had a thing saying something like 'Very special limited offer'. So given that
Of course, it will be annoying if Nikon or Canon (or Fuji) announce a new camera shortly that does IR, since the IS-Pro is quite old and lacking in things like high ISO quality and megapixel count.
For the video, I was helping L make a birthday video for YoshiElectron as it is his (YE's) birthday today. Unfortunately the eyetoy wasn't working on Mauser's comp (probably due to the comp being virused). And Mauser has my old camera (which does low quality video) on holiday with him. So we decided to do a stop motion video.
Obviously, this takes quite a lot longer to both set up and film, and then put together on the computer. So doing that took most of the evening, even though the video is only very short. Actually, L cut quite a lot of the frames from the final video.
I had a really exciting evening buying a new camera and helping L make a video.
I was looking at a camera website that had been emailed to me as being a cheap camera website, not looking to buy anything, but just to see what the prices were like. The prices did look quite good to me. Then I saw they were selling the Fuji IS-Pro for over £1000. I remembered that it was about £500 on Warehouse Express, so I looked on the WEX website, but it was no longer listed.
So I checked the Fuji website, which gives a list of suppliers that you can buy the Fuji IS-Pro from. But when you click through to the retailer, it is just the Fuji category or search page on their website with a search query like Fuji or Fujifilm. And when you look through the items on each retailers website, none of them actually sell the Fuji IS-Pro!
So I google searched, and found Clifton Cameras were selling them for £350. But they had a thing saying something like 'Very special limited offer'. So given that
- The Fuji IS-Pro is hard to find available for sale
- It is normally around £1000
- It was only available at the discounted price for a limited period
Of course, it will be annoying if Nikon or Canon (or Fuji) announce a new camera shortly that does IR, since the IS-Pro is quite old and lacking in things like high ISO quality and megapixel count.
For the video, I was helping L make a birthday video for YoshiElectron as it is his (YE's) birthday today. Unfortunately the eyetoy wasn't working on Mauser's comp (probably due to the comp being virused). And Mauser has my old camera (which does low quality video) on holiday with him. So we decided to do a stop motion video.
Obviously, this takes quite a lot longer to both set up and film, and then put together on the computer. So doing that took most of the evening, even though the video is only very short. Actually, L cut quite a lot of the frames from the final video.
Wednesday, 22 September 2010
iframes and objects
This morning I was doing some more work on my photo website. I was happy to see that my lightbox close icon was now showing up again in Chrome, so the reason it wasn't displaying before must have been Chrome bugginess rather than my own fault.
Then I had a similar thing with IE6. The lightbox was displaying at a small size, so I undid the changes I made to the code yesterday, refreshed the page a few times, but it was still the same. I then started up Visual Web Developer Express so I could debug the problem, but when I loaded up the site for debugging, it displayed okay!
I was worried that it might be that the site only works properly in IE6 when Visual Web Developer Express is worried, so I closed that and checked the site, but it was still working okay. I just don't understand how computers can be so illogical.
Next I changed the page headers so that it would be sent as html instead of XML + XSLT to IE. But when I refreshed the page, I just got the HTML in the style that IE uses to display an unstyled XML document (i.e. like viewing source). So I installed Fiddler2 to double check the headers that IE was receiving from the page, but when I restarted IE, the page now rendered correctly!
I think that probably IE must cache the content-type of a page, so if you refresh a page, it will use the content-type that the page had when it originally requested it.
After doing this, I found that my page still won't work properly when moving an object in the DOM in IE, despite working in my test page.
I spent the rest of the morning debugging this, and creating a test page: http://www.iliveinabin.com/iframe-object-test/page.html
I found that in IE, the google maps page stops working when you move the object in the DOM, and the map has been initialized using a callback function. Strange.
On my test page in IE6, it will create an object in the page, but it won't load the object's contents. Strangely, it works okay on my real website (where I use jquery to create and append the object) though.
In IE8, it won't load the Amazon home page in an object. Presumably it doesn't like it because it's a different domain to the containing page.
In Chrome and Firefox (but not IE), moving an object in the DOM reloads it.
In Chrome, when setting the display of an object to 'none', and then setting the display back to 'block', this will cause the object to reload its contents.
I found this bug report for Firefox, which says:
I also tried assigning the contentWindow of the iframe to a variable before moving it, then setting the contentWindow of the moved iframe to the variable, but this didn't work. I tried both
It seems that storing the old value in a variable works okay, but setting a new value for contentWindow or contentWindow.document doesn't work.
The only way I can think of that you could move an iframe (or object) in the DOM without it looking like it had reloaded is to keep track of all relevant interactions with the iframe before it is moved, and then recreate these interactions programatically after moving it. E.g. if the iframe contained just a simple scrolling page, you would have to get the scroll positions before moving the iframe, then set them again after moving it.
Looking into that took all morning and a bit of the afternoon. I went out in the garden and took some photos of Red Admirals, then spent the rest of the afternoon and most of the evening working on my geo clustering script.
Then I had a similar thing with IE6. The lightbox was displaying at a small size, so I undid the changes I made to the code yesterday, refreshed the page a few times, but it was still the same. I then started up Visual Web Developer Express so I could debug the problem, but when I loaded up the site for debugging, it displayed okay!
I was worried that it might be that the site only works properly in IE6 when Visual Web Developer Express is worried, so I closed that and checked the site, but it was still working okay. I just don't understand how computers can be so illogical.
Next I changed the page headers so that it would be sent as html instead of XML + XSLT to IE. But when I refreshed the page, I just got the HTML in the style that IE uses to display an unstyled XML document (i.e. like viewing source). So I installed Fiddler2 to double check the headers that IE was receiving from the page, but when I restarted IE, the page now rendered correctly!
I think that probably IE must cache the content-type of a page, so if you refresh a page, it will use the content-type that the page had when it originally requested it.
After doing this, I found that my page still won't work properly when moving an object in the DOM in IE, despite working in my test page.
I spent the rest of the morning debugging this, and creating a test page: http://www.iliveinabin.com/iframe-object-test/page.html
I found that in IE, the google maps page stops working when you move the object in the DOM, and the map has been initialized using a callback function. Strange.
On my test page in IE6, it will create an object in the page, but it won't load the object's contents. Strangely, it works okay on my real website (where I use jquery to create and append the object) though.
In IE8, it won't load the Amazon home page in an object. Presumably it doesn't like it because it's a different domain to the containing page.
In Chrome and Firefox (but not IE), moving an object in the DOM reloads it.
In Chrome, when setting the display of an object to 'none', and then setting the display back to 'block', this will cause the object to reload its contents.
I found this bug report for Firefox, which says:
Whenever an iframe node is pulled from the DOM tree, the contentWindow is set to null, forcing a reload of the iframe's content when it is placed back into theSo I tried cloning the iframe, using both shallow (
DOM tree.
iframe.cloneNode() )and deep cloning ( iframe.cloneNode(true) ), but the cloned iframe always had a contentWindow of null (even though the iframe I was cloning from had a contentWindow of DOMWindow.I also tried assigning the contentWindow of the iframe to a variable before moving it, then setting the contentWindow of the moved iframe to the variable, but this didn't work. I tried both
iframe.contentWindow = oldContentWindow and iframe.setAttribute('contentWindow', oldContentWindow). Neither worked, and doing the same thing with contentWindow.document didn't work either.It seems that storing the old value in a variable works okay, but setting a new value for contentWindow or contentWindow.document doesn't work.
The only way I can think of that you could move an iframe (or object) in the DOM without it looking like it had reloaded is to keep track of all relevant interactions with the iframe before it is moved, and then recreate these interactions programatically after moving it. E.g. if the iframe contained just a simple scrolling page, you would have to get the scroll positions before moving the iframe, then set them again after moving it.
Looking into that took all morning and a bit of the afternoon. I went out in the garden and took some photos of Red Admirals, then spent the rest of the afternoon and most of the evening working on my geo clustering script.
Subscribe to:
Posts (Atom)