Multi language Lineup.json

[emveepee]

First if this problem is due to using old firmware let me know.

A NextPVR user posted his lineup.json, is it supposed to contain mixed languages?

Code: Select all

    {
        "GuidaNumero": "71",
        "GuidaNome": "CANALE ITALIA e",
        "VideoCodec": "H264",
        "AudioCodec": "MPEG",
        "URL": "http://192.168.1.252:5004/auto/v71"
    },
    {
        "GuideNumber": "75",
        "GuideName": "TVP",
        "VideoCodec": "H264",
        "AudioCodec": "MPEG",
        "HD": 1,
        "URL": "http://192.168.1.252:5004/auto/v75"
    },

If so, is there an API call to normalize the JSON to English?

[nickk]

The field names are always GuideNumber and GuideName... they are not localized.

My guess is he opened lineup.json in a web browser that has a translation feature.

[emveepee]

Makes sense, thanks. Hard to explain curl to users.

Martin

[emveepee]

Rather than opening a new thread the user is asking if there is a limit of 15 characters to the DVB guide name in lineup.json.

"GuideName": "Radio Monte Car",

The full mux does have the full name.

It also got me looking for other things, his file had

"VideoCodec": "HEVC",

and I thought I recalled seeing ATSC 3 was.

"VideoCodec": "H265",

Martin

[jasonl]

There is a length limit in the firmware, not specifically the json.

ATSC 3.0 channels have "HEVC" in the json.

[nickk]

The ATSC 1.0 broadcast is is limited to 7 characters of UTF-16.
I would need to check for DVB-T/T2.
The firmware stores channel names as UTF8, max 15 characters.

[emveepee]

ATSC 3.0 channels have "HEVC" in the json.

Thanks I was using this example https://emby.media/community/index.php? ... 39235_menu (not being in the US) so it must have changed at one point. To be fair audio was None in those early days.

Martin