From bb38026f1c7da4cc23680c02a66d2912d2925a58 Mon Sep 17 00:00:00 2001 From: Petter Reinholdtsen Date: Thu, 12 Jul 2018 13:19:16 +0200 Subject: [PATCH] Generated. --- ...ing_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html | 9 +++++---- blog/archive/2018/07/07.rss | 9 +++++---- blog/archive/2018/07/index.html | 9 +++++---- blog/index.html | 9 +++++---- blog/index.rss | 9 +++++---- blog/tags/debian/debian.rss | 9 +++++---- blog/tags/debian/index.html | 9 +++++---- blog/tags/english/english.rss | 9 +++++---- blog/tags/english/index.html | 9 +++++---- blog/tags/video/index.html | 9 +++++---- blog/tags/video/video.rss | 9 +++++---- 11 files changed, 55 insertions(+), 44 deletions(-) diff --git a/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html b/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html index c29713f54a..9a9f9dbcab 100644 --- a/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html +++ b/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html @@ -71,7 +71,7 @@ echo rtsp://192.168.11.4:8080/test.sdp \

Note the 192.168.11.4 IP address is my desktops IP address. As far as I can tell the IP must be hardcoded for this to work. In other words, if someone elses machine is going to do the steaming, you have -to update screenstream.m4u on the Kodi machine and adjust the vlc +to update screenstream.m3u on the Kodi machine and adjust the vlc recipe. To get started, locate the file in Kodi and select the m3u file while the VLC stream is running. The desktop then show up in my big screen. :)

@@ -124,7 +124,7 @@ gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \ x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \ key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \ mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \ - udpsink host=239.255.0.1 port=1234 ttl-mc=0 auto-multicast=1 sync=0 \ + udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \ pulsesrc device=$(pactl list | grep -A2 'Source #' | \ grep 'Name: .*\.monitor$' | cut -d" " -f2|head -1) ! \ audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. @@ -140,14 +140,15 @@ echo udp://@239.255.0.1:1234 \

Note the trick to pick a valid pulseaudio source. It might not pick the one you need. This approach will of course lead to trouble if more than one source uses the same multicast port and address. -Note the ttl-mc=0 setting, which limit the multicast packages to the +Note the ttl-mc=1 setting, which limit the multicast packages to the local network. If the value is increased, your screen will be broadcasted further, one network "hop" for each increase (read up on multicast to learn more. :)!

Having cracked how to get Kodi to receive multicast streams, I could use this VLC command to stream to the same multicast address. -The image quality is way better than the rtsp approach.

+The image quality is way better than the rtsp approach, but gstreamer +seem to be doing a better job.

 cvlc screen:// --sout '#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{mux=ts,dst=239.255.0.1,port=1234,sdp=sap}'
diff --git a/blog/archive/2018/07/07.rss b/blog/archive/2018/07/07.rss
index 74be2dc46c..3f6dcc9cc7 100644
--- a/blog/archive/2018/07/07.rss
+++ b/blog/archive/2018/07/07.rss
@@ -60,7 +60,7 @@ echo rtsp://192.168.11.4:8080/test.sdp \
 <p>Note the 192.168.11.4 IP address is my desktops IP address.  As far
 as I can tell the IP must be hardcoded for this to work.  In other
 words, if someone elses machine is going to do the steaming, you have
-to update screenstream.m4u on the Kodi machine and adjust the vlc
+to update screenstream.m3u on the Kodi machine and adjust the vlc
 recipe.  To get started, locate the file in Kodi and select the m3u
 file while the VLC stream is running.  The desktop then show up in my
 big screen. :)</p>
@@ -113,7 +113,7 @@ gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
   x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
   key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
   mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
-  udpsink host=239.255.0.1 port=1234 ttl-mc=0 auto-multicast=1 sync=0 \
+  udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
   pulsesrc device=$(pactl list | grep -A2 'Source #' | \
     grep 'Name: .*\.monitor$' |  cut -d" " -f2|head -1) ! \
   audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
