Replies – Forums – Stephen Brooks

Forum Replies Created

Page 1 of 2

1 2 →

Stephen Brooks
April 8, 2009 at 8:43 pm in reply to: AfterFX.exe fails to start – cannot find FLT.dll

Yes, that’s exactly what happened. Thanks for the tip!
Stephen Brooks
May 8, 2008 at 12:37 am in reply to: AfterFX.exe fails to start – cannot find FLT.dll

Cliff! Perfect timing. The problem cropped up again last night as I updated Premiere Pro to 8.2.

Thanks!

Stephen
Stephen Brooks
April 2, 2008 at 6:24 pm in reply to: AfterFX.exe fails to start – cannot find FLT.dll

I forgot to mention:

Gateway FX540b Vista Home Premium. Have not applied SP1 yet.
Stephen Brooks
January 9, 2007 at 6:17 pm in reply to: IMPORTED AAF IS DROP FRAME WHEN ORIGINAL PROJECT WAS NON DROP

Turns out this is a bug. Avid has my aaf to test. At least I’m not crazy!

Thanks for all the suggestions.
Stephen Brooks
January 6, 2007 at 10:59 pm in reply to: IMPORTED AAF IS DROP FRAME WHEN ORIGINAL PROJECT WAS NON DROP

I just re-imported the AAF into a new Premiere project and it comes in as NDF. So it must be an Avid issue. Any other ideas?

Thanks.

Stephen
Stephen Brooks
January 5, 2007 at 5:41 pm in reply to: IMPORTED AAF IS DROP FRAME WHEN ORIGINAL PROJECT WAS NON DROP

Yes it is a sequence. All the clips are DF as well. When I try to change the sequence to NDF (right clicking, modify) I get an error message saying I cannot do that. When I try to modify the clips Avid crashes. It just disappears. No error messages.

Thanks for your insights. I’m still not sure this isn’t a Premiere export problem. But I have no way to test that.
Stephen Brooks
February 25, 2006 at 12:07 am in reply to: cannot make ISO

Hmm. Well, here’s how I solved my problem: I save the project, then started deleting things: clips, timelines, menus, everytime I deleted something I tried a preview until I found what the problem was.
Stephen Brooks
February 24, 2006 at 4:50 am in reply to: cannot make ISO

I got the same \Vobulator|TitlePlanner|CVOBUPPlanner.cpp,line331 error on a project imported from 1.5. So I started from scratch in 2.0 and got the same error. I’ve tracked it down, at least in my case.

The problem was a timeline with 4 clips. (Video and sound) I added 7 frames of black at the head with no sound. When I added the other 3 clips after it and tried to preview I got the error message. So I created 7 frames of black with sound. No error. I guess 2.0 doesn’t like a clip without sound on a multiple clip timeline.

Hope this helps.
Stephen Brooks
September 1, 2005 at 12:41 am in reply to: Premiere Pro 1.5.1 AspectHD HD Component output problem

It was a bios setting. I had already disabled the motheboard’s built in video controller, but I had to change one other setting. Don’t remember what it was but I’ll post it for future reference.

You can stop searching. It works!

Thanks for all the help.
Stephen
Stephen Brooks
August 31, 2005 at 11:12 pm in reply to: Premiere Pro 1.5.1 AspectHD HD Component output problem

Hi Tim:

Actually my case seems to be unique. Others have had flickering displays and scrubbing problems which I though might be related to my issue but Thad at Cineform thinks not.

Here’s my system:

Intel D945GNT MB
P4 D 2.8 ghz Dual Core
2 Gig DDR2 SDRAM
Nvidia FX540 with latest approved drivers. Bios 5.43.02.64.35
Seagate Serial ATA 300 gb C: drive
Maxtor 160gb Serial ATA E: driver for video/capture etc.
Sony MD-81 LCD as Display 1
Philips 17PF8946 Flat screen HD monitor
Connected from breakout box to component HD input
XP Pro SP2 and all recent updates
DX 9.0c

Premiere Pro 1.5.1
Aspect HD 3.3

Page 1 of 2

1 2 →