Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Yaobing]

Description

With build 33.0.29 comes the ability to recording multiple TV channels using a single tuner, if the channels are on the same transport stream.

This is implemented only on Windows, for bda devices, i.e. ATSC, and DVB (all three flavors) devices.  Recording format must be "Transport Stream" (TS).

 
Instructions

• Set recording format to TS, if you have not already done so.
• Schedule recordings on multiple channels, with overlapping time windows

If the channels are on the same transport (i.e. with the same transport stream ID, for ATSC typically channels with the same major channel number), the recordings will be done on the same tuner.

Limitations and known issues

Limitation:

Recording must be in TS format.  The new feature currently is not supported for JTV format.  Implementation for JTV will be much harder and thus will not happen soon (if we decide to do it).

Known issues:

• If you try to watch a channel that is currently been recorded, you may end up seeing a different channel (one that started recording on the same tuner first).  For example, if you record shows on channels 5-1 and 5-2, and the one on 5-1 happens to be started first, then you will see the show on 5-1, even though you try to see 5-2.  This is true even if the recording on 5-1 has stopped. with build 33.0.30, the behavior is better, although still not ideal: if you try to play a currently recording channel, that was not started recording first on the shared tuner, you will end up using another available tuner to watch the channel live (without being able to see what has already been recorded).
  
  Ideally, one should be able to watch the already recorded part, but this is not possible without making additional big changes in TV engine.  So you may have to live with it for a long time.
  
  
• The Status page will show a tuner is using only one channel, the one that started last (channel 5-2 in the example above), but all recording IDs are listed.  This one is minor and may be fixed easily.
  
  This has been fixed in build 30.