Changes between Initial Version and Version 1 of Ticket #340


Ignore:
Timestamp:
Sep 16, 2005, 12:06:51 AM (16 years ago)
Author:
Isaac Richards
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #340 – Description

    initial v1  
    22
    33Getting rid of the Ringbuffer way of timeshifting would be nice:
    4 * Ringbuffer's slow for local access (ie, uses the network)
    5 * Multiple semi-complicated codepaths to support the Ringbuffer and normal file access.
    6 * Unable to save an in-progress show from the timeshifting buffer.
    7  
     4 * Ringbuffer's slow for local access (ie, uses the network)
     5 * Multiple semi-complicated codepaths to support the Ringbuffer and normal file access.
     6 * Unable to save an in-progress show from the timeshifting buffer.
     7
     8
    89The idea would be to:
    9 * Just use normal files for timeshifting.
    10 * Automatically change to a new physical file on channel change or program change (from the guide data).  Would also need to segment files every few hours, in order to allow very long programs to be timeshifted and still offer the ability to limit space used for timeshifting.  Could just punt on this and just require enough recording space, though.
     10 * Just use normal files for timeshifting.
     11 * Automatically change to a new physical file on channel change or program change (from the guide data).  Would also need to segment files every few hours, in order to allow very long programs to be timeshifted and still offer the ability to limit space used for timeshifting.  Could just punt on this and just require enough recording space, though.
    1112
    1213Basically, the recorder would need to create a chain of files to play back,