anyone ever captured through mojo with a red scarlet?

[Brian Merlen]

Supposedly the mojo and nitris cant do true 24p is what i am being told... that it really does PsF despite claims it does true 24p. I hope either the kona, or black magic solution will work for us. Or that we find a work around with the hyperdeck.

[MichaelP]

When 24p is being referenced, it usually means editorial at 24.000fps progressively (all effect and such are frame-based). I/O for decks and such have always been PsF legacy wise and that is what is expected by the hardware. v6 does have some switch somewhere to output as P (for monitoring) versus PsF, but I am unsure about capture, but my feeling would be it still expects PsF.

Michael

[Brian Merlen]

Using the blackmagic multibridge pro we are feeding directly into avid logging and capturing in real time despite the P vs PsF issue. So essentially the workflow is solved and functional now. Thanks for all your help!

[MichaelP]

Excellent! I wonder if it is converting from P to PsF or not. I'll have to look into that.

Michael

[Brian Merlen]

We are noticing a lot of tearing on the pans and tilts in the deliverables to the client. The DP suspects it might be from the P to PsF conversion. The weird thing is it happens even on the Red Mag stuff we shot. The Red Mag shots are usually for frame rates the HD-SDI wouldn't support (overcranking to various FPS). So we aren't sure what is causing the tearing, youtube, the PsF conversion, the output settings for the post guys, the RedcineX Pro settings for the Red Mags. Perhaps the Redmag stuff tears because its put in the same timeline as the PsF footage? Do you know how Avid interprets the PsF? I was reading about PsF on some other site and it said some NLE's interpret it as interlaced, which also might explain the pans/tilts tearing.

Michael you have been so helpful I cannot begin to thank you for your insights, but you think you can take a look at this link and give me your proverbial two cents? The "recipes in motion" part is specifically our stuff we did for them (on Scarlet), the link is directly to the index of our stuff. Or if anyone else feels like throwing me a bone on this subject I am all ears. I just want to make sure we can get rid of the tearing tilts and pans.

http://www.youtube.com/playlist?list...7&feature=plcp

[MichaelP]

Brian -

There should be no difference between a PsF capture or bring in full progressive material via an import since PsF is really more how the frames are stored for transport. Frame splits odd/even on equipment that was originally built for interlace materiel. If you look at the original redmag material in REDCINE X, do you see a similar tearing in the material?

Michael

[Brian Merlen]

No its not in Redcine, I think its caused by the compression settings of the deliverable (specified by the client). The clients happy, the DP, not so much...

[MichaelP]

Is the compression setting throwing away 1/2 frame (1 field)? That would be strange for progressive encoding... strange.

Michael

[Brian Merlen]

The editors are making MP4's that are only 200mb's for delivery. I think that is why the final images are so terrible, relative to the less compressed acquisition formats. The DP had me talk to post about the issue but they assure us the client specified the delivery format and size and is thrilled with it. To the untrained eye, for online content it looks fine I suppose, plus most people will watch this on smart phones and tablets, so looking at the defects on huge desktop monitors might be the wrong way to QC for it.

[Björn Benckert]

My guess as stated above: the temporary P versus PsF issue on the signal. Red does PsF, not liked by so many recorders or converters... I think we solved it with a black magic up down cross converter as the first thing on the chain after the camera. Setting this converter to 1080P output will make the signal readable for your gear.

Im not 100% sure of the above but we ran into the same thing trying to go trough our milo mixer and then pass on trough some Aja converters and out in FW and MXO2Min to PC Express and thunderbolt....

not a single one of those paths worked until we got the up/Down/cross...