Jump to content

Search the Community: Showing results for tags 'interface'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace


  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Website URL







Found 4 results

  1. After some research (took me a year ) I think I finally found a solution to get a more smoother interface. I don't know if this also fixes "Channel Timeout" errors, more testing is needed. Some history: After reading several topics/post about power-states that are used on GeForce-cards, I found out that the Fermi series only has 3 P-states instead of 4 (or more). P-states can control clockings on a GPU down or up when needed. (Down when more 'power' is needed/Up when being more idle) You can check your clocks by running the tool nvidia Inspector in Windows My EVGA GeForce 450 GTS (1GB) has the following clock-speeds: State 3 (lowest energy use) CPU Clock: 50Mhz CPU Memory: 324Mhz State 2 (mid. energy use) CPU Clock: 405Mhz CPU Memory: 324Mhz State 1 (high. energy use) CPU Clock: 783Mhz CPU Memory: 1.80Mhz After looking in Windows 7 what state the nVidia card runs on, I found out that this is usually state 3. In OS X however I could only get smooth animations if the GPU was running in state 2. My theory is that OS X simple needs more 'power' because it is running on OpenGL and their are way more animations (enabled) than on Windows. I also checked how my card was running on Linux (KDE). When using their interface I also find out my card was more in state 2 than in state 1. Editing AppleGraphicsPowerManagement.kext: To set the correct clock-speeds based on load, editing AGPM.kext was needed since they are undefined for my GPU. After searching through some post, I found out that some users were using all the 4 'load-fields', when my Fermi-card only has 3. Also some users simple tried to disable the last two, by setting really high values. This should prevent the CPU hitting state 3. Some users claim that state 3 is causing the freezes and the slow interface. My theory is that the GPU doesn't switch to state 2 when needed. It is either taking to much time for the GPU to reach state 2 or it would simply mean that the GPU doesn't like being on state 2 all the time for some reason. To make a long story short: I wanted to have a smooth interface, but also don't wanted the GPU to be fully loaded all the time (causing me a high energy bill). At the moment I'm using iMac12,2 as model. This because my i5-2400 seems to be inside this model. By setting this model, it also loaded the AGPM.kext. These are the values I have chose for my GPU (device id 0dc4): <key>Vendor10deDevice0dc4</key> <dict> <key>BoostPState</key> <array> <integer>0</integer> <integer>1</integer> <integer>2</integer> </array> <key>BoostTime</key> <array> <integer>2</integer> <integer>2</integer> <integer>2</integer> </array> <key>Heuristic</key> <dict> <key>ID</key> <integer>0</integer> <key>IdleInterval</key> <integer>200</integer> <key>SensorOption</key> <integer>1</integer> <key>TargetCount</key> <integer>1</integer> <key>Threshold_High</key> <array> <integer>70</integer> <integer>87</integer> <integer>100</integer> </array> <key>Threshold_Low</key> <array> <integer>0</integer> <integer>60</integer> <integer>92</integer> </array> </dict> <key>LogControl</key> <integer>0</integer> <key>control-id</key> <integer>17</integer> </dict> As you can see (or don't) I have simply removed the last row (aka row 3). My GPU is clocking as it should be and I can enjoy movies again. Also the sound from the GPU fan seems to be lower as it normally would, since this is also controlled by the GPU-clock. Setting details: I have set the IdleInterval from 250 to 100. It seems that setting this as 250 it takes to long for the GPU to switch to a higher or lower state. My theory is that the 250 value is set for the GFX0 (aka the nVidia/ATI-GPU) because it 'only' needs to render a game/high-use application. When the 100 IdleInterval of the Intel GPU, is needed because more/faster switching is needed for 'normal' use. The BoostPState and the BoostTime simple defined what state to be used when an application needs more 'power'. The SensorOption should need to be set to read-out the GPU-status. The TargetCount should be the state were the GPU should focus on. At least I think so, please let me know if you have more/better information. Testing: I would like to see some (test) results from Fermi-card users. That's why I posted this as new topic. But please know that doing this is at your own risk! As 'proof' please check the following pictures: Idle (4% idle or less): Browsing/doing stuff: (more than 4% load) Benchmarking: (more than 45% load) AppleGraphicsPowerManagement.kext.zip
  2. Hi, Is there any PCi-E audio interface that works out of the box and supports the OSX volume control so I can control it by apple keyboard. If not, any USB interface that does it? I have currently a Digidesign 002 rack which is has a firewire interface. It's works well but volume control by OSX is not supported. I know there is a workaround with SoundFlower but I don't want that because it delays the signal. Hope to here your suggestions! Thanks in advance. BiTRiP
  3. Hello! I recently installed the OS X 10.9.2 using the following components: Motherboard - Gigabyte H61M-DS2H Socket 1155 CPU: Intel i5 3330 4GB RAM DDR3 Everything is running perfectly! However, I can't boot into the OS X while my audio interface - Avid MBox Mini 3 - is connected to the USB port (I get stuck at the Missing Bluetooth Controller error). So, I need to unplug the interface every time I'm booting and plugging it back only when the OS X is loaded. The strange part (at least for my newbie comprehension) is that my USB Wi Fi Adapter doesn't break the OS X boot like the audio interface does. Does anybody know if there's a way to solve this issue? *Some info that may be relevant (or not): > I'm using VGA output, even though HDMI works; > I did not install the audio driver / kext for my motherboard; > I'm using USBBusFix=Yes to enable USB ports in Mavericks OS X; > I do not have external graphics card. I'm using the HD 2500 that comes integrated with my CPU. Thank you so much!
  4. wocketpatch

    M-Audio Delta with Logic Pro

    I've seen around the web that a number of people have had good luck getting the Delta 1010 to work with Logic on their hackintoshes. I'm putting one together at the moment, and since my bandmate owns Logic Pro, I'm eager to give it a shot. I messed with it one time and really liked it -- actually pretty similar to Cubase which is what I'm used to. Anyway, what I have is three daisy chained Delta cards -- two Delta 44s and a Delta 66. This gives me a total of 14 channels (12 that I use the inserts on my mixer for as preamps, and two that come in via a stereo preamp I have into the SPDIF on the 66).. This works great on Win, the Delta control panel shows all three devices and I can map them all in Cubase. For the most part this works like a Delta 1010, but I wonder if anybody has tried chaining the smaller Delta cards on a hackintosh and/or in Logic.. It'll be a couple weeks to source the parts, just wondering what to expect in the meantime and if I should even bother putting all those PCI cards in this machine. Thanks!