More > JRiver Media Center 33 for Windows
MC media read speed problem over VPN
clarus7:
I am trying to share a file server from a remote location. Using a site-to-site VPN, I verified that the VPN tunnel throughput is consistently >100Mbps from the PC that's running MC. I have mapped the remote server as a network drive in Windows. Copying files from server can get ~100Mbps. However, when I try to play file from the server in MC, looking at the network Ethernet throughput in task manager, I'm only getting <4Mbps of throughput, resulting in constant buffering.
Is there any configuration that can be changed to improve this behavior? How can I improve MC read speed from the server to be close too the speed of copying files?
mattkhan:
Are you using the use local file if available option?
clarus7:
I have used local file server before and it works fine. However, My server host over 60TB of data so it's not practical to duplicate it at two locations.
I have looked into this further. Using foobar2k, I can see that there is an initial bandwidth peak when playback started, presumably to fill up playback buffer, then bandwidth will settle at media bitrate. playback was fine without buffering. Contrast to MC, the peak to fill the buffer never happen, and subsequent data rate is always at or below the media bitrate. So increasing the size of the playback buffer is not going to help. Knowing that the bandwidth of the VPN is not the limitation, I would consider this a problem with MC itself. One additional datapoint is the ping time to the server is <70ms. Understand that it could limit TCP thoughtput, but as it has shown that file copying (which is TCP traffic) can reach over 100Mbps, I don't see the round trip time of bandwidth to be the limitation here.
P.S. changing the subject to VPN problem is misleading. I don't see a problem with the VPN. It is MC inability to sustain a reasonable media read speed over VPN.
mattkhan:
I am not talking about duplicating it, I am referring to the option that tells MC to read the file directly instead of having the server serve it (potentially transcoding it along the way)
This then relies on the OS to deliver the file
Are you using this option? If not, try it to compare
clarus7:
The server is strictly a file server, not transcoding anything. The server has been mapped to a drive letter under windows explorer, so to MC it should be a local file, as Windows is handling the network portion. I believe this is what you are referring to.
Navigation
[0] Message Index
[#] Next page
Go to full version