Using Schedules Direct in UK

[jamesdisco]

Ive just followed this post and used the frq data that DDAC produces and it works although i'm still left with 100's of channels to disable in channel manager (all the radio channels are wrongly numbered and all the regional duplicates need removing) but it is a big improvement

[Fuzzy]

Originally Posted by jamesdisco

Here's a channel scan from the UK its enormous with over 900 channels.
Ive no idea how to merge the scanned channels with the list from SD which has over 600 in the sky lineup. In the past i have always edited the frq with the correct channel nos. and then followed the instructions in this post.
Really hoping someone can find a way to make sage match up the scans with the SD list.

I was hoping to see the sagetv log from a scan - so I could see what information the tuner is sending TO sage's matching logic to see if things need to be massaged to try to line up the scanned channels to the list provided by schedules direct.

[deanm]

Originally Posted by jamesdisco

Ive just followed this post and used the frq data that DDAC produces and it works although i'm still left with 100's of channels to disable in channel manager (all the radio channels are wrongly numbered and all the regional duplicates need removing) but it is a big improvement

Someone created a Channel Import/Export Plugin and is better then manualy editing the sage.properties file.

I can modify DDAC to not use DigiGuide and still produce the .FRQ files. It will still use EPG.Collector to find channel numbers etc and KingOfSat to fill in the gaps.

Still not 100% as ideally we need a way to match the channels from SD.

Deanm

[jamesdisco]

Originally Posted by deanm

Someone created a Channel Import/Export Plugin and is better then manualy editing the sage.properties file.

I can modify DDAC to not use DigiGuide and still produce the .FRQ files. It will still use EPG.Collector to find channel numbers etc and KingOfSat to fill in the gaps.

Still not 100% as ideally we need a way to match the channels from SD.

Deanm

I saw you'd used import export plugin i'll have a play with that tonight should be a good way of removing lots of channels at once.
That would be great if you could modify DDAC to produce the frq's without digiguide.

[jamesdisco]

Originally Posted by Fuzzy

I was hoping to see the sagetv log from a scan - so I could see what information the tuner is sending TO sage's matching logic to see if things need to be massaged to try to line up the scanned channels to the list provided by schedules direct.

I'll have a go at that tonight. The channel names for most channels just dont look very similar so i'm not sure how it will match them up.
Perhaps instead of doing a channel scan sage could produce an frq with just the channel no. and name(no tuning info) and then use this plugin to pull the tuning data in.

[Fuzzy]

Originally Posted by jamesdisco

I'll have a go at that tonight. The channel names for most channels just dont look very similar so i'm not sure how it will match them up.
Perhaps instead of doing a channel scan sage could produce an frq with just the channel no. and name(no tuning info) and then use this plugin to pull the tuning data in.

It might be something that could be improved at the Schedules Direct end as well. What sage presents from the scan SHOULD be the callsign that is embedded IN the stream, as well as the tuning information. That callsign in the stream SHOULD be what schedules direct is sending as CALLSIGN when getting a lineup from them, which should allow sage to match it up well. I'd have to see what information the scan is providing to verify this, however.

[jamesdisco]

Originally Posted by Fuzzy

What does Sage return if you do a scan in sage without the custom FRQ file? If you restart sage (to get into a new log file) and then go strait to a full channel scan, it should include the scan results in the log (I think). If you don't mind posting that, it would be helpful for us Yanks to get the full picture of what can be done.

Here's a log file i started the scan at 21.09 it was way too big for the sage forums.

[Fuzzy]

Originally Posted by jamesdisco

Here's a log file i started the scan at 21.09 it was way too big for the sage forums.

I've got it.. just for future reference, logfiles LOVE to be compressed. That 3.6MB log file compresses down to a 350kB zip file, much easier to attach that way (and when dealing with these types of posts, it is easy to then zip up a few associated logs together and attach).

[jamesdisco]

I've been using the channel manager in BMT to disable all the unwanted channels. It allows you to do it in batches as well as being easier to use than doing it from with in sage.