Stuck in 32bit land because of Magic Bullet Looks?

Brad C. schrieb am 01.03.2010 um 10:26 Uhr
Hey everyone,

Long time no post. I guess thats because Ive been doing quite well with 9c and haven't had too many complaints really.

Lately though I've been seeing more and more people jumping on the Windows 7 bandwagon (and for mostly good reasons) and so of course it gets my curiosity going. And at the same time I have been creating more and more complex color grading "Looks" with Red Giant's Magic Bullet builder, which is causing some really unwanted memory issue when rendering my videos.
I know that 64bit is obviously the way to go to release the memory hounds and take care of the issue. However, Red Giant has pretty much said that they have no intention on updating MBL for us Vegas users that will/are on 64bit. Its stuck in 32. I rely heavily on this software. So I have three questions for you guys if you would be so kind to comment on:

1- We all know that Vista has up to this point matured into a much more mature OS. Not awesome by any stretch of the mind, but certainly better than day 1. Would going to Windows 7 32bit OS help at all with some memory management to where it would better handle things using Vegas 9c and MBL together? (i.e. maybe not crashing out so much because of RAM)

2- If 64bit is a MUST have, then what is the logical and somewhat reasonable work around for using MBL stuck on 32bit and yet rendering the complex files in 64 bit so it will go though cleanly with plenty of RAM?

3- Are there any other color grading software platforms out there that are as easy and powerful as MBL that work with Vegas 64bit? Trials available?

Thanks in advance for any help/insight.

-Brad

Kommentare

ushere schrieb am 01.03.2010 um 10:42 Uhr
using 7 / 64bit os.

this is my general workflow IF i need 32bit fx:

compile / rough cut in 64bit

do what i need / can eg. fx in 64bit

into 32bit for mb and stuff i can't in 64bit.

render the fx'd 32 bit bit's to new track

return to 64bit for final render.

seems to work ok
Brad C. schrieb am 01.03.2010 um 13:03 Uhr
That sounds like an ok workflow, but there aren't just little bits that I use MBL for, it's for entire projects. Every scene/clip/section I use uses it.

Thanks.
TLF schrieb am 01.03.2010 um 15:21 Uhr
I feel your pain! MBL in 54 bit would be great, but it ain't gonna happen...

Instead, I use AAV ColorLab. Completely free, and uses the GPU. No instant looks like MBL, but with a little tweaking you can achieve some good results that render far quicker than MBL.

More here: http://aav6cc.blogspot.com/

Oh, and it works with 32 and 64 bit versions of Vegas (2 downloads/installers required).
Ehemaliger User schrieb am 01.03.2010 um 16:48 Uhr
I actually mirror ushere's workflow.

I cut and do everything I can in 64-bit, then move to 32bit and render what I need to there (and yes, occasionally, it's an entire project).

I'm actually frustrated with Red Giant. I've used their lens flare plugin in AE (sparingly) and it's a hassle. Video Co-Pilot now has a new lens flare plugin for AE that is, in a word, stunning.

Often, figuring out workflow is the trickiest bit of business. It's not bad. It's just another step...but it's still annoying (Ya hear me Red Giant?! (shakes fist in air)).
Brad C. schrieb am 01.03.2010 um 23:13 Uhr
I really wish that would work for me, however, my biggest issue is rendering the really intense color grading, and since that has to be done in 32bit then the 64bit OS really doesn't do me any good.

I really wish they would just do it already. They have had plenty of time to do so. Vista 64bit has been around for some time now. What could the hold up be?
rs170a schrieb am 01.03.2010 um 23:15 Uhr
What could the hold up be?

My guess is that, from their standpoint, the Vegas user base is too small to make the investment worthwhile.

Mike
Brad C. schrieb am 01.03.2010 um 23:32 Uhr
I'm obviously no software developer, but if it already exists in the 32bit form is it really night and day difference to make the 64bit variant? As in does it have to be rewritten from the ground up again? If that is the case, then I guess that it would make sense that they are not worrying about it right now.

I guess I will be trying the AAV Colorlab software. This isn't a solution though, this is a band aid on a broken leg. :(
john_dennis schrieb am 02.03.2010 um 00:28 Uhr
It is likely that rewriting 32 bit applications to 64 bit is not a trivial undertaking. If it was easier, there would be a lot more 64 bit code out there in all areas of computing.
Brad C. schrieb am 02.03.2010 um 10:35 Uhr
John, makes sense I guess.

Does anybody have any personal experience with Windows 7 32bit OS vs Vista 32bit? Now I know that 32bit is stuck at 3gig of RAM, but what I'm still curious to find out is if Win7 handles the memory better than Vista currently does. That may be a consideration for me as I'm more concerned with my color grading at this point. I'm fine with a render taking its sweet time to get done as long as it doesn't crash!
Jøran Toresen schrieb am 02.03.2010 um 12:33 Uhr
Brad.

You can use MB Looks and MB Mojo in Vegas Pro 32 bit in Vista 64 bit OS (and probably in Windows 7 64-bit). But the MB programs does not work in the 64 bit version of Vegas Pro. I have Vista Ultimate 64 bit with 12 GB of RAM and have no problems running these MB programs. And you can install both the 32 bit and 64 bit version of Vegas Pro if you use a 64 bit OS (Vista or Windows 7).

JøranToresen
Brad C. schrieb am 02.03.2010 um 17:22 Uhr
Joran,

It is my understanding that even though oneself might be on a 64bit OS and running 16gig of RAM, it doesn't really matter when you use the Vegas 32bit 9.0c and MBL, it will be limited to 3gig of RAM. Correct? This is my problem.

I have 4gig of RAM installed but only 3gig on tap because of the OS version. When I render my projects even in smaller 5 minute pieces, it will slowly keep eating away at RAM until only 850mb is left and will hang there for as long as possible and then crash. I have done B3Ts hack and everything else I know to do.

Sorry for the venting rant session guys.
john_dennis schrieb am 02.03.2010 um 20:43 Uhr
Bring up the Microsoft calculator and change the view to Programmer /Binary/Qword. Enter "1" 32 times.
Change from Binary to Dec (decimal) and you will get a decimal result 4,294,967,295. That is the number of unique address positions that 32 bits can physically address. If you subtract about a GB from that number for operating system overhead and other "folderol" you'll see why "around 3 GB" is the memory that an application has available for use under a 32 bit OS.
Using a 64 bit OS, and lots of memory, you could conceivably have multiple 32 bit applications allocated and addressing memory amounts close the maximum for the 32 bit system but no individual application could address more than the amount that 32 bits could address.
This pretty much exhausts my knowledge of the subject. My mind gets really numb when I have to think about virtual memory.