@@ -129,14 +129,15 @@ echo udp://@239.255.0.1:1234 \
 <p>Note the trick to pick a valid pulseaudio source.  It might not
 pick the one you need.  This approach will of course lead to trouble
 if more than one source uses the same multicast port and address.
-Note the ttl-mc=0 setting, which limit the multicast packages to the
+Note the ttl-mc=1 setting, which limit the multicast packages to the
 local network.  If the value is increased, your screen will be
 broadcasted further, one network "hop" for each increase (read up on
 multicast to learn more. :)!</p>
 
 <p>Having cracked how to get Kodi to receive multicast streams, I
 could use this VLC command to stream to the same multicast address.
-The image quality is way better than the rtsp approach.</p>
+The image quality is way better than the rtsp approach, but gstreamer
+seem to be doing a better job.</p>
 
 <blockquote><pre>
 cvlc screen:// --sout '#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{mux=ts,dst=239.255.0.1,port=1234,sdp=sap}'
diff --git a/blog/archive/2018/07/index.html b/blog/archive/2018/07/index.html
index daf587b344..71bc94fe7e 100644
--- a/blog/archive/2018/07/index.html
+++ b/blog/archive/2018/07/index.html
@@ -78,7 +78,7 @@ echo rtsp://192.168.11.4:8080/test.sdp \
 
Note the 192.168.11.4 IP address is my desktops IP address.  As far
 as I can tell the IP must be hardcoded for this to work.  In other
 words, if someone elses machine is going to do the steaming, you have
-to update screenstream.m4u on the Kodi machine and adjust the vlc
+to update screenstream.m3u on the Kodi machine and adjust the vlc
 recipe.  To get started, locate the file in Kodi and select the m3u
 file while the VLC stream is running.  The desktop then show up in my
 big screen. :)

@@ -131,7 +131,7 @@ gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
   x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
   key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
   mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
-  udpsink host=239.255.0.1 port=1234 ttl-mc=0 auto-multicast=1 sync=0 \
+  udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
   pulsesrc device=$(pactl list | grep -A2 'Source #' | \
     grep 'Name: .*\.monitor$' |  cut -d" " -f2|head -1) ! \
   audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
@@ -147,14 +147,15 @@ echo udp://@239.255.0.1:1234 \
 
Note the trick to pick a valid pulseaudio source.  It might not
 pick the one you need.  This approach will of course lead to trouble
 if more than one source uses the same multicast port and address.
-Note the ttl-mc=0 setting, which limit the multicast packages to the
+Note the ttl-mc=1 setting, which limit the multicast packages to the
 local network.  If the value is increased, your screen will be
 broadcasted further, one network "hop" for each increase (read up on
 multicast to learn more. :)!

 
 
Having cracked how to get Kodi to receive multicast streams, I
 could use this VLC command to stream to the same multicast address.
-The image quality is way better than the rtsp approach.

+The image quality is way better than the rtsp approach, but gstreamer
+seem to be doing a better job.

 
 
 cvlc screen:// --sout '#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{mux=ts,dst=239.255.0.1,port=1234,sdp=sap}'
diff --git a/blog/index.html b/blog/index.html
index 044a3c6ac6..2bdeeec807 100644
--- a/blog/index.html
+++ b/blog/index.html
@@ -71,7 +71,7 @@ echo rtsp://192.168.11.4:8080/test.sdp \
 
Note the 192.168.11.4 IP address is my desktops IP address.  As far
 as I can tell the IP must be hardcoded for this to work.  In other
 words, if someone elses machine is going to do the steaming, you have
-to update screenstream.m4u on the Kodi machine and adjust the vlc
+to update screenstream.m3u on the Kodi machine and adjust the vlc
 recipe.  To get started, locate the file in Kodi and select the m3u
 file while the VLC stream is running.  The desktop then show up in my
 big screen. :)

@@ -124,7 +124,7 @@ gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
   x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
   key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
   mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
