What is the most specific information about the release date of MC v3.0?

I am upgrading from 5.8 EXPro (PC) and I will also upgrade to Vista so that I can use the 64-bit architecture of my workstation.  That will require a clean install of the OS so I don't want to waste time installing 3.0 at 32-bit and then having to do it all over again.  But I'm also starting a new project and I may have to do that if the launch is late-June or even later.

Please tell me what you've heard.  Thanks.

There is no firm date. Sometime in June is the target date but that is not set in stone.

You do know that 3.0 will be ONLY 32 bit...right?

Supported operating systems

• Microsoft Windows XP Professional SP2 (32 bit)
• Microsoft Windows Vista Business SP1 (32 bit)*
• Microsoft Windows Vista Business SP1 (64 bit)*
• Apple Mac OSX 10.4.10 for version 2.8 software (not supported on v3)
• Apple Mac OSX 10.5.2 (Leopard)*

We must clarify this before we buy Vista.

Here it is loud and clear and clarified. MC 3.0 will be a 32 bit application. From what I understand, it will run in 64 but will not be a 64 bit app.

BLKDOG:

Here it is loud and clear and clarified. MC 3.0 will be a 32 bit application. From what I understand, it will run in 64 but will not be a 64 bit app.

What?

What's the point into that?

I mean 64bit CPU and OS with a 32bit app will slow it down.

MC3 is 32 bit code that will run under Vista64. It is not 64 bit. The only real benefit for now is that you can tap into a ton of RAM. Currently WinXP only uses 3GB of RAM, although you can run with more, it's not being fully utilized.

With Vista64 the max RAM number is far beyond the slots any mobo has today. I think the max I've seen is 8 sticks which if you use 2GB is 16GB or RAM.

I don't like Vista32 one bit, but we will be putting Vista64 on one of our machines with 8GB of RAM, just to see what kind of imrovements we get with MC3.

Gary

Gary it will slow it down.

And I think this could add more compatibility problems.

sverkalo:

What?

What's the point into that?

I mean 64bit CPU and OS with a 32bit app will slow it down.

Don't know but that's  the way it is so I just want everyone to be aware.

Also, and let's all be real clear about this too. My best advice to EVERYONE on these forums  that intends to load 3.0 on Vista when it is released:

Install Vista as a second partition and continue to run XP on another partition.

Vista is very new to everyone, including Avid. My feeling is that releases subsequent to 3.0 will be much stronger than the initial release. So, do yourself a big favor and leave yourself an out.

sverkalo:

Gary it will slow it down.

And I think this could add more compatibility problems.

Laptopeditor:

Why bother making MC 3.0 compatible with a 64 bit operating system if you don't make it a true 64 bit application ?

This is probably Avid's strategy to transition from 32 bit to 64 bit (Vista support first). 64 bit support requires major rewrite of the underlying code. This takes time (see FCP, Adobe, etc, etc). Also, remember that Avid NLEs is not the only app you will install in your computer. An Avid editor may need to run a 64 bit version of another software. It would be smart to not hamper your clients with Windows XP 32 bit- not to mention Windows XP is getting harder and harder to get.

With 64 bit OS, at least the OS can address more RAM thus allow more RAM to several applications at once. With Windows XP 32 bit, your Avid is sharing the same 2.75GB of RAM as with your AE or Photoshop.

Dom Q. Silverio:

This is probably Avid's strategy to transition from 32 bit to 64 bit (Vista support first). 64 bit support requires major rewrite of the underlying code.

BLKDOG:

Install Vista as a second partition and continue to run XP on another partition.

This is a great advice. But not exactly.

When I was first using Liquid I have discovered that I have to play some games but also that this could mess things in some ways.

Then I decided to have a dual boot disc.

One for Liquid and XP and another for Liquid.

I will do the same here. One for Liquid and everything else.

And another one faster (10.000rpm raptor) for MC.

But not partition. Another disc is the best option.

Dom Q. Silverio:

64 bit support requires major rewrite of the underlying code. This takes time (see FCP, Adobe, etc, etc).

Not sure if Windows is the same, but from what I remember Linux at least defaults to 32-bit ints and 64-bit pointers in 64-bit x86 mode; so unless you're doing weird pointer tricks it's just a recompile and some testing. I'd suspect Microsoft have done the same to minimise the difficulty of switching over, and the extra overhead of testing both versions is likely the biggest reason why most companies don't release 32-bit and 64-bit versions of their software.

Back when I was developing code that ran on Sun, Alpha and Mac in the 90s, supporting 64-bit was as simple as remembering to use our pre-defined data types and not copying pointers into integers (which is bad in any case).