During a playback of an album of 14 tracks of 24 bit/352.8kHz files (up-converted to DSD128 with SoX) (72.11 minutes total length) I experienced at approximately 65 minutes into the album (track 11, approximately 1:17 into the track) a complete drop-out or loss of sync of the signal data which resulted in full-code “hash”… Not a happy experience saying the least, because I was unexpectedly caught off guard, having never experienced this with Audirvana Studio in previous listening sessions… Or for that matter, in a long, long, long time, having experience with digital audio playback and sync issues that created digital hash in the symbiotic connection between my audio interfaces connected to my music production DAW…
It was not a spurious “glitch” as I was able to repeat the incident at exactly the same location in the track, so my initial reaction was that the track file had been corrupted or some other glitch in the playback… I closed and relaunched Audirvana Studio, powered my DAC (after shutting it off to prevent damage) and proceeded to the suspect track and initiated playback… and at exactly the same time-point into the track, the drop-out or loss of sync occurred again… At this stage, I deleted the track from the album folder (moved it to the TRASH) in my library HDD and replaced it with a fresh download of the suspect track from the site it was purchased… I relaunched Audirvana Studio, re-synchronized it with my library and initiated playback of the track… The hash event was produced again at exactly the same time location in the track.
At this point, I began to suspect something else was causing this recurring hash event at this time-location in the album playback… I began to wonder if it had something to do with the caching of the files after playback, and it’s relationship to the total available playback pre-load RAM, since this was a long album of 24/352.kHz files being up-converted to DSD128 in S0x and my playback buffer was set to approximately 6Mb…
I then thought that maybe, it was a cache buffer that had reached it’s maximum capacity and caused an interruption in the playback sync… I subsequently proceeded to exit from Audirvana Studio, shut down my DAC and shut down my MacBook Pro and start it from a cold boot, power ‘on’ my DAC and relaunched Audirvana Studio and initiated playback of the suspect track and it played completely through with no interruption as would be normally expected!
This brought me to a question about caching… “How much cache does Audirvana Studio retain after a track or several track have completed playback?” It seems that when only restarting Audirvana Studio after trashing the suspect track and emptying the trash, and subsequently replacing it with a fresh download, that the ‘old’ (perhaps corrupted) file was playing from the playback pre-load buffer RAM… even after resynchronizing the database. And only after shutting down the computer and starting from a cold-boot, this cache was cleared and I was able to play the refreshed track file.
So, was it a corrupted file or is it a caching/buffering issue? … I’ve increase my playback pre-load RAM size to around 9Mb… I’m a bit reticent to try a full album playback yet, until perhaps I can get some feedback on this experience, so to get a better grip on the potential causation(s)… I’m leaning in the direction of a corrupted file, however, the experience of the repeatedly recurring hash experience, after trashing and replacing the suspect file and “restarting” Audirvana Studio, versus, completely shutting-down my MacBook Pro and starting it from a cold-boot, to only then, have the freshly downloaded, suspect file, playback correctly, without interruption, is disconcerting, leaving me to question “why?”
Any feedback regarding this experience will be appreciated and welcomed.