As a long-time user of Video Pro X (I've owned and used every version up to and including X5 - can't upgrade to X6 because I'm still running 32 bit) I've now encountered a problem that has me stumped, and if I want to raise a Support ticket with MAGIX it will cost me £25 since I first registered VPX5 more than a year ago!
So, here's hoping some fellow-user may be able to offer some help and save me some money/time/exasperation.
I recently needed to export some footage to mp4 - I think this may be the first time of needing to use this facility since I first installed X5 - but whichever export profile I choose (I only have one "non-standard" one, used for preparing footage for YouTube), whatever the format of the source file (.avi, .mts, etc.) and whatever the length of the wanted export (e.g. can be as short as 12 seconds or as long as 40 minutes "playing" time), VPX5 crashes every time if I choose either "Advanced Settings" or "OK" (to start the export). The error message, if helpful, is posted below.
What is even more puzzling, perhaps, is the fact that any of those same files opened in VPX4 on the same computer can be exported to mp4, using any suitable profile (including my YT one) without problem!
I have attempted a repair install of X5 without success; I have also recently completely uninstalled (using Revo Uninstaller Pro) and reinstalled all the constituents of VPX5 - a "happy day" spent doing that and recreating all the links to folders and storage drives that are part of my particular set- up - but to no avail! (I should explain the reason for the uninstall/reinstall was NOT this problem, but a general feeling that VPX5 was becoming "unstable" on my computer. That "instability" was cured by this procedure.)
So, does any fellow-user of VPX5 have any ideas/suggestions to offer? All thoughts gratefully received!
Jeff
UPDATE (March 6): Since no fellow-user is able to offer any advice/guidance here perhaps I do need to spend £25. If anyone IS able to successfully export to mp4 from VPX5, even that information would be useful in helping to establish that it is not the software that has a "bug".
TIA