Could you tell me the specification of tuning ini file?

[daymoon]

NextPvr can't find any channels but WinTV and WMC can.
I live in South Korea where it uses ATSC and ClearQAM.
Figuring out any solutions, I got to see tuning ini file.
There are the integers which I think stand for the channels.
I modified that integer with the frequency which was found with another program.
like that..

Please see my attachment..

Then NextPvr could find that channel..
But some channel couldn't be found even though I manually input the frequency.
... some found... some not found...

So I want to know what this ini file means.
I think the first section means the name and the second section means the channels which are going to be checked by NextPvr.

In the second section, I think 0 key means the total count.
Are those right?

What I really want to know is the specification of the next 0 key's value.
There are three commas. What does each part mean?

1=what, what, what
2=what, what, what (, might be more..?)

Thanks in advance.

[mvallevand]

Is the tuning file different in WinTV?

Martin

[daymoon]

I don't know whether WinTV has tuning files like NextPVR or not.
However, WinTV can find channels.
I didn't modify any ini file in WinTV. Just using WinTV UI(searching channels menu), it could find channels.

I found frequencies with pot player (https://potplayer.daum.net).
This app can watch TV using tuner as well as play video files.

After searching channels with this app, I can check channel information(name, frequency, etc.) it has found.

like that...

Please see attachment.

I tried this frequency out for NextPVR to find channels.
Luckily, NextPVR found channels. But some channels not found.

[mvallevand]

I thought WinTV used the tuning files too, but maybe it is in their database. Except for your ATSC 3.0 channels South Korea should use North American ATSC 1.0 standards. For the missing channels you will probably need to download another program by sub, the author of NextPVR called TSCapture https://www.tscapture.com/ and provide a full mux recording via an external link to Google Drive, OneDrive type of storage. The file will be fairly large.

Martin

[sub]

There are three commas. What does each part mean?

1=what, what, what
2=what, what, what (, might be more..?)

1=x,0,0

x is either a physical channel number (for standard US rf frequencies), or if it's a big number then it's treated as a frequency.

Those last two numbers are ignored - just leave them set to zero.

[daymoon]

I tried this tuning file for ATSC.
Only 169250 frequency was not found.
However, other frequencies could be found.



Is there any way to solve this problem?

Meanwhile, ClearQAM is even more worse.
Depending on the frequencies ordering in ini file, NextPVR could find channels or not.

When the frequency 637250 is assigned to 4, NextPVR can't find any channels.



But, if the frequency 637250 is assigned to 1, NextPVR can find only that channel.
Any other channels can't be found.



It's a very strange thing...
I think... chances are NextPVR would have some bugs of finding channels.

I look forward to solving this problem.

[mvallevand]

There are tuning questions and also detection of channels in the stream post tuning. We need logs and the full mux capture to help you. Tuning will be the same in WinTV

Martin

[sub]

You're probably the only user we've ever had from Korea. If you can find a way to capture and supply a sample full transport stream (captured from some other application), I can take a look at it. Otherwise there isn't much to go on.

[daymoon]

Here are my log file and capture file.

My capture file is too big to upload.
So I use temporary file service.
This file will be deleted in two weeks.

https://file.io/FzhdSYEk4CcE

If you can't download this file, I'll upload again.

Using TSCapture, I recorded the capture files.
This program can only capture what it can find.
I'm sorry not to capture ATSC 169250 frequency and unsearchable ClearQAM frequencies.

capture.ts is from 577250 ATSC frequency.
capture1.ts is from 637250 ClearQAM frequency.

[sub]

capture.ts is from 577250 ATSC frequency.
capture1.ts is from 637250 ClearQAM frequency.

Can you summarize what NextPVR getting wrong on these two frequencies? From the screenshots above, it looks like a couple of the channel names which should have Korean characters are using the wrong character set. Is there other specific problems with these frequencies?

I'm sorry not to capture ATSC 169250 frequency and unsearchable ClearQAM frequencies.

You might have to try finding another application that is able to capture from this frequency. With an example full transport stream, I'm able to try replicating it here.