Tinko wrote:Most of the files won't start playing. I just get a spinning wheel. Is that a matter of transcoding?
Any ideas what I could check out to narrow down the cause?
That's not right. An Rpi2 can serve a large library without much issue, as long as you don't transcode. I have it serving iOS apps and atv4, m4v files only, and it works fine.
- Make sure library indexing is finished. It is slow on the Pi.
- With apple clients, use "web optimized" m4v files. Check your m4v files would play with iTunes or Quicktime. Check the file would play on Movie.app when shared by iTunes.
- Check your preferences (server, player) to make sure some tracks do not trigger transcoding. Subs burning is a common culprit, audio formats too (atv likes AAC or AC3, iOS app only AAC)
- On the iOS app *only*, try disabling "Direct Play". Keep "Direct Streaming" on.
- The web client is likely to trigger transcodes, but YMMV between Chrome, Safari, etc. Better to use the iOS app or the tvOS app.
- If nothing helps, see if your drive is not spinning down or even dismounting and takes so long to startup when you call a movie that the server or client goes into timeout. Make sure your power source is ok, too.
- Of course use ethernet to connect the Pi
- I *think* but haven't verified, that the fastest class-10 SD you can find, the better. I have had a system running on a Sandisk Extreme, replaced it with a Sandisk Ultra, and although both are class-10, I believe the Extreme worked better.
- Also, set transcoding to "fastest" in the server. You never really know when this thing starts thinking it wants to transcode...
Overall, you can probably make it work, if your library is "itunes-compatible" enough.