Thanks to Raydon and others for the excellent work on the custom firmware.
I was wondering if the scheduled recordings page could be updated so that it shows the folder location that series recordings will be made to in a similar way that af123 does on the FOX T2?
I would provide a screenshot...
I have removed channeldel and installed tunefix and configured it to just remove channels:
170-199
201-299
790-799
I have retuned and rebooted three times but tunefix has not run and the above channels are still present. Any ideas?
A handy addition would be to include the ability to delete a range of channels so for example I would configure it as follows:
201-299 would remove all the IPTV and MHEG based data services which do not work/interest me and I would not have to keep adding new entries to the channel list to be...
Cheers prpr - I feel a right numpty that it didn't twig that these weren't the database files.
Anyway, removed the old database (zipped and attached it in case anyone wants to have a look at what is corrupt) and a fresh one has been generated. Sysmon is showing empty graphs which I guess is to...
Noticed that system monitor was just hanging and not displaying any graphs. Checking webif-error.log it states:
at file "/mod/webif/plugin/sysmon/data/temp.jim", line 12
/mod/webif/plugin/sysmon/data/temp.jim:12: Error: database disk image is malformed
Have tried all the following and it still...
I have had an occurrence where the box was in standby (recording a programme) but trying to access it via the web interface I was greeted with the screen that states:
“Custom Firmware Successfully Installed!” and “To install the full web interface and supporting packages a suitably formatted...
I do find it odd that the two DVB-T2 muxes (predominantly HD) only list the 5 DVB-T muxes and don't list the other DVB-T2 mux? I have always wondered if it is just a (mis)configuration issue or whether there is some part of the standard which states they can't do this?
All happening in this thread:
http://hummy.tv/forum/threads/auto-schedule-restore-not-restoring-all-recordings.5836/
af123 has released a couple of development test versions which I have tried but it has not fixed the problem.
Just updated via the diagnostics and run it again. I'm afraid its the same - the same 4 failed again with the "Error inserting event, unrecognized token..."
Apologies for the shortness... but I need to go to bed!
Here you go. Output attached from a restore with the test version.
By the way - thanks for all the effort you guys (especially af123) are putting into this. I am just glad others (over on the other thread) are also reporting these strange unrecognised tokens when restoring and renaming folders...
Reported and posted some files for af123 to debug over in this thread:
http://hummy.tv/forum/threads/auto-schedule-restore-not-restoring-all-recordings.5836/
It's nice to see others are getting the same problem as it proves it's nothing unique to my setup which has broken it.
Hopefully af123...
Those unrecognised token errors look familiar to what I see when trying to restore schedules or change folder names. Looks as though some key file shared by multiple components is broken.
Thanks to Raydon and others for the excellent work on the custom firmware.
I was wondering if the scheduled recordings page could be updated so that it shows the folder location that series recordings will be made to in a similar way that af123 does on the FOX T2?
I would provide a screenshot...
I have removed channeldel and installed tunefix and configured it to just remove channels:
170-199
201-299
790-799
I have retuned and rebooted three times but tunefix has not run and the above channels are still present. Any ideas?
A handy addition would be to include the ability to delete a range of channels so for example I would configure it as follows:
201-299 would remove all the IPTV and MHEG based data services which do not work/interest me and I would not have to keep adding new entries to the channel list to be...
Cheers prpr - I feel a right numpty that it didn't twig that these weren't the database files.
Anyway, removed the old database (zipped and attached it in case anyone wants to have a look at what is corrupt) and a fresh one has been generated. Sysmon is showing empty graphs which I guess is to...
Noticed that system monitor was just hanging and not displaying any graphs. Checking webif-error.log it states:
at file "/mod/webif/plugin/sysmon/data/temp.jim", line 12
/mod/webif/plugin/sysmon/data/temp.jim:12: Error: database disk image is malformed
Have tried all the following and it still...
I have had an occurrence where the box was in standby (recording a programme) but trying to access it via the web interface I was greeted with the screen that states:
“Custom Firmware Successfully Installed!” and “To install the full web interface and supporting packages a suitably formatted...
I do find it odd that the two DVB-T2 muxes (predominantly HD) only list the 5 DVB-T muxes and don't list the other DVB-T2 mux? I have always wondered if it is just a (mis)configuration issue or whether there is some part of the standard which states they can't do this?
All happening in this thread:
http://hummy.tv/forum/threads/auto-schedule-restore-not-restoring-all-recordings.5836/
af123 has released a couple of development test versions which I have tried but it has not fixed the problem.
Just updated via the diagnostics and run it again. I'm afraid its the same - the same 4 failed again with the "Error inserting event, unrecognized token..."
Apologies for the shortness... but I need to go to bed!
Here you go. Output attached from a restore with the test version.
By the way - thanks for all the effort you guys (especially af123) are putting into this. I am just glad others (over on the other thread) are also reporting these strange unrecognised tokens when restoring and renaming folders...
Reported and posted some files for af123 to debug over in this thread:
http://hummy.tv/forum/threads/auto-schedule-restore-not-restoring-all-recordings.5836/
It's nice to see others are getting the same problem as it proves it's nothing unique to my setup which has broken it.
Hopefully af123...
Those unrecognised token errors look familiar to what I see when trying to restore schedules or change folder names. Looks as though some key file shared by multiple components is broken.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.