Premise File provider on a network share

Hello everyone,

Is anyone having any issues playing media from a network file-share? I created a file provider and pointed it to a network share. It finds all the media in the share, but when I attempt to play the media, Premise plays a few seconds of each item and moves to the next. Anyone else see this?


Thanks,

-John

John in VA said:

Hello everyone,

Is anyone having any issues playing media from a network file-share? I created a file provider and pointed it to a network share. It finds all the media in the share, but when I attempt to play the media, Premise plays a few seconds of each item and moves to the next. Anyone else see this?


Thanks,

-John

Click to expand...

I have had problems with music files like that before, the audio was being played for a second or so and then it would go to the next song. I have mutltiple soundcards in the system and it would work fine on one zone with one card and screw up on say the master bedroom zone. I deleted the soundcard in builder and rebooted and set it up again and it would work fine again. I used to play video off another server all the time with your UPnP AV plugin before I switched to SageTV and I never had an issue with the files being on another PC on the network.

Most of my shared media is on the Premise Host PC and I don't access files on a network share ... but I intend to so I may eventually encounter the problem you described.

I did try to point a FileProvider to a network-attached Ximeta NDAS drive and discovered a repeatable bug. The FileProvider's ConnectionStatus indicates "Searching..." and the CPU load goes to 100% (permanently). Damn ugly procedure to back out of the mess with a hobbled CPU ... I definitely do not recommend pointing FileProviders to NDAS drives!

As it turns out, I corrected my problem and can now use a network share. The problem was with my disk controller/disk. I'm using eSATA drives connected to a HighPoint RocketRAID controller. The controller was throwing errors, so I shutdown the machine, re-seated card/connectors, and restarted the machine. Everything works for now.


Interesting you mention Ximeta. That was the configuration I was trying to replace. I saw the same issue you did. The only thing I could do was to re-mount the Ximeta drives as READONLY. That cleared up the maxed-out CPU problem, but you lose automatic detection of changes. This was a bug introduced with the 2.1 version of PRKERNEL. Incidentally, the same thing happens with the TwonkyVision UPnP Media server. I suspect it has to do with the method both Premise and Twonky "subscribe" to changes to a directory. I reported the problem to both Ximeta and Twonky, but neither seemed interested to work together to correct the problem.