You are viewing an archive of the old fxhome.com forums. The community has since moved to hitfilm.com.

Can't Import Video

Posted: Wed, 30th Jun 2010, 5:55pm

Post 1 of 4

FXhomer99411

Force: 0 | Joined: 30th Jun 2010 | Posts: 2

Member

When I try to import my avi. video I get the <string expected> <void> message follow by <Object expected>. I'm new to this, so can someone tell how to fix this?
Posted: Wed, 30th Jun 2010, 7:24pm

Post 2 of 4

Axeman

Force: 17995 | Joined: 20th Jan 2002 | Posts: 6124

VisionLab User VideoWrap User PhotoKey 5 Pro User MuzzlePlug User PowerPlug User PhotoKey 3 Plug-in User FXhome Movie Maker FXpreset Maker MacOS User

SuperUser

Do you have the latest version of Quicktime installed? Is your DirectX up to date? What codec is the .avi file in?
Posted: Thu, 1st Jul 2010, 1:27am

Post 3 of 4

FXhomer99411

Force: 0 | Joined: 30th Jun 2010 | Posts: 2

Member

Yes, I'm pretty sure I have the latest Quicktime Player and DirectX installed. How would I find what codex my file is in?
Posted: Thu, 1st Jul 2010, 3:11am

Post 4 of 4

Axeman

Force: 17995 | Joined: 20th Jan 2002 | Posts: 6124

VisionLab User VideoWrap User PhotoKey 5 Pro User MuzzlePlug User PowerPlug User PhotoKey 3 Plug-in User FXhome Movie Maker FXpreset Maker MacOS User

SuperUser

I think you can open the .avi file in Quicktime, then Show Movie Inspector, in the Window menu, and it will give you the codec in the Format info. Not sure if it works the same on Windows though. If that doesn't work, then the next step is to determine:

Where did the video come from? If you exported it from your video editing software, the codec should be something you select when you export. What software in particular you are using will affect the exact process though. If you let us know what software you are using, we can probably be more specific.

If it came straight off of your camera, the codec it uses should be in the documentation for the camera.

If it came from a third-party source, you might check with them as to the codec.

Also, its probably worth mentioning, in case you didn't go to the support area first, that there is a knowledgebase article that deals with this exact issue.