Thank you Richard. I don't think the juicedLink is good enough, at least everything I've heard so far with people testing it to the 7D and 5D.
I think the problem is plugging sound directly into the 5D and most options are only slightly better work-a-rounds. I think I'm spoilt with decent XLR cables and sound options in the XL2 and XL-H1, so am searching for similar clean professional level sound option for the 5D and D3s; but still not found one.

The best sound so far seems to be with the seperate sound devices such as the Zoom 4 and Zoom 4n. I'd rather hook up sound direct to 5D but maybe the Zoom is now my only viable option, and at least I can connect my XLR leads into the Zoom and then download the clean sound files for editing without it going through the 5D onto the CF card.

It seems that a lot of people were under the misconception that the firmware update would somehow miraculously solve all 5D sound problems. Aside from the ability to to overcome auto-gain and the imperceptable shift from 44 to 48KHz very there is no great improvement here. We still have the crappy 5D preamps which (as a general rule) will only be usable for particularly loud sound sources. From my perspective this upgrade just brings us to more or less where we were with Magic Lantern, but without overlayed onscreen monitoring. As such I think Jon Fairhurst's analysis is as relevant as ever.

http://www.dvinfo.net/forum/canon-eo...-complete.html

Well, I honestly based my decision off this series of videos comparing the options. It seems they conclude that the Juiced Link is the best option over external recorders.
But until Magic Lantern is updated to work with 2.0.3, I am thinking that an external is the best choice. Since I already have the JuicedLink, I'm choosing to wait for ML update. It seems the JL sounds better IMO, plus you don't need to sync in post.

I actually believe there was one thing left out of Jon Fairhurst's series of tests on 5D sound. He didn't cover the use of a field mixer feeding the 5D through an XLR adapter like the CX231 or the even one of the unpowered Beachteks. In my experience, that combination will get you great in camera sound.

Problems?
 

Seen this?

http://www.usa.canon.com/app/pdf/5dmarkII_203popup.pdf

I saw somewhere that someone experienced some issues on the sound end. Not sure where yet.

I would have thought that Canon would have had plenty of time over the past year to test the firmware for possible issues. At least they are working on it and hopefully bringing out any needed updates very soon.

There has been reports of the old 'banding problem' returning as well.

interesting reports of ISO bugs with the new firmware.. can anyone else corroborate?

EOS 5D MKII - Loaded 2.0.3 Manual ISO Not WOrking Even In Manual: Canon EOS-1D / 1Ds / 5D Forum: Digital Photography Review

What do you mean with ISO bug?
Problem with ISO was that operator did have settigs Exposure simulation instead Movie display. That caused camera to use full automatic with video. Instruction manual page 127.

This is correct. After I installed the new firmware, the camera had reverted to exposure simulation. That will cause an auto mode to occur. Its one of those things we regular video shooters set when we first got the camera, and never touched again.

You got me worried for a moment there but I just double checked & my camera did not revert to stills mode & exposure simulation. It stayed on Movie Mode as I set it over a year ago.

It seems that the main reason Canon has placed the note is due to problems recording in C1,C2,and C3 (as mentioned earlier).

My cameras happily seem to be working Ok after the download (although extreme hissing even with off-camera mics is bugging me that possibly the firmware made things worse in that respect).

It is amazing how many people found themselves with a dead camera as soon as they downloaded the new firmware, and I feel sorry for anyone who needed the said camera for an important shoot.

I set the volume to manual set it about 1/3 rd of the way up and in manual mode it does not record audio.

I found this on Canons website:
EOS (SLR) Camera Systems - EOS Digital SLR Cameras - Lenses - Flashes - Wireless File Transmitters - EOS 5D Mark II Firmware Upgrade 2.0.3 - Canon USA Consumer Products

Important Update Information for
Firmware Update Version 2.0.3

We recently discovered a malfunction that occurs with Firmware Version 2.0.3, in which the manual recording levels for C1/C2/C3 are changed and the EOS 5D Mark II digital SLR camera becomes unable to record audio if the power is turned off (or if Auto power off takes effect) after registering "Sound Recording: Manual" in the camera user settings. For customers who have already downloaded and updated to Firmware Update Version 2.0.3, when using the camera with the mode dial set to C1/C2/C3, please set the Sound Recording settings to Auto to record with audio.
We are currently preparing a new firmware that will correct this malfunction and have temporarily disabled the ability to download the current firmware until the issue can be resolved. We will re-enable the download link on our web site and notify you via e-mail when it becomes available. If you have not registered your EOS 5D Mark II, please register so we will be able to notify you.

