Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

!! Premier 6.5 Crash

179 views
Skip to first unread message

Andrew Harwood

unread,
Dec 14, 2002, 4:09:41 AM12/14/02
to
I have upgraded to Premier 6.5 on my Shuttle SG51, Pent 4 2.2Ghz, 512Mb RAM, 80Gb Disk, ASUS8170DDR graphics on Win XP Home. All bits are using their latest versions of code and drivers.

The problem is that every time i start Premier is crashes if i select the standard DV PAL option and if i select the "Real-Time" option is says that the Project Initialisation has failed and that the DV/IEEE 1394 Playback is not setup correctly. Playback performance will be impacted. When I try to capture video from a Canon DV Mx2i camera, Premier crashes again and quits. The Fire wire works ok if i try to capture from microsoft windows movie maker stuff so I am guessing that the fire wire is ok. I have tried deleting the Premier prefs file etc. Can any one help or am i resigned to that fact that Premier 6.5 won't work?
Best regards,
a

Andrew Harwood

unread,
Dec 15, 2002, 3:10:16 PM12/15/02
to
I also got this infor from the events logger:

Faulting application premiere.exe, version 6.5.0.0, faulting module pm-dxm.prm, version 6.5.0.0, fault address 0x0000a272.

For more information, see Help and Support Center at <http://go.microsoft.com/fwlink/events.asp>.

Does this help?
a

Jeff Bellune

unread,
Dec 15, 2002, 7:21:35 PM12/15/02
to
Your fault module is part of Premiere's DirectX module and your fault address is what would typically show up in the video card memory address range. I suspect either a corrupt/outdated DX installation or corrupt/outdated video card drivers.

Jeff

James LeBlanc

unread,
Dec 16, 2002, 1:27:41 PM12/16/02
to
I've been having the same error messages: "DV/IEEE 1394 Playback is not setup correctly. Playback performance will be impacted." whenever I try to start a new DV project. Also, whenever I select DV/IEEE 1394 to capture, Premiere 6.5 crashes. My Adaptec 4300 firewire card works ok if I use microsoft windows movie maker to capture. Also, my ADVC-100 works just fine too. How did you resolve your Premiere 6.5 difficulties. Thanks.

ownby

unread,
Dec 17, 2002, 4:19:48 AM12/17/02
to

Andrew Harwood

unread,
Dec 17, 2002, 12:51:50 PM12/17/02
to
Hi Jeff & James. I still haven't been able to fix it. I have totally re-installed Win XP (re-formatted the disk), loaded all service packs, updates etc for the OS. I went to ASUS and got the latest drivers for the 8170DDR graphics card, updated pretty much everything else (including the systems BIOS - as a last hope effort). I then re-loaded the Premier 6.5 - I am unfortunately left with the exact same problem as described above. I cannot fix it - i think its a bug. Nice to know that I am not alone with this. How do we escalate this to Adobe? Patches will be welcomed.
Cheers,
a

Mark R. Bailey

unread,
Dec 17, 2002, 3:35:00 PM12/17/02
to
Have you the Prem60.ini fix?

Add:

[Override]
PreferDSCodecs=1

Andrew Harwood

unread,
Dec 18, 2002, 1:59:42 AM12/18/02
to
I haven't got a Prem60.ini file to add this to. I am using 6.5 and a search for the prem*.ini resulted nothing. Suggestions?
a

Andrew Harwood

unread,
Dec 18, 2002, 2:32:45 AM12/18/02
to
PS: I found the prmdef.ini and tried adding the line in that file - it made no difference - still got the warning messages and crashes.
a
Also upgraded to 1.2 of Adobe MPEG codec for a laugh.

Jeff Bellune

unread,
Dec 18, 2002, 8:14:06 AM12/18/02
to

I haven't got a Prem60.ini file to add this to. I am using 6.5 and a search
for the prem*.ini resulted nothing. Suggestions?


This is very bad. Even 6.5 has a Prem60.ini file. If you don't find Prem60.ini in your C:\Program Files\Adobe\Premiere 6.5 folder (or the equivalent if you didn't choose the default installation location), I'm guessing your installation is corrupt or incomplete.

Jeff

Andrew Harwood

