|
|||||||||
|
Thread Tools | Search this Thread |
November 26th, 2009, 07:44 AM | #1 |
Inner Circle
Join Date: May 2004
Location: USA
Posts: 3,005
|
Premiere CS4 can't see video
The only thing I've done recently is install Time/Date software (visual dv). Standard DV video plays fine in Windows Media but when imported into Premiere I can only hear audio. Videos also import and can be seen in Windows Movie maker. Feels like a codec problem, is there any easy way to reinstall Premiere's codecs?
BTW, its Vista 64 Laptop |
November 26th, 2009, 11:13 AM | #2 |
Trustee
Join Date: Aug 2006
Location: Rotterdam, Netherlands
Posts: 1,832
|
Where did you get the video from? How was it captured? What does GSpot say about the codec used?
|
November 26th, 2009, 04:33 PM | #3 |
Inner Circle
Join Date: May 2004
Location: USA
Posts: 3,005
|
I imported video directly from the camera into Premiere with the same result. I have a feeling that installing a time stamp software messed up Premiere's codec. This is the 2nd time with in a month that software or hardware install has caused a serious problem with Adobe. Their video software is buggy as heck in combination with windows. I'm glad I don't use it on a regular basis.
Last edited by Pete Cofrancesco; November 26th, 2009 at 07:07 PM. |
November 26th, 2009, 07:55 PM | #4 |
Trustee
Join Date: Aug 2006
Location: Rotterdam, Netherlands
Posts: 1,832
|
You can't import DV footage. You can only capture DV over firewire. What does GSpot tell you about the codec?
|
November 26th, 2009, 09:25 PM | #5 |
Inner Circle
Join Date: May 2004
Location: USA
Posts: 3,005
|
I don't know what GSpot is? I captured in Encore but when I imported into Premiere no video. When I tried to capture from Premiere it froze the program and prevented windows from shutting down. After a restart I captured from Premiere and still no video. I'm currently in the process of reinstalling.
|
November 26th, 2009, 10:30 PM | #6 |
Trustee
Join Date: Aug 2009
Location: Chicago, IL
Posts: 1,554
|
Its not a matter of Adobe being buggy within Windows. It is due to this poorly written software(Visual DV) that is not tested and certified to work with Premiere. I can't stand when people blame Windows and/or Adobe for issues that arise when using all these 'small' programs that have little to no testing done for compatibility in addition to little to no quality control. These 'small' (ie poorly coded) programs are what give Windows a bad rep. If these same programs worked on a Mac, then OS X would have a similar stigma as Windows.
Moreover, this program hasn't been updated in 2 years and there is no indication that its certified to work in a x64 OS. Sorry I didn't get to this earlier as I would have suggested using Windows to restore to a time prior to this app being installed, which should have fixed the problem. |
November 27th, 2009, 04:51 AM | #7 | |
Trustee
Join Date: Aug 2006
Location: Rotterdam, Netherlands
Posts: 1,832
|
Quote:
You do not make much sense to me. You say you captured with Encore, which is not possible. Then you say you captured with PR, but from what camera and with what project/sequence settings? Earlier you talked about importing, so what is it? FYI, importing and capturing are completely different things. |
|
November 27th, 2009, 10:02 AM | #8 |
Inner Circle
Join Date: May 2004
Location: USA
Posts: 3,005
|
I originally tried to import video I had recorded to a Firestore, then after you made a suggestion I captured video directly from the camera to the laptop using Onlocation (which I mistakenly called Encore), then I tried Premiere. All of which had the same result, when played inside Premiere I can hear audio but no video is shown. Outside of Premiere they play fine. Clearly it's a codec issue.
I downloaded and ran Gspot. System check revealed all the adobe codecs are in red for some reason. Know that doesn't help me know how to fix the problem. |
November 27th, 2009, 11:20 AM | #9 |
Trustee
Join Date: Aug 2006
Location: Rotterdam, Netherlands
Posts: 1,832
|
I repeat the question: What camera. what sequence settings and what does GSpot show. Attach a screenshot.
|
November 27th, 2009, 11:52 AM | #10 |
Trustee
Join Date: Aug 2009
Location: Chicago, IL
Posts: 1,554
|
Pete: if I came off as a jerk, I didn't mean to.
To fix your problem, use windows Restore. This little program clearly does not work with Adobe and/or Vista x64. Or try the K-Lite codec pack, which can remove broken codecs and might even replace them. Google it (site should be codec-guide.com or something similar), download just the 32 bit version of the 'Mega' pack. When installing, select the "Full w/ Media Player". There are a few other options to check but I can't remember them (besides checking Hardware acceleration/DXVA for H.264). Good luck. |
November 27th, 2009, 12:15 PM | #11 |
Trustee
Join Date: Aug 2006
Location: Rotterdam, Netherlands
Posts: 1,832
|
Steve,
I quite disagree: NEVER install K-Lite. Too many people have been bitten by that malicious software and their only solution was a complete fresh install of OS & programs. The ONLY codecs you can safely install on a CS4 system are Lagarith, HuffYuv, Morgan MJPEG and MainConcept MJPEG. Anything else, but most notable K-Lite and to a lesser degree FFDShow, puts the system stability in serious jeapardy. If you think you need other codecs than the 4 mentioned explicitly above, first check around for user experiences. |
November 27th, 2009, 12:58 PM | #12 |
Inner Circle
Join Date: May 2004
Location: USA
Posts: 3,005
|
I read that Gspot/Sherlock give false errors for adobe cs3/4 in system codec list because adobe uses quotes for their codec entries in the Windows registry.
Gspot capture: of one the video files I'm trying to edit. http://i46.tinypic.com/2el8awk.gif |
November 27th, 2009, 01:12 PM | #13 |
Trustee
Join Date: Aug 2006
Location: Rotterdam, Netherlands
Posts: 1,832
|
Pete,
You are correct that GSpot gives false errors with MainConcept codecs that are part of CS4 because of the quotes, but luckily that does not apply here. The codec is standard SD DV type2, so that should not be a problem. Are you by any chance using a dual monitor setup and you have the program monitor on the second screen? If so, your video driver could be causing this problem because of the overlay support in the driver. Is your video driver the most recent? Do you have the most recent DirectX (9.0C IIRC) drivers? |
November 27th, 2009, 01:58 PM | #14 |
Inner Circle
Join Date: May 2004
Location: USA
Posts: 3,005
|
Its a new laptop with no external monitor and I reinstalled the video driver from their site.
|
November 27th, 2009, 10:13 PM | #15 | |
Trustee
Join Date: Nov 2008
Location: Miami, FL USA
Posts: 1,505
|
Quote:
Our SOP for oddball videos we have received is to first convert to a *.dv file, which then opens in Final Cut..../Battle Vaughan |
|
| ||||||
|
|