VLC HowTo/Stream to a website - Revision history

DoesItReallyMatter: DoesItReallyMatter moved page Stream VLC to Website with asf and Flash to VLC HowTo/Stream to a website: Renaming how-to articles per Talk:VLC HowTo (permalink)

2016-11-07T10:03:06Z

DoesItReallyMatter moved page Stream VLC to Website with asf and Flash to VLC HowTo/Stream to a website: Renaming how-to articles per Talk:VLC HowTo (permalink)

← Older revision	Revision as of 10:03, 7 November 2016
(No difference)

DoesItReallyMatter: add Template:Howto for consistency, remove sortkey

2016-11-07T10:01:57Z

add Template:Howto for consistency, remove sortkey

← Older revision		Revision as of 10:01, 7 November 2016
Line 1:		Line 1:
			{{Howto\|stream VLC to a website with .asf and Flash}}
	<!-- this is not needed, this is the title: '''Stream VLC to Website with .asf and Flash''' -->		<!-- this is not needed, this is the title: '''Stream VLC to Website with .asf and Flash''' -->

Line 254:		Line 255:

	vlc dshow:// :dshow-vdev="Conexant's BtPCI Capture" :dshow-adev="Aureon 5.1 Fun Wave" :dshow-size="256x192" --sout="#transcode{vcodec=h264,vb=200,deinterlace,fps=25,width=256,height=192,ab=32,acodec=mp3,samplerate=44100}:duplicate{dst=std{access=http{mime=video/x-flv},mux=ffmpeg{mux=flv},dst=/mediaplayer/stream.flv},dst=display}"		vlc dshow:// :dshow-vdev="Conexant's BtPCI Capture" :dshow-adev="Aureon 5.1 Fun Wave" :dshow-size="256x192" --sout="#transcode{vcodec=h264,vb=200,deinterlace,fps=25,width=256,height=192,ab=32,acodec=mp3,samplerate=44100}:duplicate{dst=std{access=http{mime=video/x-flv},mux=ffmpeg{mux=flv},dst=/mediaplayer/stream.flv},dst=display}"


	~~[[Category:How To]]~~

	~~{{DEFAULTSORT:Stream}}~~

DoesItReallyMatter: Sortkey: Stream

2016-10-30T05:29:44Z

Sortkey: Stream

← Older revision		Revision as of 05:29, 30 October 2016
Line 257:		Line 257:

	[[Category:How To]]		[[Category:How To]]

			{{DEFAULTSORT:Stream}}

J-b at 20:35, 1 October 2013

2013-10-01T20:35:21Z

← Older revision		Revision as of 20:35, 1 October 2013
Line 254:		Line 254:

	vlc dshow:// :dshow-vdev="Conexant's BtPCI Capture" :dshow-adev="Aureon 5.1 Fun Wave" :dshow-size="256x192" --sout="#transcode{vcodec=h264,vb=200,deinterlace,fps=25,width=256,height=192,ab=32,acodec=mp3,samplerate=44100}:duplicate{dst=std{access=http{mime=video/x-flv},mux=ffmpeg{mux=flv},dst=/mediaplayer/stream.flv},dst=display}"		vlc dshow:// :dshow-vdev="Conexant's BtPCI Capture" :dshow-adev="Aureon 5.1 Fun Wave" :dshow-size="256x192" --sout="#transcode{vcodec=h264,vb=200,deinterlace,fps=25,width=256,height=192,ab=32,acodec=mp3,samplerate=44100}:duplicate{dst=std{access=http{mime=video/x-flv},mux=ffmpeg{mux=flv},dst=/mediaplayer/stream.flv},dst=display}"


			[[Category:How To]]

Courmisch at 11:07, 24 September 2011

2011-09-24T11:07:49Z