-  udpsink host=239.255.0.1 port=1234 ttl-mc=0 auto-multicast=1 sync=0 \
+  udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
   pulsesrc device=$(pactl list | grep -A2 'Source #' | \
     grep 'Name: .*\.monitor$' |  cut -d" " -f2|head -1) ! \
   audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
@@ -140,14 +140,15 @@ echo udp://@239.255.0.1:1234 \
 
Note the trick to pick a valid pulseaudio source.  It might not
 pick the one you need.  This approach will of course lead to trouble
 if more than one source uses the same multicast port and address.
-Note the ttl-mc=0 setting, which limit the multicast packages to the
+Note the ttl-mc=1 setting, which limit the multicast packages to the
 local network.  If the value is increased, your screen will be
 broadcasted further, one network "hop" for each increase (read up on
 multicast to learn more. :)!

 
 
Having cracked how to get Kodi to receive multicast streams, I
 could use this VLC command to stream to the same multicast address.
-The image quality is way better than the rtsp approach.

+The image quality is way better than the rtsp approach, but gstreamer
+seem to be doing a better job.

 
 
 cvlc screen:// --sout '#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{mux=ts,dst=239.255.0.1,port=1234,sdp=sap}'
diff --git a/blog/index.rss b/blog/index.rss
index 4629eda765..85727ea8ef 100644
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -60,7 +60,7 @@ echo rtsp://192.168.11.4:8080/test.sdp \
 <p>Note the 192.168.11.4 IP address is my desktops IP address.  As far
 as I can tell the IP must be hardcoded for this to work.  In other
 words, if someone elses machine is going to do the steaming, you have
-to update screenstream.m4u on the Kodi machine and adjust the vlc
+to update screenstream.m3u on the Kodi machine and adjust the vlc
 recipe.  To get started, locate the file in Kodi and select the m3u
 file while the VLC stream is running.  The desktop then show up in my
 big screen. :)</p>
@@ -113,7 +113,7 @@ gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
   x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
   key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
   mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
-  udpsink host=239.255.0.1 port=1234 ttl-mc=0 auto-multicast=1 sync=0 \
+  udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
   pulsesrc device=$(pactl list | grep -A2 'Source #' | \
     grep 'Name: .*\.monitor$' |  cut -d" " -f2|head -1) ! \
   audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
@@ -129,14 +129,15 @@ echo udp://@239.255.0.1:1234 \
 <p>Note the trick to pick a valid pulseaudio source.  It might not
 pick the one you need.  This approach will of course lead to trouble
 if more than one source uses the same multicast port and address.
-Note the ttl-mc=0 setting, which limit the multicast packages to the
+Note the ttl-mc=1 setting, which limit the multicast packages to the
 local network.  If the value is increased, your screen will be
 broadcasted further, one network "hop" for each increase (read up on
 multicast to learn more. :)!</p>
 
 <p>Having cracked how to get Kodi to receive multicast streams, I
 could use this VLC command to stream to the same multicast address.
-The image quality is way better than the rtsp approach.</p>
+The image quality is way better than the rtsp approach, but gstreamer
+seem to be doing a better job.</p>
 
 <blockquote><pre>
 cvlc screen:// --sout '#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{mux=ts,dst=239.255.0.1,port=1234,sdp=sap}'
diff --git a/blog/tags/debian/debian.rss b/blog/tags/debian/debian.rss
index 0d7839f9e9..41a16a36a6 100644
--- a/blog/tags/debian/debian.rss
+++ b/blog/tags/debian/debian.rss
@@ -60,7 +60,7 @@ echo rtsp://192.168.11.4:8080/test.sdp \
 <p>Note the 192.168.11.4 IP address is my desktops IP address.  As far
 as I can tell the IP must be hardcoded for this to work.  In other
 words, if someone elses machine is going to do the steaming, you have
-to update screenstream.m4u on the Kodi machine and adjust the vlc
+to update screenstream.m3u on the Kodi machine and adjust the vlc
 recipe.  To get started, locate the file in Kodi and select the m3u
 file while the VLC stream is running.  The desktop then show up in my
 big screen. :)</p>
