Blue Screen of Death

Okay, I have a Sony Vaio. 2 ghz Core 2 Duo Intel, 2 gig of RAM, using Edius 4. When I use the procoder to compile an edit of a wedding, I get the blue screen of death with the following info on the error log:

BCCode:9c
BCP1:00000000
BCP2:BAB4C050
BCP3:B2000040
BCP4:00000800
OSVer:5_1_2600
SP:2_0
Product:256_1

The footage was captured on P2 under DV quality (480)... it's a wedding after all :) and when I try to compile the edit into a single DV file, it will work for a while then dump. I'm assuming it's trying to overwork either the RAM or Video Card or CPU, but I'm not sure.

I've talked with Sony and I haven't heard from Canopus yet, so I'm at a loss. This is the first time I've really used the product using DV footage. No issues with HD footage... errors out with either saving HD footage as DV or saving DV footage as DV.

Any thoughts on what the Procoder is using to perform its function? Maybe that's where the contention lies.

PETE
 
I've never heard of this before. Why don't you just edit on a dvcpro hd timeline (or whatever your footage is). You're final output is going to be dvd anyways, right? When you render your m2p everything will get converted down to the sd 4:2:0 dvd compliant format. No need to edit in a dv project setting. See if editing in the proper project setting makes a difference. Otherwise, I have never heard of this issue, nor experienced it.

Later,
Jason
 
Canopus finally got back to me. It appears to be CPU contention at this point, although I would think a 2 ghz Intel 2 Core CPU would be more than enough horsepower to run the ProCoder. I made the changes they suggested and it still crapped out. I also ran a memory check on my 2 gig of RAM and it came back okay.

I tried to just dump the DV footage right to DVD out of Edius and it crapped out doing that as well. Very frustrating.

While I await Canopus' response I guess I'll try saving it as DVCPRO footage, then try and create a DVD directly and see if that makes any difference.
 
Core duo or Core 2 duo, should be more than plenty to work with DVCPRO HD footage. I do it with multiple streams, on my laptop frequently.

Yeah. Just try changing your project settings to the appropriate setting for your footage. One thing I'm not sure about though... You recorded dv to p2, or you recorded dvcpro hd to p2 and captured it as mini dv?

Anyways, good luck with your problem. I have never heard of it myself.

Maybe a fresh install would help...

Jason
 
I think I might have the same issue, and from what I've been told its Procoder at fault. I shoot and edit a 30 min 2 camera show in SD using footage direct from P2 cards and capturing from dvcpro tape, when I try to burn directly to dvd from the timeline, 60% of the time it will crash the system before it finishes, it seems totally random sometimes it doesn't crash at all other times it will take 5 tries before it actually makes it to the dvd. I burn 30 sec commercials all day long and never a problem, the issue seems to come up when its a long form project, Canopus informed me that there is a bug in Procoder and thats why the included Ulead on the system (I bought a turnkey system from them) I called as recent as yesterday and there are no patches or fixes for procoder express at this time. Its the only frustrating flaw in the canopus edius system so hopefully they will work on the procoder issues in a future update
 
Jason,

I recorded 480 on P2 then imported it into Edius using the p2 functionality. I also firewired some footage captured on the miniDV tape when the p2 cards filled up.

I also uninstalled, reinstalled Edius and updated it to 4.13.

However, now, I tried taking the DV footage to ouput a DVCPROHD footage, which I don't believe uses the Procoder, and the same thing happened when it was 95% completed. I'm at my wits end at this point. I'd actually be relieved if it is solely left to the ProCoder issues. After all, I spent $2gs on this laptop and when I try to use the software it keeps blowing up.

Frustrating. The computer never dumps except when I'm using Edius. At this point, I'm left taking all of the footage, converting it to miniDV and dumping it, old fashioned style, into Premiere Pro.

Jeff in Ocala, what computer do you use (CPU, RAM, etc.?)

Pete (in Safety Harbor, FL)
 
http://www.dvxuser.com/V6/Hi Pete this is what i have from the canopus website ( I upgraded ram to 2 gig and HDD to 600) EDIUS NX Workstation: Specifications
System Configuration:
  • Workstation: HP xw4300
  • CPU: Dual-core Pentium D 3.2 GHz
  • Memory: 2 GB
  • Hard Disk Storage: 600 GB
  • Optical Storage: 16x DVD-RW
  • Graphics: NVIDIA Quadro FX1400 with dual DVI output
  • Connectivity: 8 x USB 2.0, 1 x FireWire (IEEE 1394a)
I am really happy with my system it handles the p2 files like a champ the only flaw I seem to have is the procoder express issue What type of stuff are you doing down in Safety Harbor?
Jeff
 
Jeff,

At the time I bought the laptop, Canopus website said it would meet min standards for HD usage. So, I hope they haven't upped the ante and put me $2g in the hole.

However, the issue I'm having now is solely SD footage being saved as SD footage, which means my laptop should have plenty of horses for that. If ProCoder is the culprit, I hope they come out with a fix soon.

As for my projects? I've done various microcinema shorts and features over the past eight years. I'm now trying to focus my attention on the niche Christian market. I realized that if I walk into Best Buy and won't buy an above average flick with Julia Roberts and Denzel Washington in it, then no one is going to buy my flicks, no matter how good they are. I would never be a big fish in that pond. So, I'm working on combining my faith and my passion for movies and see if I can be an above average fish in the niche Christian film market pond. Although, with the advent of Fox Faith and various other big company entries into the market, that may be a pipe dream as well. I've written a couple of features and am trying to get some resources behind one of them to hopefully shoot this year/next year.

Pete
 
Well, I was able to edit SD DV footage that I had converted (through numerous blue screen iterations) into Canopis SD DV codec and when I put all of the pieces together (almost 60 mins total) the program worked fine.

So, I guess it is all Procoder related. I guess my HVX footage was not standard as Edius could not output it in a native format, but instead required to output it using Procoder.

Hopefully I'll hear from my Canopus techie today.

Pete
 
Back
Top