fclose seems to be taking an inordinate amount of time on OS X when using an SD card

[David Milligan]

Could this be an OS X issue? This is very strange, only happens when using an SD card (but it's the same with my built in card reader and a USB one). If I comment out the fclose call in close_chunks() in index.c, I get normal performance (about 70% of one CPU core when playing back 24 fps), but with the fclose call there, I get close to 100% CPU in all 4 cores, and frames take more than a second to load (< 1 fps).

[David Milligan]

Well, I've found this issue only happens on a specific SD card, my 128 GB Transcend 600x, all the other SD cards work fine (<=32GB). I wonder if it's an issue with exFAT...

[Albert Shih]

That wouldn't surprise me: I've encountered frustrating delays on OS X trying to use my exFAT external drive (2 TB) that don't occur when using the HFS+ partition on another external drive (1 TB).

[Audionut]

I've read of numerous issues with speed of exFAT on OS X, but no solutions.

[David Milligan]

performance improvements for mlvfs_read: only read from the MLV file and get frame headers if needed, otherwise just copy from the buffer, this fixes issue #1 with exFAT on OSX, since we only need to fclose the file once per frame, yay!

→ <<cset 81ae960ec3aa>>