Project

General

Profile

Bug #5684

Tvheadend does not detect AC3+ audio track

Added by Vlad Lanetz over 5 years ago. Updated about 5 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
General
Target version:
-
Start date:
2019-07-12
Due date:
% Done:

0%

Estimated time:
Found in version:
HTS Tvheadend 4.3-1789
Affected Versions:

Description

Recently on 13E, on FTA music channels 4Fun added AC3+ audio track. Tvheadend cuts it for unknown reasons, although it is there for sure.


Files

1.png (22.4 KB) 1.png flysat Vlad Lanetz, 2019-07-12 14:29
2.png (7.93 KB) 2.png tvheadend Vlad Lanetz, 2019-07-12 14:29
tvh2.log (66.2 KB) tvh2.log Vlad Lanetz, 2019-07-15 05:54
C+4k_UHD.log (6.37 KB) C+4k_UHD.log Rafal N, 2019-07-15 07:29
A52-201212-17.pdf (1.69 MB) A52-201212-17.pdf Rafal N, 2019-07-15 08:54
Service_detail.png (39.3 KB) Service_detail.png Rafal N, 2019-07-15 15:31

History

#1

Updated by Rafal N over 5 years ago

I have the same problem. Tvheadend does not detect the e-ac3 audio track on Canal + 4k UHD
I was building Tvheadend 4.3 on the latest commit - 6be300c

See attached samples https://mega.nz/#F!qREGWALD!UE7Dsn4EyXse1KgQVe3oig

#2

Updated by Pablo R. over 5 years ago

--trace mpegts,tbl-base,parser ; tune to the problematic service (https://tvheadend.org/projects/tvheadend/wiki/Traces) and show logs.

#3

Updated by Vlad Lanetz over 5 years ago

#4

Updated by Rafal N over 5 years ago

See my log's from C+ 4k

#5

Updated by Pablo R. over 5 years ago

2019-07-15 09:16:51.768 tbl-base: pmt:  pid 0101 estype 135
                                                 ^^^^^^^^^^

2019-07-15 08:52:52.972 [  DEBUG]:tbl-base: pmt:  pid 0309 estype 135
                                                           ^^^^^^^^^^

This is the problematic audio (estype 135) and it is not being processed by '(E)AC3 audio parser functions'.

#6

Updated by Vlad Lanetz over 5 years ago

Is it possible to fix it?

#7

Updated by Rafal N over 5 years ago

Mister Pablo R - See attachement documentation about (E)ac3 standards.

In this document, search for "Stream type" value - all are listed. If I see it well, "estype 135" is on page 259 (...)3.1 Stream Type
E-AC-3 bit streams shall be identified with a stream_type value of 0x87 when transmitted as PES
streams conforming to ATSC-published standards.(...)

But (E) Ac3 also uses other IDs so the file ""/src/parsers/parsers.c" need to be fix.

Regards

#8

Updated by Pablo R. over 5 years ago

Vlad Lanetz wrote:

Is it possible to fix it?

It should, but I'm not a programmer :(

#9

Updated by Rafal N over 5 years ago

Yes of course.
I do not understand how the current 'parsers' work so we have to wait.
But I see this is probably nothing difficult.

#10

Updated by Jaroslav Kysela over 5 years ago

  • Subject changed from Tvheadend deletes AC3+ audio track to Tvheadend does not detect AC3+ audio track
#11

Updated by Jaroslav Kysela over 5 years ago

Try to add this code bellow https://github.com/tvheadend/tvheadend/blob/master/src/input/mpegts/dvb_psi_pmt.c#L363 :

  case 0x87:
    hts_stream_type = SCT_EAC3;
    break; 
#12

Updated by Rafal N over 5 years ago

Now it's OK.
Thanks for the quick help.

#13

Updated by Rafal N over 5 years ago

@ Jaroslav Kysela - Will you also add other "Stream type" values from the documentation of the (E) AC3 standard?
For example, (page 259): 0xBD (indicating private_stream_1)

Regards
Rafal

#14

Updated by Vlad Lanetz over 5 years ago

Thanks Jaroslav. Is it possible to fix the Dolby E?
https://www.tvheadend.org/issues/5631

#15

Updated by Pablo R. over 5 years ago

Jaroslav Kysela wrote:

Try to add this code bellow https://github.com/tvheadend/tvheadend/blob/master/src/input/mpegts/dvb_psi_pmt.c#L363 :

[...]

Could it be pushed to master?

#16

Updated by Rafal N over 5 years ago

You can add to master
This fix works well.

#17

Updated by Rafal N over 5 years ago

I've created pull requests https://github.com/tvheadend/tvheadend/pulls
I checked everything and it works well.
Thanks for the help.

Jaroslav if you can, please confirm fixes and close this issue.

#18

Updated by Pablo R. about 5 years ago

Any update here?

#19

Updated by Pablo R. about 5 years ago

Fixed on 7f090c9829a98427692e06a907c3197ea7230071

#20

Updated by Pablo R. about 5 years ago

Up! That is already fixed

#21

Updated by Jaroslav Kysela about 5 years ago

  • Status changed from New to Fixed

Also available in: Atom PDF