Jump to content

Recommended Posts

Hello, i've recently got an X-T3 and ive recorded some short videos but when I try to move them onto my pc or external hard drive it says "this device is unreachable". It will also not play the videos despite apparently having the correct codecs installed. I'm relatively new to all of this so any help would be appriciated, thanks.

Link to post
Share on other sites

Can you give us a little more information to then be able to try to help you?

Are you using a Mac, Windows or Linux based pc?

It sounds like you have connected the pc to the camera with a USB-C or Thunderbolt cable, is that true?

What application / program are you using to try to view the videos?

Have you tried to use a card reader to transfer the video to you pc to then use a program to view it?

Link to post
Share on other sites

On 5/15/2020 at 12:52 AM, jerryy said:

Can you give us a little more information to then be able to try to help you?

Are you using a Mac, Windows or Linux based pc?

It sounds like you have connected the pc to the camera with a USB-C or Thunderbolt cable, is that true?

What application / program are you using to try to view the videos?

Have you tried to use a card reader to transfer the video to you pc to then use a program to view it?

I'm using Windows and at the moment i'm trying to view the clips using windows media player or VLC player, i've also tried to view the clips in Davinci resolve and it's still choppy or dosent play at all. I've not tried a card reader but I will thanks for the suggestion, to be honest I suspect it's mu video card that needs upgrading as its a little on the older side now. Thanks for the reply.

Link to post
Share on other sites

If you are recording the videos using the default 4K size, then you will need a decent video card. You can try dropping the size down to 1080p and see if that helps, but really this is only a suggestion to use to iron out any workflow bugs. The 4K size is the better to use overall because that is the way the TVs etc., etc. are going to stay. In the mean time, I hope the card reader will help some, because it puts less strain on the overall system.

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
  • 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...