unread,
Dec 18, 2002, 3:08:11 PM12/18/02
to
I installed using default settings several times. Once even after a total re-format and re-install of the OS and drivers. I guess me and James LeBlanc must have made the same error. That being said, I would still expact to chose custom install and still have the program work.
a

Andrew Harwood

unread,
Dec 24, 2002, 2:48:13 AM12/24/02
to
Does anyone else have any ideas that might help?

SNK4ever

unread,
Dec 24, 2002, 4:25:48 AM12/24/02
to
So if I understand you correctly Andrew, the problem happens before you can capture with your firewire?

If so, try loading Premiere in NTSC (even though I know you want to work with PAL) and see if it works. If you don't get any error messages, that's Premiere which have a bug with the PAL format.

Hope this can help a little. I use to have a lot of crashes with Premiere and my Matrox capture card along with my Canon DV cam but I solved them by doing what you did (reformating every drive and installing everything back) and since then, I haven't experience any problems. Of course, there's the fact that I'm still with Premiere 6.01 ;)

mike velte

unread,
Dec 24, 2002, 9:20:01 AM12/24/02
to
To eliminate the chance of a corrupt installation disc, try installing Premiere on another PC...even one without firewire if one is not available.

Andrew Harwood

unread,
Dec 25, 2002, 12:10:03 PM12/25/02
to
To SNK4ever - This happens as soon as the Premier application is started. Every time. I cannot even get to the point of trying to capture using Firewire. I tired your suggestion of using NTSC but the same thing happens - i.e. I get the warning message when I try using 'real-time' and a application crash when I use the standar mode.

To Mike Velte: I tried loading this on another PC - a Gigabyte 8IRXP, 768Mb Ram, 280Gb Striped RAID, WinXP home and the same ASUS 8170DDR graphics card that I am using on the Shuttle machine. It worked perfectly. Trouble is I can't use that machine all the time hence using the Shuttle. It looks like the actual media is ok.

Does this help?
a

mario aguilar

unread,
Dec 26, 2002, 12:22:44 PM12/26/02
to
HELP!
My Premiere 6.5 crash prblem is different:

1. I loaded in a file to the timeline (.avi DV capture file)
2. I created a title using the Premiere titling feature. set the back ground as "black alpha matte" to get the title to show over the video in video 1A)
3. Save the projedct

But when I render (enter key) I get the whole thing to work,,,,BUT
WHEN I HIT ENTER AGAIN TO SEE THE PROJECT AGAIN, PREMIERE
FREEZES UP THE COMPUTER!!!!

Any suggestions?

Dominic DeSantis

unread,
Dec 26, 2002, 3:39:05 PM12/26/02
to
Andrew,
Several months ago I had a similar problem. I tried all suggested fixes, none worked. Just by chance I read a posting about "window blinds". Uninstalled them and Adobe worked fine. Dont think so but maybee. I just upgraded my system and am now having several problems of my own including Adobe crashing. I am trying to replace my clips in a project, when rendering the timeline it for about 2/3 of the project and crashes??

Sondra Lowell

unread,
Dec 27, 2002, 3:20:39 AM12/27/02
to
What are window blinds? How do you find them to delete?

Dominic DeSantis

unread,
Dec 28, 2002, 12:10:10 AM12/28/02
to
Sondra,
Window blinds is a download you can use to create diffrent desktop settings. My response was way out in left field, however it sloved my problem and a prior unsloved problem a friend was having. I guess if you asked what they are, you have not used them, my adivse dont.

filmy

unread,
Dec 28, 2002, 12:59:34 AM12/28/02
to
This is interesting...here is what is going on with me. Premiere 6.2 worked fine...I am running Windows XP and "upgraded" to DirectX 9...now whenever I load premiere I get the error of "Error Connecting to Microsoft(TM) DV Drivers" and then the adobe error: "Project initialization failed" and th emessage about 1394 playback not being set up correctly. SO either this is a WInXP issue or a directX 9 issue. These are the only two things that changed...so it isn't a premiere 6.5 issue only.

filmy

unread,
Dec 28, 2002, 1:50:11 AM12/28/02
to
Ok so I solved thi sproblem for me - I uninstalled DirectX 9 and re-installed DirectX 8 off the XP disk. Rebooted...and now it works fine again. So this seems to be a Premiere interaction with DirectX 9 issue.

Andrew Harwood

