Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums AJA Video Systems Workflow – Phantom Cam & 35mm

  • Workflow – Phantom Cam & 35mm

    Posted by David Jahns on June 30, 2009 at 10:14 pm

    We’re putting specs together for a TV spot which will be shot 35mm & some Phantom Cam super high speed stuff, finishing 1080p23.98.

    We’ll offline in FCP at NTSC 23.98 (Cinema Tools rev telecine), and re-transfer film to HD at online stage. The Phantom Cam will be shot at 1920 x 1080, and we have a choice of delivery specs – TIFFs, DPX, or Quicktime. For offline, we’ll need NTSC 24 quicktimes, of course, but we’ll want to reconform to the original HD frames for online.

    I thought we could get DPX files, use the AJA DPX to QT Translator, then export NTSC quality QTs, which could match back to the DPX files via the timecode. Good plan, eh?

    To test this out, I had some DPX files rendered out of Color from a previous test, but the DPX Translator says, “Error: couldn’t open file.” Any idea why that would be? I read one post that said the DPX Translator only works with 4:4:4 footage. is this true? Is there some other reason 2K DPX’s rendered out of Color wouldn’t open in the AJA software?

    I suppose we could get TIFFs, but those will not have timecode info, just frame numbers, and we’d have to create quicktimes with burn-in, and then manually prep the frames for online.

    Or should we just get Uncompressed 1080 quicktimes instead of frames? Any downside to that? I suppose the 4:2:2 conversion isn’t as ideal as the camera’s raw format, but it’s just going to finish in HD 4:2:2 anyway, so the loss would be negligible.

    (We don’t know what system the online will be done with, and our local Flame guy always hates it when we bring him quicktimes – gamma shift issues, etc…)

    Thanks for any help!

    Robert Monaghan replied 13 years, 6 months ago 4 Members · 14 Replies
  • 14 Replies
  • Gary Adcock

    July 3, 2009 at 1:33 pm

    OK

    first off why are you doing an NTSC offline, with todays HD codecs that can cause more trouble than necessary especially when working with commercial content.

    Since you say the Phantom is being shot as 1080, and you are doing a 1080 4:2:2 finish, why not have both the phantom and the 35mm transferred to HDCamSR (which is 10bit as 4:2:2 or 4:4:4) and use the tapes as your masters?

    The issues that I see with all of the content from both cameras as DPX files- jumbo storage and desktop needs to handle the files, software down conversions do not always carry correct timecode for relinking.

    Let the flame guy do his own conversion from the master tapes-

    gary adcock
    Studio37
    HD & Film Consultation
    Post and Production Workflows

    Check out
    https://www.aja.com/kiprotour/

    Inside look at the IoHD
    https://library.creativecow.net/articles/adcock_gary/AJAIOHD.php

  • David Jahns

    July 6, 2009 at 4:45 pm

    Hi Gary. Thanks for your suggestions.

    We’re doing NTSC-24 offline because the creative team is more comfortable with an offline/online workflow when dealing with 35mm film – they’ll inevitably want to see the entire 4×3 full gate frame, reposition & blow up, etc.

    A few projects back, we did the dailies film transfer to SR 16-9, but when we wanted to reframe some shots, we didn’t know what was in the top or bottom of the 35mm frame, and we had to retransfer anyway – and then rent the SR deck again, too.

    We still shoot 35mm film and do this off/online workflow quite often, it’s just the Phantom Cam footage that we’re trying to figure out the best plan for.

    Since it’s just short format TV, we’ll just get TIFFs, create QTs with frame burn-ins, and manually re-conform later, but if anyone knows why the AJA DPX translator didn’t work with Color’s DPX files, I’d love to hear about it.

  • Gary Adcock

    July 7, 2009 at 2:05 pm

    [David Jahns] “Since it’s just short format TV, we’ll just get TIFFs, create QTs with frame burn-ins, and manually re-conform later, but if anyone knows why the AJA DPX translator didn’t work with Color’s DPX files, I’d love to hear about it. “

    2 reasons.
    not a standard frame size for video playback or
    the files are not standardized DPX frame sizes – is Color creating them or some other app?

    gary adcock
    Studio37
    HD & Film Consultation
    Post and Production Workflows

    Check out
    https://www.aja.com/kiprotour/

    Inside look at the IoHD
    https://library.creativecow.net/articles/adcock_gary/AJAIOHD.php

  • David Jahns

    July 7, 2009 at 4:33 pm

    Ah, yes. Thanks, Gary.

    These were DPX files created from Red 4K files. I created some 2k DPX’s from Color, and they work just fine with the KONA Translator. Thanks for your help!

  • Gary Adcock

    July 8, 2009 at 4:59 pm

    [David Jahns] “These were DPX files created from Red 4K files.”

    AJA’s app was not designed to handle 4K rasters.

    gary adcock
    Studio37
    HD & Film Consultation
    Post and Production Workflows

    Check out
    https://www.aja.com/kiprotour/

    Inside look at the IoHD
    https://library.creativecow.net/articles/adcock_gary/AJAIOHD.php

  • Robert Monaghan

    July 9, 2009 at 12:31 am

    Hi David,

    We provide a Phantom Cine Toolkit for FCP. It does a number of things which will make your editorial life better. One of these is adding a Time Code track to the Phantom Clip, which will make it possible to conform with Phantom footage. (We also sell a separate DPX package, which allows FCP to work directly with DPX footage too. But it may not be helpful to you.) Download a demo from our site..

    bob.
    ww.gluetools.com

    Robert Monaghan, CEO
    Glue Tools LLC
    629 State St. Suite 220
    Santa Barbara, CA, 93101
    United States

    tel: +1 805 456 7997
    fax: +1 805 456 7998

    http://www.gluetools.com

  • David Jahns

    July 9, 2009 at 1:07 am

    Thanks, Bob.

    I did look into Glue Tools, and have downloaded the demos of both packages.

    For this project, the Camera Tech will handle everything and deliver us both QTs and DPX’s with matching timecode. I think he’s using Glue Tools, actually… 😉

  • Julian Lalinde

    October 10, 2011 at 4:31 pm

    “We provide a Phantom Cine Toolkit for FCP. It does a number of things which will make your editorial life better. One of these is adding a Time Code track to the Phantom Clip, which will make it possible to conform with Phantom footage.”

    Hello Robert,

    I wanted to ask exactly how are you adding a time code track to the Phantom Clips? I am working in a Rental house, we have two Phantoms and have different types of external recorders like, Nano Flash, Aja KiPros, and CODEX soon the Gemini. We have bee looking at ways to make the post poduccion process easier by providing offline material which they can later reconnect with the original .cine files. The main problem is that we don’t have a time code track for them to be linked with. We find the .cine files count frames from minus zero to a value dependent on the clips size. The Aja recorders dont record a time code either.
    We know of the conversion possible from .cine files to quicktime, but this is very time consuming as it takes sometimes a whole extra day of conversion. It would be ideal if the offline clips could be obtained at the end of the day on set.
    We and a lot of post production houses already have gluetools, any help on this matter would be greatly appreciated.

    Sincerely,

    Julian Lalinde

    Chief External Technician
    Congo Films
    Bogota, Colombia
    congofilms.tv

  • Robert Monaghan

    October 10, 2011 at 4:42 pm

    Hi,

    I generate a SMPTE TimeCode track using a system that I had developed. Basically it is generated from the time stamps from within the Cine itself. In the licensed version, this timecode track is always there. You don’t need to do anything.

    In a future release of my software (which should be soon) I will be creating a TimeCode track using the same mathematics that the Phantom Flex uses. So, if you set up your Flex to playback at 1080psf24, for instance, you will get a valid SMPTE timecode out of the TC port. This timecode will match the Timecode my software generates.

    I have extended this compatibility to other cameras, too, under some circumstances.

    In a nutshell:

    SMPTE Timecode is always there, in the licensed versions. If you are conforming in FCP, the TCs of a proxy rendered using my software, will match the Cine file.

    Proxies created from the Flex’s HD-SDI Out, will match a Cine played back in my software, in an upcoming update. (This week?)

    bob

    Robert Monaghan, CEO
    Glue Tools LLC
    POBox 24124
    Santa Barbara, CA, 93121
    United States

    tel: +1 805 456 7997
    fax: +1 805 456 7998

    http://www.gluetools.com

  • Julian Lalinde

    October 10, 2011 at 5:05 pm

    Hi,

    Thanks for the quick response. That means that at the moment there is no way of getting the time code from the time code port in the back of the Phanomt Flex?
    The method you are currently using is still with the original .cine files, importing them via gluetools info FCP, right?
    With the update you mention, would it be possible to do the workflow I mentioned?
    eg.

    Flex-playback- Aja Ki Pro connected via SDI capturing 422 proxies. Time code cable connected to TC port on camera to TC port on KiPro.
    Resulting in having easy to manage 422(PX) files for editing, which have SMPTE time code, so that an edl is made to conform with the original raw .cine clips.

    Let me know if this is already possible, or we have to wait for your update.

    Regards,

    Julian Lalinde

    Chief External Technician
    Congo Films
    Bogota, Colombia
    congofilms.tv

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy