Shawn michael Lee
Forum Replies Created
-
Sorry. I thought I made it clear in my first post. I have a RAID Array consisting of two drives, both 250 GB, into a Media only drive. I also have a third drive that is only for system files and programs. 6 streams? I should be blasting 16 streams! I’ve done this on a single 300GB hard drive in the past. Something is definately wrong here.
But, I don’t need the audio on the other cams so I’ll delete them and see if it helps. Thanks for the advice.
Lowrysam
-
And let’s not forget the new Pixelmotion setting in AE 7. I have used it with amazing results in ordinary DV and DVCAM footage.
-
I don’t think that it is Premiere having the difficulty. We also have used the XL1 to capture footage that is shot with another camera. The XL1 is pretty picky, often dropping timecode and entire audio tracks as well when capturing. My recommendation is to simply use another DV camera to capture the footage (maybe the original camera it was shot on).
Lowrysam
-
This is interlacing. It’s sometimes normal to see it in the preview monitors. All NTSC footage is made up of two fields. Computer monitors are progressive scan and play both field kinda funny sometimes. Before exporting to wmv, deinterlace the footage or deinterlace on export. Use Adobe’s Help files to find out how.
Lowrysam
-
What are you capturing the footage to? DV, an uncompress 10-bit or 8-bit codec, Quicktime codec? How it was rendered to HDD can make a alot of difference to the workflow speed.
Lowrysam
-
It’s a problem in the importing. I had the same problem recently. My workaround: I rendered the fime to NTSC DV, avi file. Then I imported it into Encore and transcoded it in Encore instead.
Lowrysam
-
In film the effect is achieved by speeding up the frame rate or slowing it down, often in real time by an asistant cameraman. This makes for a a more natural acceleration and deceleration of the frame rate as the speed dial is cranked. In After Effects, you could recreate this with Time Remapping and settin the key frames to easy-in and easy-out.
Not sure how to do this in Premiere Pro though. Anyone else with any ideas?
Lowrysam
-
With so many Dual core, Dual processors available for workstations, Adobe should be taking advantage of this additional power. I bought this system because Adobe listed it as its top-of-the-line OpenHD certified system. The fact that it is slower than my old 1 chip Pentium 4 computer is upsettting.
Maybe if Gridiron reads this, they could consider working on a plug-in for Premiere that is similar to Nucleo.
Why does Adobe recognise that “Multi-processor enabled” in the start-up if it’s not going to take advantage of that?
-
One Example: rendering DV captured footage. Straight cuts edit, no effects. Rendering to MPEG2-DVD using Adobe Media Encoder. No Background processes running. 1 hour long project.
P4 HT 3.4ghz = about 54 minutes
2 Dual Core AMD Opteron 270s = 1 hr, 12 minutes
Disappointing to say the least…
-
I haven’t found a workaround for the “low system memory”, or shutdown issues. I have done more tests and found that I get these problems even when I work in an entirely NTSC DV project with NTSC DV selected from the beginning. It just seems that something since the AJA install has started a conflict with all of my formerly DV projects.
I plan to uninstall AJA entirely, then attempt to open the DV projects and see if the problems still occur. That should narrow it down, hopefully. I’ll keep you informed.