One of the benefits of using BitPerfect for playback is that it will control the bitdepth and -rate for you using the parameters you've set in other words, it will update Audio MIDI for you, transparently / in the background, so that depending on what you choose in the settings, you can always playback at the encoded depth / sample rate without having to go through all that rigamarole. If you wanted OS X to always be bitperfect, you'd have to note the bitdepth / -rate of each song before you play it, exit iTunes, update Audio MIDI for the desired settings, then restart iTunes and play the song So, as an example, if you have Audio MIDI set to 24 / 96 and are using iTunes alone to play your music, iTunes will output a ripped CD bitperfect at 16 / 44.1, but the OS will automatically resample it to 24 / 96 for output. So long as you don't turn on any of the "enhancements" on the iTunes "Playback" panel (Crossfade, Sound Enhancer and Sound Check should all be *off), iTunes outputs bitperfect streams to the OS which then resmaples (if necessary) to match what is set in Audio MIDI. ![]() Thank you for all the gifts for enjoying the music,Īudio MIDI controls the bitdepth (e.g., 16- vs. Sure this is a momentary state that will reveal a solution. Tim, I doubt I have helped in any constructive way. Probably I am behind in how to use Fidelia. What Fidelia is doing is confounding as I am confronted with a trial for earphones even though I have never sought this. The players are gloriously providing us with excellence. I am merely reporting what I experience with one bloody album.Ħ. And corrects itself with the addition of 'fixedindexing' added to Comments within iTunes library.ĥ. BitPerfect 1.01.0.99.2 only falters with the Bennett album. PM latest (1.85c), Decibel, Fidelia (is so buggy 8 am furious with them), Amarra Full and in playlist mode does NOT stumble/recover playing consecutive tracks of the new Bennett terrific album Duets II which I have played a trillion times in my desire to help Tim who I adore in the best traditions for his terrific player.Ĥ. Corrected the numbering of the total number of music tracks as Duets II 's 18th track is a data track which XLD does not convert.ģ. For some reason, absent 'fixedindexing' in the Comments column of iTunes, one album, ONE!, album Bennett's terrific album (electronically improved I imagine because his voice is mostly gone) Duets II stumbles/recovers with BP and it's latest build.Ģ. Removed 'fixedindexing' from "Comments" and proceeded to "add" Bennett's augmented latest Duets II to each player's software. I am also noticing that the players are converging towards a common (read shared) center of excellence, I.e. I am committed to loving BP for the most obvious reasons. Even after updating BP 1.01.0.99.2, which did not make a difference as far as that one problem with one album. ![]() Present state, one album has been problematic. Merely providing information that may or may not be useful. ![]() I then left the track number total of XXof17 and reintroduced 'fixedindexing' the second time, it cured the stumble/recover.įor the record, I played Bennett's Duets II in other players (without inserting 'fixedindexing' in comments) and did not experience any stumble/recover problems. This problem does not occur with other albums except for Duets II. Then removed 'fixedindexing' and the problem that disappeared with 'fixedindexing' added reappeared. I changed that to ".XX of 17" to see if that cured the stumble/recover but only after adding 'fixedindexing' to comments. Originally the redbook CD (contains 18 tracks with the 18th a data file) was converted and as with all data files XLD does not convert that file. The stumble/recover problem still exists, but only with the Duets II album.
0 Comments
Leave a Reply. |