@@ -113,7 +113,7 @@ gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
   x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
   key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
   mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
-  udpsink host=239.255.0.1 port=1234 ttl-mc=0 auto-multicast=1 sync=0 \
+  udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
   pulsesrc device=$(pactl list | grep -A2 'Source #' | \
     grep 'Name: .*\.monitor$' |  cut -d" " -f2|head -1) ! \
   audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
@@ -129,14 +129,15 @@ echo udp://@239.255.0.1:1234 \
 <p>Note the trick to pick a valid pulseaudio source.  It might not
 pick the one you need.  This approach will of course lead to trouble
 if more than one source uses the same multicast port and address.
-Note the ttl-mc=0 setting, which limit the multicast packages to the
+Note the ttl-mc=1 setting, which limit the multicast packages to the
 local network.  If the value is increased, your screen will be
 broadcasted further, one network "hop" for each increase (read up on
 multicast to learn more. :)!</p>
 
 <p>Having cracked how to get Kodi to receive multicast streams, I
 could use this VLC command to stream to the same multicast address.
-The image quality is way better than the rtsp approach.</p>
+The image quality is way better than the rtsp approach, but gstreamer
+seem to be doing a better job.</p>
 
 <blockquote><pre>
 cvlc screen:// --sout '#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{mux=ts,dst=239.255.0.1,port=1234,sdp=sap}'
diff --git a/blog/tags/debian/index.html b/blog/tags/debian/index.html
index 0e62d35004..706ab413c3 100644
--- a/blog/tags/debian/index.html
+++ b/blog/tags/debian/index.html
@@ -77,7 +77,7 @@ echo rtsp://192.168.11.4:8080/test.sdp \
 
Note the 192.168.11.4 IP address is my desktops IP address.  As far
 as I can tell the IP must be hardcoded for this to work.  In other
 words, if someone elses machine is going to do the steaming, you have
-to update screenstream.m4u on the Kodi machine and adjust the vlc
+to update screenstream.m3u on the Kodi machine and adjust the vlc
 recipe.  To get started, locate the file in Kodi and select the m3u
 file while the VLC stream is running.  The desktop then show up in my
 big screen. :)

@@ -130,7 +130,7 @@ gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
   x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
   key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
   mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
-  udpsink host=239.255.0.1 port=1234 ttl-mc=0 auto-multicast=1 sync=0 \
+  udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
   pulsesrc device=$(pactl list | grep -A2 'Source #' | \
     grep 'Name: .*\.monitor$' |  cut -d" " -f2|head -1) ! \
   audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
@@ -146,14 +146,15 @@ echo udp://@239.255.0.1:1234 \
 
Note the trick to pick a valid pulseaudio source.  It might not
 pick the one you need.  This approach will of course lead to trouble
 if more than one source uses the same multicast port and address.
-Note the ttl-mc=0 setting, which limit the multicast packages to the
+Note the ttl-mc=1 setting, which limit the multicast packages to the
 local network.  If the value is increased, your screen will be
 broadcasted further, one network "hop" for each increase (read up on
 multicast to learn more. :)!

 
 
Having cracked how to get Kodi to receive multicast streams, I
 could use this VLC command to stream to the same multicast address.
-The image quality is way better than the rtsp approach.

+The image quality is way better than the rtsp approach, but gstreamer
+seem to be doing a better job.

 
 
 cvlc screen:// --sout '#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{mux=ts,dst=239.255.0.1,port=1234,sdp=sap}'
diff --git a/blog/tags/english/english.rss b/blog/tags/english/english.rss
index 1f953f41e9..c54253e555 100644
--- a/blog/tags/english/english.rss
+++ b/blog/tags/english/english.rss
@@ -60,7 +60,7 @@ echo rtsp://192.168.11.4:8080/test.sdp \
 <p>Note the 192.168.11.4 IP address is my desktops IP address.  As far
 as I can tell the IP must be hardcoded for this to work.  In other
 words, if someone elses machine is going to do the steaming, you have
