@rickduley

Hi Rick,

What a palaver! I doubt VPX is taking revenge but I do understand your thinking!

When you carried out the uninstall/reinstall, how, exactly did you do the uninstall? Unfortunately, if you only used the default Uninstaller it is almost certain that whatever is causing the problems for you was not uninstalled. Because VPX creates files and registry entries on first and subsequent runs of the software, the default uninstaller (which is essentially a log file recording what was initially installed) does not know about those additional files and registry entries.

Often recommended here as an app dedicated to ensuring that any software is totally removed is Revo Uninstaller. There are Free, Pro and Portable versions; I use the Pro but either of the others should be adequate for what you need. Just ensure you check very carefully any additional files, folders or registry entries it says it thinks are linked to VPX and intends to remove, especially if you have any other Magix software installed.

Once Revo has completed its work, reboot (restart) you computer and try again to install VPX.

Jeff

@rickduley

Hi Rick

Is VPX taking revenge on me for complaining?

NO, from my recent experience, it may be the buggy Microsoft's security updates and bug fixes a couple of months ago, I suspect it screwed up the Windows uninstaller.

After the buggy updates, I have had to re-install Music Maker 2026, Xara Web Designer and PhotoManager. All three would not start throwing an error -59 code, which is usually fixed by a re-install, the 'normal' Windows uninstall procedure allegedly succeeded, however on trying to re-install I was getting the issue you show above with the installer.

As @emmrecs has commented, Revo may help, however this to may have an issue. I tried a forced uninstall using Revo Uninstaller Pro, I have the paid for full version, however this failed saying the uninstall files were missing.

I ended up restoring the whole C: drive using a backup I had made about 3 weeks ago using Macrium Reflect and then apply the later 'fixed' security patches with no issues, .Music Maker 2026, Xara Web Designer and PhotoManager all started up correctly.

John EB

Thanks @johnebaker, but "No, thanks!"

Not so long ago I had a very 'bad hair' experience with third-party software for reorganising my disc drive. I spent nearly two weeks getting things back in order. This left such a bad taste in my mouth that my technique for such jobs as 'clean uninstalling' is to follow MSCopilot's checklist and remove all references to the offending software using Device Manager and so on. It takes a while, is tedious, yes ... but at least I control what is removed. When Copilot says to use something third-party I demur.

FTR: VPX is reinstalled and running okay although it is still true that "Video Pro X16 cannot successfully write to DVD-DL discs".

I am about to have another go at cutting a DVD-DL the long way. I'll be back! 😶

IF IB cannot find a suitable split point it will display the "end of the world" message. Please show us a

Just plucked up the courage to have another go. Here is today's 'End of the World' message

I notice the wording is subtly different from that shown on the instruction webpage
https://forum.imgburn.com/topic/6376-how-to-deal-with-the-end-of-the-world-problem-in-imgburn/

Where to now?

This file is the log file from a VobBlanker insertion of a split into an ImgBurn file.

Then I go back to ImgBurn and use the files the FobBlanker made and get this

That's what always happens.
What do I do now?

@rickduley

Which option from the IMGBurn Ezimode picker are you choosing to give you that message?

What's the size of your VobBlanker folder?

I'm finding it's basically the same size as the original "Encode in Directory" folder from Magix, so it should be OK, size-wise.

Which option from the IMGBurn Ezimode picker are you choosing to give you that message?

Device

What's the size of your VobBlanker folder?

Sorry - I sell you all a pup! 😞

The size above is the folder created by ImgBurn. This one was the (split) set created by VobBlanker

Quite a difference, and a difference which explains why ImgBurn still finds the files too big.

Question is, why the difference in size?

@rickduley

Hi Rick,

Question is, why the difference in size?

Very good question, to which I have no immediate answer!

Can you show us screenshots of the contents of both folders? That might give us a clue!

Jeff

@rickduley

Hi

I am currently working from my laptop, so going from memory, when using VobBlocker, the only change you should be making is to set the Split point, ImgBurn recommended, this should only update the IFO file, and its backup file BUP, which contains the information about the video on the DVD, start points, end points, chapter points, menus etc.

The IFO file containing the disc layout data is a relatively small file compared to the VOB file sizes.

Check that you still have the same number of VOB files and they are of the same size as the originals, I suspect you may now have an additional one, as a result of the spilt point being inside a VOB or PGC cell resulting in some recompressing.

John EB

This is getting curiouser and curiouser.

These are from ImgBurn

and these from VobBlanker

I'm thinking dump both and start again.

@rickduley

Hi Rick

I'm thinking dump both and start again.

I would agree with that, the ImgBurn list appears to have 1 VOB missing and the numbering sequence is 'off'.

Additionally I think you are going to have to lower the bitrate when burning to directory in VPX, the Voblanker total space use is 9+ GB. For a DL DVD - ideally you should not exceed 8.5GB total to allow for defects in the disc.

John EB

This try with five episodes created 13 VOB files

before

I have attached the log file renamed to *.JPG
You should be able to download it and correct the suffix to *.TXT (or *.LOG)

[[OTHER_V2:31B7FC6ED300418F83F5335729A68AF4]]

Else I'll have to put it on OneDrive again.

I give up. Here's the log.

@rickduley

That folder's to big; you have to reduce the DVD encoder setting bitrate so that it it comes down to 8.5GB as mentioned by John.

When you get to the DVD Burning screen:

Note the "used space on media". This is the size of your project and must be kept below 8500 for a DL DVD. Ignore the 4489MB, as that is for a normal DVD. If it's greater than 8500MB, you'll need to lower the bitrate on the "Encoder Settings: screen:

Adjust the bitrate then "OK" back to the main screen to check the used space is below 8500MB. If it's well below 8500MB, you can of course bump up the bitrate to give you better quality; just don't exceed 8500MB.

When back no the main DVD Burning screen, and ready to run it, click "Encode in Directory", name the new directory, and set it off and running.

Once that's done, in IMGBurn, do a "Create Image from files/folders" and then you'll probably get the End of the World message. Take a photo of that message (for the split point), close IMGBurn and then go through the VobBlanker process.

After VobBlanker has finished creating it's new folder, back to IMGBurn and "Create Image from files/folders" again, hopefully it will display the split point/layer break created by VobBlanker. If it does, all is well, you can either proceed with creating the Image (ISO) or go back to the EziMode Picker and burn the DVD from the VobBlanker folder.