[Jeremy Garchow] “Let’s chase down what the hell is it you are trying to test. No offense, but this is a mess.
Hi Jeremy
No offence taken, I’d noticed some green flashing on downconverts when testing in an SD environment – so I was trying to test out as much as I could whilst in a room with a Tek HD scope with limited time. Main testing was 2 hour long captures and playback of ProRes SD ensuring frames not dropped (successful).
Why not use a real HD clip when testing HD outputs?
Source was an SD VTR – this is a likely workflow scenario for me – captured SD footage mixed in an HD timeline with outputs to SD. I did get the green flashes in the original SD downconvert tests with generated HD clips, this is why I was trying different HD flavours.
What scratch drive are you testing?
FW800 single drives – non raided but reporting good enough figures with AJA test. 56.9 MB/s read 79.7 MB/s write. Wouldn’t expect to use this in the real world but should be plenty for ProRes HQ single stream playback. And lack of speed would be dropped frames rather than green flashes I would think?
What easy setup have you chosen?
I am switching to AJA installed ones. 1080/50i and DVCProHD or ProRes or ProRes HD or XDCam 422 HD CBR as appropriate – checking seq settings before playback etc.
Have you opened the Control Panel yet?
Yes.
[Trevor Asquerthian] “AJA Digital out set to SD (i.e. downconvert) ”
THis isn’t the way a downconvert works on AJA products. You leave FCp in the proper Hd easy setup (with matching HD footage/frame rate timeline) then use the Koan control panel to downconvert (set output to secondary and appropriate NTSC/PAL frame rate that is based off of your HD timeline).”
That’s what I’m doing, I removed that whole explanation from my post as I thought it was too obvious 😉
Correct easy setup selected. Sequence matches easy setup. Primary output 1080/50i, Secondary output 625/50i, Digital Out set to Secondary output – control panel shows ‘downconvert’.
The thing I need to find out next, I think, is are the green flashes caused by IO Express or FCP. If FCP then I would have thought they would be apparent on laptop display? I guess I’ll see if AJA TV generates the same errors.
I’ll start with clips that are native to the timeline I’m testing too!
Thanks for your help on this…