-to update screenstream.m4u on the Kodi machine and adjust the vlc
+to update screenstream.m3u on the Kodi machine and adjust the vlc
 recipe.  To get started, locate the file in Kodi and select the m3u
 file while the VLC stream is running.  The desktop then show up in my
 big screen. :)</p>
@@ -113,7 +113,7 @@ gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
   x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
   key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
   mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
-  udpsink host=239.255.0.1 port=1234 ttl-mc=0 auto-multicast=1 sync=0 \
+  udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
   pulsesrc device=$(pactl list | grep -A2 'Source #' | \
     grep 'Name: .*\.monitor$' |  cut -d" " -f2|head -1) ! \
   audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
@@ -129,14 +129,15 @@ echo udp://@239.255.0.1:1234 \
 <p>Note the trick to pick a valid pulseaudio source.  It might not
 pick the one you need.  This approach will of course lead to trouble
 if more than one source uses the same multicast port and address.
-Note the ttl-mc=0 setting, which limit the multicast packages to the
+Note the ttl-mc=1 setting, which limit the multicast packages to the
 local network.  If the value is increased, your screen will be
 broadcasted further, one network "hop" for each increase (read up on
 multicast to learn more. :)!</p>
 
 <p>Having cracked how to get Kodi to receive multicast streams, I
 could use this VLC command to stream to the same multicast address.
-The image quality is way better than the rtsp approach.</p>
+The image quality is way better than the rtsp approach, but gstreamer
+seem to be doing a better job.</p>
 
 <blockquote><pre>
 cvlc screen:// --sout '#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{mux=ts,dst=239.255.0.1,port=1234,sdp=sap}'
diff --git a/blog/tags/english/index.html b/blog/tags/english/index.html
index a6de19ed61..084117aaee 100644
--- a/blog/tags/english/index.html
+++ b/blog/tags/english/index.html
@@ -77,7 +77,7 @@ echo rtsp://192.168.11.4:8080/test.sdp \
 
Note the 192.168.11.4 IP address is my desktops IP address.  As far
 as I can tell the IP must be hardcoded for this to work.  In other
 words, if someone elses machine is going to do the steaming, you have
-to update screenstream.m4u on the Kodi machine and adjust the vlc
+to update screenstream.m3u on the Kodi machine and adjust the vlc
 recipe.  To get started, locate the file in Kodi and select the m3u
 file while the VLC stream is running.  The desktop then show up in my
 big screen. :)

@@ -130,7 +130,7 @@ gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
   x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
   key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
   mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
-  udpsink host=239.255.0.1 port=1234 ttl-mc=0 auto-multicast=1 sync=0 \
+  udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
   pulsesrc device=$(pactl list | grep -A2 'Source #' | \
     grep 'Name: .*\.monitor$' |  cut -d" " -f2|head -1) ! \
   audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
@@ -146,14 +146,15 @@ echo udp://@239.255.0.1:1234 \
 
Note the trick to pick a valid pulseaudio source.  It might not
 pick the one you need.  This approach will of course lead to trouble
 if more than one source uses the same multicast port and address.
-Note the ttl-mc=0 setting, which limit the multicast packages to the
+Note the ttl-mc=1 setting, which limit the multicast packages to the
 local network.  If the value is increased, your screen will be
 broadcasted further, one network "hop" for each increase (read up on
 multicast to learn more. :)!

 
 
Having cracked how to get Kodi to receive multicast streams, I
 could use this VLC command to stream to the same multicast address.
-The image quality is way better than the rtsp approach.

+The image quality is way better than the rtsp approach, but gstreamer
+seem to be doing a better job.

 
 
 cvlc screen:// --sout '#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{mux=ts,dst=239.255.0.1,port=1234,sdp=sap}'
diff --git a/blog/tags/video/index.html b/blog/tags/video/index.html
index bd37a3a898..2f8e8d556c 100644
--- a/blog/tags/video/index.html
+++ b/blog/tags/video/index.html
@@ -77,7 +77,7 @@ echo rtsp://192.168.11.4:8080/test.sdp \
 