← Older revision		Revision as of 11:07, 24 September 2011
Line 80:		Line 80:
	Box 1 Set up:		Box 1 Set up:
	Select “Streaming” set up your capture devices and set the video size to 256x192		Select “Streaming” set up your capture devices and set the video size to 256x192
	Simply using the default values in the GUI, select “Stream”, then “Next” at source, at “Destinations” check the box “display locally” <optional> , select HTTP from the dropdown box, and click the “Add” button, leave the address field as 0.0.0.0 and change the port number to ~~8082~~. Activate transcoding box is checked, select the Windows WMV/asf Transcoding profile and click “next” again. You should now see the “Generated stream output string”. This is where we will make the changes and additions.		Simply using the default values in the GUI, select “Stream”, then “Next” at source, at “Destinations” check the box “display locally” <optional> , select HTTP from the dropdown box, and click the “Add” button, leave the address field as 0.0.0.0 and change the port number to 8080. Activate transcoding box is checked, select the Windows WMV/asf Transcoding profile and click “next” again. You should now see the “Generated stream output string”. This is where we will make the changes and additions.
	So. Look at what is in this field and compare with the example below. Then modify the output string with the changes listed below. Or clear the output field and copy and paste.		So. Look at what is in this field and compare with the example below. Then modify the output string with the changes listed below. Or clear the output field and copy and paste.

	First output string (box 1)		First output string (box 1)

	:sout=#transcode{vcodec=WMV2,vb=400,fps=15,width=256,height=192,deinterlace,acodec=wma2,ab=64,channels=2,samplerate=44100}:duplicate{dst=std{access=http,mux=asf,dst=~~0.0.0.0:8081~~},dst=display}		:sout=#transcode{vcodec=WMV2,vb=400,fps=15,width=256,height=192,deinterlace,acodec=wma2,ab=64,channels=2,samplerate=44100}:duplicate{dst=std{access=http,mux=asf,dst=/},dst=display}


Line 103:		Line 103:
	Second output string (box 2)		Second output string (box 2)

	:sout=#transcode{vcodec=WMV2,vb=200,fps=15,scale=1,acodec=wma2,ab=32,channels=2}:duplicate{dst=display,dst=std{access=http,mux=asf,dst=~~0.0.0.0:8082~~}}		:sout=#transcode{vcodec=WMV2,vb=200,fps=15,scale=1,acodec=wma2,ab=32,channels=2}:duplicate{dst=display,dst=std{access=http,mux=asf,dst=/}}


Line 120:		Line 120:

	<ASX version ="3.0">		<ASX version ="3.0">
	<TITLE>~~extstream8082~~</TITLE>		<TITLE>extstream8080</TITLE>
	<ENTRY>		<ENTRY>
	<REF HREF="http://youripaddress:~~8082~~" />		<REF HREF="http://youripaddress:8080" />
	</ENTRY>		</ENTRY>
	</ASX>		</ASX>
Line 128:		Line 128:


	(saved as <~~extstream8082~~.asx>)		(saved as <extstream8080.asx>)


Line 147:		Line 147:
	<br>		<br>
	</big></big>		</big></big>
	<embed src="~~extstream8082~~.asx" height="450" width="512">		<embed src="extstream8080.asx" height="450" width="512">
	</body></html></nowiki>		</body></html></nowiki>

Line 180:		Line 180:
	First example string for Win XP (and ffmpeg-x264 enabled Linux) users		First example string for Win XP (and ffmpeg-x264 enabled Linux) users

	:sout=#transcode{vcodec=h264,vb=200,deinterlace,ab=32,fps=25,width=256,height=192,acodec=mp3,samplerate=44100}:duplicate{dst=std{access=http{mime=video/x-flv},mux=ffmpeg{mux=flv},dst=~~0.0.0.0:8081~~/mediaplayer/stream.flv},dst=display}		:sout=#transcode{vcodec=h264,vb=200,deinterlace,ab=32,fps=25,width=256,height=192,acodec=mp3,samplerate=44100}:duplicate{dst=std{access=http{mime=video/x-flv},mux=ffmpeg{mux=flv},dst=/mediaplayer/stream.flv},dst=display}


