John Heagy
Forum Replies Created
-
After reading this thread I jumped to reserve my tickets. There were 40 left and the number was dropping by the minute. 10 mins ago they were SOLD OUT. Now there are 5 available… weird. Seems somehow seats are being added a few at a time.
John Heagy
-
I agree, P2CMS is a typically poorly designed Panasonic P2 product. I does a few things we find handy. We use it to combine multiple cards into one CONTENTS folder, or as we call it, an “Uber Card”. We then use P2CMS to modify the xml metadata, specifically “Program name”. We use Calibrated MXFImport to map this to Tape/Reel. Panasonic felt it necessary to omit that time honored and important metadata. We require it.
Never used Shot Put… can it do the above! We’d dump P2CMS in a second if it did. Didn’t find anything on Imagine’s web site to indicate it does.
Thanks
John Heagy -
[Jeremy Garchow] “wouldn’t it be easier to send lanc control in to Ki, then out to camera to roll it? If Ki stops rolling, so will camera with signal sent from Ki? That way camera rec indicator will essentially act as Ki rec indicator.”
I’ve never used a LANC port, but since the jacks are labeled “LANC Loop” I’d think It would allow the cmd to “loop through” the KiPro to the camera and roll the camera indicating a “rec”, even if the KiPro didn’t roll due to a full CF… etc. One may need to “blind” the camera to the “go into record” cmd from the button and make it go into record on an “I am in record” output cmd from the KiPro, if it’s even possible to do that with a LANC loop. I’d imagine the LANC Loop is designed to “daisy chain” multiple KiPros and trigger them via a single LANC controller.
Any LANC users that can speak to how devices work when “daisy chained”?
If the future implementation of the LANC loop includes the option to blank the “go into record” input cmd from the output, and instead generate an “I’m in record” output cmd that a given camera can understand, then great. Aja… make it so. Having said all that, I don’t think LANC ports are common on professional cameras and would be case by case even on cameras that do. May be too complex regardless.
The TC Rec Arm option would work well to roll a KiPro in “Rec Run” so just a LANC response from the KiPro and a remote “rec” light is needed. This wouldn’t work for TOD as TC is always there. A work around might be to use an ext TOD LTC generator, or TC output from the camera, set up so a camera start button switches the LTC stream to the LTC input of the Mini to start a record. The LANC could output rec status and light a remote indicator.
I suppose it’s either a remote button, and possibly a viewfinder “rec”, or a remote “rec” light, and possibly use the camera’s own start stop button. I don’t see a way to use both, unless some cameras have a pin out for remotely triggering the viewfinder “rec”.
The bottom line in all these “options” is getting an “I’m in record” confidence output of some kind from the KiPro. Considering the LANC ports are currently not functioning, I would propose an option that simply has one of the LANC jacks output +5 volts if a recording is rolling and 0 volts if not. If designed to power an LED “rec” indicator directly… all the better! This record status cannot be a set and forget, it must be constantly monitored. It could be tied to the KiPro’s Record button light I suppose.
Am I the only one that considers this a requirement for “run and gun” shooting? If not, please chime in! There seems to be a new compact ProRes recorder announced every week, and none of them have this feature. If Aja added this it would separate the KiPros from the pack.
Details… details…
Sorry for the length.
John Heagy
-
I’m not a cameraman, but I’d think not knowing, definitively, that the unit is still recording would distract me and elicit momentary “pucker” moments when I don’t see the comforting rec indication in the viewfinder. The obvious solution is a remote “rec” light mounted on the eye piece. This light should indicate the status of the KiPro and not the command sent to the KiPro. In other words; the indicator doesn’t light until the KiPro actually starts rolling. If the KiPro stops for any reason, then the light goes out.
It’s unfortunate that the Lens Tap port was not included in the Mini. It’s still not enabled in the KiPro. I suppose not enough customers asked for it’s activation, but then few KiPros where actually “strapped” to run and gun cameras… the Mini will be.
The devil is always in the details…
John Heagy
-
Ah… that is the case. We are using it for ProRes playback into our DaVinci for grading. It beats taking PrpRes to HDCam first. This behavior is certainly acceptable considering it provides preroll even if none was supplied in the file.
When not in 9 pin remote a cue function would be nice… maybe holding Stop then Play to recue the current clip. Using the select arrow button will cue the clip if it’s the only one on the drive, otherwise it cues previous.
Thanks
John Heagy -
I have seen the infinite timeline effect as well. When rewinding to the beginning of a clip, the beginning of the clip is reached but the timecode keeps descending. One must fast forward through this empty time to reach the actual start. Certainly makes cueing difficult. These were QT files exported from FCP.
-
While we’re in the feature request mode: Please enable the Lanc port on both the KiPro and Mini and include record start/stop input and output so third party start/stop remotes with feedback can be devised.
Ideally a Lanc start/stop would take a signal from the camera’s on board start/stop and convert it to Lanc protocol to start the KiPro. The KiPro would send record status back and light an LED that could be mounted on the camera eye piece. Considering camera men don’t have eyes in the back of there heads this seems a near necessity for doubt free operation.
Thanks
John Heagy -
fcpreconnect will only work if the TC and reel are consistent. You must either modify the seq to match your reel names or the ProRes files reel names to match the seq. If you have duplicate reel names for media across the same TC… then you may have to modify both. Modifying the seq via an exported EDL would b easiest.
Good Luck
John Heagy -
[Gerret Warner] “Vimeo says aspect ratio should be set before uploading.
“Ah… then you should not rely on an anamorphic file making it to Vimeo correctly. Export a 480×854 square pixel file from QT 7. Never use QT 10 for anything… it’s a toy. I got my 720s and 480s mixed up in my previous message.
John
-
If buy “display” you mean play in QT Player then you need to go into Movie Properties, select the Video Track then the Visual Settings Tab and change the Scaled Size to 720×854. You’ll need to uncheck Maintain Aspect Ratio.
John