[David Massachi]

Graeme,

Thanks for breaking down the formats for us. Very helpful.

Can you add one more bit info to the list, though:

Isn’t HDCAM recording 1080 as 1440 X 1080 instead of actual 1920 X 1080? Is that basically a way of electronially squeezing the image (and making it anamorphic), or is that a pixel aspect ratio difference, or is that the same thing? Is that what you mean by “raster”?

What about the other formats and/or other frame sizes? Do they have pixel aspect ratio differences?

massachi

[David Massachi]

So, going back to original question:

what is the exact difference beetween the way the hvx will have progressive image and the way sony do in 750 and 900 camera their psf mode?
for film and for video

massachi

[David Massachi]

I just did a search in this forum looking for info on “PsF” and found this older thread we’d communicated on a while ago.

Can you explain what PSF means? What does it stand for?

massachi

[David Massachi]

Where can I learn more about the difference between “FPS” and “PSF”. If not too much to ask, can you explain it further here? I’m confused.

massachi

[David Massachi]

I think I’m back up and running now. Installed new driver (v2.0) today and also new firmware. Then I uninstalled QT 7.0.1 and kept QT Pro 6.5.2. I tested a couple of times, reverting to earlier drivers (at least attempted to) and nothing seemed to fix the problem: ETT would start off frame-accurate and then at 01:03:54:29, it would start laying down video one frame early.

Finally, I re-installed QT 6.5.2 over QT 7.0.1 (using Apple’s re-installer) and that seemed to do the trick. Now it’s all frame accurate as far as I can tell.

I’ll be cutting tomorrow so it remains to be seen if the crashes still persist. But, I have a little more confidence in the system now, and especially the new AJA drivers and firmware because they’ve been beta versions for so long.

massachi

[David Massachi]

Joe,

thanks for the details on your system. I called AJA and they basically said to re-install older drivers, just do a find for “ProIO” and delete what you find, then install the driver you want.

I haven’t been able to solve my problem. On ETT, it’s dead-on frame-accurate except for this one sequence. I’ve tried to output this sequence on another FCP system with the same specs I had before my update, and it outputs perfectly. Very strange. Anyway, if I can’t solve it soon, I’ll just put everything back to the way it was, and hope that fixes it.

Any other suggestions?

massachi

[David Massachi]

Great, Joe. Thanks for checking. I look forward to your post tomorrow.

massachi

[David Massachi]

What exactly do you mean by “23.98 frame rate support?” Will I be able to capture through any of the inputs and remove standard 2:3 pulldown? What capture codecs will this work for (UN8 and/or DV25)? Will I be able to play out to tape/monitor through any of the outputs and add standard 2:3 pulldown on the fly? What timeline codecs will this work for?

My system:

G4 Dual 1.42 GHz
2 GB RAM
OS 10.3.9
FCP 4.5
QT Pro 6.5.2 (and QT Player 7.0.1)
Uncompressed 8-bit 4:2:2 via SDI to/from DVW-A500
Xserve RAID

massachi

[David Massachi]

I work on a system with this config

OS X 10.3.4 (but can update to 10.3.9), FCP 4.5, QT 6.5.2 (but can update to QT 7.0.1).

I am most interested in these 2 features of the Io Driver version 2.0b3:

– reduces the latency through Io
– added support for 23.98fps

What can I do right now (aside from upgrading to Tiger and FCP 5) to get these features?

massachi

My system:

Dual G4 1.42 GHz
1GB RAM
OS 10.3.4
FCP 4.5
QT Pro 6.5.2
Compressor 1.2.1
Xserve RAID
RAID Admin 1.3.3
RAID Firmware version 1.3.1-1.2.4
AJA Io with Driver v1.2 and Firmware Update v21-24
Uncompressed 8-bit 4:2:2 via SDI to/from DVW-A500

[David Massachi]

According to the AJA Io Support Page, these are the Non-Tiger, Non-FCP 5 benefits listed for the Driver version 2.0b3: