Breezebrowser
- Mike Lane FRPS
- Jun 28, 2010
- 1 min read
Breezebrowser is still my favourite software for editing my pictures and deciding which to keep or delete. I can work faster with this bit of software than any other I have seen, but since buying the EOS 1d Mk1v I have noticed how much slower it runs. It is especially noticeable when I bring four pictures up at once for comparison, which I do a lot. They take far too long to load and I was a bit slow to realise why.
The embedded jpgs within the raw files are much larger than on earlier Canon cameras. Breezebrowser uses these embedded jpgs rather than the raw file itself to display an image. I can’t see a setting in the cameras custom functions where the embedded jpg size can be altered, but have found a workaround that speeds things up. I am now shooting in raw mode plus small jpg setting on the camera. Then within Breezebrowsers Preferences/Image Display I have the raw and jpg files linked. When Breezebrowser views the images now it loads the smaller jpg file rather than the larger embedded jpg and things are back to the same speed I am used to.
Really appreciate how you highlighted the efficiency of using BreezeBrowser for quickly reviewing and selecting images—being able to cull photos almost instantly can make a huge difference in a photographer’s workflow, especially after a long shoot . Streamlining that early stage helps keep the creative momentum going instead of getting stuck waiting on previews. It’s interesting how workflows like this connect to the broader idea of storytelling in photography, something I’ve also seen reflected in creative spaces like AZBoyama.com, where even simple visuals are approached in a structured and engaging way.