[Andreas Schwabe]

Hi Boris!

Thank you very much for the update! That’s very good news indeed and I appreciate the BorisFX team’s pursuit of a solution. In spite of this initial hiccup, you can see from the other comments in this thread, we all see the benefits of BBC7, but were irked by the crashes.

I look forward to unleash the power of BBC7 after the next Vegas patch.

Cheers,
~A

[Andreas Schwabe]

Okay, now I’m really confused. I seriously didn’t think the docking would make any difference (I thought it was just me). Well, I’ll pass along a note to the tech I’m corresponding with and let him know.

I haven’t tried the check/uncheck thing (it didn’t actually occur to me). Though, the docked effect stability is intriguing.

And I have to agree, since I end up doing a lot of green screen work (which I hate), NOT using AE and just doing it natively in Vegas is a huge plus…if only I could do it with confidence.

Keep me posted if you see anything else.

[Andreas Schwabe]

Hi Mark,

I’ve been in touch back and forth with someone at BorisFX but haven’t heard anything back yet in terms of diagnosis or fix.

While I’m sorry you’re having the same problems I am, I’m grateful I’m not going nuts.

Do me a favor: I have a habit of using the FX as floating panels. I’ve been trying everything, and one thing on my long list of “to try” is docking the floating panel. I tried it on my work system (haven’t tried it on an alternate system yet), but it SEEMED to give me a bit more stability. I have no idea what that could possibly have to do with anything, but I’ve had weirder things happen (like a network cable just spontaneously failing).

I’ll keep you posted, and please do the same if you find something that provides some stability. The plugins are really good, but right now I can’t rely on them.

[Andreas Schwabe]

Hi. It looks like BorisFX has recently posted updates to BCC7 for Vegas Pro 10. I’m happy to report that it’s quite stable on my system and for my use (which is basic keying of interviews /testimonials and scripted dialogue shot against green screen).

Download the trial from the BorisFX website. There may have been some issue with my hardware, but whatever they did in version 4.0.3 seems to have improved stability from the consistent crashing I was seeing. That said, I’ll run tests for a couple of weeks and then migrate from AE (if BFX is finally more stable, it’ll be a huge improvement in my workflow, since the keying tools (Chroma Key and Matte Choker) and very good.

[Andreas Schwabe]

RAM definitely shouldn’t be an issue in my case. i7 920, 12GB of RAM, and 4 TB of drive space, running Win7 64-bit. ATI Radeon 4870.

Sadly, the problem is easily reproducable. You can see a video of an example crash at https://www.schwabe.ca/video.html

I have already submitted a report on the BorisFX website (twice – a week apart but haven’t heard back yet at all).

Thanks,
~A

[Andreas Schwabe]

I knew about the millions+ for rendering RGB+Alpha, but the only colour depth NOT greyed out was just the simple millions. I tried 8/16/32 bit projects, and finally was just testing using white text as a single layer for the simplest possible scenario.

The fact that the PNG compression in the output module suggests it’s a 64-bit issue. I have a second system in my office and one at home. One is XP (32) and Vista 32 at home. Both of those have no problems with rendering the exact same project files with RGB+Alpha. That said, it worked fine before QT updated itself and installed 7.6.4. Uninstalling it and rolling back to QT 7.6.2 hasn’t helped.

I’m just grateful Kevin replied because I was losing my mind (I don’t mind rendering projects at home, but it just adds a step, and any number of other weird idosychrasies my work system might have versus my system at home.

Trillions of colours sounds excessive to me too, but even the banding I get in 8 bit projects makes me crave more colour depth and headroom for whites and blacks. I’m not even using any superwhites (or in my most recent project, superyellows), and yet the colours always seem blown out when I compress to MPEG. But we’ll always solve problems and then create problems inherent to the solution. I personally love the mantra of a friend of mine who has some real weirdness on his Mac (he is of the Hunter Kressel school of Mac editors): “Working on a Mac is like seeing the doctor about an ailment…’it hurts when I do this.’ ‘Then don’t do that.'” 🙂

[Andreas Schwabe]

Kevin, you are the man….the problem is basically solved.

QT was 7.6.4 (latest), and AE is also up-to-date at 9.0.2.

I rolled back to Quicktime 7.6.2, but the problem persisted. To make sure I got everything I cleaned out everything QT from the registry. Same results.

I just rendered out a lossless to PNG, and RGB+ALPHA was actually the DEFAULT output (once I punched the color up to millions+).

It wasn’t quite as crisp as a normal but when I set it as pre-multiplied it looked much better.

So, again, my gratitude for your help!

Clearly there’s some weird glitch with QT and how its allocating colour depth in 64-bit.

For the record, this is my second QT problem. The first was actually any time I hit the “audio” tab in Vegas when rendering output as a QT file. There’s also a weird mp4 issue, but that’s for another day. For now, I’m going to start rendering my comps out with QT/PNG and get caught up.

~A