DD not recording all audio PIDs
Posted: Sun Feb 19, 2012 12:24 pm
I am using version 1.7a and set the preferences to record a ts stream with all audio PIDs.
The problem is that DD only records (or is offering while you are watching) the audio PIDs that happened (!) to be present during the transponder scan. However, broadcasters change the number of PIDs depending on the programs. This means, that DD should record any PID present at the time of the recording; and not just at the beginning since it could change during the recording as well.
Here is a scan report that shows how the number of PIDs changes depending on the time of the scan:
* Updated *
----------------------------------------
1) Sky Cinema +24 (SKY) 11797,H,27500 Number of audio pids(3=>1)
later I scanned the same transponder again:
* Updated *
----------------------------------------
1) Sky Emotion (SKY) 11797,H,27500 Number of audio pids(2=>3)
2) Sky Cinema +24 (SKY) 11797,H,27500 Number of audio pids(1=>3)
DD will only record what ever it found during those scans.
Whether this is a bug or an oversight, I don't know but I thing this is important and should be addressed.
The problem is that DD only records (or is offering while you are watching) the audio PIDs that happened (!) to be present during the transponder scan. However, broadcasters change the number of PIDs depending on the programs. This means, that DD should record any PID present at the time of the recording; and not just at the beginning since it could change during the recording as well.
Here is a scan report that shows how the number of PIDs changes depending on the time of the scan:
* Updated *
----------------------------------------
1) Sky Cinema +24 (SKY) 11797,H,27500 Number of audio pids(3=>1)
later I scanned the same transponder again:
* Updated *
----------------------------------------
1) Sky Emotion (SKY) 11797,H,27500 Number of audio pids(2=>3)
2) Sky Cinema +24 (SKY) 11797,H,27500 Number of audio pids(1=>3)
DD will only record what ever it found during those scans.
Whether this is a bug or an oversight, I don't know but I thing this is important and should be addressed.