Saturday, 2 February 2008

Answer to splitting blog postings

I promised to blog my answer to splitting blog postings earlier. As you can see I have found out how to - I have reedited my first two (longish) postings using this technique and hopefully they show up in the new form.


How did I do it?

The following help posting on Blogger solved the problem:
http://oeb1.blogspot.com/2007/05/expandable-post-summaries-short-post.html

I followed the instructions to the word and after a bit of tinkering it worked. But I learnt a few things along the way so here are a few extra tips I picked up:
  • I used WordPad to edit the template as instructed. I used the search function (ctrl-f) to find the exact strings needed.
  • You really do have to use some label for each posting or it does not work.
  • If you compose your post and then cut and paste it in (as I did for the re-edit) then it is really only possible in "Edit Html" mode. You essentially paste the summary text over the word "Summary" in the template and the body of the post over "More" making sure that all the other Html commands are not overwritten or moved so that they don't work properly.
  • Unless you want "more..." to show up as the end of a short post then you do need to add the "~short" label to the post. That brings up the "-end-of-post-" message at the end of the post instead of "more...".
  • Just in case the web page is taken down I printed out the instructions in pdf format for safekeeping.
  • Sometimes, for no apparent reason, I have found that this does not work properly and the formatting does not look right in the "Summary" part of the post; also, sometimes the "more..." tag has gone missing. After a good deal of trial and error I found that using the "Compose" editor sometimes introduced extra and statements into the post. This confused the issue and I found that searching through the text and removing all of these except the right at the end solved the problem and did not introduce any other problems.
Read more...

Epson 4800 inkjet printer nozzle clogs

A bit of history - before I bought the Epson 4800...

A few years ago I decided that the best way to take better photos and to enjoy it more was to print more. At the time I had a Canon S9000 A3+ printer and I worked out that one reason that I didn’t print very much was the sheer pain of constantly putting in new cartridges (it was a 6 colour printer), as I always seemed to be running out as their capacity was pretty small – of course there was also the cost of it all.


To overcome both problems I bought a continuous ink system (CIS) to use with Lyson dye inks and Monaco EZcolor to create my own profiles cheaply as the Lyson inks were quite different from the Canon ones. The experience was not great – I had constant nozzle clogs due to various forms of back pressure and once spilt a significant amount in ink on my office carpet while trying to sort things out. After six months of trying I decided to get a new printer – not only because of the CIS debacle, but also because some print fade tests I had been running showed that the dye ink prints were fading significantly in 6 months so pigment ink seemed the way to go; I also wanted to print panoramas longer than the Canon permitted.

Having had trouble finding suppliers for the Canon printer and help with sorting out problems with it I decided to play it safe and go with an Epson as most photographers seemed to use them. I looked at the K3 ink set 2400 and 4800 printers – the 2400 would have produced the quality I was looking for, but with even more ink carts than the Canon I was not looking forward to the constant ink cart changes and certainly was not thinking of trying a CIS again. I also hankered after printing even larger than A3+. The 4800 was much more expensive, but produced A2, would work with 17” roll stock and while having 8 ink carts there was an option of 220ml carts (versus the around 13ml for the 2400). Effectively the 4800 came with a CIS built in along with pro quality reliability and engineering. I cleared space in my office to take it by selling two printers (I used to have an Epson 1160 dedicated to B&W printing, but either of the Epsons would happily produce beautiful B&W prints).

In March 2006 I bit the bullet and bought the 4800 and print quality wise I am extremely happy with it. Early on I decided that since most people wanted gloss prints I would not do any printing on matt paper, thus avoiding that frustration of converting between the gloss and matt ink set-up which causes so much lost ink in the changeover.

For some time I happily printed with few nozzle blocks, but they started creeping in. In fact it was usually the whole colour missing rather than just the odd individual nozzle blocking.

Naively I thought that the auto nozzle check option was the way to go, but searching the web soon told me that that would probably make things worse. Since that was my experience I stopped doing them and stuck to using simple nozzle pattern check prints and cleaning cycles – which used up anywhere between 5 and 14ml of ink a time (the nozzle check each time conveniently told me how much it had used each cleaning cycle just to rub some salt into the wounds).

