Search the Community
Showing results for tags 'os x'.
Found 3 results
Hi fellow audiophiles, I've been having trouble getting seamless gapless playback for my FLAC files, regardless of the player I use. With the sole exception of iTunes and Pure Music, every other software leaves detectable clicks between quick tracks transitions. The players I've sampled include Decibel, Audirvana +, and Fidelio, the latter (version 1.2.3) being my favorite. I've tweaked with all the settings with no changes. I'm also using OS X 10.6.8, with Centrance DACport. Googling the issue, it seems that few others experience the same thing. Could it be something inherently wrong with my hard drive? Any suggestion would be profoundly appreciated. Thanks!
Hello, Not sure if this has been discussed already (couldn't find anything from a quick search), but is there any particular Mac Mini model/year that lends itself best to adaptation for a music server? I'm thinking along the lines of PSU - as I know this has changed from the early years. What are the differences here? Planning on swapping out the hard drive for an SSD and upgrading the RAM, so I'm thinking anything Core 2 Duo or above should be sufficient if its only job is serving files (which will be on an external HD, probably connected via Firewire). Obviously an i5 would be ideal for future-proofing but cost is an issue. Any knowledge will be greatly received! Cheers
There are several shell-scripts floating around (including one I made many years ago) that turn off a vast number of lanchd processes for OS X, which often have the perhaps undesirable effect of completely hosing the system. As an alternative, I have been watching /var/log/system.log to find clues about what might be problematic, and what I want to do is selectively target a few "processes" by understanding what they do, and then turn them off individually, to see if there is any difference (audible, or at least in terms of spamming the log file). I'd like this thread to become a "hit list" of processes that are unambiguously useless. (In other words, I don't want to turn off wireless or bluetooth -- this should be up to the individual user, and is easy enough to do anyway). What I want to do is target a few problem children that are unlikely to have any utility, especially if they are broken, and understand what they do, in case I change my mind (or discover an unintended consequence).