Line 186:		Line 186:
	Second example string for (stripped ffmpeg) Linux users		Second example string for (stripped ffmpeg) Linux users

	:sout=#transcode{vcodec=FLV1,acodec=mp3,vb=200,deinterlace,fps=25,samplerate=44100,ab=32}:duplicate{dst=std{access=http,mux=ffmpeg{mux=flv},dst=~~192.168.0.42:8081~~/stream.flv},dst=display}		:sout=#transcode{vcodec=FLV1,acodec=mp3,vb=200,deinterlace,fps=25,samplerate=44100,ab=32}:duplicate{dst=std{access=http,mux=ffmpeg{mux=flv},dst=/stream.flv},dst=display}


Line 195:		Line 195:

	You will probably want to check that everything is working at this stage. So point a VLC client at the stream to check it out.		You will probably want to check that everything is working at this stage. So point a VLC client at the stream to check it out.
	~~Do note the dst=xx.xx.xx.xx:port/path/stream.flv and check~~ out the “Troubleshooting” section		Check out the “Troubleshooting” section.
	.
	Next we will need a player to embed the stream into a web page. JWPlayer and Flowplayer are suitable for this purpose. Both of these players need a path to their java files.Eg. The Win XP example had /mediaplayer/ in the path This was the default folder for JWPlayer in that example. The Linux example assumed that the necessary java files placed in the root dir of the webserver and needed no path. These players are described in detail in the documentation on their websites. If you have not used these players before, take time to become familiar with them before using them in this context.		Next we will need a player to embed the stream into a web page. JWPlayer and Flowplayer are suitable for this purpose. Both of these players need a path to their java files.Eg. The Win XP example had /mediaplayer/ in the path This was the default folder for JWPlayer in that example. The Linux example assumed that the necessary java files placed in the root dir of the webserver and needed no path. These players are described in detail in the documentation on their websites. If you have not used these players before, take time to become familiar with them before using them in this context.

Line 226:		Line 226:
	Note		Note
	The href= value in this line would contain		The href= value in this line would contain
	"http://<yourIP>:~~8081~~/stream.flv"		"http://yourIP:8080/stream.flv"

	== Troubleshooting ==		== Troubleshooting ==

	OK so it all went wrong? And did not work. At the risk of stating the obvious? Backtrack. Check each stage step by step and prove that each bit is working before moving to the next. Common faults and checks are listed as follows:		OK so it all went wrong? And did not work. At the risk of stating the obvious? Backtrack. Check each stage step by step and prove that each bit is working before moving to the next. Common faults and checks are listed as follows:
	#1. The destination address dst=xx.xx.xx.xx can give rise to problems. I have found that Win XP works with dst=0.0.0.0 but some linux versions require the specific IP of the server Eg 192.168.0.42 or a qualified domain name Eg mywebsite.com.		#1. Many Linux distros may not include by default the full version of ffmpeg and h/x264 and associated libs for encoding. You may need to go research and install all necessary components to get it all working.

	#2. Many Linux distros may not include by default the full version of ffmpeg and h/x264 and associated libs for encoding. You may need to go research and install all necessary components to get it all working.

	#3. The quality of both video and sound can vary due to many factors, which may include the version of VLC, the OS platform, the version of players, plugins Etc. Problems such as stuttering, pixelation, excessive buffering delays are not uncommon. In general terms, keeping up to date with the latest versions of everything is good practice, however in some cases, a newer version may not work as well (if at all) as it’s predecessor.		#2. The quality of both video and sound can vary due to many factors, which may include the version of VLC, the OS platform, the version of players, plugins Etc. Problems such as stuttering, pixelation, excessive buffering delays are not uncommon. In general terms, keeping up to date with the latest versions of everything is good practice, however in some cases, a newer version may not work as well (if at all) as it’s predecessor.

	#4. Realtime streaming is cpu intensive and also sensitive to being interrupted in realtime. Other applications can and will interrupt. Shut down all unnecessary applications ( and the ones in background) Spikes of intensive cpu activity which will not always show up in Task Manager/System Monitor can and will cause problems with the quality of your stream output. You may wish to raise the priority of VLC to reduce the effect of interrupts.		#3. Realtime streaming is cpu intensive and also sensitive to being interrupted in realtime. Other applications can and will interrupt. Shut down all unnecessary applications ( and the ones in background) Spikes of intensive cpu activity which will not always show up in Task Manager/System Monitor can and will cause problems with the quality of your stream output. You may wish to raise the priority of VLC to reduce the effect of interrupts.

	#5 Clients need to be equipped with the necessary means to display your stream! Sounds an obvious statement? Probably not a problem if you have an up to date box, with MS Windows and a recent Flash plugin. I have encountered any number of problems with old hardware, other Operating Systems, browsers and Flash plugins. Don’t be surprised or disappointed at the apparent failure or erratic performance of your stream if you are testing it with a client that is not suitably equipped and able. Using Localhost to check out your stream may also give unexpected and misleading results.		#4. Clients need to be equipped with the necessary means to display your stream! Sounds an obvious statement? Probably not a problem if you have an up to date box, with MS Windows and a recent Flash plugin. I have encountered any number of problems with old hardware, other Operating Systems, browsers and Flash plugins. Don’t be surprised or disappointed at the apparent failure or erratic performance of your stream if you are testing it with a client that is not suitably equipped and able. Using Localhost to check out your stream may also give unexpected and misleading results.

	#6 The quality of the video input is also very important. Low quality webcams, camera and capture devices, noisy TV input devices will give even more disappointing results when transcoded.		#5. The quality of the video input is also very important. Low quality webcams, camera and capture devices, noisy TV input devices will give even more disappointing results when transcoded.

	== Notes ==		== Notes ==
