one album not playing

[PieterM]

(19-07-2014 20:02)simoncn Wrote:  

(19-07-2014 18:06)PieterM Wrote:  It wasn't cured overnight... The source is my music library on my sinology has, which has both minim server installed as well as the standard sinology media server. Normally I use minim server. Control point is normally plug player, but sometimes I use Jriver (which is my go to program for management of the music files etc). Renderer is an Audio Research Reference DAC.

All of my library is WAV or FLAC.

When trying to play the album, the DAC crashes.

I tried playing the album using jriver as control point. The first time I tried the music did not even reach the DAC, and jriver crashed. I tried using the sinology media server. At first the same (crash of jriver). But thereafter it played fine. Switched back to plug player and minim, which sometimes plays, sometimes it doesn't. In the minim/plugplayer/DAC combination, if it fails, it is the DAC that crashes and reboots.

As the rest of my music plays perfectly in all the above setups, it probably must be something with the file. I will again try stripping all metadata.

The one thing that can be trusted to play the album without fault is playing the wav files directly on my desktop, using the built in Mac OS preview.

Thanks once again for your help.

Are the NAS and renderer connected to your router or switch by Ethernet cables, or are there any wireless or HomePlug connections involved? An 88/24 WAV file needs a lot of network bandwidth. It's possible that a streaming connectiivity issue could cause the renderer to crash intermittently.

Only the control point is on my wireless network, the NAS and renderer are on a cat6 network, with a gigabit switch between the ethernet cable from my nas and the ethernet cable to the renderer, so that traffic goes directly from NAS to renderer.

Well, the album is playing now, so let's see if it stays that way.
Thanks for the help, even though by now it is clear that it's not the minim server that's causing the trouble, now that the same problem occurs on the other (synology) server that I am running.