- August 4, 2007
- 861
- 99
- Home Country
- Spain
- Thread starter
- Moderator
- #21
Hi all,
I was investigating into old bug reports that could help me in this case... and I've come across this one:
https://forum.team-mediaportal.com/...96/spanish-tswriter-problem-78380/index2.html
After reviewing all this issue, I can confirm I'm experiencing exact same issue (in fact, is the same spanish DVB-t multiplex also, and others). First of all sorry, because first time I looked into my logs I dind't see anything in tswriter.log, and that's why I concentrated all my efforts and findings in tsreader... BUT, I've gone to 1.1.0 RC2 again, and I can see tswriter logs regarding pmt changes:
What's more, I've used tswriter provided in that post, with no pmt change detection, and I don't have any stutter or glitch after more than an hour of livetv in conflicting multiplex.
Now my questions:
- is Tswriter in that post 100% compatible with RC2, or I must ask for a RC2 compatible tswriter with this feature deactivated?
- Is there any mantis open about this? What's more... is there any solution for our case, is a real bug? Any way to rescan PMT table with no glitch (I assume it's not possible)? Are we condemned to ask for compatible tswriter for each new MP TV Server release? Could it be configurable?
I repeat: No problem to record entire .ts and upload it so you can test this... In fact, I'll do it anyway.
Thanks so much for your patience.
EDIT: Perfect. I could grab entire ts while one of these pat change, using TV Server debug option. 1 Gb file. You'll have it uploaded to your ftp
Address: ftp.team-mediaportal.com
Login: tsdump@team-mediaportal.com
Password: mpuser88
tomorrow morning.
bye!
I was investigating into old bug reports that could help me in this case... and I've come across this one:
https://forum.team-mediaportal.com/...96/spanish-tswriter-problem-78380/index2.html
After reviewing all this issue, I can confirm I'm experiencing exact same issue (in fact, is the same spanish DVB-t multiplex also, and others). First of all sorry, because first time I looked into my logs I dind't see anything in tswriter.log, and that's why I concentrated all my efforts and findings in tsreader... BUT, I've gone to 1.1.0 RC2 again, and I can see tswriter logs regarding pmt changes:
Code:
26-04-2010 15:45:07.153 pmtgrabber: got new pmt version:1f 1e, service_id:8c
26-04-2010 15:45:07.153 pmtgrabber: do callback pid 12c
26-04-2010 15:45:07.161 analyzer: set video pid:12d
26-04-2010 15:45:07.161 analyzer: reset
26-04-2010 15:45:07.163 analyzer: set audio pid:12f
26-04-2010 15:45:07.163 analyzer: reset
26-04-2010 15:45:07.167 Recorder: TIMESHIFT paused=yes
26-04-2010 15:45:07.167 Recorder: TIMESHIFT Received from TvService: pmt pid:0x12c serviceId: 0x8c pmtlength:369
26-04-2010 15:45:07.167 Recorder: TIMESHIFT Old pids cleared
26-04-2010 15:45:07.168 Recorder: TIMESHIFT got pmt - tableid: 0x2 section_length: 369 sid: 0x8c
26-04-2010 15:45:07.168 Recorder: TIMESHIFT PMT parsed - Pid 0x12c ServiceId 0x8c stream count: 13
26-04-2010 15:45:07.168 Recorder: TIMESHIFT pcr pid:0x12d
26-04-2010 15:45:07.168 Recorder: TIMESHIFT SetPcrPid clear old PIDs
26-04-2010 15:45:07.168 Recorder: TIMESHIFT determine new start pcr
26-04-2010 15:45:07.168 Recorder: TIMESHIFT add video stream pid: 0x12d fake pid: 0x30 stream type: 0x2 logical type: 0x2 descriptor length: 3
26-04-2010 15:45:07.169 Recorder: TIMESHIFT add teletext stream pid: 0x12e fake pid: 0x68 stream type: 0x6 logical type: 0x56 descriptor length: 48
26-04-2010 15:45:07.169 Recorder: TIMESHIFT add audio stream pid: 0x12f fake pid: 0x40 stream type: 0x3 logical type: 0x3 descriptor length: 6
26-04-2010 15:45:07.169 Recorder: TIMESHIFT add audio stream pid: 0x130 fake pid: 0x41 stream type: 0x3 logical type: 0x3 descriptor length: 6
26-04-2010 15:45:07.169 Recorder: TIMESHIFT add subtitle stream pid: 0x137 fake pid: 0x50 stream type: 0x6 logical type: 0x6 descriptor length: 10
26-04-2010 15:45:07.169 Recorder: TIMESHIFT stream rejected - pid: 0x28a stream type: 0x5 logical type: 0x5 descriptor length: 5
26-04-2010 15:45:07.169 Recorder: TIMESHIFT stream rejected - pid: 0x28b stream type: 0xb logical type: 0xb descriptor length: 49
26-04-2010 15:45:07.170 Recorder: TIMESHIFT stream rejected - pid: 0x28c stream type: 0x5 logical type: 0x5 descriptor length: 5
26-04-2010 15:45:07.170 Recorder: TIMESHIFT stream rejected - pid: 0x28d stream type: 0xb logical type: 0xb descriptor length: 51
26-04-2010 15:45:07.170 Recorder: TIMESHIFT stream rejected - pid: 0x28e stream type: 0x5 logical type: 0x5 descriptor length: 5
26-04-2010 15:45:07.170 Recorder: TIMESHIFT stream rejected - pid: 0x28f stream type: 0xb logical type: 0xb descriptor length: 49
26-04-2010 15:45:07.170 Recorder: TIMESHIFT stream rejected - pid: 0x290 stream type: 0x5 logical type: 0x5 descriptor length: 5
26-04-2010 15:45:07.170 Recorder: TIMESHIFT stream rejected - pid: 0x291 stream type: 0xb logical type: 0xb descriptor length: 49
26-04-2010 15:45:07.171 Recorder: TIMESHIFT paused=no
26-04-2010 15:45:07.184 Recorder: TIMESHIFT start of video detected
26-04-2010 15:45:07.185 Recorder: TIMESHIFT clear TS packet queue
26-04-2010 15:45:07.185 Recorder: TIMESHIFT Info : Next broadcaster program clock reference rollover : 0 days 16:43:42 0
26-04-2010 15:45:07.263 Recorder: TIMESHIFT start of audio detected
26-04-2010 15:45:07.273 Recorder: TIMESHIFT start of audio detected
What's more, I've used tswriter provided in that post, with no pmt change detection, and I don't have any stutter or glitch after more than an hour of livetv in conflicting multiplex.
Now my questions:
- is Tswriter in that post 100% compatible with RC2, or I must ask for a RC2 compatible tswriter with this feature deactivated?
- Is there any mantis open about this? What's more... is there any solution for our case, is a real bug? Any way to rescan PMT table with no glitch (I assume it's not possible)? Are we condemned to ask for compatible tswriter for each new MP TV Server release? Could it be configurable?
I repeat: No problem to record entire .ts and upload it so you can test this... In fact, I'll do it anyway.
Thanks so much for your patience.
EDIT: Perfect. I could grab entire ts while one of these pat change, using TV Server debug option. 1 Gb file. You'll have it uploaded to your ftp
Address: ftp.team-mediaportal.com
Login: tsdump@team-mediaportal.com
Password: mpuser88
tomorrow morning.
bye!