PMT ID for channel not found

Bug #387460 reported by mb74
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Me TV
Invalid
Undecided
Unassigned
me-tv (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: me-tv

I've observed this bug in version 0.9.3-beta1.
When I use the old db-file then all channels work perfectly. But when I use the newly created db-file with the new channels scanned with the new version 0.9.3-beta1 then I get the error "PMT ID for channel not found" for all channels.

Revision history for this message
mb74 (mrb74) wrote :
Revision history for this message
mb74 (mrb74) wrote :

The channels were scanned with an external program and exported to channels.conf. Then I modified the file by hand and here is the result:
PULS 4(sevenonemedia):474000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_AUTO:3050:3051:10121
3SAT(ORF):474000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_AUTO:3055:3056:11302
ORF Sport Plus(ORF):474000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_AUTO:3060:3061:11303
ORF1(ORF):554000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_AUTO:1010:1011:10101
ORF2 W(ORF):554000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_AUTO:1020:1021:10102
ATV(ATV+):554000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_AUTO:1040:1041:10120
ORF2 N(ORF):554000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_AUTO:1020:1021:10122
P3TV(P3TV):850000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_AUTO:1070:1071:12101

I had to change some parameters to AUTO to get all channels working.
Then I imported these channels in me-tv. All of these channels work perfectly.

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

You cannot raise this bug here. You have raised this against Ubuntu and this bug has nothing to do with Ubuntu,

Changed in me-tv (Ubuntu):
status: New → Invalid
Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

New bug created.

Can you please attach a verbose output from you trying to tune to one of those channels. When you scan, are there duplicate service names in the channel list?

Changed in me-tv:
status: New → In Progress
Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

Here's what I've found,

OLD: sqlite3 me-tv-old.db "select name, frequency, service_id from channel"

PULS 4(sevenonemedia)|474000000|10121
3SAT(ORF)|474000000|11302
ORF Sport Plus(ORF)|474000000|11303
ORF1(ORF)|554000000|10101
ORF2 W(ORF)|554000000|10102
ATV(ATV+)|554000000|10120
ORF2 N(ORF)|554000000|10122
P3TV(P3TV)|850000000|12101

NEW: sqlite3 me-tv.db "select name, frequency, service_id from channel"

ORF1|474000000|10101
ORF2 K|474000000|10116
ATV|474000000|10120
ORF2 T|474000000|10136

Now, here's the interesting bit, if you look at ORF1 you can see that it's got a different frequency. I wonder if the transponder at 474000000 is reporting services for the transponder at 554000000. Do you know if this happens where you are? This might be observed if you see duplicate service names in the scan results. I ask you to -v the application and attach the result from a scan and confirm if duplicate services exist.

Another thing to try is to create an initial scan file with only the 554000000 transponder in it.

Revision history for this message
Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote :

No response.

Changed in me-tv:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.