2019-03-17, 12:51 AM
mvallevand Wrote:Try the attached.
Martin
That's brought the recordings back what did you do?
2019-03-17, 12:51 AM
mvallevand Wrote:Try the attached. That's brought the recordings back what did you do?
2019-03-17, 12:53 AM
I simply removed the 3 bad conflict records.
Martin
2019-03-17, 12:56 AM
sub Wrote:From reports over the last few we knew that 4.2.3 could generate this type of garbage in the UK, due to some change in the UK broadcasts, and there was an attempt to fix it for 4.2.4. This fix will only effect new listings though, not those already stored within a recording. They keep changing stuff here in the UK and I always get issues it looks like the edited file provided by martin brought the records back
2019-03-17, 12:58 AM
But what I mean is how did you know they were bad how would I be able too fix something like this myself if it happened again
I bet you have removed 3 super interesting recordings it best not be top gear lol Thanks for the help on that my gf will stop bugging me now
2019-03-17, 01:08 AM
Sharpy420 Wrote:But what I mean is how did you know they were bad how would I be able too fix something like this myself if it happened againWe're hoping it's not going to happen again, with the changes in 4.2.4. Martin knew what to look for because he'd seen it in recent weeks from some other users. Quote:2019-03-17 13:21:22.123 [ERROR][16] Unexpected error parsing EPGEvent xml: System.Xml.XmlException: '', hexadecimal value 0x18, is an invalid character. Line 5, position 106.There is a unexpected invalid character (which you can't see in this post) before the 'c' in county.
2019-03-17, 01:22 AM
Sharpy420 Wrote:I bet you have removed 3 super interesting recordings it best not be top gear lolThey were conflict recordings so they were never actually recorded. Martin
2019-03-17, 02:15 PM
(This post was last modified: 2019-03-17, 02:53 PM by mvallevand.)
I was confused yesterday, they weren't conflicts they were failed recordings. You have a lot of them in your database and these now show in in Kodi so you can clean them out.
@sub I wonder if recordings with the message "Recording service was stopped during recording" should be marked as 3 they do have a file attached. I guess you want to re-record them if you have a chance. If that is the case you should probably do that when the service is quickly restarted. Martin
2019-03-17, 04:04 PM
mvallevand Wrote:@sub I wonder if recordings with the message "Recording service was stopped during recording" should be marked as 3 they do have a file attached. I guess you want to re-record them if you have a chance. If that is the case you should probably do that when the service is quickly restarted.If you stop the recording service while recording, the recording will be marked as status 2 (STATUS_COMPLETED), but the "Recording service was stopped during recording" message is noted. If the recording service is restarted while the show is still airing, it'll create a new recording for the second part, and continue recording. These are often not serious, and the user might have only lost a few seconds. status 3 (STATUS_COMPLETED_WITH_ERROR) is used for major problems that cause recordings to not be watchable in any way, like device failed, or device not found.
2019-03-17, 04:29 PM
In his database I saw error 3 and ""Recording service was stopped during recording". There is really a weird situation stopping the service in EPG mode so I can't quite duplicate this, I assume the restart is after the end time.
Martin
2019-03-20, 08:55 PM
mvallevand Wrote:I was confused yesterday, they weren't conflicts they were failed recordings. You have a lot of them in your database and these now show in in Kodi so you can clean them out. i was going too say i normally keep an eye out for conficted recordings and manually sort them as for failed recordings im not sure i have been doing alot of network jobs recently cables unplugged / swapped router too pfsense and my main server has crashed a few times its probably that everything seems too be working still |
|