Netradio not working on PC Client PVR

[lif]

Hello! I've changed my GB-PVR setup and moved from standalone-box-system to client-server system (so, I could use about three gbpvr clients).

Yesterday I tried to listen Netradio, but... no audio is playing on clients! :-( On server side Netradio is working, on PC client (file-sharing mode) it connects to web radio, (...buffering...), and thats it (no audio). If you look on server share, the "buffer" file has been created and grows, on server side "netstat -an" shows connection to web radio, but stream doesn't go from server to client gbpvr.

So, is this the bug of current release of GBPVR or my setup is missing something? :-S

[ACTCMS]

When running on your server, NetRadio creates a temp file in your Recordings dir. When running on your client, it tries to create it's temp file in the same relative path as specified in your server config. Confused?

Here is my setup...
Server Recordings Directory in config is "D:\PVR\Recordings" - so on my client (which does not have a local "D" disk, I created a dir on my server called "netradio\PVR\Recordings" and shared the "PVR\Recordings" bit. I then mapped this share on my client as "D:".

If you have a local "D" disk on your client, just create your recordings directory there. I would not suggest you try to share the real recording directory on your server.

Alex

[lif]

So, actually I'm confused a bit about which one - server or client will actually connecting to web feed? Is server going to connect and forwarding radio recording temp to client or client itself connects to web feed directly? What if two clients are connected to GBPVR server at once? Do they hear then both the same station or only one hears and if second one starts netradio it breaks first ones entertainment?

btw. what about using unc paths in config for both server and client as \\gbpvr\recordings, I guess that it should work?

[ACTCMS]

Each client connects to the feed independently and needs to create it's own buffer file, so each client can tune to a different station. But each client still looks at the path as defined in the server config and assumes that it is a local path - I would not use unc paths, since this would mean all clients would be trying to create their buffer files in the same physical folder.

If you have more than one client, create multiple folders on the server and point each client at a different one.

What do you have specified as your Recordings Directory in config on your server.

Alex

[lif]

If you have more than one client, create multiple folders on the server and point each client at a different one.

What do you have specified as your Recordings Directory in config on your server.

Alex

Thanks! That's the catch! I had on server config "E:\PVR\TV" and on clients' E: doesn't exist. So, I'll try later to change the path and see if it is working.

[ACTCMS]

Thanks! That's the catch! I had on server config "E:\PVR\TV" and on clients' E: doesn't exist. So, I'll try later to change the path and see if it is working.

I would suggest that you create a directory structure on your server like:

driveletter:\NetRadio\Client1\PVR\TV
driveletter:\NetRadio\Client2\PVR\TV
etc and share each PVR\TV folder for read/write
then stick an empty txt file in each of the TV folders called client1/client2/etc (this will tell you which share is which when mapping from the clients)
map each client to the correct share as E:

Alex

[tan]

It took me a few minutes to realize that since my server recording directory is "C:\Media\Shows", all I had to do was create a "C:\Media\Shows" on my client machines. I post this in the hope that:
1. I am not incorrect.
2. It may be useful on the off chance that someone reading thread is even slower than I am and is also recording to their "C:" drive somewhere ;-).