DL Extreme PCIe – Premiere Serious Error II – HELP!

[Chaos]

Hi Bernardo,
You are better than me cause at least you can install the driver, but I can’t.

I’ve got DL SP PCIe one week ago, and still try to install it. The installation process (blue bar) goes back everytime. I’ve got recommend mainboard before buying Decklink (Asus A8N-E) and no way to install.

I think there is a bug issue in these PCIe models. Now I am thinkink to change it with PCI model.

[Wolf]

Hi chaos,

i had the same problem to install 5.3.1.
Be sure to have quicktime installed.
And a other trick that worked on my PC is:
First install 5.2.2. than don

[Bernie]

Hi guys.
Still not working…
I even try open new projects but I still getting the same error…
I did projects with the video render set to none instead of Blackmagic codec. The render goes further but 5 minutes later I get the ” Serious Error” again…

I realocate the card to other PCIe slot again but premiere still CRASHINHG!

..I don’t know what should I try now.

thanks guys.
We need to make it work!! Support please.

cheers Bernardo

[Chaos]

Hi all,

still doesnt work. Even I’ve tried at different system -Asus P5AD2-E with P4- the result was little different. There was no any interruption while setup process but when I checked “Device Manager” there was an exlamation mark the place that decklink should be. As I said I think that PCIe version cards have bug inside, what is your opinion?

[Bernie]

hi Chaos.
well, can be a PCIe bug… PCIe It’s a new “enviroment”. my DL Extreme PCIe came in regular Extreme box without manual with a stick on it, saying: sorry at the time this product was made there was no manual available.

I’m trying a new project from scratch…Now i’m rendering it none. No Blackmagic codec. It’s more stable. Now i’m getting more than 15 minutes o rendering without CRASH.
I tell you if it done sucessfully.

luck for us.

cheers
Bernardo

[Shane Chadder]

Bernardo

I’m using Decklink HD Pro 4:2:2 and version 5.1.2 was the last “stable” driver for me. With drivers 5.2 and on something changed and any significant rendering crashes premiere.

5.2 is the version that first supported PCIe….and introduced instability for my setup.

I wish they would publish setup specs so that we knew what the “approved systems” consisted of re: bios versions, graphics card drivers, etc. etc. I waste to much time trying to track down the problem at my end when BM must have a spec list that includes such details.

Shane

[Bernie]

I agree with you Shane.

[Dkh Lai]

Hi Every one,

I have been using BMD extreme PCI & PCIe card
on a recommended ASUS Intel Dual core system for
about 4 months.

Until now the “serious error” still exist and
i sincerely hope that BMD can address this problem
or I would suggest that we have to wait for PPro 2.0.

My 2 cents comment

Regards

Daniel

[Bernie]

Dear Lord! Daniel!

4 months of ” serious error” !!!

How you deal with your clients?
-Sorry client, but a “serious error had ocurred” come back tomorrow, we will try make things work…

If I do that, the clients will not come back…

This is really Serious!

I was thinking that I got a “bad” card…(a hardware issue)
Now with your post I’m not sure anymore…I think the problem it’s worst than that!

I’m running some tests with video rendering set to none( instead of using the BMD codec), and the system it’s getting more stable. Yesterday I did a 30 minutes render, without CRASH!! Yeah!
This kind of Sucess isn’t?

I’m reinstalling windows for the again (12 times in 3 days). I wiil start everything from the scratch using only video rendering set to none.

I will let you guys know if I get suceed!

cheers.
Luck for Us
Bernardo
Rio de janeiro – Brasil

[Geoff Gartside]

Hi all,

DL extreme, 10bit BM codec, YUV input.
See profile also.
5.3.1 drivers installed OK.

Where do I start with premiere ‘serious errors!! Ours don’t crash premiere, they just sit there until you close the box, then it closes premiere down. You can then only open a copy of the project. At the close of work we usually reach: a copy of a copy of a copy of a copy. All the copies work though.

It does it when a frame is dropped on capture (with abort on drop checked)
It does it sometimes when rendering (usually with 2 + video tracks involved).
It does it occasionally when you delete a file.
It does it often for no apparent reason.

I don’t know why because my knowledge of computers is fairly basic, so like most other people I just guess and try ideas out.

Why don’t Black Magic design a standard report form so that when we write in with these problems they could be assessed (hopefully) in a logical way both by BM and other readers. What about error logs etc., don’t they tell knowledgable people anything? Doesn’t system information help (if you understand it).

It seems to me that there are a lot of people out there (here in my case) struggling with things that they cannot get to grips with.

Thank goodness for Creative Cow.

Thats my few pennyworth anyway!

Cheers,

Geoff Gartside.