Messages

[Option 2]

Hi Walter,

Thanks for your answer.

I think I have half-solved the problem.

Here is the problem in more details : on 5dMIII, when I format my CF cards in ExFat with Disk Utility in El Capitan, I have multiple options to choose (GUID Partition Map, Master Boot Record, Apple Partition Map).

After formatting with any of these options and re-inserting card in Camera I get the following error: "Card1 cannot be accessed Reinsert/change the card or format card with camera"

However, in Disk Utility you have two ways to format the card:
Option 1: you can select the Type of Disk and Erase it (which gives you the options above)
Option 2: there is a small dropdown that allows you to select the Disk with the name you gave it, and format it. This does not give you any of the above options.

Now, if I format my cards first on Windows, in exFat, then in-camera with the 5d,  and then format them using Option 2 on El Capitan, then and only then do the cards work fine on the 5d.

However, as soon as I format on El Capitan with Option 1, then even if I use 5d in-camera formatting and Option 2 straight after, the card remains unusable on the 5d.

One additional note that may help figure out the problem - after formatting using Option 1 and when trying to format on Windows, I can format the card successfully in exFat, but only for 200MB...



So to summarize the solution if you have the same problem as me - never use  Option 1 in El Capitan's Disk Utility, only Option 2.  If you do use Option 1, then format first in Windows, then in-camera, then Option 2 on El Capitan.

Hope this helps someone.

I have the exact same problem - no matter with which options I format in exFAT with El Capitan, it gives me that error and I can't record longer than 4 Gigs.

okay so updating to Fuse 2.8.2 does not change things. Still having same problem.

@dmilligan: I've checked the crash files, can't find anything with MLVFS' name on it.  Not sure if it's useful but I have files for "powerstat" and resolve that match the time of the crash.  Let me know if they might be useful.   I'll see if I can find the way to launch MLVFS from the command line, not sure how to do that right now.   I've got hundreds of files so it seems tough to try and figure out which one it is by mounting X folders after X folders, restarting computer etc...

also, I was not very clear on this before, but the folder to which i've mounted MLVFS disappears completely from the finder.   I've checked hidden files and it is not there - I need to reboot the computer itself to make it reappear.

I will try downgrading FUSE first, then if it still does not work,  upgrading to El Capitan.

Trying the same thing.
Nice user DeafEyeJedi has had the same problem in the past. 
He managed to solve it by either downgrading FUSE on Yosemite, or upgrading to El Capitan, upon which his issues were solved....
Will try both of these if upgrading Fuse to 2.8.2 doesn't change anything.   
@squig let me know if something works out on your end

Hi everyone,
Thank you for all the amazing work on Magic Lantern.
I have a problem on MLVFS.
Basically I have quite a big project - 6Tb of data on a Thunderbolt 2 hard drive, on which I use MLVFS on to create a mounted folder with all my files as DNGs.
I then access the data through DaVinci Resolve, find my files, import them, etc. and start editing/colouring. 
After a while, the MLVFS mounter folder just disappears from Finder.  Files in Davinci Resolve don't answer any more, and trying to recreate a mounted MLVFS folder does not work.  There's nothing else to do but unmount/remount hard drive.
This makes it impossible to do the edit with MLFVS as the issue happens regularly and quickly.
The only closely resembling issue i've found are these:
http://www.magiclantern.fm/forum/index.php?topic=13152.200
https://secure.magiclantern.fm/forum/index.php?topic=13152.475
But I couldn't find a definite answer.   
I am on OS X Yosemite 10.10.4, using Fuse 2.8.0
Thanks for your help and sorry if the answer exists out there and I didn't find it.

Hey, thank you very much for your answer. 

I was not aware of these ethical issues.  I will try MLVFS and/or other converters and let you know. 

I will also in the future refrain from buying any software not respectful of ML's GPL. 

Many, many thanks again.

Hey, thanks for your response.

I use RAWMagic to convert to compressed CinemaDNG.  Is is supposed to read abruptly ended MLV files correctly?  I can't remember that happening for some reason.

Otherwise which software can you recommend that does that for sure?  Is that how you personally overcome this abrupt ending limitation?

Hey, thanks for your answer, as well as the link to the calculator.  Cool tool.

I knew the trick for looking up the space/remaining time on cards, but again, tough when shooting.  If anyone knows a more pragmatic way....

Maybe something can be done in post to "fix" the last shot that was corrupted?  Since all images are recorded without compression this should be possible, no?

Or just a magical way of displaying the data remaining on card whilst recording... Or any other method really.

Cheers!

Hi there everyone,

Thank you to everyone responsible for bringing us ML, such an amazing hack. 

I am using 5d3 with ML nightly build 1.1.3 to record RAW footage continuous 1920x1080 with Sandisk 160mb/s cards and Lexar 1066x (mostly 128Gb cards).  Everything works great, except the following issue that I find quite hard to handle: 

I often end up filling up a full compact flash card by recording RAW in MLV format, and the recording stops with the error message "Card really exFat?".  The final shot is corrupted and unusable when back in post.


As you can imagine this can really be tough in some cases.... Can anyone advise on any ways to tackle this problem?

My workflow at the moment is as follows: in order to prevent corrupt frames as I need as much CPU available for the recording as possible, so I record in Hack No Prev mode, with all global draw/overlays disabled.   In general I leave on the "Status When Recording" to "Icon" which has been a success until now in that I did not get any corrupted frames.  I need to try the "Debug" mode to see if it gives me corrupted frames or not, as that mode gives the amount of space that the current recording is taking.   By being aware of how much is left on the card before starting recording, this could be a workaround, but definitely not ideal.

Also, one other thing that bugs me is that after finishing an MLV recording, the amount of space left on compact flash card does not update automatically.  I need to restart camera in order to make it update the correct number.

Would be great to have the community's input on this... I hope solutions are possible. 

Many thanks again.