Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - wadehome

Pages: [1]
1
Camera-specific discussion / Re: Canon 80D
« on: February 12, 2019, 07:43:36 AM »
Nice work sombree! If you happen to get ML fully running on your 80D, I'd be interested in working with you remotely to get it running on my 5Div if you were interested? :)

2
Camera-specific discussion / Re: Canon 5D Mark IV
« on: January 01, 2019, 03:28:24 AM »
If someone can put together the code for the intervalometer and the FPS override, I can test it out on my 5Div!

3
General Development Discussion / Re: What more can/should we do with ML?
« on: December 31, 2018, 12:42:53 AM »
OK, I'll bite. Do you happen to also run firmware 1.0.4 on the 5D4? Otherwise it may take a little longer.

For M50 I've already got a very good tester; feel free to check out the progress.

Yep! I'm running 1.0.4! I didn't even realise there were newer versions till I just looked them up! All good on the M50, but I am running firmware version 1.0.0 if that helps at all! Let me know!

4
General Development Discussion / Re: What more can/should we do with ML?
« on: December 30, 2018, 10:06:44 AM »
M50... waiting for testers to reply, 5D4... no volunteer yet willing to assume this risk.

I don't have time to scrub through 500 forums to get the answer right now, but I shoot 5Div and M50, have crazy good insurance, and NEED less crop, less rolling shutter, focus peaking, and every MagicLantern godsend. I can take the risk. Gimme this responsibility pls.

5
@Danne I just ran the normal install which puts them in usr/bin, but you need to make sure you disable system integrity first.

6
Or my method is a permanent fix. But it means low level Mac editing. It's not ideal but it saves launching Terminal every time.

7
It's temporary but it works:

1. Restart the computer, while booting hold down Command-R to boot into recovery mode.
2. Once booted, navigate to the "Utilities > Terminal" in the top menu bar.
3. Enter csrutil disable in the terminal window and hit the return key.
4. Restart the machine and System Integrity Protection will now be disabled.
5. Run install from cr2hdr package to install the files.
6. (optional) To reenable System Integrity Protection follow the steps above, except use the csrutil enable command for step 3.

It doesn't change the plugin, but it does allow us to use it as per normal again, and takes a matter of minutes to do.

8
I fixed it on 10.11.... so so so so so easy....

9
I do since i have dual booted my Mac, but it's still a pain as I'm only using the standalone program because I'm currently in Bali and haven't had a chance to download Lightroom to the Windows boot, so I was just checking if we had made any progress on the 10.11 issue. I have been able to redirect Lightroom with some trick aliases but it only worked until I quit Lightroom.

10
So, we haven't gotten anywhere then?

11
I really hope that some of you can solve the issue because I'm on 10.11 and I need to process a lot of files from an assignment. I'm really stuck now.  :(
I'll do my best to do a temporary work around but if I can't, you could upload the files to Dropbox and I could just do it on my Windows computer for you.

You could try install the binary pack from app cr2hdr-r since it places both exiftool and dcraw in usr/bin through a script.

That's the whole issue; I have tried that many times, it says that it has 'installed' but if you go to usr/bin the files aren't there due to 10.11 not allowing that folder to be modified. Even through Terminal (command line) to just copy them there, it doesn't allow that. To use the non-Lightroom processing app on Mac always fails to work as well.

12
It looks like El Capitan, a.k.a. 10.11, still allows installation in /usr/local/bin. Could you give that a try?
I'll see if I can make an alias that forces it. I mean, I can just boot to recovery mode and make 10.11 stop being a pain, but I mean, that's low level file structure changes and 99% of the users of this plugin won't want to do that, I'm sure, and it's pretty complex. So I will see if I can workaround it.

No. Inside plug-in scripts cr2hdr is called and it will look for both executables via OS X because cr2hdr can't do (yet?).
I'll see if I can edit cr2hdr to not look to OSX/not look to /usr/bin for the exiftool and dcraw. Probably impossible but I'll see what I can do.

13
Uh oh--can't say I saw this coming but mentioned this a couple months ago:

« Reply #741 on: July 19, 2015, 03:05:19 AM »
The issue is that if you download the plugin you'll find exiftool and dcraw in the plugin's bin/lib directory but OS-X looks into the system path for these programs. Obviously it is time to revisit this issue.

So it's Lightroom that looks to /usr/bin/ for the dcraw and exiftool? I can probably create a redirect script for it. I'm overseas at the moment but I'll do my best to see what I can come up with, even if it's a temporary thing for now, I'll share whatever I can make, if I can make something.

14
Hey guys, I love this plugin and it has always been super efficient and amazingly useful and I use Dual ISO all the time! Only issue is; OSX 10.11 El Capitan has this new 'rootless' feature which disqualifies any access to /usr/bin which is where dcraw and exiftool are stored and installed to. So since updating to 10.11, choosing to export to Dual ISO converter shows the 'Dependancies Error: This plugin (cr2hdr) need dcraw and exiftool. Please install it before run this plugin'. So it won't work, anyone have a workaround or something that will let me continue to use it?

Pages: [1]