Although a previous post and response here reports that the transition bug was fixed in the current release, it is, unfortunately, not true. Using the 'fade' effect, when you select anything other than 'fastest' (1) it will only slow down the rotator on the first load, after which it defaults to the fastest transition (1), which is just to darn brief. You barely have time to see what's in the image.
The author needs to figure out how to make the transition speed change stay constant, and REALLY should include a function for how long the image stays fixed before rotating to the next image. Until then, this plugin is pretty much useless for most applications unless you're targeting speed readers!