Adding a RasterBandNodataSetter with a value of 255 BEFORE the Clipper seems to do the trick.
You'll want to be sure, however, that you don't have any data with values of 255 as well. Otherwise you could end up with little spots of 'nodata' all over the dataset.
I guess that might not matter depending on what format you write to (does it support "nodata"), and what application you're using the data in (how does it render "nodata" - for example the FME Data Inspector renders it invisibly, others might just show it as white).
Since you're writing to TIFF, which does support the concept of nodata, you'll need to be careful.
So I did a bit of experimenting because nodata has always confused me.
Ideally you'd set the value to something you know you DON'T have in your data. For example, if you know no cells have a value of 200, then use that. Then, after the Clipper, use a RasterCellValueReplacer to convert values of 200 to 255.
That way the original outside of the clip will be white (255) but you won't end up tagging other cells with 255 as nodata.
Of course, if you know no cells have a value of 255 in the first place, then it doesn't matter.
Hope this helps - and isn't too confusing!
Regards
Mark
Mark Ireland
Product Evangelist
Safe Software Inc
I also think FME needs to improve on how it deals with making wholesale changes to multi band rasters. It seems quite complicated in FME 2013-2014. I think some more options within the raster writers to change bit rate, no data values and other important factors would negate having to use lots of transformers and a complex workspace.