Post-Crash problem

artsmith wrote on 2/14/2013, 9:07 PM

I am currently working on a video project. I am between computers, with much of my material still archived while working on a 'old' computer while working with Video Pro-X on the 'new' (Intel i7 and all the bells and whistles). During a recent work-session, I was copying some video-clips between computers, to the 'new' one using a flash-device. I foolishly responded to 'auto-load' to find the destination-file. When I returned to Pro-X, the programme crashed, the first time I touched a key, and an 'access'violation' message appeared on-screen. I saved the programme under another name as suggested, but when I recommenced working on it I noticed that it had changed format from 1920 x 1080 to somewhat less than that. I went to 'effects>video effects.>size/position' and found that the default setting of 100 percent had changed to '90 percent' for each incoming clip added to the timeline. That showed as an undersized image in the left-hand monitor-screen, (well, both screens actually); this has happened twice.

 The image content has all been changed, manually, to the correct setting and all visual material is ready for rendering, once work on the audio is completed. Is the problem, likely to be specific to the programme, or just the 'Project' in question. If I begin another project, as I intend to do shortly, and the problem no longer appears, then, that's fine - no problem. If on beginning another project, the fault still persists, and the default is 90 percent for all incoming video clips, that will be a major problem. If need be I can wipe all vistages of Video Pro-X plus all 'configurations' and begin again, because I am able to remember most of my settings. In case the fault is locked-into some of the configuration data, I would prefer to do it that way and be rid of the problem. Has anyone any ideas? Is there an obvious 'quick-fix? Have I overlooked something simple and obvious?

I am using a modern well-specified Intel i7 based computer with 16gB of high speed RAM, first-rate graphics etc. The operating system is 'Windows 7 Home' and updates are up-to-date. The software version is v 11.0.8.0 (UDP1).

Ian Smith

Dunedin, New Zealand 

Comments

emmrecs wrote on 2/15/2013, 6:03 AM

Hi Ian.

One thing that is often suggested here is to find and delete the videodeluxe.ini file (I think that's the correct name for it!)  I've never tried that as experience has shown me that once VPX starts to throw a wobbly the best solution is to completely uninstall, using Revo Uninstaller, and then reinstall.  I do have a screenshot of all the settings and folder links I need to re-create in order to return everything to how it was before so time-consuming to do, but ultimately the program runs "much better"!

Have you tried opening a new project and seeing what happens re the default setting for size/position?

BTW, I presume you are running Win 7 64 bit since you have 16GB RAM?  Do you find it "better" (faster, more reliable, etc. etc.) than 32 bit?

Jeff

Last changed by emmrecs on 2/15/2013, 6:03 AM, changed a total of 1 times.

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, NVidia GTX 1660TI and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, PhotoStory Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition 3, CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

artsmith wrote on 2/22/2013, 5:42 PM

Jeff,

        My apologies for not getting back to you sooner. It seems my problem was specific to the project which crashed.

The introduction of fresh material to a new project freshly opened produced no problems. Accordingly, athough my current 'opus' runs for 50 minutes, on-screen, I have manually put all shots 'right' in the production, have rendered on a trial basis (in 'Cineform', 4.2.2) and vetted the results, which are OK. Current progress hinges on the stabilisation of a handful of shots, using 'Mercalli 2', (bad case of the shakes after using my camcorder on telephoto settings, in a gale). That tidies up the image-content which conforms exactly to the commentary-track, also in place and finalised, leaving the audio and music to contend with; still quite a big 'ask', when most of the music has not even been composed yet, but hey, it's worth it not to be snarled up in copyright issues and makes some practical use of all those music lessons I endured for many years as a child.

 Since everything was begun using '32-bit', I have stuck with it for the present, so its has been pretty-much  'business-as-usual' and will remain that way until the finish of the current job. On that basis, the impact of 16gB of RAM, has been minimal so-far.

 Now for some stats: Video Pro-X 4 - Movie Edit Pro MX 2013 - Panasonic HDC SD 900, with rolling-shutter problems made-good, (where necessary) using 'Mercalli 2.1' - 'Kontakt 5' for music plus Garritan and VSL instrument samplings for symphonic passages. For tidying up audio 'Audio Cleaning Lab.' and like you, I use 'Reaper' for most mix-downs. Color-Grading in 'Cineform' and occasionally in Da Vinci 'Resolve Lite' (v9). Graphics using 'Xara' or an old, but very reliable, Ulead 'Photo-Impact 11'. That's about 'it' really.

By the way, Thanks for the assistance.

Ian Smith

Dunedin, New Zealand.