Mov and Avi may mean many things...
Read Bill Hunt on a file type as WRAPPER http://forums.adobe.com/thread/440037?tstart=0
What CODEC is INSIDE that file? http://forums.adobe.com/thread/440037?tstart=0
Also, you need to provide hardware and software DETAILS
Such as version of Windows
Such as model laptop... and graphics adapter (Ati or nVidia... and exact model) and the exact driver version
Your problem is most likely a graphics adapter driver that is old and needs to be updated
Also, Read Harm on drive setup http://forums.adobe.com/thread/662972?tstart=0
- click the embedded picture in Harm's message to enlarge to reading size
- you need AT LEAST 2 drives for video editing, 3 is better
- some HD formats work better with (require) RAID
Read Hunt on Partitions http://forums.adobe.com/thread/650708?tstart=0
Where exactly did you get the original clips you're trying to edit?
Also, have you installed the licensed version or the trial?
Thanks for the help.
I had hoped that I was making a simple error, despite having followed instructions in tutorials.
The MOV file was recorded by a simple HD handheld video recorder.
I used G-Spot and it indicates that the file container is Quicktime MOV
Video CODEC is avc1, name is H.264. Status is listed as "undetermined"
Audio codec is mp4a: MPEG-4 AAC LC
When I checked the "system" menu option, I could not tell if the avc1 codec was listed. I did note several codecs listed as "missing", though none of them seemed to be for avc1.
The computer is a 2 year old HP DV5-1235dx. It has only a built-in (shared RAM, most likely) video "card". It is listed as Intel Mobile 4 Series Chipset family. I am virtually positive it is OpenGL-2 compatible. It has a Core2 duo processor. Several gig of RAM. A single HD. I realise that the program will run slowly, but I had hoped it would run properly.
I have the full version of Premiere, fully licensed and all options installed.
I can supply any further details as required.
THANK YOU FOR YOUR HELP!
AVCHD on that system, uugghh.
I realise that the program will run slowly, but I had hoped it would run properly.
Slowly in this case has to be seen from the perspective of a very old and frail snail, handicapped with a severe case of arthritis.
You are trying to edit one of the most demanding codecs, wrapped in a QuiRcktime MOV wrapper, which effectively kills the 64 bit nature of CS5 on a seriously underspecced laptop, with a slow CPU, a seriously lacking video chip (Intel with shared memory is a disaster for normal applications, but utter hell for video editing), only a single disk, which probably is not even 7200 RPM, possibly with a monitor that also does not meet minimum requirements, etc.
In short: Forget it. The system you describe is around 300 times slower than a decent system. Invest in a system that at least meets minimum requirements. That will allow you to edit DV material. For AVCHD get a way faster system, think i7-9xx on a X58 platform, 6+ (that is absolute bare minimum) GB memory, a dedicated video card with its own memory and three separate physical 7200 RPM SATA disks or better.
Thanks for the info regarding the woeful inadequacy of my laptop. I have a desktop that ought to be adequate, except for the need for a 64 bit OS. I had kept an older version of XP-32 for legacy applications. I can buy W7 and make a dual boot configuration pretty easily, except for the added cost of W7. I had been planning on making the change anyway.
As I said in my first post, I had successfully exported the video into AVI format. GSpot reports the codec as DVSD, named DVC/ DV video. And the status indicates that the codecs are installed. I still only see a picture in the program window when the playback is paused. So, I am pretty sure it is not a codec problem. It could be a video hardware problem.
I take it that there are no hidden settings that could force the Premiere software to handle my video hardware better?
I will have to get W7 on my desktop and see how it will work....
If you have a DV AVI type2, instead of that AVCHD wrapped in a MOV wrapper, that will probably edit OK and you will be much better off in terms of editing experience.
Unfortunately, I have only that MOV file type available in that video camera. However, I was able to load a (big) clip into Premiere, and then export it in a different format (I tested AVI) and it exported fine, and played fine in Windows. So, It appears that I can convert that ACVHD format to a different, more easily editable format.
I still have the program play problem on this laptop. I will try it on my desktop and see what happens.
The MOV file was recorded by a simple HD handheld video recorder.
Make and model?
It is an Aiptek HD recorder. Nothing fancy at all. I forget the model
number at the moment. I can look it up
Sent from my iPhone
This page shows 15 models http://www.aiptek.com/Camcorders/HD/ so knowing exactly which one will help lead to the exact codec used
It MAY be the same codec for all models but, since I don't use that brand, I have no way to know
The camcorded is the Aiptek model Z5X. Thank you for checking. As far as I can tell form the website, the only reference to the codec is H.264
My best guess is your choice of camera.
Make sure to use only supported camera formats inside Premiere Pro. H.264 encompasses a LOT of variables. For cameras, you want one with the AVCHD logo on the camera. Without that logo, you take a chance that the media may not work.
The Red doesnt have an AVCHD logo on the side!
Nor does my HVX!
True, bot those camera shoot in OTHER supported formats. Since the OP was using H.264 media, the format that's relevant here is AVCHD.
The part that confuses me is the fact that I can export the clip in a different format, and it is properly translated. It plays in the new format just fine outside Premiere. But when I import that new format clip, it still will not play in the Program window (though the paused frame sometimes does display). I would have thought that ig it could not handle the MOV file's codec, then it would not be able to translate it either?
I night have thought so as well. But export and playback are two different things. Export can wait as long as it needs to as it reads the frames. Playback can't.
And playback outside of Premiere Pro often has little bearing on Premiere's performance with a file.
Go to the PPBM5 website and download the test files and see if those files play nice.
While your at it run the test to see how your system is running things.
If your getting problems with those files then something is wrong besides the camera you are using.
Thanks for the link. I will be very interested to see how it works with the test videos and the benchmarking. I know that the laptop will either be totally unable to do the job or totally inadequate. I was hoping for some degree of functionality.
I will be very interested to see how my desktop stacks up. It has an I7-920 quad core, 6gm ram, (soon to be W7), ATI HD-3800 series video, and several SATA-3 hard disks. Not high performance by today's standards, pretty good for 1.5 years ago when I set it up. I am hoping it will give at least some degree of useful functionality.
I'm running CS5 on an HP dv7 laptop, which is a little better than yours, but not much. Mine runs pretty well, but like you, I didn't initially get any video in my monitors during playback--only while paused. I rarely use my laptop to edit... I usually use my workstation, but for the rare times that I'm on the road and need it, I was frustrated because CS4 worked pretty smoothly. However, I got CS5 to play nice by right clicking in the program/source monitors and selecting a playback resolution of 1/2 to 1/4. Try that and see if it helps you at all...
thanks for the great suggestion. Unfortunately for me, this did not work. I could only drop the playback res to 1/2, and no lower. the video still does not appear in the program window. I will keep trying.
I installed Premiere CS5 on my I7 system. (ATI HD3870 graphics), and it seems to work fine with no special adjustments. Therefore I can only conclude that my HP laptop is just not good enough for this software. No surprise there.... I had hoped that it was a problem with a setting somewhere, but it is just inadequate hardware.