dotnet "C:\PROGRA~1\NextPVR\NScriptHelper.dll" -Rename "C:\Users\Public\Videos\REC\Lie to Me\Season 03\Lie.to.Me.S03E13.Le.mauvais.génie.ts" "I:\Lie to Me\Season 03\Lie.to.Me.S03E13.Le.mauvais.génie.ts" does not rename the file in the DB.
Despite no error message on execution,I verified it changed nothing with export recording.
in v4 you are able to check in log the execution of NscriptHelper -rename
One other issue I've detected ... Win 10 client, v5.0.5 (200518)
If I try to skip back (either via remote, Ctrl-[Left Arrow] on keyboard or via on screen menu) when watching live tv, I'll get a client unhandled exception message.
This does not occur if watching a recording (i.e. functions as desired) - only when watching live tv.
Error is "Unhandled exception .... the method or operation is not implemented".
Logs don't appear to show much ... examples occurred at :
2020-05-23 22:28:04.309
2020-05-23 22:30:51.691
Although examples show event occurring soon after starting stream, confirm it is same result if you are e.g. 30 mins through.
To reproduce either :
- watch live tv, on screen click the skip back button ( |< )
- watch live tv, Ctrl-[Left Arrow] on keyboard
Attached logs and text of unhandled exception message.
Hey guys
As above subject matter my nvidia shield updated from 18.6 to 18.7. Since updating EPG etc all seems to work as usual but when going to try and watch anything I get sound but nothing else. It works on my android phone Kodi which is still 18.6 and have restarted windows machine which the backend is installed on so it's most definitely the Kodi update. Has anyone else experienced this at all or have any ideas on fixes at all?
Thanks in advance guys
I've finally made the move from v4 to v5, and all is working pretty well, there's just one small feature that I'm missing which is the screensaver. Was a big fan of it as it meant when we weren't watching something we could have it scrolling through our photos on the tv (set to FullscreenRandomPhoto ).
I see the setting is still in the config file but I suspect this may just be a hangover as it definitely doesn't trigger for me, even if I leave it on the default new config file setting ... any intention of including the feature in a later update?
(Note - given I couldn't find any other forum posts about it, I understand it may not be a feature used by very many and therefore not a priority - which is ok too, just thought I'd ask. )
I ran a test where I scheduled a recording and then suspended my computer. Is there any support or anyone know how to pull this off? Was thinking of have the server be on demand rather than on 24/7
This has been an intermittent issue where some recordings have started late. It seems that the server is trying to start a stream but fails and then goes on the another tuner to try. My first 4 tuners are on an internal hauppauge quad tuner card and the last is an HDHomerun tuner. I am thinking that the internal card tuners are all failing when this happens because right now I have 2 recordings scheduled but only one eventually started running 5 minutes late.
When I try to look at device status in the web interface it says no devices active even though it is recording.
To complicate things, locally in Chicago, the Willis tower where several local stations have their antenna has been without power for several days due to flooding in its basement, so I have had failed recordings due to that so it has muddied the water a little.
Here is a portion of the log:
Quote:2020-05-22 14:29:00.066 [DEBUG][8] DefaultDirectoryChoice: spread
2020-05-22 14:29:00.329 [DEBUG][8] allocating recording target filename: /recordings/Manual Recordings/Pritzker_20200522_14301540.ts
2020-05-22 14:29:00.332 [DEBUG][8] About to start recording (166132 on 23): /recordings/Manual Recordings/Pritzker_20200522_14301540.ts...
2020-05-22 14:29:00.332 [DEBUG][8] (Recording is due to be stopped at 5/22/2020 3:40 PM)
2020-05-22 14:29:00.332 [DEBUG][8] http://localhost:37649/stream/start?slip...4301540.ts
2020-05-22 14:30:40.330 [ERROR][8] Unexpected error on LocalRecorder.StartStream(): System.Net.WebException: The operation has timed out.
at System.Net.HttpWebRequest.GetResponse()
at System.Net.WebClient.GetWebResponse(WebRequest request)
at System.Net.WebClient.DownloadBits(WebRequest request, Stream writeStream)
at System.Net.WebClient.UploadBits(WebRequest request, Stream readStream, Byte[] buffer, Int32 chunkSize, Byte[] header, Byte[] footer)
at System.Net.WebClient.UploadDataInternal(Uri address, String method, Byte[] data, WebRequest& request)
at System.Net.WebClient.UploadString(Uri address, String method, String data)
at NShared.LocalRecorder.StartStream(ChannelMapping channelMapping, String target, String& reason)
2020-05-22 14:30:40.331 [DEBUG][8] Failed to start recording on allocated device (166132:/recordings/Manual Recordings/Pritzker_20200522_14301540.ts): 'The operation has timed out.'
2020-05-22 14:30:40.331 [DEBUG][8] Looking for second chance device to perform recording...
2020-05-22 14:30:40.343 [DEBUG][8] Found possible backup device
2020-05-22 14:30:40.348 [DEBUG][8] http://localhost:32811/stream/start?slip...4301540.ts
2020-05-22 14:31:31.630 [DEBUG][70] Got request [::ffff:192.168.9.120]: /services/service (recording.list)
2020-05-22 14:31:31.630 [DEBUG][44] Got request [::ffff:192.168.9.120]: /services/service (setting.get)
I can probably clear it up by rebooting, but I don't want to lose the recording that is in process right now.
So as far as anything that might need your attention, the only thing is the web interface not showing device status. That would help me in diagnosing the hardware if I can see which tuners are actually being used.
As far as the rest, any suggestions as to what might be the problem on my end? Do you think the tuner is ready to fail? It is several years old carried over from my old v4 system. Any ways to automatically detect the problems ahead of time so I can reboot the box? I've rebooted several times the last few days with that other issue in the web interface, but I have not done a full power down. I'm inclined to think it is hardware issue so mostly looking for advice.
For some reason, some channels work and then others crash. I'm thinking it could be related to the channels being in 1080? CBS and NBC crash for me. I also tried playing a recording from one of those channels and the same thing happened.
On a different kodi front end I am not having any issues. Seems like the backed is recording them fine but when I try to watch using Ubuntu 20.xx and Kodi it seems to be happening. Attached are the logs. Any ideas?
Been using V5 for the past several days for my normal recording schedule. When I brought up the web app this morning, the red "Failed" items shown are puzzling. The item marked "CMTT:TT" shows as failed but the recording completed normally and is in the correct folder.
I am having a problem going through the V5 logs and hope someone can find out why three items are marked "FAILED:"
- [CMT East] 5/21/2020 7:00:00 AM - 9:00:00 AM
- [MTV Live HD] 5/20/2020 6:00:00 AM - 8:00:00 AM
- [Hallmark Movies] 5/16/2020 9:00:00 AM - 11:00:00 AM