Note the 192.168.11.4 IP address is my desktops IP address.  As far
 as I can tell the IP must be hardcoded for this to work.  In other
 words, if someone elses machine is going to do the steaming, you have
-to update screenstream.m4u on the Kodi machine and adjust the vlc
+to update screenstream.m3u on the Kodi machine and adjust the vlc
 recipe.  To get started, locate the file in Kodi and select the m3u
 file while the VLC stream is running.  The desktop then show up in my
 big screen. :)

@@ -130,7 +130,7 @@ gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
   x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
   key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
   mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
-  udpsink host=239.255.0.1 port=1234 ttl-mc=0 auto-multicast=1 sync=0 \
+  udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
   pulsesrc device=$(pactl list | grep -A2 'Source #' | \
     grep 'Name: .*\.monitor$' |  cut -d" " -f2|head -1) ! \
   audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
@@ -146,14 +146,15 @@ echo udp://@239.255.0.1:1234 \
 
Note the trick to pick a valid pulseaudio source.  It might not
 pick the one you need.  This approach will of course lead to trouble
 if more than one source uses the same multicast port and address.
-Note the ttl-mc=0 setting, which limit the multicast packages to the
+Note the ttl-mc=1 setting, which limit the multicast packages to the
 local network.  If the value is increased, your screen will be
 broadcasted further, one network "hop" for each increase (read up on
 multicast to learn more. :)!

 
 
Having cracked how to get Kodi to receive multicast streams, I
 could use this VLC command to stream to the same multicast address.
-The image quality is way better than the rtsp approach.

+The image quality is way better than the rtsp approach, but gstreamer
+seem to be doing a better job.

 
 
 cvlc screen:// --sout '#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{mux=ts,dst=239.255.0.1,port=1234,sdp=sap}'
diff --git a/blog/tags/video/video.rss b/blog/tags/video/video.rss
index b945029693..e8aac6db75 100644
--- a/blog/tags/video/video.rss
+++ b/blog/tags/video/video.rss
@@ -60,7 +60,7 @@ echo rtsp://192.168.11.4:8080/test.sdp \
 <p>Note the 192.168.11.4 IP address is my desktops IP address.  As far
 as I can tell the IP must be hardcoded for this to work.  In other
 words, if someone elses machine is going to do the steaming, you have
-to update screenstream.m4u on the Kodi machine and adjust the vlc
+to update screenstream.m3u on the Kodi machine and adjust the vlc
 recipe.  To get started, locate the file in Kodi and select the m3u
 file while the VLC stream is running.  The desktop then show up in my
 big screen. :)</p>
@@ -113,7 +113,7 @@ gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
   x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
   key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
   mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
-  udpsink host=239.255.0.1 port=1234 ttl-mc=0 auto-multicast=1 sync=0 \
+  udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
   pulsesrc device=$(pactl list | grep -A2 'Source #' | \
     grep 'Name: .*\.monitor$' |  cut -d" " -f2|head -1) ! \
   audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
@@ -129,14 +129,15 @@ echo udp://@239.255.0.1:1234 \
 <p>Note the trick to pick a valid pulseaudio source.  It might not
 pick the one you need.  This approach will of course lead to trouble
 if more than one source uses the same multicast port and address.
-Note the ttl-mc=0 setting, which limit the multicast packages to the
+Note the ttl-mc=1 setting, which limit the multicast packages to the
 local network.  If the value is increased, your screen will be
 broadcasted further, one network "hop" for each increase (read up on
 multicast to learn more. :)!</p>
 
 <p>Having cracked how to get Kodi to receive multicast streams, I
 could use this VLC command to stream to the same multicast address.
-The image quality is way better than the rtsp approach.</p>
+The image quality is way better than the rtsp approach, but gstreamer
+seem to be doing a better job.</p>
 
 <blockquote><pre>
 cvlc screen:// --sout '#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{mux=ts,dst=239.255.0.1,port=1234,sdp=sap}'
-- 
2.47.2