I'm not sure either Mark.

There might be more than just pointers. In Mac, some developers are faced with the Carbon vs Cocoa transition. For Windows? Don't know.

I was told specifically by Sales at Avid that the 3.0 version would support 64-bit within the Vista upgrade.  There was no equivocation and I was extremely specific about wanting that.

Peter is seems it will support 64bit just fine.

It is that as some said isn't a 64bit app itself.

Then, unfortunately, you may have been mis-informed. Most sales people don't know the difference between 64 bit and 32 bit.

Again, 3.0 will be a 32 bit app running in a 64 bit OS. It will support the 64 bit OS but the app itself  will not be.

 Thanks for the words of comfort.  It seems like my only decision now is whether I want to create a dual-boot with XP and Vista 64-bit.

Thanks.

At least we would be able to run all of our memory.

Inmy case XP SP2 sees only 3, meaning I miss a whole 1 GB of real ram.

sverkalo:

At least we would be able to run all of our memory.

Inmy case XP SP2 sees only 3, meaning I miss a whole 1 GB of real ram.

Well unless I am mistaken (not a software engineer, so some one can step in and correct me) it can be even more. For example if your system has 8 GB of RAM under Vista 64 bit, Avid can take 4 GB while AE can take the other 4GB. Currently, Windows XP 32 bit must share the same 4GB (actually less) for both apps.

You are right BUT my system has only 4G.

MarkG:

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).

Yes, Mark, that's all quite true.  But remember, there's buckets of legacy code in Avid written by a range of programmers.  Would you like to guarantee that none of those programmers have used 32-bit overflows to change state, or treated a boolean false as numeric -1 or 4294967296, or any of a host of other "quick and dirty" approaches that rely on knowledge of how numeric values are stored in 32 bits.

I would welcome a conservative approach to moving Avid to 64 bits.  I'm also enough of a realist to believe that no matter how careful they are, in 5 years time there will still be 32-bit/64-bit bugs being found in Avid's code.

 Is the current avid hardware, Adrenaline/Mojo going to be compatible with vr3? Obviously it will not work in the way the new hardware does but will it work at all?

 It will.

SDNY:

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

Please tell me what you've heard.  Thanks.

hi sdny,

i received an email invitation from our avid dealer for June 5th. It says they going to show

Media Composer® (v3.0), NewsCutter® (v7.0) und Symphony™ (v3.0) and even

the Mojo DX und Nitris® DX. (On windows vista and Mac OS 10.5.3)

I´ll go and have a peek.

regards

fsd

Just to clarify, FSD is just mentioning a reseller event on June 5th.

There is no release date yet set of MC v3.0.

sverkalo:

At least we would be able to run all of our memory.

Inmy case XP SP2 sees only 3, meaning I miss a whole 1 GB of real ram.

 No,

XP sees 4 GB, but allocate max 2GB to one program. The 3GB hack from Avid increase this to 3GB. In addition to the program, XP must have RAM to it self and lots of services, and other program.

We get off topic here but this is what my XP sees.