I'm writing a camera control program in Xcode 7.2 on OS X 10.11.2 and every once and a while my program will crash at EdsInitializeSDK(). Most of the solutions online suggest downloading other EDSDK.framework file, but this hasn't worked for me. Also, most of the solutions were written almost 3 years ago.
The thing that doesn't make sense to me is that the program runs most of the time and only occasionally crashes. Has anyone found a work around to prevent the bad access?
This seems to be related to an incompatibility between OSX 10.11+ El Capitan and the "older" EDSDKs, for us when using it in combination with swift. It seems not to be a problem in OSX 10.10 Yosemite. Canon EOS Utility, and other pure objective-c / C++ are mostly unaffected by this. I can confirm that EDSDK 3.4, released Apr 8 2016, includes fixes in this area.
Related
All I've done is unpack the zip, and when I try to open Android Studio, it crashes immediately. I see the icon in the dock for two seconds tops, before it crashes.
I also tried using the latest Canary build and have the same results.
I checked and apparently JDK comes bundled with it, so I don't need that installed in advance.
Am definitely using the M1 / ARM build for macOS running macOS Monterey Beta.
The traceback error is incredibly long and I am unable to pin where the issue lies, and I'm not sure that I should really post the entire thing. Where I am confused is that this is a relatively new Macbook Air on the M1 chip with hardly anything installed on it, so I don't understand what the conflict is or where to begin here...
Fixed by upgrading to the latest beta.
I'm porting some code to OSX and am in need of some copies of older OSX versions. Does the Mac Developer program allow downloading of previous OSX versions? A few forums mention it, but I've found conflicting/old info on this. It doesn't appear to be here:
https://developer.apple.com/downloads/index.action
I'm also aware of this post Does the Mac Developer Program have old versions of Mac OS X?, but this is now 3 years old. I'm aware some versions can be purchased on Amazon--would rather not go that route though unless necessary. What is the common way to test OSX applications for backwards compatibility?
Thanks!
I'm trying to update a simple sequencer I wrote a few years ago in XCode 3. I hit a brick wall at the very outset because AudioComponentCount and AudioComponentFindNext do not find my software instruments.
They just find two: Apple's DLS music device and their sampler.
I have several others which I can see in the library Components file. Auval sees them too, and passes them OK. They also work fine with my old sequencer, where they are found OK by the same functions. And I have checked that the components are up to date.
I do have the AudioUnits framework linked in (and the program compiles OK, it just doesn't do the right thing). Trying CountComponents with the CoreServices famework gives the same problem.
All the Apple documentation and sample code I have found indicates that my code should work.
Can someone suggest why these functions should be blind to perfectly good synths?
(I am compiling using XCode 4.3.3 on a Mac Quad-core Intel Xeon running Mac OS X 10.7.5. Could it be incompatibility between the up-to-date XCode and the Lion OS??)
I recently bought a new computer that came with Mountain Lion (OS 10.8). I'd like to start working with mex files on this machine, but I'm having a hard time getting 'mex -setup' to find any compilers.
Specs:
Mountain Lion 10.8
Matlab 2012a
XCode 4.4
I noticed that matlab has released a patch for XCode 4.2, and 4.3. I also realize that XCode 4.4 (and Mountain lion, for that matter) is not officially supported by Matlab. As far as I can tell, there is not a way to install 4.3 on Mountain Lion. So I know it is a long shot to ask the community, but has anyone found a way to get XCode 4.4 to work with Matlab's mex functionality?
Thanks, David
I have the same specs as you mentioned and I reproduced your situation. However, I found a working solution from the Mathworks. It was designed for XCode 4.2 and 4.3, yet it works for XCode 4.4. The fix is simple and involves only running a patch from the Matlab command line.
All information can be found this bug report in the MathWorks support forum.
I had changed 10.7 to 10.8 in each *opt.sh offical patch file from MathWorks, and it works just fine with Mac OS X 10.8, Xcode 4.5, matlab 2012a.
This may not be the answer you want, but you could always use xcode to install a supported version of gcc, and then have Matlab use that...
(Blog post on compiling gcc for Mac)
I've recently discovered that when upgrading from 10.7.3 to 10.7.4 that OpenGL Profiler no longer appears to be able to hook into a program. It can launch an app fine, but no break points, traces, resources etc work.
I found this question: https://discussions.apple.com/thread/3958500?start=0&tstart=0 but can't seem to figure out the soltuion the poster suggests, can someone shed some light on how to do this in xcode?