August 2012 Camera Update

Hi Everyone,

If you read my Kickstarter update #22 and the comments then you know that we are pushing the release date of the camera, and I promised I would give you more detailed information about where we are and what still needs to be done.Where we are now:
In the Kickstarter update I talked about the team and being ready to move forward. I wanted to go into that a little more. Vahesan is the name of our new project manager. As I described in update #20, he has experience with both military and medical equipment projects. I haven’t met him in person, but I wanted to tell you about my experience with him so far. Vahesan has over 16 years of experience in research and development, embedded systems, product development, and project management. Embedded systems is key by the way; it involves FPGA based designs like the backend of our camera. The first time we spoke was tense at first. He was calling me as the final step in bringing him on board, a sort of telephone interview. He was already vetted by the rest of the team, and had the technical skill and understanding needed to receive their endorsement. The question now was could I work with him, specifically over the phone since this is how we would interact most. Vahesan speaks with a strong accent, and in the first 5 minutes I thought this might be a problem for us, as I have had problematic language barriers before. His job requires him to be very knowledgeable about electronics, but at its core it is more about communication than anything else. Almost immediately I was impressed with how good he was at explaining complex concepts in very simple ways and how direct he was in his general communication. These were two of my major concerns. We talked for over an hour and he told me about many of the projects he had worked on in the past. He told me about his experience with one medical product in particular that really impressed me. He was brought on as project manager, the same role I was interviewing him for, when they were already over a year behind their original forecasted deadline. It seemed that as time passed, the time needed to complete the project kept growing instead of getting shorter. He quickly discovered that the team building the device didn’t have the education necessary to use the newer technology, so they were working with older processors and electronics concepts. The team had built many things in the past and were a legacy feature at the company, and they were several years into the project, so building a completely new team was not an option. Educating everyone on all of the components necessary was also going to take too long. The CEO had given him 6 months to get the project completed or it would be scrapped. He was in a nearly impossible position. When he was telling me this, I thought to myself, “I have no idea what I would do in that situation,” but he did. He broke the large team up into smaller teams with the express purpose of learning small specific micro projects. He also convinced upper management to allow a few of the older engineers to retire early so he could bring some very necessary new blood in the mix, and he set out redesigning all of the boards and component relationships himself. It was a Herculean effort, but they got the job done on time and on budget!

As I stated in the kickstarter update, Vahesan is very pleased with the team we have assembled. He is also pleased with the chosen electronics and layout we have done so far. He doesn’t feel this will be anywhere near as challenging as the medical device project. He would like to add one more position, someone dedicated to GUI (Graphical User Interface), but other than that he feels like it’s one of the best teams he has gotten to work with! We do have someone working on GUI, but that engineer is also working on other firmware elements. We originally thought our menus will be so simple that we wouldn’t need a dedicated person, but Vahesan feels that a dedicated person is key to a good user experience.

My next interaction with him was just as impressive. I had given him the very difficult task of getting up to speed on all of the electronics, interviewing all of the engineers working on the project, and writing me a report based on his findings in just three days. I wanted to write an update for you guys by Friday August 10th, and Monday the 6th was a holiday in Canada so no one was there. I hadn’t heard from him by closing time on Thursday so I gave him a call, a little nervous that I was going to hear, “sorry there just wasn’t enough time.” Instead he answered the phone “I am working on the report right this minute and was going to email you!” He promised to send me the report that evening and he did as he said. Well after midnight his time, I received his report, and it was thorough! A lot of it is internal stuff, but I pulled a few lines for you to get a sense of it…

All of the components for the Sensor board and FPGA boards are secured. The DSP processors for DSP board also have been secured. Most other components are being ordered now, and should come in within a few weeks.

The mechanical design of the housing has been progressing steadily, Proto rev 3 is now complete and in fabrication. Mechanical parts are expected to start coming in 2 weeks. In general complete fabricated housing is expected in 4 weeks’ time.

The SATA interface has been tested on an eval board even with the DNG file format at 100MBps. The test was successful.

HDMI and display interfaces have been fundamentally validated, but they still need to be ported into the Bolex design.

The entire report is three very dense pages like this. I think I read it at least 3 times trying to absorb all of the information. Basically, like I said in the Kickstarter update, we are over some of the biggest hurdles. We have in our possession a lot of the components, and what we don’t have is on order. Most importantly, except for one more hire, we have everyone we need in place and are working hard to complete the project!

