Messages

Each of these were done with the 192MHz mode enabled using the same 128GB Sandisk Extreme Pro 170MB/s card:








And for reference, here is a benchmark done with the build I had been using prior to this newest one with that same card:



Solid improvement, amazing work! 

Thanks theBilalFakhouri but unfortunately it looks like the build Danne provided does not allow for additional modules to be included. Adding the bench.mo from the EOSM nightly build seems to not allow any of the modules to load correctly. I saw Walter Schultz's mention of another method but I don't see that option available either. I guess I will just wait for now 

Tested working in 170MB/s mode with the Sandisk Extreme Pro 128GB 170MB/s version on EOSM. Ran the 2.5k preset in an overexposed frame for a solid 30 seconds or so. I can run a benchmark if anybody would be so kind to let me know how to do that 

I have been using this build with sd_uhs and card spanning running without any issues for a few weeks also. None of this patching issue, works for me with custom presets too. It has been really solid so far but if that changes I will report back. Thanks a ton Danne 

You compiled with OP option? If so openmp is included.

Edit: also retry the official build. Maybe the compiler script iinstalls your faulty dependency.

Yes I used the OP option and that fixed it. Also replaced it with the official build again and that kept it working too. This is all on my MBP with 10.13.6, haven't tested 10.14 yet but I feel like that device I am on my own with the hardware being used. Thanks again everyone, I will keep this in mind if I run into a similar problem in the future 

Sounds your computer is ideal for debugging this. If you like install the toolchain, compile the app as debug version and start it with debugger. The debugger tells you the line of code of the crash. This would be intersting. I got no crash at all with debugger...

I will give that a go over the weekend and report back. I am also trying Danne's recommendation in the meantime.

Edit: Self compiling did fix this for me, not sure if compiling the app as debug version is useful still, if so I'd be happy to do that. Sorry for the hassle and thanks for the help!

No matter which debayer method I use, either with the force options in the export settings or using the receipt configuration, I always get this same crash. If there is a debugging tool that I could run on my end to find anything else out let me know. Thanks for taking the time to look into this.

I trust only screen recordings. But, could be a number of things.

I have a screen recording of it, I will upload that in a few hours.

Edit: https://we.tl/t-NOWe73RkyK

https://imgur.com/a/qtVTV7K

The report tells exactly the same.

Yes, I just thought it was worth mentioning since you said there were no issues with 10.13, this MBP is running 10.13.6 that produced the second crash log. As opposed to the original one where it was taken from a 10.14 device. I guess I will try to see if there is any updates available for my 10.13.6 device though and go from there.

Hello Masc and Danne, thank you both for getting back to me so fast, as well as for creating these amazing tools for all of us to use. I just tested this same MLV from my MBP running High Sierra and am getting what seems like a similar crash. Here is the crash report from it: https://pastebin.com/8STnArw5

Edit: Here are screen captures of my export settings that both crash similarly: https://imgur.com/a/HMpVIEH

Hello everyone! First off thanks so much everyone involved for making MLV App it has been such a great tool. I have been having some problems with it crashing at 98-99% point of exports when using the AVFoundation ProRes export options though. It seems to only happen when using the 5K 1x3 preset modes for the EOSM, I am using the most recent build released. I've tried all variations of settings in MLV App and it will even crash when no changes are made to the file and it is exported immediately. It seems as though maybe it has something to do with the Transformation being applied? I have the crash message here: https://pastebin.com/PL1PyEcU. This one was taken from a custom built hackintosh however I have a normal 2015 Macbook Pro and this gives the same behavior. If there's any other info I can throw in let me know, thanks!!!

Edit: Uploaded sample MLV: https://we.tl/t-rC7vKZaTbp

First just want to thank everyone (especially Danne!) for all of the hard work put into this amazing project. Does anyone have experience using the EOS-M with a Zhiyun Crane 2 by any chance? I recently picked one up to use with my 5D II, and it works perfect with that running the experimental 10-12 bit firmware.

However, trying it with my EOS-M running the most recent firmware release when I try to use it the same way it gives me a computer connection symbol on the screen. It seems like it has something to do with the fact that the M is mirrorless so doesn't have a non live view to switch out of like the DSLR 5D does, but I just figured it was worth checking in to see if anyone has any insight!

I do not have any video of this behavior to show currently, however I can get some over the weekend to show what I mean if it is something anyone is willing to look into, thanks!