VSO Software Forum

Installed v2 and tried to run it with the following settings, MKV Full HD (1080p) H264 *HQ* with English: forced only subs and it errors out. I installed it on another PC and had the same results. I've attached the logs for your review.

Regards

Thank you. I confirm the problem and have reported it here
http://bugs.vso-software.fr/view.php?id=5084


It is not related to forced subtitles but simply the *HQ* MKV profiles according to my tests.

Ok, I will wait for the next build.

Thank you

Hi,

Have you tried with another output profile (like mkv 720p/1080p "normal", not *HQ*)?

Thanks.

No, because I only want the HQ outputs :) I'll do a test and let you know if it works or not.

Worked fine on one computer (Windows 7 Ultimate 64-bit) but not on the other (Windows Server 2008 R2 Standard 64-bit). Same errors. v1 DOES work on the Server 2008 without problems. I'm going to install it on another PC to test.

and you are talkinga about version 2.0.0.5 I sent I PM?

Ok, I’ve performed 3 tests now with version 2.0.0.5 (4 technically). Here are the results:

PC 1: Windows 7 Ultimate 64-bit
Movie: Underworld Rise of the Lycans
Settings: MKV Full HD (1080p) H264 *HQ* with English: forced only subs
Result: Gets to 100% and crashes

PC 1: Windows 7 Ultimate 64-bit
Movie: Transformers
Settings: MKV Full HD (1080p) H264 *HQ* with English: forced only subs
Result: Gets to 100% and crashes

PC 2: Windows 7 Ultimate 64-bit
Movie: Terminator 3
Settings: MKV Full HD (1080p) H264 *HQ* with English: forced only subs
Result: Gets to 100% and crashes

PC 3: Windows Server 2008 R2 Standard 64-bit
Movie: Any
Settings: MKV Full HD (1080p) H264 *HQ* with English: forced only subs
Result: Crashes when starting conversion process

I’ve uploaded the log files and some screen shots that will hopefully help.

thanks for your thorough report.

As for your test on PC3 we might have reproduced this in a different context.

I've tested
Settings: MKV Full HD (1080p) H264 *HQ* with English: forced only subs
On windows 7 32 bit (in trial) no problem at all (not with the same video you have)

We are working on these issues. Thanks for your help.

No problem. Let me know if I can be of any more help. I'll wait for the next build.

I've had a few successful conversions with the Windows 7 PCs, but still no luck on the Server 2008 PC (crashes as it starts to convert).

One thing I’ve noticed is the file sizes are about 3x as large as they were with 1.0.4.8, with no noticeable visual difference. Is there some reason for this? I’d rather stick with v1 if this is the new norm.

I just did a test with Transformers (1). I used my usual settings (listed above):

VSO Blu-ray Converter v1.0.4.8 = 6,600,567,164 bytes
VSO Blu-ray Converter v2.0.0.6 = 21,523,751,935 bytes

And for kicks I did a conversion with Handbrake v0.9.6, High Profile with RF18 = 18,924,359,601 bytes

It's a HUGE size difference with v1.0.4.8. To my eye I can't see any noticeable difference. What did you change in v2 that is causing the file size to go up so much (the small size is what turned me onto Blu-ray Converter to begin with)

Hi,

Blu-ray converter is not yet Windows Server 2008 compatible, but I can take the time to see if it can make it compatible for future versions.

If the final filesize is too high for you, why you don't fix a custom filesize in output settings (I think you selected "no size limit"?)

Thanks.

How come v1.0.4.8 works fine with Server 2008?

The file size with v1.0.4.8 is considerably smaller with the exact same settings [MKV Full HD (1080p) H264 *HQ* with English: forced only subs with no size limit]. This very discouraging since the small output was part of what drew me to Blu-ray Converter.

The actual movie for Transformers is 36,127,942,275 bytes. With v2.0.0.6 it is only compressing it about 1/3, but it should compress down by closer to 2/3 up to 3/4 as it does with v1.0.4.8.

I just did another test.

Movie: Sucker Punch
RAW Movie Size: 22,836,617,703 bytes
v1.0.4.8 Output Size: 3,888,069,228 bytes
v2.0.0.6c Output Size: 16,988,434,780 bytes

That's a night and day difference (and minimal compression). Since the app is not writing any of the settings (i.e. MKVMerge or Handbrake) I can't tell what it is you've changed in this version to cause such a huge difference in outputs.

I'm no expert, but I do a lot of conversions and I can say that these large file sizes are unnecessary. Again, the smaller output of v1 is what makes this program so attractive to begin with.

I just did another test, this time converting it with High Profile Handbrake at 8000 k (2-pass) and it came out to 6,583,984,716 bytes. Nearly twice the size of v1.0.4.8, but still a much more acceptable size in my opinion.