unread,
Dec 29, 2002, 4:52:49 AM12/29/02
to
Filmy, I had the problem with DirectX8 so tried version 9 as well - same result. I'll try down grading again - just in case.
PS: I looked for the window blinds but couldn't find any reference on the forums.
Cheers,
a

Andrew Harwood

unread,
Dec 29, 2002, 5:11:24 AM12/29/02
to
I just tried re-loading v6.02 and got all this info from the crash:

Faulting application premiere.exe, version 6.0.0.0, faulting module dv-device.prm, version 6.0.2.1, fault address 0x0000a8b5.

the machine also wrote the following error log file:

<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="premiere.exe" FILTER="GRABMI_FILTER_PRIVACY">
<MATCHING_FILE NAME="AGM.dll" SIZE="610304" CHECKSUM="0xCD769FC4" BIN_FILE_VERSION="3.4.16.1" BIN_PRODUCT_VERSION="3.4.0.1" PRODUCT_VERSION="3.04" FILE_DESCRIPTION="Adobe Graphics Manager" COMPANY_NAME="Adobe Systems, Incorporated" PRODUCT_NAME="AGM" FILE_VERSION="3.04.16" ORIGINAL_FILENAME="AGM.dll" INTERNAL_NAME="AGM" LEGAL_COPYRIGHT="© 1984-1999 Adobe Systems Incorporated" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="3.4.16.1" UPTO_BIN_PRODUCT_VERSION="3.4.0.1" LINK_DATE="07/22/1999 00:22:06" UPTO_LINK_DATE="07/22/1999 00:22:06" VER_LANGUAGE="Language Neutral [0x800]" />
<MATCHING_FILE NAME="CoolType.dll" SIZE="733184" CHECKSUM="0xC2A00350" BIN_FILE_VERSION="3.4.16.1" BIN_PRODUCT_VERSION="3.4.0.1" PRODUCT_VERSION="3.04" FILE_DESCRIPTION="CoolType Typography Engine" COMPANY_NAME="Adobe Systems, Incorporated" PRODUCT_NAME="CoolType" FILE_VERSION="3.04.16" ORIGINAL_FILENAME="CoolType.dll" INTERNAL_NAME="CoolType" LEGAL_COPYRIGHT="© 1984-1999 Adobe Systems Incorporated" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="3.4.16.1" UPTO_BIN_PRODUCT_VERSION="3.4.0.1" LINK_DATE="07/22/1999 00:30:28" UPTO_LINK_DATE="07/22/1999 00:30:28" VER_LANGUAGE="Language Neutral [0x800]" />
<MATCHING_FILE NAME="cutlist.dll" SIZE="45056" CHECKSUM="0x1F2FA3CD" BIN_FILE_VERSION="6.0.1.1" BIN_PRODUCT_VERSION="6.0.1.1" PRODUCT_VERSION="6.0" FILE_DESCRIPTION="Adobe Premiere Plug-in" COMPANY_NAME="Adobe Systems Incorporated" PRODUCT_NAME="Adobe Premiere" FILE_VERSION="6.01" INTERNAL_NAME="Adobe Premiere" LEGAL_COPYRIGHT="Copyright 1991-2000 Adobe Systems Incorporated. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10001" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x15AC6" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="6.0.1.1" UPTO_BIN_PRODUCT_VERSION="6.0.1.1" LINK_DATE="04/06/2001 00:49:51" UPTO_LINK_DATE="04/06/2001 00:49:51" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="i-play-lib.dll" SIZE="49152" CHECKSUM="0x4D29D4D2" BIN_FILE_VERSION="6.0.0.0" BIN_PRODUCT_VERSION="6.0.0.0" PRODUCT_VERSION="6.0" FILE_DESCRIPTION="Adobe Premiere" COMPANY_NAME="Adobe Systems Incorporated" PRODUCT_NAME="Adobe Premiere" FILE_VERSION="6.0" INTERNAL_NAME="Adobe Premiere" LEGAL_COPYRIGHT="Copyright 1991-2000 Adobe Systems Incorporated. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10001" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x18D9F" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="6.0.0.0" UPTO_BIN_PRODUCT_VERSION="6.0.0.0" LINK_DATE="12/15/2000 04:08:23" UPTO_LINK_DATE="12/15/2000 04:08:23" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="plugin.dll" SIZE="31744" CHECKSUM="0xD525FF4C" BIN_FILE_VERSION="5.6.32.27" BIN_PRODUCT_VERSION="5.0.6.0" PRODUCT_VERSION="5.0" FILE_DESCRIPTION="Photoshop Plugin Utilities" COMPANY_NAME="Adobe Systems, Incorporated" PRODUCT_NAME="Adobe Photoshop" FILE_VERSION="5.0" ORIGINAL_FILENAME="Plugin.dll" INTERNAL_NAME="Plugin" LEGAL_COPYRIGHT="© 1989-1997 Adobe Systems Incorporated" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.6.32.27" UPTO_BIN_PRODUCT_VERSION="5.0.6.0" LINK_DATE="12/19/1997 19:06:37" UPTO_LINK_DATE="12/19/1997 19:06:37" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="pngu3266.dll" SIZE="386560" CHECKSUM="0x3F49CF2" BIN_FILE_VERSION="6.6.0.170" BIN_PRODUCT_VERSION="6.6.0.170" PRODUCT_VERSION="6.6.0.170" FILE_DESCRIPTION="GUI Library" COMPANY_NAME="RealNetworks, Inc." PRODUCT_NAME="RealPlayer (32-bit) " FILE_VERSION="6.6.0.170" ORIGINAL_FILENAME="PNGUI.DLL" INTERNAL_NAME="PNGUI" LEGAL_COPYRIGHT="Copyright © RealNetworks, Inc. 1995-2000" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x0" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="6.6.0.170" UPTO_BIN_PRODUCT_VERSION="6.6.0.170" LINK_DATE="11/22/2000 20:39:32" UPTO_LINK_DATE="11/22/2000 20:39:32" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="premiere.exe" SIZE="950272" CHECKSUM="0x60FABADF" BIN_FILE_VERSION="6.0.0.0" BIN_PRODUCT_VERSION="6.0.0.0" PRODUCT_VERSION="6.0" FILE_DESCRIPTION="Adobe Premiere" COMPANY_NAME="Adobe Systems Incorporated" PRODUCT_NAME="Adobe Premiere" FILE_VERSION="6.0" INTERNAL_NAME="Adobe Premiere" LEGAL_COPYRIGHT="Copyright 1991-2000 Adobe Systems Incorporated. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10001" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0xEEB59" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="6.0.0.0" UPTO_BIN_PRODUCT_VERSION="6.0.0.0" LINK_DATE="12/15/2000 04:16:21" UPTO_LINK_DATE="12/15/2000 04:16:21" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="preminfo.dll" SIZE="3813376" CHECKSUM="0xFFC7A5B8" BIN_FILE_VERSION="6.0.2.1" BIN_PRODUCT_VERSION="6.0.0.0" PRODUCT_VERSION="6.0" FILE_DESCRIPTION="Adobe Premiere" COMPANY_NAME="Adobe Systems Incorporated" PRODUCT_NAME="Adobe Premiere" FILE_VERSION="6.02" INTERNAL_NAME="Adobe Premiere" LEGAL_COPYRIGHT="Copyright 1991-2000 Adobe Systems Incorporated. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10001" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x3A3805" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="6.0.2.1" UPTO_BIN_PRODUCT_VERSION="6.0.0.0" LINK_DATE="01/11/2002 21:47:07" UPTO_LINK_DATE="01/11/2002 21:47:07" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="qtcompat.dll" SIZE="65536" CHECKSUM="0xFD21D58F" BIN_FILE_VERSION="6.0.0.0" BIN_PRODUCT_VERSION="6.0.0.0" PRODUCT_VERSION="6.0" FILE_DESCRIPTION="Adobe Premiere" COMPANY_NAME="Adobe Systems Incorporated" PRODUCT_NAME="Adobe Premiere" FILE_VERSION="6.0" INTERNAL_NAME="Adobe Premiere" LEGAL_COPYRIGHT="Copyright 1991-2000 Adobe Systems Incorporated. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10001" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1E49C" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="6.0.0.0" UPTO_BIN_PRODUCT_VERSION="6.0.0.0" LINK_DATE="12/15/2000 04:08:30" UPTO_LINK_DATE="12/15/2000 04:08:30" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="Uninst.dll" SIZE="49152" CHECKSUM="0xB68CDC35" BIN_FILE_VERSION="3.9.8.2" BIN_PRODUCT_VERSION="6.0.0.0" PRODUCT_VERSION="6.0" FILE_DESCRIPTION="Uninst" COMPANY_NAME="Adobe Systems, Inc." PRODUCT_NAME="Adobe Premiere" FILE_VERSION="3.9.8.2" ORIGINAL_FILENAME="Uninst.dll" INTERNAL_NAME="Uninst" LEGAL_COPYRIGHT="Copyright © 1997-1998, Adobe Systems, Inc. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="3.9.8.2" UPTO_BIN_PRODUCT_VERSION="6.0.0.0" LINK_DATE="11/22/2000 01:27:04" UPTO_LINK_DATE="11/22/2000 01:27:04" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="Plug-ins\RNCompiler\rnuninst.exe" SIZE="89600" CHECKSUM="0xA88555B6" BIN_FILE_VERSION="6.0.9.268" BIN_PRODUCT_VERSION="6.0.9.268" PRODUCT_VERSION="6.0.9.268" FILE_DESCRIPTION="Uninstaller Shell executable" COMPANY_NAME="RealNetworks, Inc." PRODUCT_NAME="Uninstaller Shell executable (32-bit) " FILE_VERSION="6.0.9.268" ORIGINAL_FILENAME="RNUninst.EXE" INTERNAL_NAME="RNUNINST" LEGA

