We didn't see this in testing, but were able to figure out how it could happen.

Basically, there is (well, was) a hardcoded default bitrate we set when there is trouble scanning the files to be converted, specifically how long the playback time is.

This default is too low, obviously :)

Combine this with the fact that the user is never alerted to this, and the quality controls still function...you get a file @ 350-400kbps.

What we've done is change the way we handle files like this; vx+ will now instead match the bitrate of the file thats being converted, and let you know this is happening...as well as turn off the size slider to avoid confusion.

If all of that was a bit too techincal for you, the upshot is:

"It will *just work* again..like it is meant to."

Look for a new release in the next 24 hours.

Thanks!