|
When serving files, the size of the files make no difference to the devices ability to serve them. As long as they are small enough to store the files, (if they weren't you couldn't have saved them in the first place,) then you should be good to go.
When playing them back it's all about the "throughput" - the bit rate. The source device (NAS) needs to be able to supply the data at a high enough rate, the infrastructure between the source and sink device (ie the network) need to be able to sustain transmission at a high enough rate, and the sink device (player) need to be able to "cope" with the required file.
That masks all kind of issues. If (for example) your NAS is real time transcoding the files on the fly (converting them from one file format to another) that could cause problems, the network could not be fast enough or have so much "other" traffic on it that congestion is a problem (Wi-Fi and HomePlugs are more susceptible to this,) or the player may not have the grunt required.
In the first instance, it can be a process of elimination to figure out what is culpable so that you can determine what needs fixing. For example, if you can directly attach a device to your player (e.g. a USB stick or SD Card) and play from there and all is well, you know the player is up to the job; if you can play from an NFS or SMB share (ie not use Plex - so definitely no transcoding) you know the source/sink and network are not culpable; if you have Wi-Fi or powerline between source and sink and test using exclusively ethernet (preferably Gigabit, but 100mbps should be OK for media streaming) you know network infrastructure is fine; if you are serving multiple streams concurrently, test with everything else off and see what happens; what happens if you use a different playback device (PC for example); etc. With some IT issues, there's nothing for it but to slog through some methodical testing and analysis. |
|