Jump to content

Recommended Posts

Hi,

I wonder if anyone can help. I'm shooting video on an X-T3 and running into a file size problem. The file seems to corrupt when it hits the size of 4.29gb

For example: after transfering to my Mac, the video duration will be listed as 10 mins, but it will only play up to around the 5 minute point and then freeze. Looking at the transfered file size it will be listed as 4.29gb. So it appears to hit a wall at this size.

But if I watch the video on the camera it will play the full 10 minute video. So it's not corrupted in camera. Just in the process of transferring out.

I'm on a Mac, with OS Extended (Journaled) so no file size limit there? I've tried transfering, using Image Capture, on two different Macs - 10.14.6 and 10.12.5

I've updated the camera to the latest firmware 3.21

My SD disk is 64GB Sandisk Extreme Pro 170MB/s  - so this should work?

So I'm stumped as to why it wont transfer out of my camera to the Mac?

Many thanks!

Link to post
Share on other sites

This shouldn't happen - what do you see if you look at the files on the card without transferring them?

How large are they?

Try reformatting the card in the camera and create another video (over 4GB) - then look at the file on the card without transferring it - is there a single file and how large is it?

Link to post
Share on other sites

Thanks for everyone's help.

The video clip plays in camera, so it's not corrupted at source. It's just in the process of transfer to my mac and always hits a 4.29gb wall. I'm doing a direct transfer from camera, and I think this is the problem.

I don't know how to check the file size of the video clip in camera, but I'm postive it's over 4.29 gb.

It's about 10 mintes long, and only plays for 5 mins before freezing - after transferring. So my guess is its about 8gb in size, and for whatever reason the Xt3 transfer process limits it to 4.29gb, even though the firmware was updated to record clips longer than this.

Based on the other thread, listed above with the same problem, I've ordered a card reader so hopefully that will solve the problem!

I'll report back later with an update.

 

 

 

Link to post
Share on other sites

There are a couple of ways that this could be caused by, a software regression ( older code got accidentally merged into new update code) or a hardware issue where some older incompatible parts got used instead of the new ones.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Similar Content

  • Posts

    • A fungus in the forest.

      Welcome, dear visitor! As registered member you'd see an image here…

      Simply register for free here – We are always happy to welcome new members!

      (p.s. Open Topic.)  
    • The backslashes you are referring are just symbols denoting path.  Once you import into these LUTS into Davinci Resolve those backslashes are removed by default and you only see is the true file name which has no backslashes.  Convince yourself of this by opening the LUT folder from the Davinci Resolve Project Settings.  Do you see any backslashes in those LUT names? Of course not.  The only name you see is the one that has the underscores and the periods. These LUTS work as designed without having to change any path names.  However, they need to be set up properly through CSTs and by what is supported in Davinci Resolve.  Hence, the FLog2C film simulation LUTS cannot be used because Davinci Resolve does not support Fuji Gamut color space and the FLog2C gamut. Alternatively, Davinci Resolve does support Flog2 film simulation LUTS because the color space for FLog2 is Rec 2020 and there is an FLog2 gamut. If all you are doing is changing the path names then you are not getting the correct results.
    • I found the reddit topic i refere to :  https://www.reddit.com/r/davinciresolve/comments/1pc3f1e/cant_apply_new_fujifilm_gfx_55_lut/ "Update for y'all, It's just like what @ExpBalSat said, it's because of the backslashes in the names break them. I changed the file name and it works now. "   For me it was the solution. Realy annoying if it doesn’t work for you 😕  
    • Here is the solution to using the Eterna 55 file simulation LUTs in Davinci Resolve.   In general, do not use the FLog2C to film simulation LUTs as they are not supported by Davinci Resolve for two reasons: 1) Davinci Resolve does not support Fuji Gamut Color Space and 2) Davinci Resolve does not support FLog2C gamma.  Instead, use Flog2 which is supported by Davinci Resolve.  Here is an example.  Let's say that you want to use Classic Chrome simulation.  Do the following: Complete your color grade and use a CST to get to Rec 709. Add a node.  Use a CST to convert from Rec 709 to FLog2.  Output Color space is Rec 2020 and Outout Gamut is FLog2. Add a node.  Apply the FLog2 to Classic Chrome LUT Create a combination node from node in steps 2 and 3. Apply a Key to the combination node and adjust the Key Output Gain to get the amount of the combination node that you want applied. So that you do not have to do this over and over again, generate a LUT for the combination node.  Remember to turn off all other nodes before generating the LUT. Hope this helps others. Don  
    • Thanks for the insights. I think it's really hard to make a decision without having the two side by side! 
×
×
  • Create New...