| User review:
|
I've been using this app for quite a few years and having nothing but high praise for its ease of use and quality, that being said, the last few revisions have been quite odd in it changes they've introduced...mainly with the output sizing...i can remember last summer using this app on a 5 gb mkv and setting it to a custom 4478mb's and it getting very close after finishing, like 4.2...which i'm ok with...i'm doing a mkv at the moment thats 6.6 gb's in size and regardless of the custom size setting or setting it to dvd5, its produces a file size ridiculously smaller than it needs to be...this title i'm doing is 1hr and 55mns long and the output size comes out to 2.6gb's. I can set it to slow, medium or high and cant get past 2.6gb's, so i thought i'd first go to VSO's site and see if others were having the same issue. Ofcourse others were but the only answer to the issue is that particular way of encoding is equal in quality to filling out a dvd5 so theres no use to bother posting or asking why this change has been implemented. The first thing that came to my mind is that the creators of Dvd Shrink/Nero Recode, Dvd Rebuilder, DvdFab, Dvd2One and others apps similar that hit the size mark or get close, must all be wrong or they don't have a clue about encoding. I'm guessing this is probably incorrect cause the apps are still being used and are quite popular and the results speak for themselves. Also, why wouldn't have Hollywood or companies that do encoding not go for the same type of encoding theory that VSO does and cram a trilogy of titles onto 1 dvd9 to save space and money? There's an answer to that question though, it's because the quality isnt as good. VSO, please fix this and make it to were your customers actually get close to what they want, a title that's close to a size they want...not 40 to 50% off the mark...If not, why not just get rid of the "Custom" size feature..its useless and doesn't work to begin with(it use to) |
