TV-Server Version: 1.0 SVN 21720
MediaPortal Version: 1.0 SVN 21720
MediaPortal Skin: Blue 3 wide
Windows Version: Vista Home Basic SP1
CPU Type: Intel E4500, 2.2GHz
HDD: 500GB
Memory: 2GB
Motherboard: Dell Vostro 200SL
Video Card: XFX 9500GT low-profile
Video Card Driver: 181.20
Sound Card: Creative SoundBlaster Audigy SE
Sound Card AC3: Creative SoundBlaster Audigy SE
Sound Card Driver: P17X_PCDVT_LB_1_04_0079
1. TV Card: Kworld DVB-T 399U
1. TV Card Type: DVB-T
1. TV Card Driver: V8.4.28.1
2. TV Card:
2. TV Card Type:
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec: PDVD7
MPEG2 Audio Codec: FFDShow (libavcodec)
h.264 Video Codec: MPC-HC
Satelite/CableTV Provider:
HTPC Case:
Cooling:
Power Supply:
Remote: USB-UIRT -> EventGhost
TV: Panasonic TX37LZD80 @ 1920x1080p
TV - HTPC Connection: DVI -> HDMI
I have a twin-tuner DVB-T setup.
If MP is recording from a channel, and I then skip between viewing a channel on a different DVB-T 'mux' and one on the same (as the recording) DVB-T 'mux', the TV-server doesn't appear to delete/re-use the timeshift buffer files for the tuner being used for the recording - it keeps creating new ones (until the small 256MB ramdisk I use for timeshifting runs out of space, when the 'live' TV just freezes). It looks like all of the 'sets' of timeshift files are being actually being updated (the file modification times stay in step).
Logs and screenshot of the timeshift disk files attached.
TV-server is configured to use a maximum of 3 x 20MB timeshift files per tuner (the minimum possible settings), the timeshift files are stored on a 256MB ramdisk.
The problem is completely repeatable:
start MP -> start TV -> manually start recording on current channel -> switch to channel on different DVB-T mux -> switch to channel on same mux as recording -> (repeat last 2 steps a few times) -> result is multiple sets of timeshift files e.g. live1-0.ts.*/live1-2.ts.*/live1-3.ts.* etc all being continually updated (I've never noticed a 'live1-1.ts.*' set created - it always starts with 'live1-0.ts.*' then creates a 'live1-2.ts.*' set next).
Tony
(and yes, the thread title has a spelling mistake.....)
MediaPortal Version: 1.0 SVN 21720
MediaPortal Skin: Blue 3 wide
Windows Version: Vista Home Basic SP1
CPU Type: Intel E4500, 2.2GHz
HDD: 500GB
Memory: 2GB
Motherboard: Dell Vostro 200SL
Video Card: XFX 9500GT low-profile
Video Card Driver: 181.20
Sound Card: Creative SoundBlaster Audigy SE
Sound Card AC3: Creative SoundBlaster Audigy SE
Sound Card Driver: P17X_PCDVT_LB_1_04_0079
1. TV Card: Kworld DVB-T 399U
1. TV Card Type: DVB-T
1. TV Card Driver: V8.4.28.1
2. TV Card:
2. TV Card Type:
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec: PDVD7
MPEG2 Audio Codec: FFDShow (libavcodec)
h.264 Video Codec: MPC-HC
Satelite/CableTV Provider:
HTPC Case:
Cooling:
Power Supply:
Remote: USB-UIRT -> EventGhost
TV: Panasonic TX37LZD80 @ 1920x1080p
TV - HTPC Connection: DVI -> HDMI
I have a twin-tuner DVB-T setup.
If MP is recording from a channel, and I then skip between viewing a channel on a different DVB-T 'mux' and one on the same (as the recording) DVB-T 'mux', the TV-server doesn't appear to delete/re-use the timeshift buffer files for the tuner being used for the recording - it keeps creating new ones (until the small 256MB ramdisk I use for timeshifting runs out of space, when the 'live' TV just freezes). It looks like all of the 'sets' of timeshift files are being actually being updated (the file modification times stay in step).
Logs and screenshot of the timeshift disk files attached.
TV-server is configured to use a maximum of 3 x 20MB timeshift files per tuner (the minimum possible settings), the timeshift files are stored on a 256MB ramdisk.
The problem is completely repeatable:
start MP -> start TV -> manually start recording on current channel -> switch to channel on different DVB-T mux -> switch to channel on same mux as recording -> (repeat last 2 steps a few times) -> result is multiple sets of timeshift files e.g. live1-0.ts.*/live1-2.ts.*/live1-3.ts.* etc all being continually updated (I've never noticed a 'live1-1.ts.*' set created - it always starts with 'live1-0.ts.*' then creates a 'live1-2.ts.*' set next).
Tony
(and yes, the thread title has a spelling mistake.....)