Yes it would be nice to be able to save to older formats. But it does warn you if you try to save over a project from an earlier version. A dialog comes up that says you won't be able to open the project with older versions of Vegas.

Personnaly I don't consider it advantagous or practical - rather bordering on rudness - as I can't share my .veg files with others who have 4.0 or keep my 4.0 and let the Trial expire -

Am I alone in feeling that a more prominate warning would be a polite gesture?

//Garo

Here, here.
Plenty of warning about it before it does a save.
Just so I know where I'm at I've added -V5 and -V2 to my Vegas and DVDA projects as I go. One thing I've learnt in this game, housekeeping is everything (my wife would beg to differ!).

My point being that there is no obvious or explicid indication that this is so BEFORE you impliment v 5

:-)

//Garo

True,
but just opening a V4 project in V5 shouldn't cause the problem, saving it with the same name as the V4 project sure will.

Guess one solution would be to cripple the trial version so you cannot save but I can hear the howls already.

Bob

An additional problem is (I could be mistaken?) that you can't Cut and Paste between V4 and V5 - if this is true I am embarrased for SONY!!

:-)

//Garo

" . . if this is true . ." It is, I can't . . just tried it V4><V4 okay V4><V5 .. nope!

. . .could this be done between V3 and V4? I know I can Copy and PAste between versions of Word for Windows .. and other wordprocessors too. Must be NLEs work differently - yeah?


Grazie


.. next . . ..

My God folks, upgrade and forget about it. Egads, an upgraded programs files not being backwards compatible ? Just how is this an issue and just how did you not know better ? There are NEW FEATURES that Vegas 4 DOESN'T EVEN HAVE ! Duh ! You expected them to work why ? And you would want to copy and paste between Vegas 4 and Vegas 5 ... why ? Vegas 5 is fine just the way it is, haven't had any need to go back to Vegas 4, so why wouldn't you just open two instances of Vegas 5 and copy past your little heart out ? Embarrassed for Sony ? You should be embarrassed for making such a pointless argument.

Don't mean to bust your balls but, c'mon now, this is just silly.

- Ray

www.undergroundplanet.com

Okay . .for example . .. My Shuttle don't work in the keyframes for FXs or the 3D . . It did and does in V4 . . Mutts, I'm joining in here not to be a gainsayer of the NEW, but to reiterate what I can and can't do . .and maybe, just maybe there will be a fix . . I really don't need to copy and paste betwixt to Versions of Vegas . . but I would like to have my Shuttle Pro work in V5 keyframe timeline .. you try it if you have a Shuttle pro, in say Pan/Crop . .for example ..

Putting ALL these points together Sony and the other Gurus here may just have a thought as to why this is happenning and maybe a solution . .nothing more nothing less . . .

.. . oh yes, my shuttle pro works on the actual timeline AND in the VidCap programme . . but not in Pan/Crop and not in the new 3D keyframing timeline . .

Cheers

Grazie

Dear Mr. Muttly
Thare are many considerations as pertaining to buying the upgrade - one is financial - so I am investigating the realms of V5 to see if the investment will be defensable. As I mentioned earlier MOST programs have very good backward capabilities INCLUDING Saving in older versions so I don't honestly belive this is a unsounded comment or issue, to keep things on a politer lever - which you might take note of?
Thanks, Garo

Garo:


"MOST programs have very good backward capabilities INCLUDING Saving in older versions so I don't honestly belive this is a unsounded comment or issue"

Many programs do, but many others do not. The music notation program, Finale, comes to mind. So does MSAccess. I've run into databases that are neither forward or backward compatible - but there are always work arounds. I'm not certain how Sony could cripple features exclusive to V5 in a veg file so that V4 might make sense of them - if they found a way, I'm not certain how they would justifiy any development expense for such a feature - after all, the one of the reasons for developing an upgrade is to sell product.

IMO, both SOFO and Sony gave ample warnings about backward compatibility - the work around is quite simple - save the V5 version with another name.

Not to criticize, but, why would you do real work in a trial version of V5 using features that are exclusive of V4 anyhow other than to try out the new (ie - not available in V4) features? Until you decide to actually pay for the upgrade, you should (again, IMO) either render that V5 work for keeps, duplicate the work in V4 vegs, or just stick with V4 until you're sure.

If for collaborative reasons, you really need to share veg files, everyone should be using the same version.

The question of backward compatibility is a valid one, and the original poster is free to voice his/her opinion, but, I side with Sony (and SOFO before them) on this one.

Caruso

garo,
I feel your pain and maybe I'm a bit older and wiser but potentialy not be able to save in a previous version could not have been the least of your problems.
If what yor're doing is in anyway important installing and running any new software has the potential for disaster. For all you know someone could have hacked into the Sony site and the first time you ran V5 it might have deleted everything on your hard drives. Unlikely for sure but it can happen.
I would never put myslef in that position, I downloaded the upgrade but didn't install it until my clients safely had whatever time critical stuff they needed in their hands.
Given that V5 has added new object types and properties to existing ones the only way to save in V4 format would be by loosing any of the new objects or properties potentialy making the project useless in V4 anyway. Bear in mind that something like Word doesn't have a project file so backward compatibility is much easier. A more valid comparison would be that the files that V4 and V5 outputs are fully compatible, you can interchange .AVIs between all flavours of Vegas.

I think we can proceed to other topics now. I agree that I should have saved my project with another name immediatly upon opening it in V5 but I am/was too stupid or inexperianced to have grasped that simple fact/proceedure at that perticular time. Further I rescued my work by, as farss mentioned, rendering it to a .avi file - that I actually thought out myself!!

So now I will return to V4 until I can realize the revenue nessasasry to upgrade to V5 - which on the whole seems to be worth the investment. I enjoy the program and the feed back on this group.

Thanks all, Garo