Line 255:		Line 253:


	vlc dshow:// :dshow-vdev="Conexant's BtPCI Capture" :dshow-adev="Aureon 5.1 Fun Wave" :dshow-size="256x192" --sout="#transcode{vcodec=h264,vb=200,deinterlace,fps=25,width=256,height=192,ab=32,acodec=mp3,samplerate=44100}:duplicate{dst=std{access=http{mime=video/x-flv},mux=ffmpeg{mux=flv},dst=~~0.0.0.0:8081~~/mediaplayer/stream.flv},dst=display}"		vlc dshow:// :dshow-vdev="Conexant's BtPCI Capture" :dshow-adev="Aureon 5.1 Fun Wave" :dshow-size="256x192" --sout="#transcode{vcodec=h264,vb=200,deinterlace,fps=25,width=256,height=192,ab=32,acodec=mp3,samplerate=44100}:duplicate{dst=std{access=http{mime=video/x-flv},mux=ffmpeg{mux=flv},dst=/mediaplayer/stream.flv},dst=display}"

MrGreg: /* Method 1 wmv/div3 - asf */

2011-04-22T00:20:37Z

Method 1 wmv/div3 - asf

← Older revision		Revision as of 00:20, 22 April 2011
Line 103:		Line 103:
	Second output string (box 2)		Second output string (box 2)

	:sout=#transcode{vcodec=WMV2,vb=200,fps=15,scale=1,acodec=wma2,ab=32,channels=2}:duplicate{dst=display,dst=std{access=http,mux=asf,dst=0.0.0.0:8082}}		:sout=#transcode{vcodec=WMV2,vb=200,fps=15,scale=1,acodec=wma2,ab=32,channels=2}:duplicate{dst=display,dst=std{access=http,mux=asf,dst=0.0.0.0:8082}}

MrGreg: /* Troubleshooting */

2011-04-22T00:06:59Z

Troubleshooting

