Saturday, March 29th, 2025, 00:32 UTC | ||
[00:32:02] | Steve-Goodey (Steve-Goodey!~steve@host86-131-70-218.range86-131.btcentralplus.com) has quit (Quit: Konversation terminated!) | |
[01:32:04] | mad_enz (mad_enz!~mad_enz@2607:f2c0:e241:fe84:a889:df0c:1462:e1e2) has quit (Ping timeout: 260 seconds) | |
[01:44:34] | mad_enz (mad_enz!~mad_enz@2607:f2c0:e241:fe84:d4be:274e:342f:fa00) has joined #mythtv-users | |
[07:31:08] | Steve-Goodey (Steve-Goodey!~steve@host86-149-198-168.range86-149.btcentralplus.com) has joined #mythtv-users | |
[07:31:08] | Mode for #mythtv-users by ChanServ!ChanServ@services.libera.chat : +v Steve-Goodey | |
[08:15:12] | clueminati (clueminati!~clueminat@gateway/tor-sasl/clueminati) has quit (Remote host closed the connection) | |
[09:07:12] | clueminati (clueminati!~clueminat@gateway/tor-sasl/clueminati) has joined #mythtv-users | |
[09:21:49] | mad_enz (mad_enz!~mad_enz@2607:f2c0:e241:fe84:d4be:274e:342f:fa00) has quit (Ping timeout: 272 seconds) | |
[09:38:52] | mad_enz (mad_enz!~mad_enz@2607:f2c0:e241:fe84:d4be:274e:342f:fa00) has joined #mythtv-users | |
[11:01:37] | mad_enz (mad_enz!~mad_enz@2607:f2c0:e241:fe84:d4be:274e:342f:fa00) has quit (Ping timeout: 248 seconds) | |
[11:16:50] | mad_enz (mad_enz!~mad_enz@2607:f2c0:e241:fe84:d4be:274e:342f:fa00) has joined #mythtv-users | |
[11:35:13] | Sabotender (Sabotender!uid52353@user/sabotender) has quit (Quit: Connection closed for inactivity) | |
[13:15:08] | Sabotender (Sabotender!uid52353@user/sabotender) has joined #mythtv-users | |
[14:05:54] | Steve-Goodey (Steve-Goodey!~steve@host86-149-198-168.range86-149.btcentralplus.com) has quit (Quit: Konversation terminated!) | |
[14:31:02] | Sabotender: | One thing about the Mythweb that doesn't seem very logical. It will tell you that a recording is "Failing", but won't tell you why. |
[14:33:41] | Sabotender: | There's no methodology set up where the user could view the logs, especially error logs through the web view. It would be most useful if the user had easy access to this information, so they can troubleshoot issues when they arise. It leaves everything up for the user to investigate the issue. Since a 'Failing" error is a sign for numerous reasons. |
[14:35:16] | Sabotender: | If a programme is sheduled to record , and it is currently recording, there should have readouts of the signal strength and quality in which the channel is tuned. |
[14:37:00] | Sabotender: | also, it would be most helpful,for a pie-chart or bar graph for recording directories with more detailed information about the drives that are in use. |
[14:40:50] | Sabotender: | If files are suddenly missing, there should be a method that allows the user to search for the missing file automatically and either make note of the new file location, aand/or ask the user if they wanted to move the files back to the parent directory, to clean up the clutter. Half of these issues arise when the user is making changes to the recording directories, and then Myth TV suddenly forgets where they had been working previously, |
[14:40:50] | Sabotender: | and then the frontend spews errors. |
[14:42:37] | Sabotender: | If the frontend reports that a file had been damaged, it should have more information regarding the reason that cause dthe file to become damaged, and what led up to the error. |
[15:56:20] | Steve-Goodey (Steve-Goodey!~steve@host86-149-198-168.range86-149.btcentralplus.com) has joined #mythtv-users | |
[15:56:20] | Mode for #mythtv-users by ChanServ!ChanServ@services.libera.chat : +v Steve-Goodey | |
[16:27:20] | clueminati (clueminati!~clueminat@gateway/tor-sasl/clueminati) has quit (Read error: Connection reset by peer) | |
[16:27:45] | clueminati (clueminati!~clueminat@gateway/tor-sasl/clueminati) has joined #mythtv-users | |
[16:28:46] | Toasty (Toasty!~quassel@w-233.cust-u11407.ip.static.unobb.net.uk) has joined #mythtv-users | |
[16:39:12] | clueminati (clueminati!~clueminat@gateway/tor-sasl/clueminati) has quit (Ping timeout: 264 seconds) | |
[16:40:58] | clueminati (clueminati!~clueminat@gateway/tor-sasl/clueminati) has joined #mythtv-users | |
[18:40:53] | clueminati (clueminati!~clueminat@gateway/tor-sasl/clueminati) has quit (Remote host closed the connection) | |
[18:41:14] | clueminati (clueminati!~clueminat@gateway/tor-sasl/clueminati) has joined #mythtv-users | |
[18:51:19] | Scopeuk: | on the file thing, myth doesn't store where files are, just their names, if you move recordings between recording directories they will "just work" the issue arises when you lose a mounted drive or similar |
[20:29:35] | Steve-Goodey (Steve-Goodey!~steve@host86-149-198-168.range86-149.btcentralplus.com) has quit (Quit: Konversation terminated!) | |
[20:47:33] | Toasty (Toasty!~quassel@w-233.cust-u11407.ip.static.unobb.net.uk) has quit (Ping timeout: 244 seconds) | |
[21:30:19] | Sabotender: | Scopeuk: Perhaps, but MythTV doesn't alwasy record programmes where you tell it to. I don't ever want it putting recordings in the default folder. That is why I bound it to another directory using two methods: a mounted bind directory via etc/fstab, AND a hard linked directory. The default directory is a very undesirable location, and should not ever be used to save the userfor recording anything. I would rather it just not make any |
[21:30:19] | Sabotender: | recordings, but there is no method to disable this. |
[21:31:01] | Sabotender: | I have ordered that 20TB hard drive, but I am going to format it to a partition scheme that allows hard linking directories. |
[21:33:12] | Sabotender: | I even tried just deleting the default directory, but MythTV adds it back. |
[21:35:05] | Sabotender: | I thought that setting the default directory in the recording profiles would resolve this issue, because I left every configuration to defaults, but still some recordings made its way into there. |
[23:32:51] | Steve-Goodey (Steve-Goodey!~steve@host86-149-198-168.range86-149.btcentralplus.com) has joined #mythtv-users | |
[23:32:51] | Mode for #mythtv-users by ChanServ!ChanServ@services.libera.chat : +v Steve-Goodey |
IRC Logs collected by
BeirdoBot.
Please use the above link to report any bugs.