Print

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

[ssands]

I set up a ReadyNas on my home network and moved my media to it. Everything seems to have gone well. However, when I use MC to look at files, I see a near duplicate for each and every audio file (this issue doesn't apply to video files, only audio). I say "near duplicate" because there are two differences that I have noted: the bit rate is higher on one, and there is a http url for one, while the other has a network mapping. I can't figure out why this is happening.
When I look at the ReadyNas with Windows Explorer, I only see the one file I placed on the ReadyNAS.
The ReadyNas is set up as a DLNA server and is also set up to support the HTTP protocol. I turned off the HTTP protocol support but the duplicate audio entries remained.
I'm running MC 18.0.106 on Win 7 - 64.
Does anyone know what's going on with these duplicate files?

[doulos]

seems like the ReadyNAS is configured as a DLNA server and also as a Windows share, and MC is looking at both. You can either disable one protocol on the ReadyNAS, or configure MC to not look at one

[ssands]

seems like the ReadyNAS is configured as a DLNA server and also as a Windows share, and MC is looking at both. You can either disable one protocol on the ReadyNAS, or configure MC to not look at one

I think you are right. I'm really new to this. Can you point me to where I can instruct MC to not look at one of the protocols?
Also, why would there be different bitrates, but the same file size, for each song? Am I going to get better sonic quality with one over the other?

Thanks for your reply!

[doulos]

I cant tell you where to look in MC, I dont have it in front of me.

With regard to the bitrates - on a Windows share,  MC figures that out by directly looking at the file. Over DLNA, its the server software on the readynas that does that, and passes the info on to whoever receives it. I dont really understand why they both come to different conclusions, though..