jasperfdo:

I heard Lucas speak at Fox a couple years ago, and he mentioned he's working or wanting to work on a new NLE that is more intuitive or something like that.  If and when he does that....wow...that would revolutionize things.

He did it before and I can think of no one better qualified to do it again. The ancestor of Media Composer was a pre-ILM George Lucas creation known as "EditDroid".

Atomike:

Contrary to some posts, you don't need a top of the line machine to run Vista. If you've purchased your machine in the last 3 years, you'll be just fine. To say you need a top-of-the-line machine to run Vista well is simply factually wrong. I don't want to sound patronizing, but I simply have to wonder where some folks here get their information.

If this is in reference to my post, my information comes from personal experience. My laptop (hp dv2500) was purchased in January and has a "Vista experience" rating of 4. I have Aero and auto indexing turned off. Core 2 Duo 1.8Ghz processors with 2Gig of RAM. I installed the updated Service Pack and upgraded the Vista Home to Vista Ultimate.

Vista just doesn't perform well for me. I have read other users with 64bit systems with 8+ Gigs of RAM that are extremely happy with Vista to the point of sounding like Mac fanboys. For me, it just doesn't work.

Your system specs are just fine for Vista. If you're having slow-down problems with your machine (especially with Aero off) then you have some other problem, which is not related to Vista. Perhaps a bad stick of RAM, or a spy-ware or virus infection (most likely solution).

With your hardware specs, Vista runs like a champ. So, you may want to look into other issues and find the real problem, rather than simply throwing up your arms and blaming the OS.

Laptopeditor:

 ...OK Brian. I got a few warnings that I was running out of memmory running MC 3.0 and I never received this warning before. (??) Is MC 3.0 more memmory intensive than 2.8.3 ? I have 4 GB of Ram installed. I was wondering if going up to Vista 64 bit with my HP nw 9440 would solve this issue, since I would then have a full 4 GB available in my machine to address to Avid. 

 Theoretically it should help.  We worked hard to keep the memory footprint of the application down, but it's hard to have a zero increase in footprint when you add significant new features.

Vin:

 

Brian,

 

Does render acceleration work with approved quatro cards in Vista Business 64 as it does in XP Pro with MC 3?

 

Thanks

Hi Vin,

I believe there were issues with the Vista 64 nVidia driver that reduced performance of GPU accelerated affects when compared to Vista 32 or XP.

Atomike:

Your system specs are just fine for Vista. If you're having slow-down problems with your machine (especially with Aero off) then you have some other problem, which is not related to Vista. Perhaps a bad stick of RAM, or a spy-ware or virus infection (most likely solution).

With your hardware specs, Vista runs like a champ. So, you may want to look into other issues and find the real problem, rather than simply throwing up your arms and blaming the OS

Windows XP and OSX Tiger run like champs. Vista and Leopard both have bug issues that are being worked on and both have hardware and software compatability issues. Just depends on how many extra problems you want to introduce into your everyday editing life. I'm sure that both new OS programs will smooth out in the next year.

bobcat:

Vista and Leopard both have bug issues that are being worked on and both have hardware and software compatability issues. Just depends on how many extra problems you want to introduce into your everyday editing life. I'm sure that both new OS programs will smooth out in the next year.

Couldn't have put it better myself.

Brian Williams:

 

Laptopeditor:

 ...OK Brian. I got a few warnings that I was running out of memmory running MC 3.0 and I never received this warning before. (??) Is MC 3.0 more memmory intensive than 2.8.3 ? I have 4 GB of Ram installed. I was wondering if going up to Vista 64 bit with my HP nw 9440 would solve this issue, since I would then have a full 4 GB available in my machine to address to Avid. 

 Theoretically it should help.  We worked hard to keep the memory footprint of the application down, but it's hard to have a zero increase in footprint when you add significant new features.

If it has to bei Vista, I'd go for vista64, especially as your system has 4gb of ram. the theoretical performance loss with small projects due to 64 bit address management may be measured, but surely not felt, but you'll gain a lot of performance once your memory footprint reaches 32 bit limitations.

macjaeger:

the theoretical performance loss with small projects due to 64 bit address management may be measured, but surely not felt, but you'll gain a lot of performance once your memory footprint reaches 32 bit limitations.

I can only confirm this. I have been running MC3.0 for a few days on Vista Business 64bit and after disabeling all the eye candy (Aero and the like) and tweaking the OS the same way as XP pro before, the system is flying. Very responsive!

In MC3 I cannot see or feel ANY performance loss at all. Large bins seem to open a little quicker, but this may just be subjective. Avid startup and shutdown seems to be faster but this is certainly not relevant for editing.

I was expecting to run into trouble and to find loads of bugs with MC3 under Vista 64, but couldn't find any so far (I kept MC2.8.1 on my other workstation with XP Pro, just in case).

There were also no problems with all my third party applications and plugins (well, so far!).

I'll post back as soon as I find any major bugs.

AquaPix:

macjaeger:

the theoretical performance loss with small projects due to 64 bit address management may be measured, but surely not felt, but you'll gain a lot of performance once your memory footprint reaches 32 bit limitations.

 

 

I can only confirm this. I have been running MC3.0 for a few days on Vista Business 64bit and after disabeling all the eye candy (Aero and the like) and tweaking the OS the same way as XP pro before, the system is flying. Very responsive!

In MC3 I cannot see or feel ANY performance loss at all. Large bins seem to open a little quicker, but this may just be subjective. Avid startup and shutdown seems to be faster but this is certainly not relevant for editing.

I was expecting to run into trouble and to find loads of bugs with MC3 under Vista 64, but couldn't find any so far (I kept MC2.8.1 on my other workstation with XP Pro, just in case).

There were also no problems with all my third party applications and plugins (well, so far!).

I'll post back as soon as I find any major bugs.

Bjerregaard:

Dose that mean we can load Vista x64, load it up with LOTS of memory and run MC happily?  Strongly suspect that the answer is "only if MC is written as an x64 application."

You can run MC 3.0 on vista x64, take a quick search tour through the forums to find proof. MC still is a 32bit application though, this will cause _slightly_ less performance on x64 systems, but the effect is barely noticeable, if at all. With memory intensive applications - which Avid MC surely is - the performance loss is far outweighted by the performance sustainance in complex editing situations. In other words: MC 3.0 may be a little slower on vista x64, but it will keep it's performance up longer when things get rough. And even though 32bit apps won't benefit from 8GB or more ram, your system as a whole might benefit when running multiple memory hungry applications concurrently.

macjaeger:

And even though 32bit apps won't benefit from 8GB or more ram, your system as a whole might benefit when running multiple memory hungry applications concurrently

I can vouch for that. Vista 64 on a fast machine with lots of RAM is very fast when tweaked (eye candy and other stuff disabled). I can see no benefit  using Vista 32 over XP Pro though.