Severe problems with VPX5

emmrecs wrote on 11/24/2014, 1:25 PM

The image above is one I am seeing very regularly at the present time, to the point where VPX5, despite a recent uninstall and reinstall, is becoming unusable for me. And that is very serious since I use it as part of my business.

Background: (my computer spec is in my signature). The current project is a personal one (i.e. not for my business); it is a series of full HD video clips (shot with my Canon EOS 600D) "mov" files and a large number of quite high res jpg stills. (The proportion of videos to stills in terms of time is about 30:70, videos are the 30). Editing on the timeline produces the above message, with an almost immediate freeze or complete crash of the program. (I can save the project first, though recently I have been manually saving at least every two minutes!) It seems to be most common when the video files are being played (I am using proxies) though it can occur when a still is on-screen. Any attempt to export to any format I have attempted (DVD, AVCHD DVD, BD (either mpeg 2 or H264)) has resulted, again in a crash, usually with the above message.

As a result of all the above I attempted a repair install of VPX5, but (and I think this may be the root of at least part of the problem) the installer was unable to install/repair the SpeedBurn part of the program. This failure created an automatic notification to MAGIX who replied very quickly with the information that a recent Windows Update was causing problems with their installers. the advice was to remove a particular update, ensure that two others were present and then try again. I did all of this, but the problem persisted.

Hence the complete uninstall and reinstall, which seemed to go without a hitch (no error messages etc.) but still I cannot proceed with this project. Also, perhaps more worryingly, I have discovered that previously-completed and exported (to AVCHD and/or BD) can no longer be exported to those formats; the latest crash, when attempting to export the current project to DVD (so only SD), means I'm getting nowhere fast!

I have replied to the email from MAGIX support detailing the problems with those Windows Updates to say that there has been no change! I have received an acknowledgement (automatic, I suspect) and await any further help they may offer.

In the meantime, if anyone here can suggest anything I'll be only too happy to listen!!

TIA

Jeff

Comments

johnebaker wrote on 11/24/2014, 2:57 PM

Hi Jeff

This error may not be caused by VPX.

I would suggest you cary out the following:

A full Anti virus scan
A full malware scan
A full memory check use something like Memtest or similar.
If you are using Symantec or McAfee AV disconnect from the Internet and try running with them turned off / disabled.
Try shutting down all non essential programs and run VPX

HTH

John

emmrecs wrote on 11/24/2014, 4:27 PM

Hi John.

Many thanks for ths suggestions, each of which I will try or, in the case of "shutting down all non-essential programs" I have already tried, without any change.

I don't run McAfee or Symantec AV so that can be discounted. My AV/Firewall is VIPRE 2015, I will run a full scan.

Have also downloaded Memtest, about to burn it to CD in order to run it.

Here's hoping!

Jeff

Update:

Memtest found no problems
Full AV/Malware scan found one file which it considered a trojan, now removed

emmrecs wrote on 12/6/2014, 9:20 AM

Thought I really ought to finally update this thread with some information as to how the problem was finally resolved.

First, MAGIX Support (aka Ralf!), via the data sent in when I ran the SysCheck utility, mentioned that some chip drivers needed to be updated. Safely done. However, the "memory allocation/low memory" messages continued and any attempt to export the project failed. Tried removing the clip which was situated at precisely the point where export from the beginning of the project failed, no change!

Second, as a result of everything tested so far I decided to completely re-start the project, but to build it as a series of "short" projects, each max 5 minutes long, export each to MPEG and then combine those MPEGs in order to create the final BD. This I did quite successfully until, on the third "part/mini-project" the dreaded error message returned!!! However, when I removed from the timeline the last still image inserted, the problem disappeared; reinstated it, problem returned. Then, (moment of great revelation) I realised what the problem was and why it was happening! This project is intended for BD output and consists of a few Full HD videos and a quite large number of H-Res jpgs from my 18MP camera. However, I had also stitched together some of the stills to create panoramas, with the intention of panning across them; it was whilst attempting to insert one of these that the project/VPX crashed. A quick look at the properties of the particular image showed it to be a file of more than 160Mb! For whatever reason, this was apparently too big for VPX5 to handle on my 32-bit system.

When I reflected further on this I realised that this specific file had been originally placed on the timeline to immediately follow the clip during whose export all the crashes had occurred!

So, regrettably, at least two of my carefully-stitched panoramas cannot be used but I now have a BD of the finished product (am about to go and view it on my TV).

Jeff

johnebaker wrote on 12/6/2014, 4:01 PM

Hi Jeff

. . . . So, regrettably, at least two of my carefully-stitched panoramas cannot be used . . . . .

Can you not split them up into smaller sections and scroll them across the screen, as Terry has posted here, but without the gaps.

I do this with a hires map of Europe which covers UK - Italy, west/east and Denmark to Sardinia north/south - in nine sections varying from 35 - 95 MB in size.

At least we now what the issue is/was.

HTH

John

emmrecs wrote on 12/6/2014, 4:13 PM

Hi John.

Thanks for this and for the link, which I shall study fully later. I had considered using the individual components of the panoramas but wasn't sure how feasible it would be to do this. Will investigate!

Thanks again.