View Full Version : Crash on file save/create new folder
Ian Stark April 22nd, 2013, 06:12 AM Any thoughts as to why Vegas might crash on trying to create a new folder when saving a project?
The flow of events is as follows:
2. File/Save or Save As
3. In Save or Save/As dialogue, click on new folder icon
4. Crash
This is repeatable. No plugins in the project. Tested on several projects with different media types.
Interestingly it does not happen if I create a new project and save/create new folder before I add media.
I will report it to Sony of course, but I wondered if anyone else has experienced the same thing.
Vegas Pro 12, build 563, updated to latest nvidia graphics driver yesterday (although this was happening before), Win7
Leslie Wand April 22nd, 2013, 06:40 AM sure you're running in admin mode?
Ian Stark April 22nd, 2013, 06:54 AM I'm running using an administrator account, but should I be running Vegas in 'Run as Administrator' mode each time? I'm a bit vague on what Run as Administrator actually does! I assumed it was used in situations where an administrator wanted to run an app on a non-administrator's account and would have to enter a password to do so.
I'd still be confused, though, as I am able to create a new folder when there is no media present; I only have the issue when there's media in the project. I wouldn't have thought Run As Administrator would be choosy like that.
Duane Adam April 22nd, 2013, 11:27 AM I know you stated there are no plugins running, does that include audio plugins? The most recent version of 12 now crashes when I run Sonnox audio plugins which I've been using for years without issues.
Ian Stark April 22nd, 2013, 11:34 AM Good question - to which the answer is no (other than the three default plugins set up with an audio track)
Jay Massengill April 22nd, 2013, 12:06 PM Is the "copy media with project" box checked or unchecked in the save dialog?
Ian Stark April 22nd, 2013, 01:03 PM Always unchecked. However, I don't even get as far as clicking 'save' - the crash occurs as soon as I hit the 'create new folder' button. Just for 'laughs' (ha ha) I tried it again on a project I'm working on at the moment. I have saved it perhaps fifty times today, but a few moments ago I did a file/save as, clicked on the new folder icon and zap. Instant crash. I have tons of disk space, plenty of RAM and I don't believe I have made any changes to any of the default settings.
Ian Stark April 22nd, 2013, 01:10 PM OK, I might have sussed the cause. Could someone else try the following to confirm please:
Open a project (any project with media on the timeline).
Do a file/save as, then click on the new folder icon. Shouldn't be a problem.
Now, open up the video scopes (view/video scopes)
Do a file/save as, then click on the new folder icon. What happens?
In my case the crash is repeatable with the scopes open but does not occur with the scopes closed.
Leslie Wand April 22nd, 2013, 05:46 PM sorry ian - worked ok here.
interesting to see if anyone else can replicate.... the more sophisticated the code, the less dependability on it working as it should - unfortunately.
good luck
Ian Stark April 22nd, 2013, 05:57 PM Damn!
I'm certainly able to repeat it at will (and prevent it at will) and for me the scopes are most definitely the catalyst if not the root cause. Maybe there's a difference in our configurations (graphics card/driver being the most obvious)?
Thanks for trying!
Anyone else able to give it a whirl?
Duane Adam April 22nd, 2013, 06:08 PM Saved with scopes open on mine.
Ian Stark April 22nd, 2013, 06:13 PM Just to be clear, it isn't the save action that causes the crash, it's the action of creating a new folder by clicking the new folder icon. In other words, click file, save as, but BEFORE clicking the save button, click on the new folder icon. I'm sure that's what you meant, Duane, but your wording suggested (to me) you were clicking the save button. Apologies if I got that wrong!
Duane Adam April 22nd, 2013, 07:53 PM Yes I caught that about clicking the new folder icon. Didn't cause a crash.
Graham Bernard April 22nd, 2013, 09:23 PM All of you, where have you the Scopes?
G
Juris Lielpeteris April 22nd, 2013, 10:17 PM Window for browsing of rendering folders belongs system not Vegas. I think Vegas is using .NET to comunicate with the system's resources. Ian, you should try to reinstall all of .NET frameworks, maybe will help.
Graham Bernard April 23rd, 2013, 12:37 AM Copy and paste the line below into your Windows Explorer bar and read off the VERSIONS in your "Framework" Folder.
%windir%\Microsoft.NET\Framework\
Post what you see here.
G
Graham Bernard April 23rd, 2013, 12:48 AM Here's what is advised by the Official VP12 White Paper what .NET is needed:
Microsoft .NET Framework 3.5 SP1 (included on application disc)*
*.NET 3.5 adds functionality to .NET 2.0. After installing the .NET Framework 3.5, versions 2.0 and 3.5 will be displayed in the Windows Add or Remove Programs listing. Do not attempt to uninstall version 2.0; it is required by version 3.5.
I have .NET 4xxxxxx and versions below this.
OK, here's mine:-
http://www.dvinfo.net/forum/attachment.php?attachmentid=29574&stc=1&d=1366699575
Ian Stark April 23rd, 2013, 05:46 AM Not at home now but will do so as soon as I get back. Many thanks.
Ian Stark April 23rd, 2013, 05:53 AM Ah, just remembered the wonderful LogMeIn allows me to do this remotely!
Grazie, I have exactly the same six folders as in your screenshot. In answer to your earlier question (where are the scopes), how do you mean exactly? In terms of where they were in the Vegas UI when I first discovered the problem, they were docked under a tab. After I closed them and re-loaded them they were in a floating palette (the default, I believe?). Is that what you meant by "where"?
Graham Bernard April 23rd, 2013, 06:03 AM Ah, Oui!
G
Graham Bernard April 23rd, 2013, 06:05 AM So you have ALL .NET you need - according to the VegSpecs, others please note. All we need to establish just what is happening to make Vegas fall over.
Easy!
G
Ian Stark April 23rd, 2013, 06:09 AM Yeah, piece of cake :-)
By the way, I was introduced to a few Vegas chaps at NAB a couple of weeks ago and your name came up in conversation - Gary Rebholz, Leigh Herman and Michael Bryant among others. Good bunch of people.
Graham Bernard April 23rd, 2013, 07:08 AM OK, I'm getting a crash which happens when I'm using the Auto Hide Dock Area AND pulling DOWN the Dock Area, but ONLY when I have my 2nd Monitor active as a Preview. However, no second monitor, no crash. It's now a known Bug; I've reported it; it's been written up - I know it has. The Vegas Team needs to have evidence-based results; I've submitted what seems to be hours of the stuff.
I'm thinking that what you are experiencing is a graphical-choking not dissimilar to having a Dock and then not.
G
Gerald Webb April 24th, 2013, 06:00 AM I commend you all on your troubleshooting patience.
I've had the crash when creating a new folder through Vegas for longer than I can remember.
For a long time I've just used windows explorer to create the folder and navigate to it in Vegas. Annoying, but easier than a crash.
Side note. Ive been using Final Cut X for 3 long days, edited and burnt about 70 individual DVDs of a dance eisteddfod.
Its good, I must say I'm a fan, but it has just as many little quirks as we find in Vegas. Just find a work around and keep going.....
Back in Vegas for the last cpl of hrs and its like being home :)
Ian Stark April 24th, 2013, 08:04 AM Good to know I'm not alone, although better not to have the problem in the first place!
It's very weird because I can create a new project and immediately file/save/new folder without hitch, then if I immediately add a piece of media to the medial pool (don't even have to put it on the timeline) then file/save/new folder - splat. Quite why the presence of a piece of media that hasn't even been saved to the project file should have this effect is beyond me.
Grazie, I suspect you're right in that it is a graphical thing, even if the above symptom doesn't immediately suggest that. Two reasons for believing this:
1. I just tried disabling my second monitor and going through the process - all OK, like you. Enabled the second monitor and tried again - crash.
2. I also tried it with both monitors active but with GPU acceleration turned off. The problem went away. Turned GPU acceleration back on - crrrrrash!
I think I will leave GPU acceleration off for now and see if general crashes go away (maybe turn it on for rendering).
Graham Bernard April 24th, 2013, 08:53 AM I have given SONY video of the issues I can repro. They acknowledge them and have logged them.
Until such time I am in a position to "test" any improvement, I am not in a position to comment/say.
Grazie
|
|