Archive for the ‘Troubleshooting’ Category

A new version of crossover is available, that fixes the Steam update problem (a temporary fix had been available here). You may backup stemApps folder before updating (as it may require creating a new bottle if Crossover application replacement does not work).

Driver San Francisco game experiences stutter (some pause) every few seconds on Mountain Lion (using Nvidia 320M chipset). Some tried to disable V-sync, however as the preference is reset, the game config file (in the now hidden user’s library folder, available through Go to folder menu) has to be edited and permissions modified.

In fact it runs fine (even with medium settings) under Snow Leopard (no pause), then it also didn’t come from the 256 MB shared memory (512 MB dedicated memory listed in requirements).

EnableTrim utilities do not work since OSX 10.8.2 update, as the searched binary sequence changed. We then have to use the following commands (errors/warnings are ok, just wait for the commands to complete).

As Google closes AdSense accounts without prior message and blocks all gains in case of incorrects clicks detected (also gains before these), and that claim request does not lead to account restore in most cases (and do not provide any hints, see here), some are reporting doubts on this service (see here), as it happened for accounts that were close to the payment treeshold (that is also higher than initially).
Moreover we can’t open a new account once a previous one has been closed.

We can however find many alternatives (see also here and there).

There is also to note that Google provides free Ad Words gifts, however the user then agrees to pay for additional amount in case of many clicks (above the provided amount).

A step by step video about replacing mac mini 2010’s hard disk is available. We can also find a comparative review of most recent SSD.

The long awaited MacOSX 10.6.7 update is finally available through Software Update (313 Mb). It notably enhances graphics stability and fixes flickering problems on recent macs when using some external displays.

However it does not fix the grays colors flickering problem on June, 2010 Mac mini (tested at least with a Samsung synchmaster 206BW display, using Apple’s HDMI to DVI). This could be tied with memory speed, as the Nvidia 320M chipset uses the main memory, however it is the same with the stock 2*1 Gb memory modules, or third-party 2*2 Gb and 2*4 Gb ones.

Some users suggest using the mini display port to DVI adapter.

As previously reported, Apple’s mini display port to VGA adapter does not experience flickering, however colors are over-satured, making it useless (with this same Samsung display). Colors seem better when using an Espon projector.  Some people also reported that using a non-Apple mini display port to VGA adapter worked better.

Apple announced a special event that will take place March, 2. We expect the presentation of iPad 2, and the release of new MacBook Pro fitted with Lightpeak transfer technology (renamed Thunderbolt by Apple, and whose connector is similar to mini display port).
Last June mac mini wasn’t then the real/full revolution, and Firewire 800 daisy-chaining problems on Snow Leopard with PLX chipsets (that acquired Oxford) are less likely to be fixed. This would explain why Apple didn’t have used USB3 nor Firewire 3200 in recent macs, and had been waiting to jump directly to the next technology, as they did 12 years ago with Firewire.

Here is a detailed procedure to update Yellow Tools Software Suite (Independence Pro, Independence Live, Independence FX) from version 2.5.4 to version 3.0, and to create a new (required) license file for the installed library (Basic or Pro) :

– In the My Account/Products section of the Yellow Tools’s site User Area (once connected), enter the serial number for the new 3.0 version (has been received by email after the free update request email sent to yellow tools support).
Then from My Account/Downloads section download Yellow Tools Software Suite 3.0 and Yellow Tools Independence Basic (or another, required as it contains the updated instrument files – layers – for 3.0 version).

– Launch the installer from Yellow Tools Software Suite 3.0 archive. It replaces the applications from Applications folder by the new 3.0 ones, as well as the YT E-License Manager. The installer also creates a Yellow Tools folder under Library/Appliction Support (system), that contains the applicative part (Independence subfolder), however not yet the licences subfolder stated in the documentation. The Library/Application Support/Yellow Tools/Independence/images files folder contains the common image files (Autoload Sinus, Origami, Special and vinyle noise).

– Create a new folder to store the new layers and images files from the library (can be named Independence Basic config), and create layers and image files subfolders.

Expand the downloaded Yellow Tools Independence, and copy its layers content into the newly created layers folder. Then copy the image files from the old Yellow Tools Root Folder (only the files corresponding to the library, not the common ones) in the new image files folder.

Launch Independence Pro 3.0, and in the Libraries tab from Preferences, click on Add Library button and select the newly created folder for the library (Independence Basic config for example). Click on save preferences and quit Independence.

– Relaunch Independence 3.0 and click on Activate Independence Pro button (if not activated, a message will be displayed in Mapping and Performance tabs, stating that the software does not run in Pro mode, with also a link to register it). The E-Licence Manager then opens and displays a generated product code for Independence Software Suite 3.0. Copy this code in the My Account/Products section of the site, after having clicked on Activate button for Independence Software Suite 3.0 line. Wait a few seconds (if the activation server is down, wait for some minutes and try again, or later). When the page displays a success message, get the response code (has been emailed) and paste it in the E-Licence Manager.

