Since installing the latest build (770) I've been plagued by system freezes & "out of memory" errors. I have 24 Gigs of Ram. Anyone else have these problems? I'm uninstalling and reverting back to version 586.
Some people wait a long time before they here back from support. I seem to be lucky because I often get a response with 4-7 days.
Also the support process is a little convoluted. You report and issue. They sent you an email telling you they received your request. Then later they send another email telling you they have responded to your request. Then you login to "My Support" to view the response.
If I remember correctly, your login to view "My Support" is NOT the same as your Vegas login. I have to look mine up each time I use it (Old Timer's).
I don't see any issue here with either of your problems. The refresh button is working fine and if you delete a file outside Vegas you have to press the refresh button first. It is hard to report/solve a problem that the tech team may not be able to reproduce.
Agree, that is how I would expect it to work. When I have Vegas open and I delete or add a file outside, then I select the "Refresh" button on Vegas and the change will show up in the Vegas Explorer window. But it doesn't for me! Instead I must close Vegas and reopen and then my changes take effect for the Vegas Explorer.
I seldom delete files in the above fashion so I cannot say with certainty that this piece does not function. But I do add files for various reasons so I know that piece does not function. I haven't played around to see if it's related to different Vegas Explorer views such as Details, Thumbnails, etc.
For me it's an annoyance that I keep forgetting to report. Not a deal breaker.
Same here. The Refresh button simply doesn't do anything on either of my systems. I think it used to work for me in an earlier build of Vegas 12, and it certainly worked for me in all versions prior to 12--not exactly sure in which build the Refresh button stopped working. I do find it curious that this feature apparently is working for some users with build 770.
FWIW, I recall that a log for an earlier build noted this problem and mentioned that was fixed but that hasn't been the case here. (Just checked--it was build 335.)
I don't know exactly how to report about the random 'crash on quit' bug, since it's, well, random. FWIW, it occurs on two completely different computer systems (described above) with Vegas, and I have seen other users and colleagues reporting the same issue for the last couple of versions. I'll just continue to keep submitting the crash logs then.
Kimberly, thanks for the info for official bug reporting.
For me, the Refresh button problem isn't a deal breaker either but it's certainly an annoyance. For example, when we get new animation scenes sent to the directory, the new files do not appear in the window to drag onto the timeline unless I quit Vegas and restart. To work around the problem, I keep a regular Explorer window open and drag the files in from there. It's not ideal but it's an okay solution.
That said, I'd still like to see it fixed. If tech can't reproduce this issue in the current build then I'll get in touch with some of the users who also experience this issue and see if we can figure out a common cause.
As mentioned earlier, it is hard to fix something that doesn't happen everywhere. You may have other hardware/software issues that don't allow Vegas to refresh the Explorer Window.
If Vegas is not able to read system resources proprely the problem is most probably in Vegas. Some sloppy coding and lousy testing can produce this kind of intermittent results... I have seen this problem too. Must test if its still there. Meanwile we wait for a new build...
"If Vegas is not able to read system resources proprely the problem is most probably in Vegas. Some sloppy coding and lousy testing can produce this kind of intermittent results... I have seen this problem too. Must test if its still there. Meanwile we wait for a new build..."
Why do you bother even writing stuff like this? It serves no purpose and lends no assistance to anyone. If you have knowledge that "sloppy coding" and "lousy testing" is ACTUALLY taking place then I would love to hear it. Heck... I'll even stand in line with you to file my objections, but to write it just because you can is no help to anyone.
You guys are way off topic! But just to clarify, the Explorer pane in Vegas does have a working refresh, but it has a few known bugs. If you have nothing selected and hit F5 or the refresh button then nothing happens -- that's a bug. But if you first click a folder in the left tree pane or a file in the right detail pane then both F5 and the refresh button should work.
The bug that it doesn't work when nothing is selected, I think may have started when I overhauled the context menus in that panel -- I added a refresh option to the menu but I think I might have broken the connection for when there's no context.
I'll try to get a fix on the schedule for the next release. But in the meantime, I hope one of the workarounds mentioned above (click a file or a folder first) will suffice.
I had some problems with .mov files (specifically those from an iPhone 5) and Sony had me regress my QuickTime back to version 7.6 (1292) and that seemed to fix the problem.
First, I did not mean to offend anyone with my comments. My apologies if I did so. I admit it was a little provocative on purpose, but not completely without reason. Best of all, it might have triggered Chris to chime in with explanatory comments that ends this discussion. Your comments will save our time and efforts since we can stop speculating. Now we know the mechanism and how to reproduce the problem and why some could not reproduce. And most importantly, how to work around it. This is great.
I appreciate this kind of openness from SCS. If there is a known issue it will generate less bad blood to openly publish it, instead of just keep silent about it. I somehow still miss a short form list of known issues... Such a list ( accessible by registered software users) would save many people lots of time, and reassure us that the issue is acknowledged and will be fixed sooner or later. There could also be a workaround suggestions listed, if available.
I still claim that the testing of software - not particularly at SCS but generally - is lacking behind considering the huge complexity of modern software, such as VP. Automating the testing procedure is the only efficient way of catching newly generated issues. Sadly VP has suffered from quite many. Quickly withdrawn builds that we have seen recently is another indication of the same.
Thanks Chris for chiming in on this! Highly appreciated. And once more, apologies for my blunt comments. Please remember that I'm not a native English writer and I'm not hiding behind a nickname.
If you have nothing selected and hit F5 or the refresh button then nothing happens -- that's a bug. But if you first click a folder in the left tree pane or a file in the right detail pane then both F5 and the refresh button should work.
Thank you Chris! I can live with this workaround. For me it was just a minor annoyance that I was going to get around to reporting . . . but you were already on it : )