HPX170 and Adobe OnLocation CS3

[eXe69]

Hi everyone. I've been a reader for a while but this is a first post.

Got an hpx170 over the weekend and love it but can't get it to work properly with OnLocation.

1. On location recognizes hpx as hvx200
2. Doesn't capture footage at specified frame rates. Like I'll choose 720p not PN. at 24fps and it will capture it at 29.97.
3. Even if it captures properly at and only one I was able to find 1080i / 60 when imported into Premiere CS3 can not edit real time and have to render the timeline first.

I worked with firestore hvx200 / MXF and premiere cs3 before and was great real time editing. I was kindof expecting same experience from OnLocation. Which is not the case, very frustrating.

Wondering if anyone has had any experience with hpx or hvx, onLocation and premiere and can shine some light on some basic workflow ideas.

Also I'm thinking that onLocation should be able to detect the proper model of the camera. Not sure if that's what's cousing the framerate issues.

Thank you.

[David Saraceno]

When you are capturing at 720p/24, what have you set you frame rate to in the cam?

Default or something else?

[eXe69]

yes it's default

[David Saraceno]

If it is default and you aren't shooting 24pNative, would it be 29.97 with pulldown?

[eXe69]

Thank you very much for your help. I think I just stumbled on a solution. Seems to be working despite initial impression.

Basically I changed the capture format in OnLocation to AVI type 2 vs 1 like before. Now AVI type 2 seems to record proper framerate that is set in the cam. When I import it into the Premiere timeline it still shows up with red bar on top that it needs to be rendered despite matching video / compositon settings. But to my surprise the video plays smoothly in HD with ocassional frame drop in the viewport. But I think that's a credit to my laptop performance.

I'll mess around with it some more and update the post if I come to different conclusion. For now I have a different dillema on my mind. But I think I'll start a different thread for that one.