Discussion:
Very unstable capturing: "Unknown recorder error"
(too old to reply)
D***@adobeforums.com
2005-09-20 16:11:42 UTC
Permalink
I have had some problems with turning the CPU's off and on with PPro running. If you run into the program locking up then try the work around below. The changes to the previous work around are in ().

I hope all of this information will help Adobe get a fix for the new generation of dual processors. I have been editing in PPRO with the AMD X2 for a few days now and have had no problems other than capture. I never have to render to see full resolution with multiple effects and transitions. When I do render it seems to be faster. So far so good.

1. Start PPRO (To the welcome page)
2. Get into task manager by pressing CTRL, ALT, Delete at the same time.
3. Select the Processes tab
4. Find Adobe Premier Pro under the Image Name and right click on it.
5. In the drop down menu left click on Set Affinity
6. Uncheck one of the CPU. Either CPU 0, or CPU 1
7. Capture with PPro
8. (Save the project and restart PPro this will reset the CPU's)
D***@adobeforums.com
2005-09-26 00:48:34 UTC
Permalink
I have also found that setting the in and out points for a batch capture will also give an error message. The msg says.... Adobe has had a serious error and needs to shut down......This would happen randomly just as I was logging a in-out for patch capture. When I turned off one of the CPU's as as described earlier the problem never happened again.
D***@adobeforums.com
2005-10-03 21:19:28 UTC
Permalink
Same set-up and same issue as everyone else (Using Premiere Elements, but I guess the capture module is using the same codebase):

AMD X2 3800+
Abit AN8 SLI
2x512Mb Matched DDR1 Ram
SATA OpSys HD and IDE Capture HD

Glad to report the Affinity work around 'fixes' this, but now Adobe know about this I hope they get on the case!!
J***@adobeforums.com
2005-10-07 06:50:34 UTC
Permalink
Im having the same problem with intel dual core but i set the Affinity and still freezes :( any help?
L***@adobeforums.com
2005-10-07 10:34:38 UTC
Permalink
If anyone finds patches of fixes on the web anywhere PLEASE post the link here! It's surely only a matter of time..
D***@adobeforums.com
2005-10-07 19:57:41 UTC
Permalink
What Motherboard is everyone using?
I have an Abit AN8 SLI.

POSSIBLE SOLUTION!!

In desperation I did a complete re-install of Windows:
-before re-install I downloaded latest nForce motherboard driver from link on Abit site (I also previously flashed the bios of the MoBo to the latest, and it was still current). Also downloaded the AMD Athlon driver from link on same webpage.
-wiped hard drive and re-installed from scratch.
-Installed XP SP2 and used windows update to fully patch
- Installed nForce driver and AMD driver.
- Didn't install nForce Firewall (as have hardware firewall already in router and when I did have nForce firewall installed I had a problem with corrupted downloads - not sure if it this has any bearing or not)
- Re-installed Premiere (Elements in my case)
- Capturing footage (DV via firewire) with no problems with both cores working.

Hope this sorts you guys out too. Fingers crossed it stays working!
S***@adobeforums.com
2005-10-08 19:19:43 UTC
Permalink
New Info for More Technical Than I:

Just compared the capture rates for the exact same video files in .avi (via Windows Movie Maker) and the finished .mov (via process in previous post).

The Quicktime file had a variable rate while the .avi captured at a fixed rate throughout the clip (and it was much lower).

Would a steady, low capture rate cause indigestion in the capture/playback mode of PPRO?
S***@adobeforums.com
2005-10-08 19:12:38 UTC
Permalink
All: My first post. Indeed smart-eyes looking in on this forum! Thanks! Here's another possible solve for those, like me, who are not getting results from processor tweaks as they capture VHS via FireWire:

1. Capture via Windows Movie Maker, .avi format.
2. Open PPRO and choose to EXPORT clip.
3. Browse to clip in .avi format.
4. Export that clip as a .MOV, picking Sorenson 3 as the compressor.
5. Remider: Confirm audio sampling rate.
5. Save clip, then drop finished clip into timeline.

Now, I realize this is time/processor intensive. And replicative. Try a batch and let you system digest/process the data overnight.
S***@adobeforums.com
2005-10-13 11:16:23 UTC
Permalink
Final resolution: Decided my hard drive, which was heavily fragmented, may have been the problem, as I was capturing via 7.0 straight to drive. Connected a Western Digital EXTERNAL drive via USB 2.0 and laid the files there. As I routed DV via Canapus ADVC-100, I had NO problems capturing footage from my VHS player!

Ahhh! Frustration gone!
P***@adobeforums.com
2005-11-16 19:11:28 UTC
Permalink
Dear Luke
Maybe you have sorted your problem by now. I have new dual core processor on new computer new video camera as well.
Solved problem by doing the following:-
Open Premiere and minimize it
Control Alt Delete
Task Manager Box appears
Select Processors
Find Adobe Premiere and right click it (not SYSTEM)
Then click on set affinity
Untick either CPU and OK
You will then be OK when you close Premiere your computer will default back to both processors.
Hope this helps
Pete Gibbons

Loading...