Project

General

Profile

Bug #2897

pipe:// mux generates two services

Added by Hanspeter Müller over 9 years ago. Updated over 9 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
DVB
Target version:
-
Start date:
2015-05-27
Due date:
% Done:

100%

Estimated time:
Found in version:
4.1-75
Affected Versions:

Description

All my pipe:// muxes started (can't exactly tell when, the problem wasn't there in the beginning) to generate two services.

If i'm adding a mux with Mux&Service Name set to "ABC", i'm getting in the Services Tab with the Name CW and Service ID 10929 (the same ID on all my channels, using the same avconv build from ubuntu-trusty), this Service is not working. The second Service has the Name "Service01" (which seems to be the default from avconv) and Service ID 1, this one is working fine.

https://tvheadend.org/boards/5/topics/15853?r=16339#message-16339 at least confirmed the behavior, András is also using avconv.

As i didn't knowingly update the avconv, but maybe ubuntu did, i'm not sure if this is a bug in tvheadend, one in avconv or just a missing parameter. I at least tried settings -metadata service_id=1 in my script, but it didn't change anything...

History

#1

Updated by Hanspeter Müller over 9 years ago

Update (is there really no way to edit my own posting?):

Andreas is using ffmpeg; so i would guess it's not a bug in avconv, would be a real big coincidence if ffmpeg added the same bug at the same time ;)

#2

Updated by Jaroslav Kysela over 9 years ago

  • Status changed from New to Fixed
  • % Done changed from 0 to 100

Applied in changeset commit:tvheadend|b5f23b3e1bd61ac35efdd22a7ea66292474c03d9.

#3

Updated by Jaroslav Kysela over 9 years ago

  • Status changed from Fixed to New
  • % Done changed from 100 to 0

Could you retest with v4.1-78-gb5f23b3 ?

#4

Updated by Jaroslav Kysela over 9 years ago

  • Status changed from New to Accepted
#5

Updated by Jaroslav Kysela over 9 years ago

  • Category changed from Service Mapping to DVB
#6

Updated by Hanspeter Müller over 9 years ago

Damn, you're fast :D

Yes, i can confirm it's fixed, thank you very much, another bug squashed :)

#7

Updated by Jaroslav Kysela over 9 years ago

  • Status changed from Accepted to Fixed
  • % Done changed from 0 to 100

Applied in changeset commit:tvheadend|10d3dc51479f866e1fd5258e24516a85602af0be.

Also available in: Atom PDF