Luiz Barrichelo

unread,
Dec 29, 2002, 8:02:34 AM12/29/02
to
I was reading this discussion and I had some problems also. I saw about uninstall the DirectX. I tried to do so, but I cannot find where to uninstall. There is no option in Add/Remove software, and also I could not find it in the Start>Programs.
Can someone help me?

Brewer Shettles

unread,
Dec 29, 2002, 2:19:28 PM12/29/02
to
How do you uninstall Direct X 9?

filmy

unread,
Dec 29, 2002, 9:06:27 PM12/29/02
to
If you are running WindowsXP you just restore to the point before you installed DX9. If you did not create a restore point you can try to do a semi-manual uninstall and re-install. You need the XP install disk and and you need to boot into safe mode and then download and run the file found here: <http://www.majorgeeks.com/article.php?sid=2935&cat=28>

Andrew Harwood

unread,
Dec 30, 2002, 5:06:15 PM12/30/02
to
I tried down grading - the www.majorgeeks.com thing didn't work. I found an restore point and built the machine back up from there. After all that effort, Premier 6.0 and 6.5 still don't work.

mario aguilar

unread,
Jan 3, 2003, 9:54:33 PM1/3/03
to
what are "window blinds?"

mario aguilar

unread,
Jan 3, 2003, 9:56:00 PM1/3/03
to
You cannot and should not uninstall direct X....instead make sure you have the latest version for your operating system...