About 6 months ago I learnt that I was not alone – I found the Yahoo Epson 4000/4800 forum and discovered that nozzle clogging was a real problem for quite a few owners. Unfortunately there does not seem to be a simple solution, but printing something every day seemed to be the best bet along with quite a lot of magic. This I have been trying to do; gradually refining my practices but often not being able to print from one week to the next because of the day job.

Recently I have been able to print every day - I have just had 5 days with absolutely no problems - then yesterday I printed a nozzle check first thing (as I have learnt I have do to spot problems early). The dreaded "auto something or other" (which sounds like head cleaning before the print – I have learnt to dread hearing this as it often leads to problems) happened and sure enough a couple of colour blocks were missing. I did a head clean - another block went missing. I then did another one with no improvement. I then printed a test chart as recommended rather than just do another clean, another clean which did nothing and then ran out of time to do the job I needed to.

I have tried practically everything I can, most of the ideas gleaned from the Yahoo Epson 4000/4800 forum. I have tried Harvey Head Cleaner, but for some reason it will not work on my system (Windows XP SP2) and MIS autoprint, but it only prints seven colour blocks and required me to change the way I set up my computer. I put a wet sponge inside the lid when not in use to try to keep the humidity up (some people think dry air causes the problem although my house is not particularly dry, I live in central
England not Arizona). Despite all this and several days without a problem I routinely wake up the next day and it has stopped working again. The culprit often, but not always, seems to be the "auto something or other" that happens routinely whether I want it to or not.

I have used the puddle method with distilled water or fixyourownprinter fluid when it gets bad, but I can't see why I should need it in normal circumstances. I also regularly swab the wiper blade to clear off ink build ups.

The only thing I can think of is that some of the cartridges are getting quite low (but the printer is not flagging them as low yet) and it tends to be these nozzles that are prone to stop working. I regularly take them out and shake them, but cannot see what else I can to other than to throw them away with lots unused ink in them, which would be an expensive hobby.

As far as I can see I am dong everything I can to keep my printer healthy and am getting really fed up with it – so I decided to start this blog to share my experiences.

Read more...

Starting to use Adobe Lightroom

I am a keen amateur photographer with a day job, although I sometimes use my photography skills in the day job to shoot images for press releases etc.

At the end of 2007 I decided that it was time to look at my digital photo workflow, largely because I bought a Canon G9 planning to use RAW files and found that my exisiting workflow would not work with it as the RAW converters I used did not support the G9.


I use Canon 30D and 10D DSLRS along with the G9.

My colour managed workflow was to take RAW photos, download them to my PC (running under Windows XP SP2) using Downloader Pro, then I viewed them and made initial decisions on what to delete and what to work on using Breezbrowser Pro (both these excellent pieces of software are developed by Breeze Systems). I kept track of what I had where by using a pretty organised file structure; renaming files and moving them about within Breezebrowser. I did my RAW conversions in Capture One LE, Photoshop CS to work on the images, printing to an Espon 4800 Pro inkjet printer through Qimage (a truly excellent package once you get to know it).

I had dabbled with early beta versions of Lightroom, but was not too impressed. I had also tried out various cataloging packages, but had not liked them enough to use either.

By the end of 2007, however, I felt that the press was saying that Lightroom had improved enough to be worth another look and so I downloaded the 30 day trial version from Adobe to try out as my Christmas project. I also had a look at Bibble as a RAW converter and tried out the Canon software that came with the G9 - neither of them really did what I wanted.

So this blog over the next few weeks is aimed at sharing my experience of coming up to speed with Lightroom and using it effectively. Along the way I will share experience with the G9 as I get to know it and the Epson 4800, which is an excellent printer when it works, but in my experience frustratingly and expensively prone to nozzle clogging at unexpected moments.
Read more...

Splitting blog postings

My challenge now is to work out how to split these blog postings so that you don't have to read pages and pages of stuff on topics you are not interested in. I want to work out how to put in a taster paragraph and then put in "Read more..." for those that want to read the whole thing. So far I have found a few web postings telling me how to do this with HTML, but so far none of them have worked. When I work out how it will be obvious from the look of the blog and I'll post my solution. Read more...