Muxdump

Creating and sharing a Muxdump will allow the developers to test for issues using the same raw TS data that you feed into TVHeadend.

This can be useful for testing e.g. odd codecs, or other oddities in the streams.

Each Muxdump can be plumbed into TVHeadend, almost as if it was a tuner card, allowing the developers to experiment with various TVHeadend settings etc.

How to create a Muxdump

1. Start by tracking down the Service that matches that channel you are having issues with.
   1. We need to record the from the Service URL, and NOT record from the Channel URL.
   2. Trace the Channel from the Channels tab to the Services tab, using the "Services" field.
   3. Right Click the Play Icon on the service tab, and choose Copy URL / Copy Address to Clipboard / etc.
   4. If the URL does not contain "play/stream/service", it's not the correct URL.
2. Now, record 30 seconds of raw Mux data. Doing this on your TVHeadend server though SSH is likely the simplest.

• curl -m30 --user "Username:Password" "http://XXXXXXXX:9981/play/stream/service/5478eff9f241326841ec0aeef1f49ef9?title=10818V%20%2F%20DVB-S%20Network" > sample.ts
• Be sure to include the trailing > sample.ts - which will cause Curl to save the data to a file, rather than spew it onto your SSH session.
• Be sure to surround the URL and User:Pass with double quotes ("), Bash will treat some of the characters in the URL as special and won't do what you expect.
• If a channel issue takes some time to appear, e.g. say it takes 10-15 minutes of watching a channel to appear, then you'll need to change the -m30 to however many seconds it will take to reproduce the issue. This will result in larger filesizes, but may be necessary.

3. Check the file is sane

• file sample.ts should tell you the file is "data". If it says anything else, the URL, username/password, or similar is wrong.
• du -h sample.ts should tell you the size of the file, 30 seconds on DVB-S SD mux results in about 100MB of data, if this file is tiny (less than 20MB), it's certainly not recorded correctly.
• Optional: Use ffprobe (part of the FFMpeg suite of tools) to check the streams included: ffprobe sample.ts (Ignoring all the errors, these are usually expected. Lots of output will be included, but you should see channel names (often more than 1), and video, audio, subtitle and other misc streams for each.

4. GZip the file to make it easier to share

• This will barely make a difference to the filesize, but ensures the file is in a known format for filesharing services.
• gzip -9 sample.ts

5. Finally, download the sample.ts.gz file from your server and share:

• This depends on how and where your running all these commands.
• One option is SCP - Google for "Mac SCP" / "Windows SCP" etc for tools to connect to your TVheadend server over SSH to copy the file.
• Upload this file to a filesharing service. e.g. Dropbox, OneDrive etc and provide the developers with the address to download

When sharing the file, plus include the name of the channel showing the issue, what device you tested with, what version of Android it's running, what version of TVHeadend you're running, a description of the issue, and any other details that may be relevant!