Here are a few pictures of some of the people doing this awesome work for us…

I hope this gives you all a better idea of where we are and how we are moving forward. Please feel free to ask further questions and I will as always do my best to answer them.

Thank you all for your support,     Joe

This entry was posted in News by joerubinstein. Bookmark the permalink.
joerubinstein

About joerubinstein

Joe Rubinstein is one of the founders and CEO of Digital Bolex. At Polite in Public, a photo marketing company he also co-founded, Joe was the Chief Technology Officer who worked with electronics developers and software developers to create the Polite in Public Photobooth which helped define modern photo marketing services.

19 thoughts on “August 2012 Camera Update

  1. Thanks for the update! Better focus on getting this thing pushed, instead of answering our stupid questions, I’d say! (like how will the trigger on the grip be connected, or hundreds of others ;-) )

  2. There is a 3 pin connection for the pistol grip on the bottom side of the camera. We are tying to think of everything :) And answering peoples questions is not holding up the camera. If you guys like reading this stuff I’m happy to write it :)

  3. A few more stupid questions! How fast does the CF card need to be? What brands and speeds do we need to buy? Since the SD cards are not “fast” enough just need to get a feel for what will be good enough?

    On the pistol group could we have a 3/8 threaded hole to attach say a monopod? Monopods make good steady cams in a pinch…

    Of the awesome vintage glass available on ebay I am finding some are “TV Camera” cmount and some are actual “bolex” lenses some have electronic control and some are reflex lenses… How do I make sense of what would work well on this camera? I know if I am spelling it right “Kern Paillard” “Angenieux” are good ones yes?

  4. Thank you for the update and the transparency Joe.
    I like “Filmgeek’s” idea of the 3/8 threaded hole added to the pistol grip a lot. Can you make this possible Joe?

    • Though that might be good for occasional mounting to a tripod, there must also be a more robust solution to attach the camera to a tripod, trigger it, and have 15 mm rails mounted thereon. I suggested a special base plate with mounting options for:
      -15 mm rails front and back (i.e. reach through the base plate)
      -the normal grip (including electrical connections for the record knob)
      -a video head base (1/4″ inch)
      -an Arca Swiss quick release base mount.

      I am not sure how all this could be integrated into a single base plate, but believe its mostly like a puzzle ;-)

  5. Please don’t leave the GUIs up to the engineers, “simple menus” don’t come easy you know? Hire a proper interface designer and have him work with the engineers.
    A good example of engineers’ user interfaces vs designers’ interfaces would be windows vs OSX…

    • Hey Joe!

      I was a UI designer for online games for years after graduating from college, so trust me, I took care of the UI and menu trees for the camera already! I’ll also be working with whichever engineer is hired to do the programming.

      Elle

  6. Maybe an intrusion to your workflow, but could Bluetooth be included in its function package? Bluetooth pairing to the Slate-Clapper iPhone app leaps to mind. I know, I know, its a little accessory for limited functionality, but Bluetooth can also carry audio, (wireless headphones & mic pickup for the Soundy) and tramsit camera data.

    Battery life/facility? will it be on-board (a la the maligned BlackMagic option) or will you use batt packs or external tethering?

    Mad keen about this camera. MAD KEEN!

    • Yes, I agree with Ivorbiggun,
      Mac compatibility is essential, and some degree of slo-mo would be nice (at least as a modification later).
      Final Cut 7 compatible, possibly (with a converter program)?
      Or would I need to get the Adobe Suite of programs to work with the CinemaDNG files?
      (BTW, I still think ProRes is still a viable codec).
      Thanks for your efforts and I’m looking forward to the camera’s release!
      -Mike

  7. To convert DNG to ProRes 12-bit 4444, you only need AE CS5.5 or CS6 and the Adobe DNG plug-in.

    This works really well as the DNG processing is floating point and the AE export math is 16-bit. I hope the camera is not held back waiting for un-needed software as nice as it might be for some.

  8. Two questions about specs:

    1) “320×240, 2.4” diagonal, with Focus Assist” how is FA implemented when the LCD, I think, is B&W? Peaking?

    2) In 720p mode, what frame-sizes and frame-rates are available?

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>