There is no 64bit version, so it is slow when adding HD material. Has no else noticed this?

Tim20 I will get back with my specs soon. Sorry vegas is not working well for you & the others.

Why do you imagine that a 64-bit version would have any effect on this ?

geoff

as there have been many postings in the DVDArchitect Forum about what is needed or wanted for the further development of that authoring DVD/Blu-ray product - to Zeitgeist- your expressed concerns here are new and IMO probably way off track of the issue.

The underlying code and purposes for the authoring package has very little to do with anything of a 64bit nature. In fact the program runs quite effectively in a healthy 32bit environs.

You express concerns about adding HD material? where / in Vegas Pro where it should be? I author complex Blu-ray programs almost constantly with SCS DVDAPro. All sources come from VegasPro and of course are HI-def.

Here are my specs. Hope it helps.

OS Name Microsoft Windows 7 Professional
Version 6.1.7601 Service Pack 1 Build 7601
System Type x64-based PC
Processor Intel(R) Core(TM) i7-2600K CPU @ 4.10GHz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 2302, 2/16/2012
SMBIOS Version 2.6
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.98 GB
Available Physical Memory 4.44 GB
Total Virtual Memory 16.0 GB
Available Virtual Memory 11.4 GB
Page File Space 7.98 GB
Page File C:\pagefile.sys
direct x 11
gtx550ti
driver296.10

I edit AVCHD, mov, avi, jpeg, psd, png sequences with alphas. I use Boris Red, New Blue, & MagicBullet, Neat Video effects.

I usually get crashes near the end of projects, where the autosave saves or sequential file saving saves me.

I have my video to ram preview set to 400 mb.

I edit off external sata HD's & render to an internal sata HD with the latest version of Vegas 11.

If you need any more info, I will try to give it. Good luck. There has to be a way to get vegas 11 to work on your system.

On a side note, AVCHD media files take a very long time to uncompress (open) in DVDA. 64 bit would definitely help. If you are working with mpeg 2 you would probably not know this. Bring in a 2hr AVCHD file into DVDA & see how long it takes to open. Then you'll start to understand why 64 bit is needed for DVDA.
64 bit helps in opening AVCHD files because they are highly compressed. These are facts, but we digress.

@ Zeit: Our systems are very similiar but I have more ram and a larger video card.

I understand that I am expecting way too much with large PNG files and don't blame Vegas there. It's when I have much smaller clips on a few video tracks and it starts creeping that I get frustrated. Along the way I have run across some things in Vegas that are inherently wrong and causing problems, but my crashes are way down with the new system.

I'm working in a 1920 x 1080i template right now.

1. When importaing clips not all interlaced clips are recognized as such. Example: My camera videos are m2ts files and in the video properties will always be interlaced. Files renedered in AE are .mov interlaced using the PNG or DNxHD and these will import into Vegas as progressive. That caused slowdowns until I went in and manually set them as interlaced.

2. Working on clips in a single track with A/B performs better than using two tracks.

3. Vegas only recognizes the Alpha channel on the PNG files. It won't recognize it on the DNxHD

4. Vegas continually tries to preview the project as progressive. If I go in and select "preview at project settings" this will make the preview interlaced. However that selection is not a global selection. It has to be set for each choice, i.e. Best: Auto, Full, Half, Quarter and on down the line. Doing this does increase fps performance.

What turned me to Vegas was Forge because Forge was solid as a rock. At the time I had Premier which was as solid as the Titanic. The only other application that I have that is as solid as a rock now is Quicken. I can't edit video in Quicken so I am up the creek so to speak. So I still use Vegas 32 bit in Vista 64.
JJK

Tim20 sorry if this has been asked & stated before, but are you using an external monitor with Vegas? I lose a few frames a second when using an external monitor & notice Vegas is less stable with the external monitor on. I toggle it off when I am fast editing & toggle it on when Icolor correcting & applying effects.

Otherwise I am puzzled as to why similar systems would not behave the same. I have Vegas 11 on two computers. One for simple edits & one for complicated edits. The simple edit computer never crashes, but the complicated edit system usually crashes near the end of an edit right when I am in a hurry to finish editing & take a break. My solution is to sequential saves & close vegas every 20 minutes & take a short stretch/walk break and then come back to edit to avoid the crashes.

