[mythtv-users] Recent "pixelation" or "glitches" in recordings (HDHR related?)

[Raymond Wagner]

On 24/04/2013 at 2:30PM, Joseph Fry wrote:
>>> Using a SSD as described above would allow the drives to remain spun
>>> down except when transferring recordings from the SSD, or watching one
>>> that was already transferred.  Because the transfers would occur
>>> faster than recording directly and because only a fraction of all
>>> recordings would actually make it to the magnetic drives, they would
>>> remain spun down far more.
>>
>> Unfortunately, the storage drives in this scheme would be started more
>> often than you would like.  When mythfrontend displays a list of
>> programs, it makes a check for the presence of the recording's file
>> and displays an X icon for those it can not find.  That checking
>> process would start all the storage drives every time it happened as
>> all partitions in all storage groups are scanned to find files.  There
>> is no way the current operation of MythTV would allow just the drive
>> needed to play a specific recording to be started, as the actual
>> locations for the files are not stored in the database.
>
> Interesting, I had never heard that before.  Sounds like it would be
> worth lobbying to have changed, perhaps have it confirm they are
> available on some sort of schedule rather then every time the user
> opens the watch recordings screen.

With any luck, this should be committed to master in a week or two, in
time for 0.27. I have a replacement file scanner for the video library
written, but not yet committed or well tested, that keeps track of all
files in all storage groups. Rather than storing a file and group name,
recordings and videos would merely store a reference id, and MythTV would
look up the cached locations instead of performing an exhaustive search
each time it needs to access the file.