Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
b) Card spanning? Are there plans for any firmware that allows spanning for the Ki Pro Mini?
Reply: At this time, the Ki Pro Mini does not provide the ability to "span" cards; if AJA provides such a feature in a future firmware update, it will be considered "rollover" as opposed to spanning (to be precise about the terminology used). Contrary to another posting on this thread, this was not a promised feature of the device, but rather something that AJA has said it would like to offer in the future. The device has two CF slots so that users can use the SLOT button to unmount the first piece of media and mount the second piece of media without having to physically remove and insert new media to quickly begin recording again. You can refer to the Ki Pro Mini operation manual, page 10, for proper use of the SLOT button. I would strongly recommend reviewing the operation of the CF media and the SLOT button as appropriate removal of CF media from the device is an important procedure.
Duke M. - Often, when a feature is not promised on a product, that does not mean that it has not been considered at some point during the development process. Having said that, un-promised features always come later in the development cycles for products if they are deemed possible to implement and users express a demand for them; feedback, like you are providing, is of course helpful. At AJA, we sincerely try to incorporate feature requests and feedback in an effort to improve our products and their operation.
I also appreciate that, in an ideal world, you would keep your eye in the camera's eyepiece and all of the data from the Ki Pro Mini would be reported in the eyepiece so that you didn't have to monitor the recording device's status separately; however, that simply isn't possible for a recording device that attaches to a camera via baseband video connections. There isn't any data conduit for the video recorder to report it's status back to the camera the way there is for the camera to report it's own internal recorder's state. A good analogy for video recorders attached to video cameras via baseband connections is this: think of them like film magazines that are used on film-based motion picture cameras. Film-based cameras required the user to keep an eye on the magazine and evaluate it's state. If the film was running low, you knew to switch the magazine; if the Ki Pro Mini CF card capacity reported on it's UI is low, you might consider switching the card out before the next take.
Thanks for the reply. I think you misunderstood part of what I was trying to say. My apologies for being less than clear. I didn't mean to imply there should be a connection between the Ki Pro Mini and the monitor (although that's an intriguing idea.)
It seems the most common ki pro mini mounting options are behind the camera on rails (which helps with balance) and on the right side, especially when being hand held. In both locations the operator can't see the AJA screen to see how much time is left.
At the same time recording times on CF cards are short. At ~$1k per 64gig card, the 32gig cards are more common. On HQ, and if you don't use the full card, you have maybe ~15 minutes of record time. It would be easy to miss a card change and miss a shot if you can't see the AJA view screen because its behind you, etc.
I imagine the development of those features is made more difficult by speed or size of the write buffer. Maybe a scheme of dynamically reallocating the buffer would help.
Don't get me wrong, I like my Ki Pro Mini and I understand it's a new product that will mature with time just as my Nanoflash firmware matured with time. However, some of the most important features they enabled were 1) time code trigger (which you have) 2) spanning or rollover (which would nearly double the recording time) and 3) hot swapping (most helpful for live events but which may be precluded).
All of these features help to avoid missed shots and in a professional environment protection of the footage is paramount. That points to where your firmware development efforts should be aimed.
Thanks for listening,
Duke