Here's to a more stable Vegas 12 in the future.

I am running dual monitors. When I open preview up , yes it slows things down a little. My tascam firewire interface is a culprit for the some of the crashes. They quit talking to each other, but having a shuttle jog is a dream and of course the other bells and whistles that go along with mackie emulation mode.

I am learning to live with the above but what is chapping me right now is that I have to remember to check/set my imported clips to interlaced. Next short I do is going to be 720p. What was I thinking.

And here is to a free upgrade to Vegas 12 from Vegas 11 users :) Stable of course.

I haven't tried Vegas 11. But I was having enormous problems with Vegas 10. I solved them by going back to Vegas 8. Maybe not for everyone, but sure worked for me. I don't see the need to give Sony more money for an increasingly inferior product.

Vegas 11 was the first upgrade I resisted buying, having been bitten by the nightmare of Vegas 10 and cineform files.
I now use 10e for paying jobs, but still only use cineform files in a limited manner.
I will not purchase Vegas 12 unless I know it is fully stable and also works flawlessly with cineform files. I would hope that it would be a free upgrade for users of 11 who have had so many problems.
If Sony do not manage to resolve its issues then they really do run the risk of loosing many loyal customers to the likes of Edius and Adobe

so, if read all this correctly:

vegas 6 had some issues for some people
vegas 7 had some issues for some people
vegas 8 had some issues for some people
vegas 9 had some issues for some people
vegas 10 had some issues for some people
vegas 11 had some issues for some people

and we can assume vegas 12 will have some issues for some people?

Is that right?

Even so, after my personal testing about 10 of the top editing suites (not including FCP because it is on MAC) available for trial, I STILL found vegas to the be fastest, most useful editer out there, and probably will move on to 12. It was literally down to vegas and premier... and premier was too slow (on my gear), too bloated, and too over priced when compared to vegas.
I guess I'm turning into a fanboy. :)
I enjoy it everytime I fire it up.... and rarely have glitches. Maybe occasional rendering, but that seems straitened out now.
Compared to all the other proggys I tried, I'd say about HALF of them had weird malfuctions and I just gave up and uninstalled them. And I am a computer tech by trade, so I know what I am doing and run a tight, clean system.

Vegas FTW

(to me anyway)

Vegas is full of bugs/glitches. Heck I could write a white paper on it. Today in 8 hrs of editing I spent about 6 hrs in After Effects with zero crashes and 2 hrs in Vegas doing multiple short clips for AE. Vegas crashed at least 6 times for no apparent reason.

And today is another lesson learned about Vegas. It doesn't render Alpha channel on .mov png files. Oh that's been an issue for sometime I finally figured out. REALLY?

Oh an here is a stupid Vegas performance tip: When fps starts dropping just go into the project properties and click a button. Doesn't matter which one, I guess it just slaps the program and says stop slowing down.

Oh and when your external controller and Vegas stopping interacting minimize Vegas and then maximize. All will be good.

But always hit save after a few minutes of editing.

ditto I bought but hated 11 instantly so have been using v10 this past year+.

let's hope 12 is better though I'm not crossing fingers lol.

all vegas releases seem to cause bsods/memory crashes within a day or so after using them on my pc, will be upgrading to SSD soon though, that may help, memtest and no ram/temp issues, only within 24-48 hours after doing a vegas render, my pc is slow, vegas prolly still has mem leaks like many years ago

I've been out of the loop the past two years or so from Vegas (used to post a bit here & there as "Cclub" but that account is messed up some how). I just do projects now as a side business/hobby, and I've gone Mac and I've been trying to learn FCPX as my main NLE. You know what I always end up using: Vegas Pro (10... never saw the benefit of 11). It's comfortable, and the workflow makes sense. I thought I was going to be able to discard Vegas as I had my complaints also. Now, for me... Vegas is like the wife you think you want to leave until you're viewing the replacement options.

I do like some of the workflow of FCPX, but I'm actually quite interested in the Vegas Pro 12 new feature of "Smart Proxy Workflow." I know there are workarounds so you can do something like this in Vegas already, but if it works like they're saying it does... that's one of the best options in FCPX to bypass many of the system issues that people have with the high quality video these days. Ingesting original video files, editing with proxies, and then automatically rendering in top quality? Smooth like butta.