Faq » History » Version 9
Adam Sutton, 2013-04-05 12:10
1 | 1 | Andreas Smas | h1. FAQ |
---|---|---|---|
2 | |||
3 | 2 | Andreas Smas | h2. General |
4 | 1 | Andreas Smas | |
5 | 2 | Andreas Smas | h3. How do I interact with Tvheadend? |
6 | |||
7 | 1 | Andreas Smas | Tvheadend is controlled via a web user interface that runs on an internal HTTP server within Tvheadend. By default the HTTP server listens to port 9981. So if you have installed Tvheadend on your machine you can access the user interface by pointing your browser to http://localhost:9981. |
8 | |||
9 | 2 | Andreas Smas | h3. Help! I can’t login to the web user interface. |
10 | 1 | Andreas Smas | |
11 | 9 | Adam Sutton | If you build Tvheadend from source and just execute it, it won’t let anyone in. The rationale behind this is that we think it is bad to have services running with wide open administrative access. |
12 | 1 | Andreas Smas | |
13 | If you start Tvheadend with the ‘-C’ argument. A default user with no user-name or password will be created. Make sure that you later edit this via the Configuration / Access control tab in the web ui. |
||
14 | |||
15 | 9 | Adam Sutton | If you start Tvheadedn with the '--noacl' argument, all Access Control will be removed and you can setup required users via Configuration / Access control tab. |
16 | |||
17 | 1 | Andreas Smas | If you installed the Tvheadend debian package you should have been asked for a superuser username + password during the install. This super user account can not be modified from within Tvheadend itself. If you want to change it, you need to reconfigure the Debian package. To do that, execute the following line in a command prompt: |
18 | |||
19 | 8 | Adam Sutton | sudo dpkg-reconfigure tvheadend |
20 | 2 | Andreas Smas | |
21 | 1 | Andreas Smas | h3. Why does HTSP use TCP? I thought it was bad to use TCP for realtime sensitive traffic? |
22 | |||
23 | 9 | Adam Sutton | [[HTSP]] – (Home Tv Streaming Protocol), the protocol used for streaming TV, sending meta information updates and RPC between Tvheadend and a HTSP client uses a transmission scheduler with multiple queues on the Tvheadend side. This means that Tvheadend can measure the available bandwidth between itself and the media player and when congestion happens it’s even capable of dropping less important data (such as B-frames). HTSP has been tested over WAN links and DSL connections with no video or audio artefacts. |
24 | 5 | Adam Sutton | |
25 | 1 | Andreas Smas | h2. Video recorder (DVR / PVR) |
26 | 2 | Andreas Smas | |
27 | h3. Sometime it's called "DVR":http://en.wikipedia.org/wiki/Digital_video_recorder and sometimes PVR, why? |
||
28 | 3 | Andreas Smas | |
29 | 2 | Andreas Smas | It's really the same thing I just seem to never be able to decide which one of the abbreviations to use. Sorry for the confusion. |
30 | |||
31 | h3. I try to transcode the video with FFmpeg but it fails for HD content. |
||
32 | 3 | Andreas Smas | |
33 | 2 | Andreas Smas | The problem is this: |
34 | |||
35 | * Matroska (.mkv files) does not include a DTS (Decoding Time Stamp) for each frame (or packet) |
||
36 | |||
37 | * ffmpeg needs a DTS for each packet when remultiplexing video. If a DTS is not available it will try to make one up which it fails to do when the video content is h264. (ie HD video) |
||
38 | |||
39 | 9 | Adam Sutton | h2. I think I found a bug |
40 | 1 | Andreas Smas | |
41 | 7 | Adam Sutton | Please check details [[Bugreporting|here]]. |