The Library/Application Support/Yellow Tools/licenses subfolder is then created and contains the license (.lic) for Independence Software Suite 3.0.

– Relaunch Independence 3.0 (the Pro features are then available). Load an instrument, which opens the E-License Manager to create a new license file for the ibrary : the displayed/generated product code does not match the one that had been provided during the initial install of the library (2.5.4 version), however we can replace it with the previous product code, and enter the corresponding response code (that had been emailed during the initial install). The license file for the library is then created in Library/Application Support/Yellow Tools/licenses (the previous license file for the library – from the old Yellow Tools Root folder – couldn’t be used). However the license count for the library is left unchanged on the site (one per computer).

Activating the library also creates a Yellow Tools folder in the connected user’s Documents folder (its path is setted in User Folders tab of Independence Preferences). It contains a layers folder (without any instruments) and no image files (these are searched again the path specified in Libraries tab of Preferences).

By discovering Wifi networks listed in Snow Leopard’s menubar, and after verifying on Apple’s site, it is confirmed that the mac mini includes an Airport card. Then the mac mini’s Ethernet based internet can be shared with an iPhone using Wifi : in Sharing preferences, select Internet Sharing, then choose connection from Ethernet, to computers through Airport, and check the box.

Echo FireStudio 2

Posted: August 31, 2010 in Audio, Troubleshooting
Tags: , , ,

Despite the latest MOTU Fastlane’s driver version started as Snow Leopard compatible, it doesn’t send Midi data over the out port (only manages incoming messages from Midi IN). This problem has been confirmed here and there, however MOTU didn’t release an update since early January.

So my initial choice of the Apogee Duet (419 euros, audio only) had to be changed to an audio and Midi interface instead, the Echo FireStudio 2 (184 euros). No latency problem has been encountered, a 128 samples buffer works nice, that is (as reported by Logic) 11,4 ms round trip (recording and playback through the mix), in fact 5-6ms latency when using virtual instruments.

The sound seems more powerful (better dynamic) and more present for bass than with Echo MIA PCI card (that could achieve 256 samples on the G4), despite the later perhaps sounding clearer and more opened/precise (less mudded, less masking) – to be confirmed however. There is to note that the mac mini’s integrated converter sounds very close, and perhaps more pleasant.
Finally the Firestudio doesn’t require any driver.

Under intensive audio work (plugins) the new mac processor load stays very low (a few percents where the MDD G4 was near the limit), and the tasks are well balanced on the cores by Logic. The fan doesn’t run faster and the computer doesn’t turn hot.

The integrated converter sounds warm and with an interesting color, despite probably not being as clear, and not allowing as low latency as a pro audio interface. There is still to compare it with an Apogee Duet to conclude, hoping not experiencing the hiss noise some users did (for most due to a ground loop through the audio wire).

Sometimes the Finder quits without reasons (when opening a disk image), and it also did many times while browsing/opening plist files in user/Library/Preferences (seemed due to two bad preference files whose creation/modification date is 2009 – no hints on their role).

Sometimes the system writes data (more than 600 Mb for a basic use) without obvious reason, and is then more disturbing than the very quiet fan. The resident memory is also huge (700 Mb – was only 150 Mb on the G4), in part due to the shared video memory (256 Mb), however it should be less.

Performance on games was great : Tomb Raider Anniversary demo, Lego Indiana Jones demo, and even Bioshock demo played very smooth in 1680×1050 (default medium graphics details for the later). The rendering was a huge step from the G4’s Radeon 9000 Pro (water textures and effects).

Crossover 9.1 allowed to play old Jedi Knight (DF2) demo perfectly in 1680×1050 (through activating the 3D accelerating in the game options), despite 2D option screens (and cutscenes) not rendering correctly (bad colors, and then close to unreadable text) – no problem for in-game (3D).

However the half back case was very hot (probably more than any macbook or imac) after playing 45 minutes of the most demanding demo. In fact the fan didn’t seem to run faster when playing, and those over-heating could lead to problems.

To transfer applications (Mobile Applications) from a mac to a new one, two ways are provided :

The old disk is available (or has been extracted from the old computer if the later is not working anymore) :
– Copy the files iTunes Library, iTunes Library Extras, iTunes Library Genius and iTunes Music Library to the new iTunes folder under user/Music/iTunes.
– Copy Mobiles Applications (that was at the root of iTunes folder under Leopard) to iTunes Media (new subfolder in iTunes folder under Snow Leopard).
– Launch iTunes while pressing Option key: locate then the new iTunes folder for the library.

A message “This computer isn’t allowed anymore to use applications installed on the ‘iPhone, do you want to authorize this computer…” click on Yes –> n computers on 5 registered message.

Applications are now listed on the Applications tab in iTunes (once the iPhone is selected). There isn’t anymore an Applications section in the left pane contrary to iTunes under Leopard.

The disk isn’t accessible (the data are only available on the iPhone ) :

– Through the Store menu list under iTunes, authorize the new computer.
– Right-click on the iPhone (left pane) and choose Transfert purchases.