[MacOS] How To Uninstall Waves Entirely
Leave a reply
Tag Archives: Problem
[Ableton] Normalize Recorded Audio Samples
Situation:
You recorded a nice sample from an external source (name it a bass synthesizer or anything else). After recording you see that the sample’s gain is too low.
Solution 1:
- copy that pattern from the pattern view to the arrangement view
- consolidate that sample in the arrangement view (
CTRL+ Jon Windows orCMD + Jon Apple) - increase the sample’s own gain to
0dB - the tiny downside: bass samples get often distorted. If you don’t like auto-distortion take Solution 2 ;-)
Solution 2:
- get yourself Audacity
- load that recorded sample from Ableton into Audacity
- go to
Effects -> Normalize - et voilà: gain set to 0dB and no distortion
Enjoy…
[iOS5] Workaround for iPad and iPhone w/ iOS5 running Animoog
Abstract
You absolutely like Moog’s latest iOS application named Animoog and wanna control it from your Mac but it doesn’t work and you are running iOS 5 or iOS 5.01. So at the moment it seems there is an issue in Animoog related to a modification in Apple’s CoreMidi stack. On iOS 4.3.x devices the CoreMidi connection worked.
Walkthru
I. On your iOS device do the following:
- I assume you already installed AniMoog, didn’t you?
- Please shutdown the AniMoog app, in case it is running. Don’t just put it into the multitasking background (or just reboot the iPad or the iPhone)
- then open the
AppStore - download
Pad MIDI - run Pad MIDI
- put Pad MIDI into the multitasking background
- start Animoog
II. On your Mac/HackMac/iMac/MacPro/whatever do the following:
[Win] Oracle VirtualBox: Workaround For Initialization Issue Pt. II
Find our previously released workaround for initialization issues here.
CPU VT-X/AMD-V Issue
After configuring a dual core virtual machine and trying to start you may encounter a message box indicating:
- Hyper-V launch failed; Either VMX not present or not enabled in BIOS.
- Hyper-V launch failed; at least one of the processors in the system does not appear to provide a virtualization platform supported by Hyper-V.
This issue may occur no matter which host operating system you’re using. The reason for this might be:
- you’re not using a CPU that supports hardware virtualization
- your BIOS does not support hardware virtualization properly
- hardware virtualization is disabled in your BIOS settings (check it!)
- there is a bug in your current BIOS version
- the trusted execution flag prevents booting properly
Known Workarounds
Try these settings in your BIOS:
- Enable Execute Disable bit (depending on the motherboard manufacturer this can be called: XD-Bit, EDB, NX-Bit, AMD EVP)
- Enable Virtualization bit (depending on the mobo manuf. this can be called: VT, IVT, AMD-V)
- Enable VT for Direct I/O Access (depending on the mobo manuf. this can be called: VT-d based I/O)
- Disable Trusted Execution Technology (depending on the mobo manuf. this can be called: Intel TXT, TET)
Of course, upgrading your BIOS to the latest version can also be of help, but flashing the BIOS is always a little risky.
Final Words
As we’re currently using VirtualBox only on the Windows XP platform we categorized this article under Win, anyway it is very likely that the same issue also occurs under Linux or Mac OS, as VirtualBox on all platforms derives from the same source code.
The above settings apply for example for installing MacOS SnowLeopard in a VM under Windows 7 on Gigabyte EP35-DS3 or Dell Optiplex 745/755.
[Win] Oracle VirtualBox: Workaround For Initialization Issue
“and first for something complete different”: Muzaq… coding or administrating system can’t do without gooood muzaq. Check our latest tunes here :-)
History
VirtualBox is an open source virtualization software. Originally it has been developed by a german company named Innotek, which has been acquired by SUN Microsystems in 2008. SUN Microsystems in turn has been acquired by ORACLE in 2010.
Innotek originally collaborated with Connectix on Virtual PC – a virtualization software targeting the Mac OS platform. Connectix has been bought by Microsoft in 2003. Innotek then decided to develop VirtualBox.
Status Quo
VirtualBox is used by many companies for virtualization and thus developing. Palm for example uses VirtualBox for WebOS development in an emulated environment. Thus allowing either Linux, Mac OS or Windows host systems for development.
CPU VT-X/AMD-V Issue
After configuring a dual core virtual machine and trying to start you may encounter a message box indicating:
VERR_VMX_MSR_LOCKED_OR_DISABLED
This issue may occur no matter which host operating system you’re using. The reason for this might be:
- you’re not using a CPU that supports hardware virtualization
- your BIOS does not support hardware virtualization properly
- hardware virtualization is disabled in your BIOS settings (check it!)
- there is a bug in your current BIOS version regarding
Known Workarounds
- Disable USB for the virtual machine
- Reduce the amount of CPU cores to 1
- upgrade your BIOS to the latest version (this might be dangerous)
- Disable VT-X/AMD-V
- Disable 3D acceleration
- Shutdown your host machine, unplug (!) from electricity for say 30 secs, reboot then
As we’re currently using VirtualBox only on the Windows XP platform we categorized this article under Win, anyway it is very likely that the same issue also occurs under Linux or Mac OS, as VirtualBox on all platforms derives from the same source code.
Any suggestions, hints or things need to be added? Don’t hesitate to tell us below…
[iPad] iPad Banned From University Networks In The U.S.
The Inquirer reports, that Apple’s latest gadget has been rejected from using on networks of George Washington University and Princeton University. The iPad seems to have massive issues with network stability.
Read more on The Inquirer…
[Pre] Palm Pre’s Slider Oreo Issues
Forum reports seem to be growing about this issue. A certain amount of first generation Palm Pre’s being sold all over the world seem to have slider issues. “It just wobbles too much, thus making it feel like a 500€ plastic toy.”, said a customer in a local O2 store.
Our testing device received from a local O2 store in November, 2009 here in Berlin suffers the same slider issue.
When talking to O2’s customer support, he by the way confirmed: “my Pre had the same issue. It is being repaired currently.”
Fortunately the repairing procedure with O2 is quite painless. If a customer realizes a defect within the first seven days of purchase, the local O2 store offers direct exchange of the device (this not only applies to Palm’s devices but to any cell phone O2 offers here in Germany). If defects are reported after seven days, they will be repaired within two weeks. Business customers are offered exchange devices at any time within 48hours.
If Palm Pre’s having the orea offect can be repaired at all, is still not really proven. According to a report on PreThinking, U.S. american devices are getting exchanged. Repair centers are not allowed to repair them.
When asking O2’s customer service, if the slider issue has been reported often, he answered: “No, this is a very rare issue, and we also asked Palm about this, and they also said, there is no slider issue.”
This might be the case for Germany, but in the meantime Palm in the U.S.A. seem to have implicitly confirmed the slider issues. In a PreCentral.net review article of the second generation Palm Pre (called Palm Pre Plus for the Verizon network), Dieter Bohn mentioned that “Palm says that they’ve fixed up the slider action (..)”.
In the meantime we’ve received our exchange device, and guess what? Although it still is a first generation Palm Pre, this slider has no orea effect.
It feels a lot more stable, making it eventually a serious tool for all the people who don’t want to follow the iPhone hype.
Picture is courtesy of PreThinking.com…
[MacOS] Is EFI-X illegally using 3rd Party Program Code?
About a year ago a company called ASEM released a device called EFI-X. This device has been claimed to be capable of booting several Microsoft Windows versions and Mac OS X Leopard.
Legal concerns
From the beginning there were question regarding the legal status of the device. But ASEM claimed the device is legal, although it circumvents Apple’s binary protection using Apple’s copyrighted secret operating system keys (OSK1 and OSK2).
Technical issues
Anyway EFI-X devices had some issues. Many forums reported about problems with Bonjour and sharing in general. In the meantime articles from the official EFI-X support forums have been suddenly disappeared. Customers reporting issues or solutions and workaround to severe bugs have been banned from EFI-X support forums – our own help article to recover almost lost data was removed aswell and one of our members has been officially banned from their forums (the reason was this article in october 2008).
Examining EFI-X in deep
Now some frustrated customers who are on the other hand technologically very familiar have examined the EFI-X device in deep. One of the main points AsereBln found: in contrast to what EFI-X is stating: “Our approach is entirely different, (..) all our code and development is our own only” – they seem to be using program code that has been developed by the OSX86 community though. They seem to be using “Disabler.kext“. Moreover another user (RezRov) found out the EFI-X Windows update software seems to be violating the LGPL as it incorporates a modified USB device library (libusb-win32).
Use of possibly unlicensed 3rd party program code, possibly illegal use of Apple security keys, and customer support below grade for a 170€ (250US$) commercial product that seems to be the summary about a year after product launch.
Lessons learnt
We suppose end users should be aware of this possible hassle. Only an original Apple Mac is really hassle free and 100% compatible to a Mac. But if you are technologically interested and have the time and motivation search the OSX86 communities for setups. The OSX86 forums are full of knowledge and willing to help. But remember a PC won’t ever be 100% compatible to a real Mac.
[Pre] Merry Me again: Update Reunites Palm Pre with iTunes
The “little Palm Apple battle” goes into its next round. A week ago Apple released iTunes 8.2.1. This update blocked Palm Pre users from synchronizing music and movies with iTunes. We reported about this update and the technical implications of the sync feature here.
Palm has now released a firmware update (webOS 1.1.0) for the Palm Pre. According to Palm’s blog entry this update contains the following features:
- Exchange ActiveSync (EAS) (including remote wipe, PIN/password requirements, inactivity timeout, improved certificate handling and more)
- support for emoticons in the messaging app
- person reminders (“Next time you get a message or phone call from that person, a message pops up showing you a reminder to ask them about their vacation in Maui” ct. Palmblog)
- and Palm webOS 1.1 re-enables Palm media sync with music, photos and videos with the current version of iTunes (8.2.1).
Got issues with the Update?
Our fellow Heise.de News (german only) recommend not to update your Palm Pre while it is connected to iTunes. In case you did that and your Palm Pre does not interact on USB anymore, do a hard reset with unplugging the battery.
[iPhone] Issues with iPhone DFU mode in MacOS 10.5.6
According to forum reports the iPhone DFU mode, which is required to install custom firmware with PwnageTool, does not get detected properly after updating Mac OS X to 10.5.6.
That means you cannot Jailbreak or Unlock the iPhone currently. The iPhone Dev Team has investigated in to this issue and comes to the conclusion that this is not a countermeasure by Apple, but a bug in the new kernel.
The Phone Dev Team names possible fixes for 10.5.6. As always: you do this at your own risk!
1. Replace the following plugin kexts from within IOUSBFamily.kext with the ones from 10.5.5 and then rebuild kextcache (if you don’t understand this, then you shouldn’t attempt it!)
/System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBHub.kext
/System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBCompositeDriver.kext
2. Use a USB hub in-between the DFU device and the Mac and insert/reinsert the iPhone’s USB cable.
3. Use a PwnageTool created .ipsw on Windows! Oh the irony!
If you did not update yet to 10.5.6 better don’t do it and wait for a fix or for 10.5.7 to be released.