With reference to this question mentioned here SGNewChannel error -9405 on Mac 10.9.1, I am facing the same problem with my code but what's weird for me is that if fails for MAC OSX Version 10.8.4 (On MacBook Air). I have another MacBook with version 10.8.5 and the code works good.
The only difference I notice is with the camera. On 10.8.5 I have the camera named as "Build-in iSight" while on 10.8.4, I have the camera name as "FaceTime HD Camera".
Has anyone encountered this problem with this camera and the OS Version ?
Please guide as to what are the other alternatives possible, or what are the potential solutions to this problem.
I googled much but could not found any solutions / alternatives to get around this problem.
So I request someone with the knowledge to guide me past the problem.
Thanks & Regards
LazyCoder7.
This has to do with the particular version of MAC OS 10.8.4. There is a bug which prevents FaceTime HD camera on MacBook Air to be used by certain application.
Details of the update can be found at
http://support.apple.com/kb/HT5815.
Updating the OS version to 10.8.5 will do the trick for me, but I wonder what would happen if I upgrade it to 10.9 ??
Thus, so far so good. Will update to the latest version and test it.
Thanks & Regards,
LazyCoder7.
Related
In just one MacBook Air machine running Mac OS X 10.8.2 I get the following error:
???.app/Contents/MacOS//libdbunwind.1.0.dylib: mach-o, but wrong architecture
On another two MacBookAirs it works nicely.
Checked with lipo of course the architecture is i386. All the dylibs are deployed by Delphi 10.1 Upd 2
I'm completely lost with this error. Any feedback will be highly appreciated. TIA.
Regards,
According to the Embarcadero documentation Delphi supports OS X 10.9 Mavericks and newer but not OS X 10.8.2 Mountain Lion.
So I'm afraid you or your clients would have to update their OS to newer version for your program to work on it.
does anyone notice any issues when using your mac (running OS X 10.10 yosemite DP 6) as an iBeacon? I tried several tools and I also developed it myself (using the CBPeripheralManager startAdvertising) but without any luck.
When running those apps (+ the the code I developed myself) on a mac running OS X 10.9 Mavericks, it works like a charm.
Is there anything specific required for OS X 10.10 yosemite or is this a bug?
Any help is appreciated!
EDIT: Radius Networks has confirmed this issue has shown up on subsequent pre-releases of Yosemite. This OS veesion blocks sending an iBeacon transmission with the internal interface, but allows it with external interfaces. So you can add an external Bluetooth dongle like the GBU521 and transmission works again.
It's gotta be a bug in the code or something specific to your machine. We have tested our MacBeacon OSX app on Yosemite and have not noticed any problems.
In fact you can indeed advertise your Mac running Yosemite as an iBeacon with an external compatible Bluetooth 4.0 (USB).
I wrote a simple iBeacon transmitter for Yosemite written in Swift, look here https://updatemycode.com/2014/11/29/yosemite-as-an-ibeacon-swift/.
This does seem to be a problem with Yosemite 10.10. This is acknowledged now on the radius network website: http://www.radiusnetworks.com/ibeacon/macbeacon/
I'm having to buy usb beacons that I can easily power on and off for testing because of this issue.
I didn't test this with 10.10, but I'm able to use 10.11.3 to advertise as a beacon (at least with the project from #mgigirey). Perhaps Apple opened this again?
I have difficulties installing the latest version of Adobe Flash Player (14.0.0.125) on my Mac OS X 10.9.3 (Mavericks). Every time I do so, it fails at 90% with the following error message.
Error: Unable to proceed with the installation
When I go to troubleshoot the problem, I find that I have version 13.0.0.214 of Flash Player installed on my system, and that the (alleged) latest version (for Mac OS X 10.6, 10.7 and 10.8) is 13.0.0.201 (see following URL).
http://helpx.adobe.com/flash-player/kb/installation-problems-flash-player-rvm.html
Further research has revealed that the latest version of Flash Player (for Mac OS X 10.6, 10.7, 10.8 and 10.9) is 14.0.0.125 (see following URL).
http://helpx.adobe.com/flash-player/kb/installation-problems-flash-player-mac.html#main-pars_heading_7
This is not the first time I have experienced problems upgrading Adobe Flash Player. I experienced a similar problem before upgrading to Mac OS X 10.9 except with different version numbers of the same software. That is, the version that was installed was greater than the version that was downloaded. Note that I did not experience this problem with prior versions of the OS (i.e. Mac OS X 10.6 and 10.7).
This time I went one step further and used a different default browser to locate, download and install (what I presumed was the latest version of) Flash Player. No difference....
My question is, why does my default browser point to an older version of the installation software, and how can I resolve this? Also, correct me if I am wrong but, the reason I have a 'later' version of the software (that is, version 13.0.0.214) is due to the OS upgrade? I do not recall ever upgrading Adobe Flash Player....
Not sure whether or not this is relevant, but I also have Adobe Creative Suite 5 installed on my system (which was also successfully upgraded during all OS upgrades).
UPDATE: Did a bit more searching on the Adobe forums and found a link to a previous version of Adobe Flash Player version 13.0.0.223. Although not the latest version, I have successfully installed it. That is, after I uninstalled the older version of Flash Player. The problem I experienced sounds almost identical to this installation problem.
I am still, however, experiencing the same problem when upgrading to version 14 of Flash Player (even through System Preferences). Seems to be a problem with the installer, and not my system configuration since, to resolve this problem, I uninstall Flash Player (like before) and successfully installed Flash Player version 14 OS X, which I found and downloaded from the same web site.
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?