Jump to content

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



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

Categories

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 7 results

  1. Premise: the following explanation is only to exploit the little APFS Recovery (less than 600 MB) embedded inside the APFS File System, so avoiding an external USB Installer, you can't reinstall macOS from here but use just the Utilities (Terminal, DiskUtility) in case of emergency, however as known from a Recovery Terminal can do a lot of things, especially troubleshooting an unbootable macOS. To those who have installed Mojave on APFS file system with a GUID/GPT Scheme (I suppose it will work even on MBR scheme), I have managed to "fix" the "APFS Recovery Volume" to make it bootable from any computer (capable of HighSierra and Mojave) with USB input devices (trackpad, keyboard, USB mouse and so on) responsive, working wifi and everything else, just follow next steps, totally safe and harmless for any Mojave installation, after booting normally from your Mojave APFS Volume, launch Terminal and type:diskutil apfs list{locate your "APFS Recovery Volume" on diskXs3 [for an internal "APFS Container" is typically mounted on disk1s3]} On APFS scheme the "APFS Recovery Volume" is tipically on the 3rd (hidden) partition.diskutil mount diskXs3 open /Volumes/Recoverylanding on Finder, double click on the "random-numbers-letters" folder (it's the gpt UUID folder where Recovery stores itself), once inside rename these files:prelinkedkernel into prelinkedkernelbackup immutablekernel into immutablekernelbackup PlatformSupport.plist into PlatformSupportbackupDon't close this opened Finder window yet, once you renamed those 3 files, now you have to open a new Finder window, then from this new Finder window go into your Mojave path: /System/Library/PrelinkedKernels/ while inside this path copy the file prelinkedkernel into the previous Finder window exactly where you renamed those 3 files lastly rename this fresh copied file from prelinkedkernel to immutablekernelNow you have a working APFS Recovery Volume. Note for those who use Clover bootloader in the config.plist you have to don't "Hide" the APFS Preboot and Recovery hidden partition, otherwise you can't use the APFS Recovery.
  2. fru1tyJuice

    Volume Problem

    I have decent sound and nice volume after installing apple.alc with [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] and then rebooting the machine, but after the next reboot is my max volume very low I can barely hear something from Spotify with max volume and on YouTube nothing. I have already tryed it to reinstall the kext a few times but after the second reboot is my sound always gone ... Someone any ideas ? Soundchip alc887 Hardware: i5 7500, Msi B250m pro vdh, currently using the GPU from the i5, (no Mojave driver for my 1050ti).
  3. Hackintosher1

    Control Volume with Keyboard?

    Hi I made this topic to get help on controlling volume with the internal keyboard. The slider at top right on menu bar works and audio works with patched AppleHDA. But seems like somethings missing.. I think I need to assign the keys to volume up/volume down. The closest I can get is by enabling accessibility settings to enable on-screen control - still not able to adjust with keyboard. These controls appear: https://www.dropbox.com/s/bis3qa2ro1goyfd/Skjermbilde%202014-07-15%20kl.%2001.11.08.png?m= The kext Im using for keyboard is Rehabman's VoodooPS2Controller.kext
  4. Recently, I have been having weird issues installing Sierra to my newly created partition. It always ended up with a NASTY error message saying that it could not unmount the volume for repair (what repair, anyway?). At the first, I thought the volume was dirty, so I booted to my working El Capitan again and had formatted the partition again. It still failed. Then, I thought it was the fact that I was using the installer in El Capitan to install it to the new partition. So, I created an installation USB. The problem surprisingly appeared! The problem: The problem I believe was due to the createinstallmedia tool. If the USB is in fact created with that tool, the installer divides the installation process into two. First, it copies the installation files to the HDD partition (that part creates problem), and then it reboots from that partition to install the files and eventually create the Recovery partition. The problem is that it for some reasons tries to unmount the partition it has booted from, which is obviously not possible; hence, it fails. The root problem probably has much to do with the partitions structure. In my case, I used MiniTools Partition Manager to migrate my Windows installation from my HDD to the new SSD drive. It could have been due to that, although MSR partition is also known to cause problems in some situations. The partition structure was as follow: ESP = EFI Partition MSR = Microsoft Reserved (culprit, too?) Win10 = Windows drive Sierra = New partition created for Sierra Macintosh HD = El Capitan drive (already installed and working) RecoveryHD = El Capitan recovery drive. The solution: Use the "Restore BaseSystem.dmg" method to create the installation USB. Follow these steps: I assume that you have downloaded the installation from Mac App Store. If so, then right click on the file, click "Show Contents Packages". Click on "SharedSupport". You should see InstallESD.dmg. Double click on that file to mount it. Open the OS X Install ESD partition. Make sure that hidden files visible (there are many ways, use Google). Right click on BaseSystem.dmg and click open to mount it. Open Disk Utility. Plug in your USB drive. Click "Partition" and create too partitions. One with 200MB and the other one with whatever size you want. The 200MB partition format should be MS-DOS (FAT) and give it CLOVER as name. The second one's format should be OS X Extended (journaled) and give it USB as name. And click "Apply" to format the USB. Of course, everything on that drive will be destroyed. It's needless to say that you should backup its contents first. While still inside Disk Utility app, click the second partition (it's should be named USB). On the status bar, click on "Edit" and choose "Restore". You should see "Restore from: OS X Install ESD" click on "OS X Install ESD" and choose "OS X Base System" from the dropdown menu. Now click "Restore". You might need your password to complete this task. If so, type it in and click ok then wait. Upon finition, smartly unmount OS X Base System disk under "Disk Images" in Disk Utility. Open the USB drive (the name "USB" will become "OS X Base System", that's why you need to smartly unmount the other one using Disk Utility to avoid confusion.) Inside the USB drive, go to "System" then "Installation" remove the file named "Packages". That's actually an allias (or a shortcut if you want). Go to OS X Install ESD drive. Copy "Packages" folder from there and paste it in your USB/System/Installation. The same way, copy the other files from OS X Install ESD drive to the root of your USB (the root, not inside a folder on the USB drive). You need to typically copy the following files: AppleDiagnostics.chunklist, AppleDiagnostics.dmg, BaseSystem.chunklist, BaseSystem.dmg Install Clover to the first partition of your USB drive named CLOVER (unless named otherwise). Reboot from the USB drive and everything should go smooth and without this error. This should also work for Chameleon bootloader. You might of course not need to create two partitions in this case. You should probably not directly upgrade from El Capitan to avoid this problem. If it happens while you were trying to do an upgrade, you might need to do these steps inside a virtual machine or a working hackintosh.
  5. 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
  6. My friend (code) and I (idea and hints) developed a small tool for changing sound volume even for aggregate devices cause native sound volume controller can't change volume of aggregate devices (it was always pain in the ass with my laptop). Features: Changing sound volume of every device (even virtual aggregate device volume by changing volume of every device in aggregate device) Changing default output device Native appearance (looks like native volume controller) I think it can be very useful if you're using VoodooHDA with 4.0+ sound on the board (my use case), but you can find another use cases. For example if you want to play 2 or more output devices at the same time you should: Create aggregate device in Audio MIDI Setup Add all output devices you want to this new aggregate device Hide default sound controller icon if enabled (by dragging away or in audio preferences) Use our app to control sound volume Add our app to startup (if you need) You can find source code here: https://github.com/rlxone/MultiSoundChanger/tree/master Latest build here: https://github.com/rlxone/MultiSoundChanger/releases
  7. I installed lion 10.7.3 using an external flash drive on a tutorail i saw, in my hp Pavilion dv4-1235ee, everything is working except the wifi (intel 5100) which i didn't care about now since there isn't a prober kext for it. my problem is the volume, what ever i do i couldn't fix. when i open a song or video it works at the maximum volume. my multimedia keys are working. even the volumes in the menu bar not working. I installed the VoodooHDA0.2.7.3 from ###### Lion edition. in the attached photo, these are the kexts i installed if they help to identify my problem. if anyone knows some kexts that will do the trick, i appreciate the help.
×