Testing your DVB device - Revision history

CityK: /* Using dvb-apps */ minor edits

2012-09-09T20:05:10Z

Using dvb-apps: minor edits

← Older revision		Revision as of 20:05, 9 September 2012
Line 82:		Line 82:
	For example, while keeping ''{a,c,s,t}''zap running in the first console shell, open up another console and run		For example, while keeping ''{a,c,s,t}''zap running in the first console shell, open up another console and run
	mplayer /dev/dvb/adapter0/dvr0 <options>		mplayer /dev/dvb/adapter0/dvr0 <options>
-	If you have more than one dvb device installed in your system, then you will have to pass the correct ''adaptor'' number. See the ~~mplayer~~ man page (i.e. in a console run "man mplayer") for a lengthy list of options.	+	If you have more than one dvb device installed in your system, then you will have to pass the correct ''adaptor'' number. See the [[MPlayer#Usage_with_more_complex_DVB_device_configurations\|MPlayer article]] for some further information, as well as the MPlayer man page (i.e. in a console run "man mplayer") for a lengthy list of options.

Wirbel: fix link to szap-s2

2012-01-16T15:21:36Z

fix link to szap-s2

← Older revision		Revision as of 15:21, 16 January 2012
Line 15:		Line 15:
	\|'''feature \ utility'''		\|'''feature \ utility'''
	\|'''dvb-apps [[zap]]'''		\|'''dvb-apps [[zap]]'''
-	\|'''[[~~szap~~-S2]]'''	+	\|'''[[Szap-s2]]'''
	\|'''[[dvbtune]]''' and '''[[dvbstream]]''' from dvbtools		\|'''[[dvbtune]]''' and '''[[dvbstream]]''' from dvbtools
	\|'''[[dvbsnoop]]'''		\|'''[[dvbsnoop]]'''

Wirbel: add comparison

2012-01-15T16:33:51Z

add comparison

← Older revision		Revision as of 16:33, 15 January 2012
Line 5:		Line 5:
	:* installed the drivers for your hardware and have the proper modules loaded (see "[[How to Obtain, Build and Install V4L-DVB Device Drivers]]" for such details)<br>		:* installed the drivers for your hardware and have the proper modules loaded (see "[[How to Obtain, Build and Install V4L-DVB Device Drivers]]" for such details)<br>
	:Having completed such tasks, you should at least now have a ''/dev/dvb/adapter0/'' directory. (If you have additional DVB devices installed in your system, they will be assigned an increased ''adapter'' number accordingly).}}<br>		:Having completed such tasks, you should at least now have a ''/dev/dvb/adapter0/'' directory. (If you have additional DVB devices installed in your system, they will be assigned an increased ''adapter'' number accordingly).}}<br>
		+
		+	== Comparison of DTV testing applications ==
		+
		+	The following table lists the main features of the different command line DTV testing utilities. For specific information on usage, have a look at its specific wiki article.
		+	<br>
		+
		+	{\| border=1 cellpadding=10 cellspacing=0 valign="top"
		+	\|- bgcolor=#efefef valign="top"
		+	\|'''feature \ utility'''
		+	\|'''dvb-apps [[zap]]'''
		+	\|'''[[szap-S2]]'''
		+	\|'''[[dvbtune]]''' and '''[[dvbstream]]''' from dvbtools
		+	\|'''[[dvbsnoop]]'''
		+	\|-
		+	\|'''download'''
		+	\|[http://linuxtv.org/hg/dvb-apps linuxtv.org/hg/dvb-apps]
		+	\|[http://mercurial.intuxication.org/hg/szap-s2 http://mercurial.intuxication.org/hg/szap-s2]
		+	\|[http://sourceforge.net/projects/dvbtools http://sourceforge.net/projects/dvbtools]
		+	\|[http://dvbsnoop.sourceforge.net http://dvbsnoop.sourceforge.net]
		+	\|-
		+	\|'''supported delivery systems'''
		+	\|DVB-S, DVB-C, DVB-T, ATSC
		+	\|DVB-S, DVB-S2
		+	\|DVB-S, DVB-C, DVB-T
		+	\|DVB-S, DVB-C, DVB-T
		+	\|-
		+	\|'''comments'''
		+	\|useful for debugging, but inappropriate for newer delivery systems.
		+	\|satellite only.
		+	\|outdated.
		+	\|outdated, but still the most powerful tool for reading and parsing DVB tables. Hint: use another tool to tune and dvbsnoop in parallel to read data. Unfortunally, dvbsnoop misses support for newer descriptors.
		+	\|-
		+	\|'''supported features'''
		+	\|
		+	* channel scan for legacy systems
		+	* tuning
		+	* streaming
		+	* show signal strength/lock
		+	\|
		+	* tuning
		+	\|
		+	* tuning (dvbtune)
		+	* streaming (dvbstream)
		+	\|
		+	* analyse DVB tables and MPEG streams
		+	* show signal strength/lock
		+	\|}
		+
		+

	== Using dvb-apps ==		== Using dvb-apps ==

Ulfschaper at 15:01, 4 December 2010

2010-12-04T15:01:24Z

← Older revision		Revision as of 15:01, 4 December 2010
Line 22:		Line 22:
	$ /usr/bin/''{a,c,s,t}''zap -r -c ~/.''{a,c,s,t}''zap/channels.conf "''channel name''"		$ /usr/bin/''{a,c,s,t}''zap -r -c ~/.''{a,c,s,t}''zap/channels.conf "''channel name''"
	where, respective to the type of transmission, [[azap]] is used for [[ATSC]], [[czap]] for [[DVB-C]], [[szap]] for [[DVB-S]] and [[tzap]] for [[DVB-T]].		where, respective to the type of transmission, [[azap]] is used for [[ATSC]], [[czap]] for [[DVB-C]], [[szap]] for [[DVB-S]] and [[tzap]] for [[DVB-T]].
		+	Make sure you do not overlook the -r option for setting up the /dev/dvb/adapterX/dvr0 interface. Otherwise, you cannot record data from dvr0.

	{{Note\|If (dvb)scan was unable to correctly resolve the audio or video [[PID]] values for a channel in the previous step, a manual adjustment to the channels.conf file will be necessary to correct any inaccurately written PID(s) information. Such occurrences tend to be rare, but nonetheless, they do happen -- often, one only becomes aware of a problem with the PID values after unsuccessful attempts to tune a particular channel. The correct values may be determined using using [[dvbtraffic]] (see step '''4.c)''' below). Another method for finding correct PID values for a channel is also outlined in the section entitled "[[Scan#A_word_about_dvbscan_and_audio_streams\|A word about dvbscan and audio streams]]".}}		{{Note\|If (dvb)scan was unable to correctly resolve the audio or video [[PID]] values for a channel in the previous step, a manual adjustment to the channels.conf file will be necessary to correct any inaccurately written PID(s) information. Such occurrences tend to be rare, but nonetheless, they do happen -- often, one only becomes aware of a problem with the PID values after unsuccessful attempts to tune a particular channel. The correct values may be determined using using [[dvbtraffic]] (see step '''4.c)''' below). Another method for finding correct PID values for a channel is also outlined in the section entitled "[[Scan#A_word_about_dvbscan_and_audio_streams\|A word about dvbscan and audio streams]]".}}

CityK: fix link

2010-10-21T03:35:01Z

fix link

← Older revision		Revision as of 03:35, 21 October 2010
Line 127:		Line 127:

	For some further inspiration on what's possible with more advanced software usage see:		For some further inspiration on what's possible with more advanced software usage see:
-	* the [[~~Commented software list~~]] and	+	* the [[TV Related Software]] page, a commented software list, and
	* [[Example setups]]		* [[Example setups]]

CityK: get rid of double properly; minor edits

2009-09-07T04:52:44Z

get rid of double properly; minor edits

← Older revision		Revision as of 04:52, 7 September 2009
Line 1:		Line 1:
-	This page provides a few suggestions on how to test that a properly installed DVB device <sup>'''1'''</sup> is functioning ~~properly~~. The command line steps described are also indispensable for quick setup and no frills viewing with DVB hardware under Linux.	+	This page provides a few suggestions on how to test that a properly installed DVB device <sup>'''1'''</sup> is functioning correctly. The command line steps described are also indispensable for quick setup and no frills viewing with DVB hardware under Linux.

	{{Note\|<sup>'''1'''</sup> In other words, this article assumes that you have already both:		{{Note\|<sup>'''1'''</sup> In other words, this article assumes that you have already both:
Line 69:		Line 69:
	-PID--FREQ-----BANDWIDTH-BANDWIDTH-		-PID--FREQ-----BANDWIDTH-BANDWIDTH-

-	~~The above output is from tuning to an HDTV channel.~~ In this ~~example~~ PID 0x0200 is for the video stream and PID 0x028b is for the audio stream.	+	In this case, for the frequency that has been tuned, PID 0x0200 is for the video stream of an HDTV channel and PID 0x028b is for the associated audio stream (both of these have been highlighted in red in the above output for easier visual identification). These PID values presented by dvbtraffuc are in hexadecimal form and need to be converted to their decimal representation (respectively, 512 and 651) for use in a channel.conf file.<BR>
-	These values are in hexadecimal and need ~~conversion~~ to decimal (~~resulting in~~ 512 and 651 ~~respectively~~) for use in ~~the~~ channel.conf file.<BR>	+

	This is the line you would create in the file "channel.conf" given the PID values from the dvbtraffic output shown above:		This is the line you would create in the file "channel.conf" given the PID values from the dvbtraffic output shown above:

-	Nine High Def Gold Coast:746625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_3_4:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:512:651:1138	+	Nine High Def Gold Coast:746625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_3_4:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:<span style="color:#ff0000">512</span>:<span style="color:#ff0000">651</span>:1138

	And finally		And finally

CityK: /* Using dvb-apps */ add link; add colour highlight

2009-09-07T04:38:08Z

Using dvb-apps: add link; add colour highlight

← Older revision		Revision as of 04:38, 7 September 2009
Line 42:		Line 42:
	$ /usr/bin/dvbtraffic		$ /usr/bin/dvbtraffic

-	dvbtraffic which will access the /dev/dvb/adapter0/dvr0 device.	+	dvbtraffic which will access the [[Device nodes and character devices#DVB character devices\|/dev/dvb/adapter0/dvr0 logical device]].
	An example of output from dvbtraffic is:		An example of output from dvbtraffic is:

Line 56:		Line 56:
	0101 25 p/s 4 kb/s 38 kbit		0101 25 p/s 4 kb/s 38 kbit
	0102 24 p/s 4 kb/s 37 kbit		0102 24 p/s 4 kb/s 37 kbit
-	0200 8567 p/s 1572 kb/s 12885 kbit	+	<span style="color:#ff0000">0200</span> 8567 p/s 1572 kb/s 12885 kbit <span style="color:#ff0000"> <--- </span>
	0201 4708 p/s 864 kb/s 7081 kbit		0201 4708 p/s 864 kb/s 7081 kbit
	0205 926 p/s 170 kb/s 1392 kbit		0205 926 p/s 170 kb/s 1392 kbit
	0240 49 p/s 8 kb/s 75 kbit		0240 49 p/s 8 kb/s 75 kbit
	0241 49 p/s 8 kb/s 75 kbit		0241 49 p/s 8 kb/s 75 kbit
-	028b 261 p/s 47 kb/s 393 kbit	+	<span style="color:#ff0000">028b</span> 261 p/s 47 kb/s 393 kbit <span style="color:#ff0000"> <--- </span>
	0294 174 p/s 31 kb/s 262 kbit		0294 174 p/s 31 kb/s 262 kbit
	0295 130 p/s 23 kb/s 196 kbit		0295 130 p/s 23 kb/s 196 kbit

Devin.heitmueller: djh - clarifying text. PLEASE DO NOT markup the text when you do not understand something. That is what the "Talk" section is for, or send a question to the linux-media mailing list.

2009-09-04T13:46:30Z

djh - clarifying text. PLEASE DO NOT markup the text when you do not understand something. That is what the "Talk" section is for, or send a question to the linux-media mailing list.

← Older revision		Revision as of 13:46, 4 September 2009
Line 69:		Line 69:
	-PID--FREQ-----BANDWIDTH-BANDWIDTH-		-PID--FREQ-----BANDWIDTH-BANDWIDTH-

-	~~THE FOLLOWING SECTION DOES NOT MAKE SENSE -- CLARIFICATION PLEASE~~	+	The above output is from tuning to an HDTV channel. In this example PID 0x0200 is for the video stream and PID 0x028b is for the audio stream.
		+	These values are in hexadecimal and need conversion to decimal (resulting in 512 and 651 respectively) for use in the channel.conf file.<BR>

-	This ~~output~~ is ~~for a HDTV channel. In this example PID 200 is video 28b is audio.~~	+	This is the line you would create in the file "channel.conf" given the PID values from the dvbtraffic output shown above:
-	~~These values are~~ in ~~hex and need conversion to decimal(512,651) for use channel.conf.<BR>~~	+
-	~~This is~~ the ~~record in~~ channel.conf ~~using~~ the PID values from dvbtraffic:	+

	Nine High Def Gold Coast:746625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_3_4:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:512:651:1138		Nine High Def Gold Coast:746625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_3_4:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:512:651:1138

Fermulator: Added clarification request

2009-09-03T23:41:28Z

Added clarification request

← Older revision		Revision as of 23:41, 3 September 2009
Line 68:		Line 68:
	2000 15329 p/s 2814 kb/s 23055 kbit		2000 15329 p/s 2814 kb/s 23055 kbit
	-PID--FREQ-----BANDWIDTH-BANDWIDTH-		-PID--FREQ-----BANDWIDTH-BANDWIDTH-
		+
		+	THE FOLLOWING SECTION DOES NOT MAKE SENSE -- CLARIFICATION PLEASE

	This output is for a HDTV channel. In this example PID 200 is video 28b is audio.		This output is for a HDTV channel. In this example PID 200 is video 28b is audio.

Kens: frequency typo

2009-06-15T21:55:27Z

frequency typo

← Older revision		Revision as of 21:55, 15 June 2009
Line 18:		Line 18:
	Note that you may have both a program <code>scan</code> and <code>dvbscan</code> installed on your system, and only one of them may work.		Note that you may have both a program <code>scan</code> and <code>dvbscan</code> installed on your system, and only one of them may work.

-	'''3. Tune a ~~frequncy~~ and program'''<BR>	+	'''3. Tune a frequency and program'''<BR>
	Refer to the [[Zap\|zap]] article for details of how to perform this step. Once familiar with the content of that article, you will recognize that this step can be summarized (in general form) by:		Refer to the [[Zap\|zap]] article for details of how to perform this step. Once familiar with the content of that article, you will recognize that this step can be summarized (in general form) by:
	$ /usr/bin/''{a,c,s,t}''zap -r -c ~/.''{a,c,s,t}''zap/channels.conf "''channel name''"		$ /usr/bin/''{a,c,s,t}''zap -r -c ~/.''{a,c,s,t}''zap/channels.conf "''channel name''"