Take whatever time you need to get it right...

Tramm or Jon:

In first release are we getting any way to monitor other than LCD ? I assume, as previously indicated, we are losing Video when we get phones monitoring through AV jack.

Hi Chris,

Tramm will have to answer that. I'm just doing audio testing. I do a quick test and immediately pull the battery to remove the firmware and any possible infinite loops that could heat up the chips. That way, Tramm can send me his very latest builds with various audio tweaks without doing delivery-level testing.

But, yeah, hopefully we won't lose any features when we add the new ones...

Unfortunately, no. By disabling the hotplug task, the camera no longer responds to HDMI cables, USB cables or A/V cables. Many users have reported significant noise on the audio track when using the composite video output with the stock firmware as well, which might steer you away from trying to use it.

This is, after all, still a first beta release. HDMI support may be implemented once someone with a HDMI monitor has a need to write the code necessary to switch the camera into HDMI output mode. I don't have an HDMI field monitor, so it hasn't been a huge priority...

Yikes! Just a personal response here, but that kind of prohibits my use of the software.
My 5D is primarily used on a Glidecam X-10 rig. Monitoring video is this configuration is
more important than audio for obvious reasons. The size and placement of the camera lcd make it somewhat useless for a stabilization rig. Its a bummer that there is this either or situation. Regardless, I do appreciate the added capabilities you have created for the camera!

I fully anticipate fixing that soon after the initial release. Since you're using an HDMI monitoring, you'll be a great beta tester for that code. If I had a Steadicam and a field monitor, it would be one of the first additions that I'd make!

It looks pretty easy to switch between the different modes; set a global variable in the hdmi_config_state structure, call the refresh_video_state() function and, I hope, it all works. That is what the hotplug_task() code does; we should be able to make the same sequence of calls to force it. But I don't have any way to test it, so it won't be in the first release, and all of my gui elements are hard coded for the 720x480 LCD.

Likewise, I'm not supporting use of the internal mic. My code forcibly selects the external input regardless of if it is connected. This won't work for everyone, but we're still in a early beta state and hopefully anyone who cares about audio quality will be using an external mic.

Field Monitor
 

FYI this is the monitor I will be use with the 5D stabilized rig (when its available in about a month)
SmallHD.com - 8.9" High Definition - the DP1

Love to help
 

[QUOTE=Tramm Hudson;1161602]I fully anticipate fixing that soon after the initial release. Since you're using an HDMI monitoring, you'll be a great beta tester for that code. If I had a Steadicam and a field monitor, it would be one of the first additions that I'd make!

I'd love to help, just as soon as I can purchase one from smallHD.

Very neat. The only thing that seems to be missing is a headphone amp. If we could get HDMI audio output to the monitor and use it for audio monitoring that would be one less cable to connect to the camera.

The other major hurdle for HDMI output is to fix the mode switch when recording starts so that it doesn't blank out for a few seconds while the screen resyncs. I haven't seen any reason that it happens.

Continued Optimism
 

Whew! Im glad there are possibilltes regarding video output. I will continue to be optimistic
and assist any way I can.

You will need to have an external monitor in a lot of setups. A Glidecam or Steadicam is just one of them. Video output is more than secondary.