Posted 26 February 2006 - 02:33 PM
I'm sure that you found that V 8 is much different than V 7.and a lot of things have changed. A simple example is that not all the transitions that were in V7 are supported in V8 so it doesn't know how to handle them. Perhaps you used one of those transitions?

I jury rigged a V7 production into V8 and it opened but I I tried to go to the timeline, VideoWave crashed.
If you want to, of course you can burn a production to a video file and then import it into V8 to edit in timeline. That works if you do not have to make a lot of changes. I took that crashed production, found and removed an image and the transition associated with that image that was mis-located and then added the audio that I wanted. I did save myself from starting over but I probably not much.
dvsails, on Feb 26 2006, 02:31 PM, said:
Thanks, I re-installed my old VideoWave 7 and at least it still works ok with my previous *.dmsm productions.
Any Idea why the VS 8 VideoWave program crashes immediately when told to open a VS 7 production?
Should 8 not be backward compatible?

Regardless of what I say about computer maintenance, there is no need to defrag a solid state hard drive.
PC Windows 7 Ultimate 64bit
Velocity Micro ProMagix ©HD 60; evga x58 motherboard, Intel i7 @2.93, 12G RAM, EVGA Nvidia 560TI superclocked video card, SoundBlaster X-Fi Xtreme audio card, Buffalo external blu-ray burner; Creator 2012. PhotoShow 6, VHS to DVD 3Plus.
Laptop - Windows 7 Home
Dell XPS 1645, Intel I7 1,6G with overdrive ,4G RAM, 1 GB ATI Mobility Radeon HD 5730, Sound Blaster X-Fi MB Panzer, 500G hard drive.
Apple =OSX 10.5
MacBook Pro; 15.4-inch widescreen display, 2.4GHz Intel Core 2 Duo, 2GB memory, 200GB hard drive, 8x SuperDrive (DVD±R DL/DVD±RW/CD-RW), NVIDIA GeForce 8600M GT with 256MB of GDDR3 memory. ILife 08, Toast 10, Final Cut Express 4 and Photoshop 4.