Canon always strives to provide the highest quality products to our customers. We sincerely apologize for any inconvenience this may have caused. We appreciate your kind patronage and support.

http://web.canon.jp/imaging/eosd/fir.../firmware.html

Olof, is your manual recording level not working only when you are in the custom modes? Try setting your camera off C-1,2,3 and see if the manual recording levels will then work correctly. Mine seems to be OK...but I'm getting worried I've missed something important.

It sounds like a lot of those folks, if not all maybe (?), updated with an incomplete firmware file. Doh! It's not like upgrading firmware isn't a delicate operation where every step counts (or you can brick permanently in some cases), and it's not like the instructions EXPLICITLY said to check the file size (they did, RTFM people) -- although I'd prefer a checksum personally. I mean don't get me wrong, I sympathize with those users, I feel bad and all, but seriously, who updates firmware without making sure the file was complete? That's suicide!

That's true. If you run a powered field mixer with clean preamps and a line level output into a juicedLink or other XLR to mini adapter, you will get great sound. The key is that first stage after the microphone and a nice hot signal into the 5D2 with the 5D2 gain turned down.

I would be less inclined to run the mic into a passive mixer and then to the juicedLink. My preference is to go straight from mic to preamp with as little as possible in between. Once you've brought the signal level up, then the signal path is more forgiving.

I had no audio at all in the manual mode. I went back in and set it to auto again. And now I get audio like before.

I may try some other things tomorrow, but for now everything is working OK except the manual audio.

It sounds like Canon knows about this and is working on a fix.

BTW, I find the new live histogram very helpful for setting exposure, even if it dissapears after recording starts.

-----------

Hannu,

On p 131 and 132 it does state you can see the histogram in manual mode.

And it works very nicely for me at least.

Sorry Olof,

It's 5:00 am in Finland, not the brightest moment for my brain... I need my morning coffee.

Hannu, it happens to me all the time.

Is it still real wintry in your part of Suomi. My mothers family is from Turku, and I have heard it is a really hard winter there still. Lots of ice problems in Turku even.

You are right winter stay still cold and my area middle of Finland about 0.7 meter snow. Not even one time so warm that snow will fall down from the roof. Not at all normal...

the new 2.0.4 firmware is out. No problems with the C modes for me although I do not use them. Still trying to figure out the best manual audio level setting for the MKE400 mic input.

Jeff has already updated the opening post of this thread with the download links for the recently revised firmware version, 2.0.4 (thanks Jeff!)

When I downloaded the new firmware 2.0.4 it immediately affected my computer. After a lot of delving it seemed to have affected a rundll.exe file and I've managed to change the rundll and also deleted the Canon 2.0.4 firmware file. Now my PC runs perfectly again.

It seems more likely that something was latched on to the 2.0.4 firmware file during download. Not something that should happen from an official Canon site, but at least I've sorted it out before I tried to go any further or cause problems with CF cards or the camera.

I'm not so keen on trying another download from Canon and will leave it a few days to make sure nobody else has had problems. By the way, I downloaded via the firmware update pages of Canon UK and not Canon USA.

Strangley, I didn't actually have any problems with the earlier 2.0.3 firmware and that seems to be functioning OK.

I also had a sudden rundll.exe error shortly after downloading the 2.0.4 firmware.

Pat

I have now re-downloaded a second time, this time from the Canon USA website and this time everything seems Ok...so I can breath a sigh of relief.

Pat, regarding the rundll problem, I would suggest that you do the same as me. The error will probably try to shut down any part of your system where it is located, for example if it is located in Documents it will try to close documents page, if in Pictures it will try to close the main pictures file page each time you open it. A couple of warning boxes will appear and one will probably be a rundll.exe warning and also probably an explorer shut down warning box. If this happens, first go to your downloads page and delete the 5D 2.0.4 firmware downloaded file, then go to your Recycle bin and empty it.
Now locate the problem rundll file and either delete it if it is not a working file, or if it is connected to an important sytem file then simply rename the rundll by adding 1 in front of it.

For example, if it is latched to your Nero and you are using Vista, simply do this fix:

1. Click "Start" then go to Computer, your main drive, program files, common files, Ahead, DSfilter.

2. Rename "NeroVideoProc.ax" to say "1NeroVideoProc.ax"

3. Rename "NeVideo.ax" to say "1NeVideo.ax"

4. Reboot