← Older revision		Revision as of 00:06, 22 April 2011
Line 231:		Line 231:

	OK so it all went wrong? And did not work. At the risk of stating the obvious? Backtrack. Check each stage step by step and prove that each bit is working before moving to the next. Common faults and checks are listed as follows:		OK so it all went wrong? And did not work. At the risk of stating the obvious? Backtrack. Check each stage step by step and prove that each bit is working before moving to the next. Common faults and checks are listed as follows:
	#1. The destination address dst=xx.xx.xx.xx can give rise to problems. I have found that Win XP works with ~~dts~~=0.0.0.0 but ~~Ubuntu~~ linux ~~requires~~ the specific IP of the server Eg 192.168.0.42 or a qualified domain name Eg mywebsite.com.		#1. The destination address dst=xx.xx.xx.xx can give rise to problems. I have found that Win XP works with dst=0.0.0.0 but some linux versions require the specific IP of the server Eg 192.168.0.42 or a qualified domain name Eg mywebsite.com.

	#2. Many Linux distros may not include by default the full version of ffmpeg and h/x264 and associated libs for encoding. You may need to go research and install all necessary components to get it all working.		#2. Many Linux distros may not include by default the full version of ffmpeg and h/x264 and associated libs for encoding. You may need to go research and install all necessary components to get it all working.
Line 241:		Line 241:
	#5 Clients need to be equipped with the necessary means to display your stream! Sounds an obvious statement? Probably not a problem if you have an up to date box, with MS Windows and a recent Flash plugin. I have encountered any number of problems with old hardware, other Operating Systems, browsers and Flash plugins. Don’t be surprised or disappointed at the apparent failure or erratic performance of your stream if you are testing it with a client that is not suitably equipped and able. Using Localhost to check out your stream may also give unexpected and misleading results.		#5 Clients need to be equipped with the necessary means to display your stream! Sounds an obvious statement? Probably not a problem if you have an up to date box, with MS Windows and a recent Flash plugin. I have encountered any number of problems with old hardware, other Operating Systems, browsers and Flash plugins. Don’t be surprised or disappointed at the apparent failure or erratic performance of your stream if you are testing it with a client that is not suitably equipped and able. Using Localhost to check out your stream may also give unexpected and misleading results.

			#6 The quality of the video input is also very important. Low quality webcams, camera and capture devices, noisy TV input devices will give even more disappointing results when transcoded.

	== Notes ==		== Notes ==

MrGreg: minor syntax edit to Appendix

2011-02-16T01:26:59Z

minor syntax edit to Appendix

← Older revision		Revision as of 01:26, 16 February 2011
Line 250:		Line 250:


	The following is an example of a full command line with the same settings as Method 2 Win XP. The first part, up to ”sout” is the input string. The vdev= and adev= are the (your) input devices and can be viewed and extracted from the first “streaming” window or tab in the GUI, with the “show more options” box checked. You will need to apply the correct syntax for your OS. In Windows ( note the double quotation marks,Eg ”<xxx>” syntax in Windows , for Linux use the single quotation marks '<xxx>') you would enter this at the command prompt path at C:/program files/videolan/vlc . You will also have to add quotation marks around any devices (see example below).		The following is an example of a full command line with the same settings as Method 2 Win XP. The first part, up to ”sout” is the input string. The vdev= and adev= are the (your) input devices and can be viewed and extracted from the first “streaming” window or tab in the GUI, with the “show more options” box checked. You will need to apply the correct syntax for your OS. In Windows ( note the double quotation marks,Eg ”<xxx>” syntax in Windows , for Linux use the single quotation marks '<xxx>') you would enter this at the command prompt path at C:/program files/videolan/vlc . You will also have to add quotation marks around any devices in MS Windows (see example below).
	Also note, in this example, video size has been defined twice, both in the input and output sections. If you did not include a setting for Video Size in the GUI screen it would not be present in the (generated) input string. Try adding and changing options to see how the VLC GUI builds the input string for you. It is not necessary for video size to be defined here, but should work OK with or without this parameter in the input section. I have included it to show how the string is generated in the GUI. The complete input and output sections can be simply copied and pasted from the GUI into a text editor and built into a complete string to create full working command line. Note, avoid using "word wrap" in the text editor, it can sometimes introduce unwanted characters in the string.		Also note, in this example, video size has been defined twice, both in the input and output sections. If you did not include a setting for Video Size in the GUI screen it would not be present in the (generated) input string. Try adding and changing options to see how the VLC GUI builds the input string for you. It is not necessary for video size to be defined here, but should work OK with or without this parameter in the input section. I have included it to show how the string is generated in the GUI. The complete input and output sections can be simply copied and pasted from the GUI into a text editor and built into a complete string to create full working command line. Note, avoid using "word wrap" in the text editor, it can sometimes introduce unwanted characters in the string.


	vlc dshow:// :dshow-vdev="Conexant's BtPCI Capture" :dshow-adev="Aureon 5.1 Fun Wave" :dshow-size="256x192" --sout="#transcode{vcodec=h264,vb=200,deinterlace,fps=25,width=256,height=192,ab=32,acodec=mp3,samplerate=44100}:duplicate{dst=std{access=http{mime=video/x-flv},mux=ffmpeg{mux=flv},dst=0.0.0.0:8081/mediaplayer/stream.flv},dst=display}"		vlc dshow:// :dshow-vdev="Conexant's BtPCI Capture" :dshow-adev="Aureon 5.1 Fun Wave" :dshow-size="256x192" --sout="#transcode{vcodec=h264,vb=200,deinterlace,fps=25,width=256,height=192,ab=32,acodec=mp3,samplerate=44100}:duplicate{dst=std{access=http{mime=video/x-flv},mux=ffmpeg{mux=flv},dst=0.0.0.0:8081/mediaplayer/stream.flv},dst=display}"

