Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[josdewaard]

I have noticed that JRiver MC 20 does not work well with the Lacie Fuel 1TB which is only used as a wireless music storage device. The number and duration of hiccups makes the combination useless. The higher the bitrate (FLAC files with bitrates of 450 to 5000), the worse the problem gets. A hiccup of 5-10 minutes is not uncommon.
MC19 gave the same problems but less severe and less often.
I've tried Mediamonkey which suffers from the same problem. Foobar however runs perfectly well, which makes me wonder whether this is related to the difference in buffer sizes that can be chosen.
I'd rather return to using JRiver because of the great GUI, and hope someone has a great idea how to overcome the hiccups issues.

[JimH]

You started a poll, which I've removed.  Use "New Topic" in the upper right corner of the index screen next time.

Windows or Mac?

Are you using DLNA or UPnP?  If so, try just playing directly from the disk instead.  You can probably use it as a drive, not as a DLNA server.  That may be what you're doing with foobar.  If it works with foobar, it will work with MC.

Antivirus programs have been causing a lot of problems lately and that's also a possibility. 

[josdewaard]

Morning Jim,

Thanks for the quick reply and the corrections. I'm running Windows 10.
A simple switch from the Laciefuel library (DLNA) to the "Main Library" did the job.
Streisand (Guilty) with a bitrate of 5500 showed no hiccups at all.

Muchas gracias,
Jos de Waard

[AndrewFG]

Jim just out of interest, when MC is serving a track from a third party UPnP library (DMS) to a third party UPnP renderer (DMR), how does it actually do it? I never checked.

I am guessing that MC pushes (SetAVTransportURI) to the renderer a track URL on its server. And when the third party DMR starts to download from that URL, MC itself starts to download the track from the third party DMS, and re-serves it onwards to the third party DMR. i.e. it back to backs a download and an upload, which would certainly limit the performance, and face potential buffering issues.

Whereas, it would actually be possible for MC to push to the DMR the original URL of the track on the DMS. Then it could just step back and let the DMR download directly from the DMS without having to do anything more itself. Just an idea..

[JimH]

My primitive understanding is that the controller (MC in this case) sends a list of tracks to play to the renderer, and then steps aside.  After that, the renderer is just requesting tracks from the server.  I don't think MC has any involvement.

But Bob can provide better details.