[Scot Walker]

[Bj

[Scot Walker]

I’m confused.

The 64 bit of Cinema for Windows is a separate version and 3rd party plug-ins require updating to work with it. It requires a 64 bit Windows and a 64 bit X86 processor.

You have a 64 bit version and a 32 bit version, for Windows.

If that’s not separate code base, what is? Maybe I’m wrong. I’m no CS major, obviously, so any explanation is very much appreciated. 🙂 Maybe “code base” isn’t the proper term.

But if Maxon were to update Cinema for OS X Tiger, there would still only be the one version of Cinema for the Mac. Like Motion 2, the one Cinema 4D would work in Tiger on a G5 and give us more than 4 gigs of RAM, and it would also work in OS 10.3.9 on a G4. I also noticed that Motion 2 for OS X uses 32 bit plug-ins just fine.

BTW, why doesn’t Cinema use more than 2 gigs of RAM? Thanks!

[Scot Walker]

One other point – isn’t Maxon keeping two different code-bases for Cinema on Windows now? 32 bit and 64 bit? That wouldn’t be necessary with Cinema for Tiger that accesses more than 4 gigs of RAM like Motion 2 does. Maybe Apple’s method is better for that reason alone?

[Scot Walker]

I’m guessing that Apple won’t go full 64 bit, breaking compatibility with 32 bit applications, for a very long time, especially when there isn’t any real benefit for doing so.

I’m speculating, obviously, but I think Maxon could make the Mac version utilize more than 4 gigs (it doesn’t even use 4 gigs yet, so what’s up with that?) and require Tiger and they wouldn’t have to update it again for a few years.

And I would assume that any changes they had to make to the application to utilize more than 4 gigs in Tiger would carry over to a 64 bit GUI version, so it’s not like efforts today wouldn’t be utilized in the future.

I could be wrong, but this is what I gather from reading.

If one of Maxon’s competitors comes out with more than 4 gigs access on Tiger, that might put a burner under Maxon’s seat.

[Scot Walker]

It is true 64 bit, it’s just the GUI isn’t 64 bit.

The math is 64 bit (128 bit, actually) and the memory addressing is now 64 bit.

There is no advantage in making OS X not be able to run 32 bit binaries by making it “fully 64 bit”, as far as I can tell.

[Scot Walker]

The only thing that isn’t 64 bit is the GUI, and there are supposedly some positives and negatives doing that.

I’m not knocking Maxon, I’m just saying that Motion 2 uses more than 4 gigs of RAM. I don’t know how difficult it was for Apple to do that.

[Scot Walker]

https://www.apple.com/finalcutstudio/motion/upgradeguide.html

Access to all the RAM your Mac can handle
Got boatloads of RAM installed in your system? Motion 2 can use it. With Mac OS X

[Scot Walker]

Apple’s Motion 2 is 64 bit. I wonder how they did it.

It would be nice if Cinema would use the 4 gig limit 32 bit applications have. I always assumed it did until I read that press release and the 2 gig barrier it talks about.

[Scot Walker]

OK. Thanks for the reply.

[Scot Walker]

Yes, great idea!

Please copy and paste the “What’s New” copy to this forum, if you get a chance.

Thank you!