MrGreg: /* Appendix */

2010-11-25T22:44:48Z

Appendix

← Older revision		Revision as of 22:44, 25 November 2010
Line 250:		Line 250:


	The following is an example of a full command line with the same settings as Method 2 Win XP. The first part, up to ”sout” is the input string. The vdev= and adev= are the (your) input devices and can be viewed and extracted from the first “streaming” window or tab in the GUI, with the “show more options” box checked. You will need to apply the correct syntax for your OS. In Windows ( note the quotation marks,Eg ”<xxx>” syntax) you would enter this at the command prompt at C:/program files/videolan/vlc~~.exe~~. You will also have to add quotation marks around any ~~spaces~~ (see example below).		The following is an example of a full command line with the same settings as Method 2 Win XP. The first part, up to ”sout” is the input string. The vdev= and adev= are the (your) input devices and can be viewed and extracted from the first “streaming” window or tab in the GUI, with the “show more options” box checked. You will need to apply the correct syntax for your OS. In Windows ( note the double quotation marks,Eg ”<xxx>” syntax in Windows , for Linux use the single quotation marks '<xxx>') you would enter this at the command prompt path at C:/program files/videolan/vlc . You will also have to add quotation marks around any devices (see example below).
	Also note, in this example, video size has been defined twice, both in the input and output sections. If you did not include a setting for Video Size in the GUI screen it would not be present in the (generated) input string. Try adding and changing options to see how the VLC GUI builds the input string for you. It is not necessary for video size to be defined here, but should work OK with or without this parameter in the input section. I have included it to show how the string is generated in the GUI. The complete input and output sections can be simply copied and pasted from the GUI into a text editor and built into a complete string to create full working command line.		Also note, in this example, video size has been defined twice, both in the input and output sections. If you did not include a setting for Video Size in the GUI screen it would not be present in the (generated) input string. Try adding and changing options to see how the VLC GUI builds the input string for you. It is not necessary for video size to be defined here, but should work OK with or without this parameter in the input section. I have included it to show how the string is generated in the GUI. The complete input and output sections can be simply copied and pasted from the GUI into a text editor and built into a complete string to create full working command line. Note, avoid using "word wrap" in the text editor, it can sometimes introduce unwanted characters in the string.


	vlc dshow:// :dshow-vdev="Conexant's BtPCI Capture" :dshow-adev="Aureon 5.1 Fun Wave" :dshow-size="256x192" --sout="#transcode{vcodec=h264,vb=200,deinterlace,fps=25,width=256,height=192,ab=32,acodec=mp3,samplerate=44100}:duplicate{dst=std{access=http{mime=video/x-flv},mux=ffmpeg{mux=flv},dst=0.0.0.0:8081/mediaplayer/stream.flv},dst=display}"		vlc dshow:// :dshow-vdev="Conexant's BtPCI Capture" :dshow-adev="Aureon 5.1 Fun Wave" :dshow-size="256x192" --sout="#transcode{vcodec=h264,vb=200,deinterlace,fps=25,width=256,height=192,ab=32,acodec=mp3,samplerate=44100}:duplicate{dst=std{access=http{mime=video/x-flv},mux=ffmpeg{mux=flv},dst=0.0.0.0:8081/mediaplayer/stream.flv},dst=display}"