5. Problem fixed!
(Note, this fix will probably also work if you miss action 2 and only rename as in 3).

When you now try to open the main located Documents or Picture page containing the problem rundll Vista may try to open a warning box again, but this will quickly disappear (depending how fast your system is working) and all systems will then return to normal.

Now go back to the Canon US website and download the new firmware again and all should run smoothly.

Regarding updating the firmware in the camera, I prefer to do it using EOS Utility rather than via a card reader. Downloading the firmware direct to the 5D Mark II using the Camera Settings/Remote Shooting option in EOS Utility seems to work well for firmware updates without the need of a CF-card reader.

Thanks Tony,

How do you locate the problem rundll file(s)? I have gotten rid of the firmware update file, and I am not getting rundll error warnings on reboot. I am, however, having some functionality issues with Windows XP SP3. For example, when I right click on any file in explorer to open it up in a selected application, the menu box only shows an outline with no text within it.

Pat

Windows Host Process Rundll32 is probably the problem.

I've got a feeling that this will fix your problem if you follow the instructions given in my previous post for re-nameing "Nevideo". I would also suggest that you make sure all Windows updates are in place before checking if all is working OK and going ahead with another download of the firmware from Canon.

If that doesn't work, then try this:

1. Click on Start Button, and type msconfig in the search box type; hit the enter key on the keyboard. It should open the System Configuration Utility window.

2. Click on Services over the top and then at the bottom right corner, put a check in the "Hide all Microsoft services" checkbox.

3. Click on "Disable All" button.

4. Click on "Startup" tab, and then click on "Disable All" button again.

5. Press OK button and then "Restart" button on the following window. Let the computer restart.

6. Once you are back on the desktop, a window for System Configuration Utility will appear. Put a check in the box "Don't Show....." and then press OK button.

7. Re-check the issue. If the issue is resolved, open System Configuration Windows again and then enable all the services from Services tab and then check the issue after restarting the computer in the same way as mentioned above.

8. If the issue is still unresolved, enable half of the Startup items from Startup tab and then check issue.

9. If issue occurs again, it means there is a problem in the checked startup items. But if issue doesn't occur, then the issue could be with the rest of the Startup items. Now, uncheck the first half startup items (that were checked before), and then check rest of the half items. Check the issue again.

10. Now, if the issue occurs, make a note of all the names of the startup items and then follow the same procedure. Be careful, as by design the System Configuration will sort all the enable startup items to the top. So, it means all the entries would be mixed on next reboot. From now on you need to make a note of all the entries that you're enabling or disabling.

On another note, try to use Mozzila Firefox as your browser as this tends to make things run much faster and does not have so many problems as when starting Internet via the Explorer icon.

Thanks Tony!

Pat

Hi.
I have a brand new MkII - with installed 2.0.4 software and a 24-105 Canon optics. I just realise - the image stabilizer don`t works (by pressing the shutter button halfway) on any programs (M, P, Tv, Av) except the two automatic. But it works fine on all programs during Live View. Can someone test it to know - if its a bug in the new sofware or a problem only with my Camera? Thanks a lot.

My 70-200 f/2.8 IS works in all modes with 2.0.4.

Just checked with my 24-105 and it works perfectly on all programs.

Thanks guys. I did spoke to Canon and the camera will be changed to other one.

133X is now too slow
 

Well, I can report that my Kingston 32GB 133x cards I've been using since day one are no longer able to keep up. My guess is it's because of the uptick in data rate with the new firmware. To save $ I went with slower cards and never had any problems. I compared them head to head with UDMA and saw no difference in image quality at all - though obviously a big difference in speed.

But now after seeing the buffer fill up completely and an instant later have the camera stop recording, I'm retiring the 133x cards and moving up to 300X. Can't complain about this amazing firmware though.

Erik, one of my cards is a Kingston 16GB 133X and I've not noticed any difference before or after the firmware update in terms of CF performance. My 32GB cards are mainly 400X Transcend CF, but even though they are of course faster speeds I've not noticed any problems in 5D performance swapping and changing with the Kingston.

We had cameras fill the buffer and stop recording several times yesterday, first shoot with the new firmware, having never had a problem before on our seven 133x cards. We shot for hours and really gave the cards a workout, and they failed too often. These are no longer an acceptable speed for the 5D IMO.

That's strange; everything works fine with my 16 gigabyte, 133x Transcend cards...

I just filled two 16GB 133x Transcend cards with video yesterday & they worked fine too.