I removed the code because the update action may be accessing the master files so there would be no benefit to skipping it.  A separate pull request could add this to the workflow and other areas.  Many of MediaObject's callbacks generate a state based upon the objects that are associated with it.  I've seen something like this before to set object state:

```ruby
def realize
  populate_something!
  populate_something_else!
end
```

I'm not sure if it's the right pattern but ```set_duration!``` and ```set_media_types!``` could be wrapped in something like this.

I know there are some AF problems that require us to save an object multiple times in a request but it's probably abnormal for a rails app.  Why would @skip_permalink_check need to be reset?