MrGreg: /* Method 2 H264 and Flash .flv */

2010-11-25T22:26:34Z

Method 2 H264 and Flash .flv

← Older revision		Revision as of 22:26, 25 November 2010
Line 178:		Line 178:
	The following output strings can be copied and pasted into the empty field. Do make sure that there are no spaces in the string when you copy/paste.		The following output strings can be copied and pasted into the empty field. Do make sure that there are no spaces in the string when you copy/paste.

	First example string for Win XP users		First example string for Win XP (and ffmpeg-x264 enabled Linux) users

	:sout=#transcode{vcodec=h264,vb=200,deinterlace,ab=32,fps=25,width=256,height=192,acodec=mp3,samplerate=44100}:duplicate{dst=std{access=http{mime=video/x-flv},mux=ffmpeg{mux=flv},dst=0.0.0.0:8081/mediaplayer/stream.flv},dst=display}		:sout=#transcode{vcodec=h264,vb=200,deinterlace,ab=32,fps=25,width=256,height=192,acodec=mp3,samplerate=44100}:duplicate{dst=std{access=http{mime=video/x-flv},mux=ffmpeg{mux=flv},dst=0.0.0.0:8081/mediaplayer/stream.flv},dst=display}
Line 184:		Line 184:


	Second example string for Linux users		Second example string for (stripped ffmpeg) Linux users

	:sout=#transcode{vcodec=FLV1,acodec=mp3,vb=200,deinterlace,fps=25,samplerate=44100,ab=32}:duplicate{dst=std{access=http,mux=ffmpeg{mux=flv},dst=192.168.0.42:8081/stream.flv},dst=display}		:sout=#transcode{vcodec=FLV1,acodec=mp3,vb=200,deinterlace,fps=25,samplerate=44100,ab=32}:duplicate{dst=std{access=http,mux=ffmpeg{mux=flv},dst=192.168.0.42:8081/stream.flv},dst=display}
Line 191:		Line 191:
	The above examples should work OK when adapted to your destination IP and port. That said, they are examples of two different approaches. The Windows approach utilises the H264 codec.		The above examples should work OK when adapted to your destination IP and port. That said, they are examples of two different approaches. The Windows approach utilises the H264 codec.
	The Ubuntu Linux approach example provides for a working solution in FLV1 which should work OK with the “Stripped” standard version of ffmpeg in a standard installation. This method would benefit from a two stage transcode to improve quality.		The Ubuntu Linux approach example provides for a working solution in FLV1 which should work OK with the “Stripped” standard version of ffmpeg in a standard installation. This method would benefit from a two stage transcode to improve quality.

			As of Ubuntu 10.04 – VLC 1.0.6 there is a more complete and up to date version of ffmpeg and x264 support in the standard repos'. Eg libavdevice-extra52 & x264. Note VideoLan currently recommends VLC versions 1.1.x . See VideoLan Ubuntu Downloads page for further information

	You will probably want to check that everything is working at this stage. So point a VLC client at the stream to check it out.		You will probably want to check that everything is working at this stage. So point a VLC client at the stream to check it out.