One thing is the menu system has been revamped. Some items on the view menu have been moved to the view/windows sub menu.It cleans up a very long menu.

The docking of windows is easier.

Because I just got the packaged today I can't talk about all the differences but those are the things I noticed.

I have to think that the drive towards .NET4 has been executed to improve stability. Why and the outcomes would be good to hear from SCS. I'm getting an understanding that with the frequent presence of a SCS engineer here on this forum bodes well. While this is not necessarily answering your "what's new" it does augur well. The VP13 release indicates a noticeable Line In the Sand having been drawn. This is reassuring.

Grazie

There were many, many reasons for the .NET4 upgrade. But the easiest reason to explain is that Win8 comes with .NET4 pre-installed and no other version, and Microsoft does not permit any developers to bundle any .NET versions with our installers.

This is the most stable I've seen Vegas since V9 and V10. V13 is absolutely rock solid on my system! At some point I'll get around to checking out the new features, but for now, I am just tickled pink with the added stability! Whatever changes were made under the hood... they're working!

Thanks Chris. Presently I'm experiencing stability I've missed since VP9

Grazie

Hate to p in the pool but Vegas 13 is not playing nice with my nested files.

For instance, I have a 30 minute nested file that I import into a new timeline. All is well so I save the timeline. However, I cannot reopen this timeline file again: Vegas 13 hangs indefinitely. (I can open the file in Vegas 12, however, without problem.)

The only way that Vegas 13 will work is if I hide the nested file so Vegas 13 can't find it, and use Replace in the Project Media window. Then it works, until I need to reopen the file again.

Weirdly, if I drag & drop the same nested file in Vegas 12 it works fine. But opening a veg file that contains the same nested file will hang. I use tons of nested files in my work---because of this (and fear of what I may encounter later) I'm retreating to Vegas 12. I'll start a ticket on this...

I've also had problems nested files. Previewing nested files in VP13 is slow so that the nested files aren't in sync with the timeline. I didn't find this in VP12. Maybe someone from Sony could confirm if there's been some changes to the way nested files work?

Yes, I personally made several changes to the nested project code to enable saving nested projects via the new Archive feature and to fix recursively nested projects. We tested it a ton, and I didn't really touch the preview/render code at all, but maybe there's a bug we overlooked. If possible, could you post a small complete project (outer .veg, nested .veg and media) somewhere that demonstrates the problem?

Hi Chris,
I've put a link to Master, nested files & media in my ticket (140508-000122). This project, created in v13, always hangs when reopened in v13, but is ok in v12.
Thanks in advance!

cold ones,
I got your demo project from Customer Support (thank you) but I'm not having any problem at all loading it into VP13 b310. Both the master and the nested project preview well on my machine.

I'm trying to think of ways that my project might be different from yours. A few possibilities:
* a corrupt audio proxy (.sfap0) file for the nested project?
* do you have audio or video proxies (.sfap0, .sfvp0) files for any of the media?
* did yours relink incorrectly perhaps? When I downloaded you .veg and media, they were all in the same folder so VP13 successfully relinked without prompting me at all. If you try that on a machine where the original media *are* still in their original locations then Vegas will behave differently.

It's possible that a simple Save As of the .veg in VP12 might fix it in the latter case.

I did fix quite a few bugs in the nested relink code (needed for Archive which, naturally, has all different file paths) so maybe that's a key detail.

Chris what settings do set preview to? I'm trying to set Vegas to preview nested file optimally. My system has 12GB RAM, AMD X2 1090T with a GTX780 which should be able to handle nested files in preview. I'm trying to work out why preview is slow syncing nested projects.

ChrisDolan,

First, thank you for following up, you are a very welcome presence on this forum!

Weirdly, the sample file I sent (containing nested files) that hung on Friday now opens today. (This file, and others like it, would hang v13 but would open without mishap into v12, same files, same location, etc.) This morning, both v12 & v13 open it without mishap (albeit v12 opens it a bit quicker). This is puzzling, because the computer ran all weekend (no hibernation or sleep, etc), so it should be in essentially the same shape as Friday... I can't tell you how many times this project failed on Friday...

I didn't upload the proxies because of size, but I've learned to delete/recreate them if I'm having problems. These files were dumbed-down versions of others on another drive that I saved to a test folder. That's why I set up the Master File to link directly to files in its own folder for simplicity sake---regardless, that file failed in v13 here time after time. Since proxies were created from scratch, multiple times, they should be ok.

I don't know if others are seeing this, or if this is germane, but it is rare for me to be able to close v12 or v13 without the "Vegas Pro has stopped working" dialog box popping up. (I just sent the results of a typical crash.) Just now, I opened v13, didn't load anything or add anything to the timeline, and upon exit I got the above message again. v12 is the same. This is a minor annoyance because Vegas saves its list of recent files, window layouts etc upon exit, and when it crashes it loses all that.

As I think of it, I recently had a similar problem while using TimeLineTools. If TLT was active while loading nested files, Vegas would hang. If I exited TLT, then opened the nested files, all was well. I could then open TLT with no problem. TLT was not active in my machine during my Friday mishap---but it seems that some other culprit may be at work here.

cold ones - I am not sure what versions of what you are running - so can you be very clear?
1) Your NetFrame directory setup on the boot drive - a screensnap would be nice.
2) Please ONLY run VegasPro 13 version 310 build?
3) How did you install Net4 framework? from update of Microsoft before the install of VegasPro13?
4) Please run Timeline Tools ONLY Version .058 ? not .057 beta or earlier

Let us know your answers for forum members...

Here goes:

1
https://www.dropbox.com/s/tsy8tndf627cknh/Framework%20folder.jpg

2
Vegas 12 Build 770 64-bit & Vegas 13 Build 310 64-bit

3 Installed .Net4.5.1 from Microsoft on 2/18/2014

4 TLT v058 only

Thank you to cold ones - what I find interesting in the test posts we are getting back is the NetFrame structure of different installations.
I cannot exactly tell of your folder structure - but I am under the impression that the "proper" structure would be of two major different sets of subfolders - one being for NetFrame 32bit and the other for NetFrame 64bit.
Does anyone have an explanation of why these differences among user installations exists?
Cold ones - you are on OS Windows version? for the picured installation you posted?