64bit OS, 32bit application, 8 gb ram ?

[swsw1550]

Imagine you have a 64Bit Edius Code sometime in the future - not only a 64Bit NX Driver as announced - and you have as much of e.g. 8 GB or more memory in your workstation.What do you think would happen with the Edius Performance ?
I was in the SW development business when we changed from 16bit to 32bit environment and do not understand the big problem they build around this change from 32bit to 64bit.
In principle it is to build a 64bit development environment and to take the 32bit source code and to compile it with the 64bit compiler.Nothing more - I accept that there may be some adressing errors but those to fix is not the big problem.
So don't believe your programmers it is not the big work !

I agree with you 100% on this, I have been saying the same thing to companies for a long time, But we always get the same reply from a lot of them, (when it is more main stream maybe!)

Cheers
Steve

[BobGiff]

I just added another 4 GB last week. No science behind this but the system feels more stable. Edius, After Effects and Photoshop all open and using the extra memory. Real smooth. Running 64 bit Vista Ultimate.

[Crespel]

Imagine you have a 64Bit Edius Code sometime in the future - not only a 64Bit NX Driver as announced - and you have as much of e.g. 8 GB or more memory in your workstation.What do you think would happen with the Edius Performance ?
I was in the SW development business when we changed from 16bit to 32bit environment and do not understand the big problem they build around this change from 32bit to 64bit.
In principle it is to build a 64bit development environment and to take the 32bit source code and to compile it with the 64bit compiler.Nothing more - I accept that there may be some adressing errors but those to fix is not the big problem.
So don't believe your programmers it is not the big work !

[swsw1550]

Hi guys a bit of information that might help you's out, There are two memory limitations in Windows that are mutually exclusive - the OS's 4GB limit and the 2GB Win32 application limit. Every 32-bit Windows application has a 2GB limit, but you're forgeting that there are probably 30+ applications running on your machine at any given time (background processes, anti-virus, IM, etc.), so even though the app has a limit, the more memory that is available to the OS the better. This is the reason these 32-bit apps will only use up to 2GB on the 64-bit version of Windows.

The OS limit has to do with address space reserved for devices in the mahince. Typically a 32-bit versions of Windows will show 2.5 - 3.4 GB of available memory when 4GB is installed in the machine. 32-bit Windows technically has a 4GB limit, but that can be extended through machanisms like PAE.

There are pros and cons to running 64-bit now, even though the apps you're going to run are 32-bit. Because the OS can natively access much more memory, older 32-bit application will each have their own full 2GB where avaialble. You also benefit from the security of running a native 64-bit OS.
Every manufacturer has been releasing 32 and 64-bit drivers concurrently as of late, so driver developments on both sides is about equal now. And MS has done a good job of patching the OS for performance and stability. The ONLY applications I had to sacrifice to make the switch were applicationst that weren't Vista compatible - it wasn't because they weren't 64-bit compatible. (FYI the apps were from MS)

Don't think of your upgrade strictly from a memory perspective. You've got the 4GB of RAM, keep it and use it. If you want to do less tinkering and be more confident your apps are going to run, stick with 32-Bit Vista. If you're willing to potentially sacrifice some applications for the sake of compatibility (and this is only a maybe) and want the benefits of a 64-bit OS, make the switch.

cheers
Steve

[GrassValley_BH]

32-bit applications still have an addressable memory limitation (2-3GB), but running in 64-bit Windows, Windows itself has more RAM to parcel out.

Case in-point, allowance...
Sa you have 4 children...
As a 32-bit parent, your wallet can only hold $40 maximum.
The "house rule" is that 32-bit children can only have $20 maximum in their wallets, lest they go run off and do something naughty with it.

So as a 32-bit parent you can only afford $40 on your children's allowances, so each of your 4 children (assuming you love them all equally) now gets $10 each. The children might fight or come up with some arrangement so sometimes 2 children have $20 each and the other 2 children are broke that week. Or they might come up with some other allocation but no matter what, there isn't a situation where all children have full wallets, because that would require 4 x $20 = $80, and you just don't have $80 to give your kids.

Now upgrade your job and you're a 64-bit parent. Now you can afford $160 for your children's allowance because you're a rich yuppie now. So now your children can all get full wallets at $20 each, and you still have $80 leftover, because your children still can't have more than $20 in their wallets.

Moral of the story: I didn't get an allowance, so this is all foreign to me. Oh, and a 64-bit OS has more RAM to parcel out, but it doesn't change the amount of RAM that each application can accept (smaller limit for 32-bit apps).

[GrassValley_KH]

If this thread becomes an OS debate, I have this padlock button here...

[STORMDAVE]

32bit apps work fine under Vista x64. They are limited to 3GB per application though, but if you have memory hungry apps such as Photoshop, After Effects, it can run along side EDIUS without a problem. You can switch between them without a slow down through ALT+Tab.

[rando]

I heard when SP2 comes out it will have a new state of the art installer! That automaticlly uninstalls VISTA SP1 and installs Windows XP SP3! Seriously the only issue I have with VISTA is the security and the fact that it uses almost a gig of memory just sitting there.

[STORMDAVE]

Windows 7? I think that's the next major OS that will be released in 2010.

[Jerry]

Vista x64 SP1 is ok but nothing to get excited about. It has it's fair share of problems which I'm sure will be fixed in SP2, but that won't be for another year or two.

And I believe it will be called something else.

[STORMDAVE]

Vista x64 SP1 is ok but nothing to get excited about. It has it's fair share of problems which I'm sure will be fixed in SP2, but that won't be for another year or two.

[Jerry]

Jerry, what you need to keep in mind is that Vista handles memory quite differently to say, XP. You can't compare the two.
Despite some adverse comments, Steve and I and many others really enjoy the benefits of Vista with editing, particularly memory and obviously so does Canopus because Vista compatibility is its primary focus this next release.

I'm definitely considering it because of CS4 later this year or early next.

[redgum]

Jerry, what you need to keep in mind is that Vista handles memory quite differently to say, XP. You can't compare the two.
Despite some adverse comments, Steve and I and many others really enjoy the benefits of Vista with editing, particularly memory and obviously so does Canopus because Vista compatibility is its primary focus this next release.

[Jerry]

The benefit comes from an overall Windows computing perspective - more ram means less disk thrashing with a swapfile.

More ram means, that while EDIUS' buffer setting remains capped at 512MB, the remain system ram can assist in clip loading, task switching, and also having other applications running (e.g. Photoshop).

But yes, I'm sure Brandon has a better explanation up his sleeve (with a good analogy, too).

I thought that might be the case, just was not sure.

You could have tried an analogy. Hey, why not make Brandon proud!

[GrassValley_KH]

The benefit comes from an overall Windows computing perspective - more ram means less disk thrashing with a swapfile.

More ram means, that while EDIUS' buffer setting remains capped at 512MB, the remain system ram can assist in clip loading, task switching, and also having other applications running (e.g. Photoshop).

But yes, I'm sure Brandon has a better explanation up his sleeve (with a good analogy, too).