Good luck to you!!!!

Mitch411

unread,
Jan 8, 2003, 8:03:12 PM1/8/03
to
Hmm.. This is pretty good, I mean pretty bad. This definitely seems to be a DX9 related problem. I'm personally running DX9 and XP pro and Premiere 6.5 (and 6.0 for that matter) with out any of these problems. I have what is probably a lame idea but at least it's something new to test. Here goes:

Open your system registry by selecting Start > Run and typing regedit in the Open dialog. Once the registry editor is open, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\1394\A02D&10001. Select the folder A02D&10001 and delete it. Also, if you have a folder A02D&10000, delete it too. Now close the Registry Editor. If your DV camera is attached to the computer via the FireWire port, turn it off, then back on. If your DV camera is not attached to the computer, attach it and turn it on. This will force Windows to re-initialize the DV camera and re-load all the Microsoft drivers for the device. Once Windows has finished doing it's whiring and clicking routine, launch Premiere and see if you can choose one of the DV presets without getting the "DV/IEEE playback is not setup correctly..." error message.

So? Does it work?

Mitch411

Mitch411

unread,
Jan 9, 2003, 1:58:06 PM1/9/03
to
Never mind the above post. I think I've got it figured out. How many of you with this problem installed the Nimo Codec pack V5.0? Yeah well, I suppose that's what you get for installing stuff that designed to help crack DVD's and do illegal MP3 encoding. On the first splash screen of the Nimo installer it says:

"Warning!!! There is an INCOMPATIBILITY with the TFM Audio Filter v1.0 beta 7 and the Morgan Multimedia Stream Switcher .095, DO NOT Install them together, chose one of them only if needed"

If you install this codec pack, and not read the warning, you'll get the "Project initialization failed. DV/IEEE 1394 Playback is not setup correctly. Playback performance will be impacted." error message when choosing a DV preset in Premiere.

So... In short, this doesn't appear to be a DirectX 9 problem, a Windows XP problem, or a Premiere problem. It appears to be an over-zealous download problem.

How did I figure this out? Well, let's just say a friend of mine (and you know who you are!) made the same mistake you guys did.

Mitch411

filmy

unread,
Jan 9, 2003, 7:25:12 PM1/9/03
to
I replied to Mitch in another post. To mario - you *can* uninstall DX, even the MS site tells the "best" way. DX usually has a "one version installer" that will autodetect your OS - NT/XP/98(SE) so you do not need to download the "correct version" really.

Anyhow per a MS response about Premiere and DX -
=========
Adobe Premiere 6.5 was tested with DirectX 9 on several machines with OHCI
cards prior to release without issues. My search of the Adobe forum and Usenet news shows one other report with the same symptoms as yours. So, we need to narrow this down. Further info on DirectX 9.0 changes on XP:
* The MSDV Driver (msdv.sys) is not updated by DirectX 9, so it cannot be contributing.
* Key Kernel Streaming (ks.sys and stream.sys) and kernel to user mode interaction ("proxying" via kswdmcap.ax) files are updated.
* The user-mode qdv.dll component containing the DV splitter, mux, and codecs have some minor changes.
Nearly all of the changes were made prior to the public beta, and they have quite a bit of beta site and end user mileage.

Although you have already reverted to 8.1, please provide a dxdiag dump (Start Menu->Run.., type dxdiag, hit Save All Information...). It is possible that your specific OHCI card has a marginal compliance problem, or that the Kernel Streaming changes exposed a problem with your audio driver.
The dxdiag file will help us in attempting to reproduce your issue.

Stan Pennington
DirectShow Program Manager
============

Some notes I might pass along here are that the MSDV codec *IS* part of the DX 9 install package...the DV codecs are in the "BDA" named cab packs - so for XP it would be the "BDAXP.CAB". So I dunno how he can say that those drivers are not part of the DX install. (Though in my case that driver is not the problem anyway) Also he mentions only finding one other post like my DX9 issue so I asked him what "adobe" forums he was searching. Obviously there are more than just my post and one other on this board about a DX 9 issue with Premiere.

Andrew Harwood

unread,
Jan 12, 2003, 3:00:32 AM1/12/03
to
I don't think this is a DX9 issue as it occured on a machine where I had done a fresh install of XP plus the standard XP patches loaded by Wundows Update i.e it was using DX8. I only ever loaded DX9 as a last resort when all of my other attempts at fixing the problem failed.

