Can anyone help with the following issue?

My WSF in Brumbaer DNG appears somehow corrupted into an intense moire pattern (see attached). The preview window of the WSF in Brumbaer has been showing these patterns for a while but with no effect on the actual converted file so I ignored it.

In my latest shoot this pattern was applied to to the actual converted DNG (see attached example), ruining the image. It only happens when making 'new' wsf's as I was able to load old WSF's )from previous shoots) and process the raw files that way.

The white files were correctly exposed at about +1 with no clipping.

The only aspect of my workflow that might have changed is that my apple software update automatically updated my system software from 10.4.10 to 10.4.11 - but I am not sure exactly when this occurred.

This problem is only occurring on my location computer, my laptop, which is a new macbook pro (intel) running tiger (10.4.11) and using Brumbaer DNG Converter 1.44.

Has anyone else experienced this?

Would possibly updating to Leopard help - does Brumbaer DNG converter work with Leopard yet?

Cheers

MurrayClick to view attachmentClick to view attachment

havent seen this before .... you should probably contact stefan.
brumbaer works with leopard.

I'm working with this software with Leopard. No problem on older dual G5 and MacBook with Intel.

I did have a few problems that Stefan helped me with.

I might suggest you go into your Library/Application Support/eMotionDng folder and move (and probably later discard) the 'dat' and 'ref' files. these will be auto-replaced if you then re-install the Sinar software. This files are specific for your back (or, you can copy these two files from the computer that is working). These are the defaults you get when you click on 'default' white ref button.

alternately, do you have more than one tab on the white ref pop out window? if you do, you may be using a set of data for another back. by clearing out the above folder, this issue will also be fixed.

Dear Murray,

Like "rljones", it is very likely that the reference files are corrupt. Try to trash it as suggested.

Best regards,
Thierry

Hi All,

thanks for the responses...

I tried trashing the reference files and it was not enough.

Last night Stephan, very kindly, wrote a new version of the program and it has fixed the problem.

All is good now I can carryon.

Cheers

Murray