Ron, I would definetely just write to the card for now. I was just writing to the FMU when I had my "Data Error" problem.

I had tested both of my cams for about 15 hours each before I had my first (and only so far) Buffer Overflow. So I really don't think anyone should feel safe. This is clearly a design flaw and not some sort of random problem. And that's why I'm so upset with Sony...they are treating this like a normal warranty issue where we pay to ship it to them. They sold us professional cameras with a design flaws that put our livelyhoods at risk and they should be bending over backwards to make up for it...not telling me I have to pay roughly $60 to ship two cameras back to them to fix. That is nonsense! Canon never treated me that way.

Also, my Sony guy called today after talking to the product manager and told me to send the cams back for the repair....so I guess that's "official".

You were given VERY incorrect information. They will naturally suggest MemoryStick media as it's Sony's product, as well as Sandisk as they have some sort of agreement with them. Other than that, any reliable Class4+ card will work just fine with this camera. Most of the flash media is only made by a few companies and just resold, rebranded, etc.

Class6 is better suited from extensive testing, but that's about it as far as comparing Class4, Class6, and so forth.

The buffer issues are corrected ONLY via a firmware upgrade as it pertains to the sustainable transfer rate of recording when using both the SDHC/MemoryStick media AND the FMU128, in HD/HD mode.

I do not believe of any 'known' statement regarding having the cameras fixed, or a recall for that matter. Just call Sony, send the cameras in, write-off the shipping cost, and move on...that's all anyone can do at this point, but at least it's working.

Marshall could you send me an email with the coordinates of your USA Sony rep? I will give this information to a Canada Sony rep.

Unfortunately, before doing anything, i.e sending the camera, I have to ensure Sony Canada believe there is a problem.

As per the type of SDHC card to use for this camera, I did not see anywhere in the documentation where recommended cards have been explicitly listed. As anyone, seen such a recommendations?

Many thanks for helping on this issue!

Firmware number
 

Hi, Joe...I recently got my camera a few days ago. Do you know how to search in the menu to find the firmware version number for our cameras. It would be interesting to compare version numbers as these firmware issues get sorted out. So far, no backfocus issues, image quality is stunning on a 42" HD screen, and I ran my battery down to EIGHT minutes remaining without a premature shutdown at 30 minutes that some earlier users were experiencing.

Thanks, John

Hi John,

I searched the menus and online and can't figure out how to find the firmware ver.

Joe

1) The brand of your SDHC / MemoryStick makes no difference to reliability in my experience. I've had buffer overflows with top-speed SanDisk and Sony cards. In fact, my class 4 Kingston cards have been better than my other, faster, cards.

2) My info is that this repair for the buffer overflow issue might have a hardware element -- anyway, that was the implication of the emails Sony sent me.

Now, we need to start pressuring Apple to make Final Cut Pro's Log & Transfer work with footage from this cam... what a low-grade product that is right now!!! Crashes continually.

Adam

As per the timecode in FCP.

Today, I've used markers to signal where yo start and to finish the tranfer. Surprise, surprise, it looks like the timecode was than carried over.

I''ve got to do more test. I will try later on with inserting markers right at the beginning (time 0 + 1 sec) and at the end (time x -1 sec) of the shot.

If the solution to the problem is so easy, I can't understand why Apple nor Sony never mentioned it !

Looking forward to hearing a more detailed explanation of this possible timecode workaround you mention, Daniel.

FCP 6 and timecode
 

Daniel, I have FCP 6 and I experimented today with Log and Transfer and marking a clip with an in point several seconds in after the start of the clip and an out point several seconds before the clip ends. When I inserted the in and out, it did NOT reveal camera timecode in the L & T window....and when I transferred the clip over to Pro Res, it did NOT preserve original camera timecode.

Please let me know if you have FCP 7 and if your results are different or the same. It would be nice if FCP 7 did have the ability to preserve camera timecode even if you had to tag every clip with an in and out point in the L & T window.

Thanks, John

Hello John,

I have FC 7 and did not have the chance to do more test yet.

What I had done was I've inserted some video sequence right in the middle of the entire clip into FCP via log and transfer. The selection of was done using marker in and out.

What I had as result was a clip with the timecode not starting at 0 but from where the timecode of the "IN marker".

As I said I did it only once but would like to look at it when time permits.

Hope it helps!

clarification of timecode
 

Hi, Daniel...

Just to clarify that I am referring to the preservation of the original camera timecode. Right now the timecode of every clip when you bring it into FCP 6 or 7 will be reset to a start time of zero...as indicated in the Log and Transfer window. That of course is not the camera timecode. And when you say you insert an IN marker, yes, it shows an incremental advance of timecode (as I saw in FCP 6), but unless you prove me wrong with FCP 7, the timecode you are then seeing from the IN marker is only showing an incremental advance from that clip's zero start point...which again is not the original camera timecode.

The value of original camera timecode is high up on the scale for those of us trying to use this camera for documentary work. It may not be of such great importance for those doing other kinds of videography. But Sony marketed the timecode as a selling point...and I hope there will soon be a workaround or a fix for it...I found that I can go back into each imported FCP clip and reset the timecode to match the original camera source timecode...which is a pain...but that will be my workaround for the moment as I need it....John

John, how do you know what the original timecode is for each clip? Does a Sony utility tell you this? That sounds quite time consuming to "fix" each clip this way. Also, how do you "set" the timecode on a clip to the correct timecode once you know what it is?

reading camera timecode
 

Hi, Alan...

Inside the NX5U camera menu it gives you the ability to start the timecode at any number you want...for example, if you were doing a two card shoot...you could assign the first card timecode starting at the 01 hour and for the second card you could assign it timecode starting at 02. In order to do this you would have to have finished shooting card 1 and go in and change the timecode setting to hour 2 before continuing on with card 2.

Later, when you put the camera into PLAY mode you can see all the thumbnails of your clips on the LCD screen along with the first frame of the camera timecode with each clip. Also, when you playback the clip through the camera you can see the visible timecode running in the frame by toggling on the datacode display option.

Let's say you imported a clip into Final Cut Pro via Log & Transfer and now that clip's TC starts at zero. You park the playhead at the first frame of your clip in the timeline, select the clip, go to Modify>Timecode from the FCP dropdown menu, and you can insert any timecode number you wish. In this case as a "temporary workaround" I would give it the same camera source timecode number that was originally associated with it.

I don't want to regularly work this way, but for projects of short duration or where you are working off of fewer clips, it could be a viable workaround until FCP or a third party encoder like Cineform gets the TC recognized and carried over into Pro Res.

Hope this helps...John

That makes perfect sense, thanks John. Sounds like a real pain of a workflow though.