I am interested about the idea that the codecs might be messing things up. I have a Haupauge PVR card loaded and it has its own codec too. Is there a way to review the codecs that are installed? Is there a way to get Adobe to use its own codecs and ignore others? (Assuming that it isn't). I will try unsinstalling the Haupague card and see if that fixes the problem.
a

BusyB

unread,
Jan 13, 2003, 5:18:01 PM1/13/03
to
Hello All,

I wanted to submit this post to inform you all as to what I've seen with my own testing regarding the main topic of this thread. My system config is a Dell Precision 650, running Windows XP Pro, the Canopus DVStorm2, and DirectX 8.1. I began my testing by downloading and installing the Nimo CODEC Pack - Version 5.0 / Build 9. The first time I launched Premiere 6.5 after installing this CODEC Pack, Premiere ab-ended (crashed) before the execution even reached the Project Preset screen. Further testing revealed that the cause of the problem was produced with the installation of the Lame MP3 Encoder ACM 0.9.0, which installs the lameACM.acm file. Incidentally, the lameACM.acm also crashed RUNDLL32.DLL when attempting to open/browse the Audio CODEC list in the OS'es Device Manager.

It is important to note that I stopped testing after finding this information as it became obvious that the primary issue posted within this thread is the cause of some third party installation, and most likely a CODEC, that is not provided with either Premiere 6.x or DirectX9.

My only suggestion is to be more selective about what to download and install on your video workstation, and keep a tight record and system restore point so you can easily roll things back if problems occur. I hope this has been at least a small help in helping folks figure out what is causing the problem.

Best,

-B

filmy

unread,
Jan 14, 2003, 2:42:46 PM1/14/03
to
Andrew - to check what codecs are installed you can do a few things - first you can run the DX diag and it will give you a run down of all the DX files and what versions they are. If you have DX 9 on your system most should all end in .0900 (For the default XP install most are 5.01.2600.0000 or 6.04.2600.0000) Also if there are any DX related issues that should tell you.

Second from the desktop right click on "my computer" and select "properties". Then click on the "hardware" tab. You should see three sections now - click on the "Device Manager" section on the same named box (Device manager not the Driver Signing)

Now comes the "fun" part...ready? Click on the "+" next to the entry "Sound, Video and game controllers". You should see an overview of what is installed on your system. You will also see entrys for "Video Codecs" and "Audio Codecs". You may also see entrys for "Legacy Video Capture Devices" and "Legacy Audio Drivers". So lets start with "video Codecs" - Double Click on that entry and it will open another window. Click on the "Properties" tab and there you are - your list of video compression codecs. You can highlight any of them and double click for info about that codec. If you feel sure you do not want it you can click on "remove".

Now you can do the same for the "audio Codecs", "Legacy Video Capture Devices" and "Legacy Audio Drivers".

Hope that helps.

Now my 3 cents on the whole Codec issue - Andrew did say it was an upgrade to XP so maybe there are some older drivers causing the problems. This should come to light be checking the codecs installed. But here is the next quesiton(s) - did Premiere work before the upgrade? Did it work after the upgrade but before applying any sort of SP1/XP patchs? If it did than it is somthing that was recently installed. If it didn't than either you need to delete all the codecs and start over, so to speak, or you need to just re-format your hard drive and do a fresh clean install of XP and then Premiere. (Yeah I know - I hate being told that and I have been lucky to have never had to do it when I have been told to. But I am just the geek who would rather sit there and move each DLL file one by one until the program works - for most it would be "easier" to just reformat and a do a fresh install)

Now in my case with the "same" problem it only happened *after* is tried to install DX 9 and after I uninstalled DX 9 and went back to DX 8.1 (The default XP install version) the problem went away. As I have stated I feel that in *my* case there is something conflicting with Premieres interaction with DX 9 because nothing else was put into the system other than the DX 9 files when I got the "DV/IEEE 1394 Playback is not setup correctly" and nothing was removed from the system other than the DX 9 files to get the problem to go away. Everyone refers to the Nimo Codec pack and for me I have never used that. I will say I have some codecs like WhitePine that were installed with/for CuSeeMe and deleting them didn't matter...plus they are not DV drivers that would affect with IEEE output I feel.

Arnoldo Arellano

unread,
Jan 15, 2003, 1:40:57 PM1/15/03
to
This is another problem -- i wrote it as a topic, but after a week i received no answer... maybe someone there has an idea for this one --

Matrox RT2500 - Intel 845 - PIV 1.7 - Windows XP Pro (Spanish)

I´ve installed the premiere update (6.5) today (on a clean machine, fresh windows install), and the titler doesn´t work. All windows begin to blink and nothing can be done in the titler.
If you try to close the window, you can suppose you recive the prompt "Do you want to save changes?" (it cannot be seen) for if you press "enter" there is the posibility to save.
Please help...! It's the only new thing in the program... and it doesn't work!!!!????
It's frustrating. Any ideas?
Arnoldo.
* ** Premiere 6.0 was working without issues.
All other functions of Premiere 6.5 are OK. Just the titler doesn't work.

darrendarsey

unread,
Jan 16, 2003, 4:11:50 PM1/16/03
to
Just thought I would share this: I have had problems too with Premiere crashing every time I tried to capture video. After reading Dominic DeSantis post about WindowBlinds being a possible cause (which I use on my computer) I deactivated it and selected the default XP gui. IT WORKED! No more crashes when trying to capture from my dv camera.

William ESBailey

unread,
Jan 16, 2003, 6:08:04 PM1/16/03
to
Help - I have been tossing up between Premiere and Final Cut Pro. I have had so mnay problems with premiere but now with 6.2 and apparently 6.5 all the problems are over - is that right? or should i switch

Andrew Harwood

unread,
Jan 18, 2003, 3:13:29 AM1/18/03
to
Hi All,
Adobe sent me an email saying that this is a bug and that they are tracking it. They suggest "This error is most commonly caused by two or more conflicting 3rd-party DirectX filters". This agrees with what some people have been saying in this thread. They suggested that I also get Microsoft involved - this i have now done. If I get any more updates I will post them here for all to see.

PS: William ESBailey - I have used Premier for some time and think that (with the excption of a few users like me who have a problem) that the Product is pretty damn good. 6.5 Works fine on the other computer i tired; this bug just affects a limited number of installations - you will probably be fine.

filmy

unread,
Jan 22, 2003, 8:59:50 AM1/22/03
to
Andrew - glad that you also have told MS about the problems. As minor as they may be thay are still prblems that rest somewhere with DX and premiere that doesn't seem to affect other programs so it would be nice if they get figured out.

William ESBailey: Every edit system has it's pros and cons. Premiere for me, since version 5.1 has been super and with version 6 it just kicked butt for me. My only real complaint, as it were, has been the fact you can not output a TC window burn. The problems I have had with 6.5 so far have not really been problems really, just minor quirks, such as the DX issue in this thread.

Brandon Wilson

unread,
Jan 22, 2003, 1:13:24 PM1/22/03
to

Mitch411

unread,
Jan 29, 2003, 2:35:38 PM1/29/03
to
Hey Andrew,

Just a thought here, but do you have a sound card installed? Or are you seeing problems with the sound card listing in Device Manager? You know, like a conflict between a sound module built onto the mother board and a sound card in a PCI slot?

If you pull your sound card (and don't have sound I/O built into you MoBo) you'll first get a VERY long winded error message that says "Premiere was unable to connect to the native Microsoft DV support...." then that error message is followed up by the infamous "Project initialization failed. DV/IEEE 1394 playback is not setup correctly...." error message. This might be another avenue for you to follow. Although I still suspect a DirectShow filter compatibility issue. Besides just checking DirectShow video filters, consider any audio filters that might causing you this grief.

One last idea here if you really want to try bucking the system... Locate an application on the web called DVCSwitch. Also download the trial version of the MainConcept DV Codec. With these two software pieces, you should be able to force Premiere into a DV editing mode that uses the MC codec (ICM codec not a DS filter).

I figure you're probably burnt out on this by now and may not even find/read this posting but..... if you do, please post back and let me know if any of this helped.

Mitch411

Andrew Harwood

unread,
Feb 10, 2003, 8:45:51 AM2/10/03
to
Thank you Mitch411. I am getting a bit fused by all this. Since Adobe and Microsoft got involved I haven't heard a thing from them about this issue. Typical eh? Anyway - The Shuttle SG51 (SS51) has a built-in sound board so i son't know how this affect the situation?

I liked the idea about the DVCSwitch as I think it is a Codec issue (don't ask me to explain why - it's just a wild guess) I tired down loading the file of the net but all links to the authors web site seem to be lost (http://home.hetnet.nl/~jackwburger/). Do you have a copy you could email to me to try? my address is andrew....@madbat.co.uk
Many thanks.
a

Jeff Bellune

unread,
Feb 10, 2003, 11:55:52 AM2/10/03
to
Andrew,

Absent the DVCSwitch utility, you can run this command line from the Start>Run menu:

regsvr32.exe /u qcap.dll

This unregisters qcap.dll (which contains the MSDV codec) and makes the MC DV codec (or any other) available in a Premiere DV Playback project.

When you are done, just Run

regsvr32.exe qcap.dll

which will re-register qcap.dll and return things to default behavior.

Jeff

Andrew Harwood

unread,
Mar 6, 2003, 3:54:32 AM3/6/03
to
Sorry for the delay. I have just tried this and it didn't work... There was me, getting my hopes up that it would resolve all the issues. The application performed the same as usual i.e. displayed its error messages and continued to crash. Arrghh...

:(

Thanks for your ideas.
a
PS: I have not heard a thing from Adobe or Microsoft since they first said they knew about the problem and were looking into it.

0 new messages