Recording Stream Existed Early
I'm not able to play TV while they are still recording, but I can play them when recording is done.

How could I fix that?

I use ServerWMC, build: 1244
By providing the serverwmc log after this happens (trying to play a live stream while a recording is going on). You can find the log on the debug tab of serverwmc, post it on and put a link to it here.
Windows Media Center PVR addon (pvr.wmc) and server backend (ServerWMC)
Here is the log:

I guess, the following is the reason, still not sure how to fix:
2017/04/13 10:23:58.827 AddMuxOutput> error: System.UnauthorizedAccessException: Access to the path 'T:\Recorded TV\TempSWMC\RecordingTV_Kodi^HPQUADSEB_2017_04_13_10_23_58.ts' is denied.
Working now. The folder was newly created by ServerWmc or WMC but with a read-only flag, I removed the flag and that started to work. I think ServerWMC should do assertion at startup that it's writable (it give warning about recording folder not existing), and if able should remove the read-only flag.
I think that check it already there, but I'll look again. Glad you got it working.
Windows Media Center PVR addon (pvr.wmc) and server backend (ServerWMC)
The problem came back and I didn't really do anything. I try again to workaround by removing read-only flag but didn't work.

The log file has a different error:

2017/05/25 16:52:38.971 Local WMC 'RecTV' folder: 'T:\Recorded TV', ShareStatus: OK
2017/05/25 16:52:38.972 Format: NTFS
2017/05/25 16:52:38.972 Stored Network 'Recorded tv' path:
2017/05/25 16:52:38.972 > Samba: smb://NoaTardif:********@LIVINGROOM/Recorded TV
2017/05/25 16:52:39.025 > UNC: \\LIVINGROOM\Recorded TV, ShareStatus: OK
2017/05/25 16:52:39.029 HandleFolders -------------(DONE)----------------
2017/05/25 16:52:39.711 SocketServer> starting up SocketServer
2017/05/25 16:52:39.711 SocketServer> permission to access sockets granted
2017/05/25 16:52:39.716 SocketServer> exception: System.Net.Sockets.SocketException (0x80004005): An attempt was made to access a socket in a way forbidden by its access permissions
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Bind(EndPoint localEP)
at ServerWMC.Worker.SocketServer.Start(Int32 port)
2017/05/25 16:52:39.718 InitializeWorker> SocketError found, give user chance to change
2017/05/25 16:52:45.692 InitializeWorker> successfully started: True
2017/05/25 16:53:01.660 Session Ending: Shutdown - closing...
I think this is a totally different problem. Have you changed your anti-virus/security software?
Windows Media Center PVR addon (pvr.wmc) and server backend (ServerWMC)
I'm running Windows 8.1 with firewall disabled and defender enabled. Well, maybe the change is that I had problem to get ServerWMC started when the computer start, it's now always starting... but maybe it start as a service or from a restricted user.

It ended-up starting when it's configured in Task Manager -> Startup Tab to start.

Everything else work beside live streaming, this is so special feature...keep breaking, but it's also why I use Kodi, Plex cannot do that.

<?xml version="1.0" encoding="utf-8"?>
<Settings xmlns:xsd="" xmlns:xsi="">
<sepG>------------------------- General --------------------------------------</sepG>
<LastLocalRecFolder>T:\Recorded TV</LastLocalRecFolder>
<NetworkRecFolder>smb://NoaTardif:********@LIVINGROOM/Recorded TV</NetworkRecFolder>
<MACAddressOverride />
<ForceLocalServerIPAddress />
After trying many things I found a fix...

I think the issues is that "running as a service" is not really running kodi when the computer start (strange/rare behavior). Instead it run when 'the' user that had enabled that feature log in, and in my case, that user was not an admin.

I made the user an admin, and the auto startup at login didn't start the app when setup in the "C:\Users\USERNAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup" or using the flag in ServerWMC config.

But when I run the script using the Task Scheduler, with high privilege, everything work. Also, the task schedule has way more options, maybe even watchdog functionality (to restart the process if die).

I think things fail too much, too easily.
Thread Rating:
  • 0 Vote(s) - 0 Average

Logout Mark Read Team Forum Stats Members Help
Recording Stream Existed Early00